Every Payment Lands in the Books

For many small organizations, accounting happens at the end of the month: download statements from the payment processor, the bank and maybe a few apps, then try to make them agree. Every payment that was not recorded at the time becomes a puzzle to solve later.

We designed the payment flows in our platform so that accounting is not an afterthought. When money moves, the records that explain it are created as part of the same flow. Here is how that works and why we insist on it.

Accounting is part of every payment flow

Our engineering standards treat accounting integration as mandatory for any feature that takes or returns money. A new checkout, a new subscription type or a new add-on is not finished until its payments create the right records. Payment code that skips accounting is treated as incomplete, the same way a form that does not save would be.

That rule exists because adding accounting later is always harder. By then, there are payments without records, and someone has to reconstruct them.

Records come from verified events

Accounting records are created from verified payment events, not from screens or redirects. When the payment system confirms a charge, a refund or a fee, that confirmation creates the invoice, payment and related records. A customer reaching a thank-you page creates nothing on its own. You can read about why in only a verified payment signal grants paid access.

Fees are recorded, not hidden

Payment processing involves fees. When an organization sells through our platform using its own connected payment account, our platform fee is deducted from the sale. We record that fee in the organization's own books as an expense from the platform, in a clear platform fees category. When the organization compares its processor deposits with its accounting, the fee is already there, so the numbers match.

When a sale is refunded and part of the fee is returned, that returned amount is recorded too. We explain the full flow in letting customers get paid directly.

Refunds and disputes have records

Refunds and disputes are where books most often go wrong, because they happen later, in a different place and often in a hurry. In our platform, a refund is recorded against the original sale, including any platform fee it returns, and each dispute step is recorded with the payment processor as it happens, including amounts recovered and returned. Nobody has to remember to adjust the books after a difficult conversation with a customer.

Background work for accounting

Some accounting steps happen in the background, such as recording a platform fee in an organization's books after a sale completes. Those background jobs remember which organization they belong to and are designed so running twice does not record twice. Financial records are exactly the kind of data that must never be duplicated or written to the wrong account.

Financial evidence is kept separate

When we change payment or accounting code, we keep evidence about money separate from evidence about code. That the code builds and passes tests is one fact. That a real payment was accepted, recorded and reconciled is a different fact that requires its own proof. Our handoff notes record those separately so nobody mistakes a passing test for a reconciled ledger.

Reconciliation should be routine

Reconciliation is the process of confirming that recorded payments match what actually arrived in the bank. When books are updated by the same events that move money, reconciliation becomes a routine check instead of a detective story. Differences are rare and easier to explain, because each record points back to the payment event that created it.

Built into our own products

The same thinking is at the heart of Pay by Jag, our payments and bookkeeping product, which keeps invoices, payments, reconciliation and reports next to the payments that feed them. We built our platform's payment flows with the same conviction: books should stay current because they are updated by the same events that move the money.

Frequently asked questions

Why connect payments to accounting automatically?

Automatic records created from verified payment events keep books current and avoid reconstructing missing entries at month-end.

Are platform fees shown in my books?

For sales through a connected payment account on our platform, the platform fee is recorded in your books as an expense so your records match your deposits.

What happens to my books when I refund a sale?

The refund is recorded against the original sale, including any platform fee that was returned to you.