Beancount.io LogoBeancount.io

How to Reconcile Payment Processor Payouts: A Clearing Account Guide

10 min readMike ThriftMike Thrift
How to Reconcile Payment Processor Payouts: A Clearing Account Guide

Your customers paid you $10,000 last week. Your bank account shows a deposit of $9,412.55. Where did the other $587.45 go—and why does the deposit amount never seem to match a single invoice?

If you take card payments through Stripe, Square, PayPal, Shopify Payments, or any other processor, you have already met the single most common bookkeeping headache in modern small business: the payout that doesn't tie out. The fix isn't more spreadsheets. It's understanding what a payout actually contains and recording each piece in the right place.

Why the Deposit Never Matches the Sale

A payment processor sits between your customer and your bank. When a customer pays, the money does not go straight to you. The processor collects it, holds it briefly, nets out everything it is owed or holding back, and then sends you the leftover in a batch called a payout (or "settlement" or "deposit," depending on the platform).

That batch almost never equals a clean number, because a single payout typically bundles together:

  • Gross sales — the full amount customers were charged
  • Processing fees — the processor's cut, usually around 2.9% + $0.30 per card transaction
  • Refunds — money returned to customers during the period
  • Chargebacks and disputes — forced reversals, often with an extra fee
  • Sales tax — collected on top of the sale price (this is a liability, not revenue)
  • Rolling reserves — a slice of revenue the processor holds back as a cushion
  • Adjustments — currency conversion differences, corrections, and miscellaneous fees

Your bank statement shows only the final net number. If you record that net number as "income," your books will be wrong in at least three ways: your revenue will be understated, your processing fees will be invisible, and your sales tax liability will vanish. Come tax time, none of it will reconcile.

The goal of payout reconciliation is simple to state: explain the gap between what customers paid and what hit your bank, line by line.

The Clearing Account: Your Bridge Between Gross and Net

The cleanest way to handle this is a clearing account (also called a holding account or, in some software, "undeposited funds"). Think of it as a temporary holding pen that mirrors your balance inside the processor.

Here is the mental model:

  1. When a customer pays, money flows into the clearing account (you record gross revenue here).
  2. Fees, refunds, and reserves are recorded against the clearing account as they occur.
  3. When the processor sends a payout, money moves out of the clearing account and into your bank.
  4. At any moment, the clearing account balance should equal your real balance inside the processor's dashboard.

If your clearing account balance matches the processor's reported balance, you are reconciled. If it doesn't, something is missing—and you know exactly where to look.

This approach works in any double-entry system. Because plain-text accounting tools like Beancount make every transaction explicit and auditable, they are an excellent fit for this workflow. The examples below use Beancount syntax, but the structure translates to any double-entry ledger.

Setting Up the Accounts

You need a small, dedicated set of accounts:

Assets:Stripe:Clearing          ; mirrors your balance inside the processor
Assets:Stripe:Reserve           ; funds the processor is holding back
Assets:Bank:Checking            ; where payouts land
Income:Sales                    ; gross revenue
Expenses:ProcessingFees         ; the processor's cut
Expenses:Chargebacks            ; lost disputes and dispute fees
Liabilities:SalesTaxPayable     ; tax collected on behalf of the state
Income:Sales:Refunds            ; contra-revenue for returned sales

Keeping the reserve in its own asset account matters: that money is still yours, it is just not spendable yet. Burying it in the clearing account hides a real asset from your balance sheet.

Recording a Sale

When a customer is charged $200 plus $16 in sales tax, the full $216 enters your clearing account. The revenue and the tax liability are recorded separately:

2026-05-12 * "Customer payment - Invoice 1043"
  Assets:Stripe:Clearing          216.00 USD
  Income:Sales                   -200.00 USD
  Liabilities:SalesTaxPayable     -16.00 USD

Notice that no fee appears yet. Most processors charge the fee at the transaction level, but you can also let it accumulate and record it at payout time. Pick one method and stay consistent. Recording fees per-transaction is more precise; recording them per-payout is faster. For most small businesses, per-payout is the practical choice.

Recording Fees

Processing fees are an operating expense—a real cost of doing business, fully deductible. When you record them at payout time, you simply pull the total fee figure from the processor's payout report:

2026-05-15 * "Stripe processing fees - payout period"
  Expenses:ProcessingFees          18.45 USD
  Assets:Stripe:Clearing          -18.45 USD

The fee leaves the clearing account because the processor kept that money—it never reaches your bank. A common mistake is netting fees against revenue (recording $181.55 of income instead of $200 of income and $18.45 of expense). That understates both your revenue and your expenses, distorts your margins, and can quietly inflate your taxable picture in ways that don't survive an audit.

Recording Refunds

When you refund a customer, money flows back out. Use a contra-revenue account rather than reducing Income:Sales directly—this keeps gross sales and refunds visible as separate figures, which is what you want for analyzing return rates.

2026-05-14 * "Refund - Invoice 1039"
  Income:Sales:Refunds             50.00 USD
  Liabilities:SalesTaxPayable       4.00 USD
  Assets:Stripe:Clearing          -54.00 USD

Most processors refund the sales tax to the customer but do not refund their original processing fee. That asymmetry is real money lost, and it stays sitting in your Expenses:ProcessingFees account—correctly, because the fee was genuinely incurred.

Recording Chargebacks and Disputes

A chargeback is a forced reversal: the customer's bank pulls the funds back, usually adding a dispute fee of $15–$25. Until the dispute resolves, the processor debits both the original amount and the fee from your balance.

2026-05-13 * "Chargeback - Invoice 1031 plus dispute fee"
  Expenses:Chargebacks            115.00 USD
  Assets:Stripe:Clearing         -115.00 USD

If you later win the dispute, the processor returns the original amount (though often not the fee). Record that as a reversal when the funds come back. Tracking chargebacks in their own expense account is worth the effort—a rising chargeback rate is an early warning sign of fraud, fulfillment problems, or a processor relationship at risk.

Recording Rolling Reserves

A rolling reserve is a risk cushion. The processor withholds a percentage of your sales—typically 5% to 15%—and releases it back to you after a fixed delay, often 90 to 180 days. It is common for newer businesses, high-risk industries, and merchants with elevated chargeback rates.

The critical accounting point: reserve money is still your asset. It is not an expense and not lost revenue. It is cash you own that you simply cannot touch yet. Record it as a transfer between two asset accounts:

2026-05-15 * "Stripe rolling reserve withheld - 10%"
  Assets:Stripe:Reserve           120.00 USD
  Assets:Stripe:Clearing         -120.00 USD

When the processor releases the reserve months later, it flows back into the clearing account and then out as part of a normal payout:

2026-08-15 * "Stripe rolling reserve released"
  Assets:Stripe:Clearing          120.00 USD
  Assets:Stripe:Reserve          -120.00 USD

Treating the reserve as its own account keeps your balance sheet honest and gives you a clear picture of how much cash is locked up. Businesses that ignore reserves are often surprised to find thousands of dollars they "earned" but cannot spend.

Recording the Payout

After all of the above, whatever remains in the clearing account is what the processor actually sends you. The payout transaction simply moves money from the clearing account to your bank:

2026-05-15 * "Stripe payout to checking"
  Assets:Bank:Checking            412.55 USD
  Assets:Stripe:Clearing         -412.55 USD

When this transaction posts, your bank statement and your books agree on the deposit. And because every other piece—gross sales, fees, refunds, chargebacks, reserves—was recorded against the same clearing account, you can now prove the entire chain.

A Complete Reconciliation Walkthrough

Suppose a payout period produced this activity:

ItemAmount
Gross sales+$600.00
Sales tax collected+$48.00
Refunds−$54.00
Chargeback + fee−$115.00
Processing fees−$18.45
Rolling reserve (10%)−$48.00
Net payout$412.55

Walk it forward: $600 in sales plus $48 in tax is $648 into the clearing account. Subtract $54 of refunds, $115 of chargebacks, $18.45 of fees, and $48 held in reserve, and you are left with $412.55—exactly the payout. After every transaction is entered, the clearing account returns to zero (assuming no transactions are still pending), and the reserve account holds $48.

That zero balance is the proof. If your clearing account does not return to zero—or does not match the "pending" balance in the processor dashboard—you have a missing or miscategorized transaction, and you know precisely which payout period to investigate.

Why Accurate Payout Records Matter

This is not bookkeeping for its own sake. Recording payouts correctly drives real decisions:

  • True revenue. Net deposits understate your sales. Investors, lenders, and the IRS all expect gross revenue. The 1099-K you receive from your processor reports gross volume—if your books show net, you have an instant mismatch to explain.
  • Visible costs. Processing fees are often a business's third- or fourth-largest expense. You cannot negotiate a better rate or shop processors if you have never measured what you are paying.
  • Correct sales tax. Tax you collect is a liability you owe the state, never your income. Mixing it into revenue overstates earnings and risks underpaying tax.
  • Honest cash position. Reserves and in-transit funds are real assets. A balance sheet that ignores them understates what you own.
  • Audit readiness. A clearing account that ties out to the penny is the difference between a five-minute reconciliation and a five-hour forensic exercise.

Common Mistakes to Avoid

  • Booking the net deposit as income. The single most common error. It erases fees, refunds, and tax in one stroke.
  • Netting fees against revenue. Always record gross revenue and fees separately. Margins and benchmarks depend on it.
  • Treating reserves as an expense. Reserve funds are an asset you will get back. Expensing them understates both profit and assets.
  • Ignoring refunded fees. When you refund a sale, the original processing fee usually stays gone. Don't reverse it.
  • Reconciling once a year. A payout that didn't tie out is easy to fix the same week and miserable to untangle eleven months later. Reconcile every payout, or at minimum monthly.
  • Comingling processors. If you use Stripe and PayPal and Square, give each its own clearing account. One shared bucket makes it impossible to tell which platform is out of balance.

Keep Your Finances Organized from Day One

Payment processor payouts are where messy books usually start—and a clearing account is how you keep them clean. Every dollar a customer pays you should be traceable from gross sale through fees, refunds, and reserves all the way to the deposit in your bank.

Beancount.io provides plain-text accounting that makes this kind of reconciliation natural: every transaction is explicit, every account balance is auditable, and your entire ledger is version-controlled with no black boxes and no vendor lock-in. You can model clearing accounts, reserves, and contra-revenue exactly as shown above, then visualize it all with a dashboard like Fava. Get started for free and see why developers and finance professionals are switching to plain-text accounting.


Sources: Ridgeway Financial Services — Payment Processor Settlement Accounting, Stripe Documentation — Payout Reconciliation Report, Lightspeed — Payment Reconciliation, PaymentCloud — What is a Rolling Reserve, Checkout.com — What is a Rolling Reserve.