Why net payouts lie

What a payout is

A payment platform does not send you your sales. It sends you a payout: the net of everything that happened to your balance since the last one. Charges add to the balance. Fees, refunds, disputes, dispute fees, reserves, adjustments, and currency conversion take from it. On a schedule, the platform sends whatever is left to your bank as a single transfer.

The bank sees one deposit. That deposit is a true number. It is also almost useless on its own, because it is the answer to a sum nobody wrote down.

What gets netted

• Processing fees on every charge, usually a percentage plus a fixed amount, sometimes at more than one rate depending on card type or country.
• Refunds, which reduce the balance when issued, not when the original charge was made, so a refund can land in a different payout than its sale.
• Disputes, which remove the disputed amount immediately and add a dispute fee, then sometimes return the amount weeks later if you win.
• Reserves and holds, which keep part of the balance back and release it on their own timetable.
• Adjustments, which is the platform’s word for everything else: a fee correction, a manual credit, a currency rounding difference.

Each of those is a real line with a real amount. The payout is their sum. Nothing about the sum tells you what the lines were.

What the books see

A sync tool moves the payout into the ledger. Depending on how it was set up, it posts the net deposit as revenue, or posts the gross as revenue and the fees as an expense, or posts the gross and forgets the fees. Whatever it posts is what the books say.

Then the bookkeeper reconciles the bank, and the bank ties, because the deposit matches the payout line. That reconciliation is correct and it proves almost nothing. It proves the platform sent what the platform said it sent. It does not prove the platform’s number was right, or that the sync recorded it correctly, or that the pieces it was built from are in the books at all.

A worked month

Take one month with the figures on Recouped’s home page. Gross charges of $52,418.90. Stripe nets fees, seven refunds, and one lost dispute, and pays out $48,013.48 across six payouts. The bank receives $46,988.31, because the sixth payout was created on the 30th and landed on the 2nd. The books show $52,418.90, because the sync posted gross and nothing else.

The bank rec ties five payouts to five deposits and carries one in transit. Fine. But the books are $4,405.42 above what Stripe actually paid, and the difference is three exceptions: $1,571.42 in fees that were never booked, $2,204.00 in refunds that were never synced, and a $630.00 dispute that was never recorded. Revenue is overstated. Expenses are understated. Profit is wrong by the sum, and it will stay wrong until someone matches the platform’s itemized report to the ledger.

Two errors that cancel

The nastier case is when the net is right and the pieces are wrong. A fee overcharge of $400 and an unsynced refund of $400 leave the payout exactly where it should be. Bank ties, books tie, and two errors sit inside a correct total. The only way to see them is line by line, which is the one thing a net payout is designed to spare you.

What to do about it

1. Book at gross. Revenue is the gross charge; fees are an expense; refunds and disputes are contra-revenue. The net deposit is the arithmetic result, not the entry.
2. Tie three ways, not one. Platform to bank catches missing deposits. Platform to books catches unbooked fees and refunds. Books to bank is the rec you already do.
3. Use the itemized report. Every platform publishes one. It is the sum, unpacked.
4. Do it monthly. A refund from March that shows up in April’s payout is a timing item in April and a mystery in June.

Or let Recouped do the matching and hand your accountant the exceptions. Either way, the net is not the answer. It is the question.