OfinTech
Finance practice

The payout is not the sale

The bank shows one deposit. The sales behind it were many, less fees, refunds and a dispute. Tying the two is arithmetic, and arithmetic can be shown.

2 min read · Updated 17 November 2026 · Documentation version 1

This page is also available in Arabic.

A shop sells 430.00 through its payment provider over two days. Two deposits follow: 197.25, then 77.38. Nothing is missing, and nobody could tell that from the bank statement.

Between the sale and the deposit sits the provider's own ledger. A charge adds to a balance. The provider's fee comes off each charge. A refund comes off, and sometimes brings part of a fee back with it. A dispute takes the sale and adds a fee of its own. A reserve is held, and released weeks later. Then, on a schedule the provider chooses, whatever is in the balance is paid out as one figure, with a reference the bank may or may not repeat. The payout is not the sale; it is what was left.

Most of what finance teams call reconciliation is undoing that by hand: export the provider's report, sort it by payout, add up each kind of row, compare the total with the deposit, and write down what the difference was. It is the same arithmetic every month and it goes wrong in the same places — revenue booked at the net figure, so the fees never appear as a cost; a refund counted in the month it was paid out rather than the month it was given; a reserve taken for a loss.

Desk does the arithmetic and shows it. It reads the report the provider already exports — one row for every charge, refund, dispute and fee, each naming its payout — and puts the rows back together into the payouts the bank received. Each payout is matched to its deposit, and the month is set out as one statement: what was sold, then every reason it is not all in the bank, by name. Fees. The tax on them. Refunds. Chargebacks. Reserve withheld. Money still on its way. In the shop above that is 30.37 of fees, 40.00 refunded, 60.00 disputed and 25.00 held, which with the two deposits is 430.00 exactly. The last line of the statement is what could not be named, and the point of the page is that it is usually nothing.

Three things it will not do are worth saying. It does not guess at a row it has no name for: a loan repayment, or a balance carried into the next payout, is kept as what it is — another movement — so the payout still adds up. It does not convert currencies: a workspace keeps its books in one, and rows in another are left out and counted where you can see the count. And it does not post anything to your accounting system; the journal is a file you import.

The layouts for the four providers it reads by itself — Stripe, Adyen, Shopify Payments, PayPal — were written from what each provider publishes about its own report, and the import page says so until a real export has been read. Any other report is mapped once, column by column, and remembered.

None of this is clever. It is a subtraction done the same way every time, with the working left on the page.