Picture month-end close. Revenue ties to bank deposits. Fees expense looks reasonable. The P&L tells a clean story and the client signs off. Meanwhile, Stripe Clearing shows $2,847. It was $312 in January, $711 in March, $1,484 in July. No transaction stood out as wrong. No reconciliation report flagged it. The balance just kept growing.
This is the payment processor float balance sheet problem. The income statement reflects what hit the bank, so it looks correct. The balance sheet reflects what is in transit, in dispute, or unreconciled, and nobody pulls a trial balance every month to spot the trend. By the time a CPA asks, the balance has compounded across twelve cycles and three or four root causes.
What is payment processor float on the balance sheet?
Payment processor float is the balance that accumulates in a clearing account when processor payouts don't fully reconcile each cycle. A temporary clearing balance is normal — Stripe holds funds for 2 business days, PayPal up to 21 days for newer sellers, Square releases next business day. Float becomes a balance sheet problem when the clearing account doesn't return to zero after each payout settles. Unreconciled float accumulates from cross-period refunds, fee rounding, dispute holds, and manual entry errors. Left unchecked, $50/month in drift compounds to $600–$2,000 by year-end and creates a forensic accounting problem at tax time.
Standard bookkeeping rewards P&L matching. Deposits get categorized, invoices get marked paid, the P&L renders cleanly. Clearing accounts get reconciled monthly at best, often quarterly, sometimes only at year-end. The per-cycle variance feels immaterial. Stacked, it becomes a four-figure question.
The clearing account sits on the balance sheet as an asset. A bookkeeper running the clearing account method correctly should see it oscillate around zero — rising as charges are recorded, falling as each payout clears to the bank. If the trend is monotonically upward instead of oscillating, something is not closing out each cycle.
Most bookkeepers notice the P&L. The balance sheet gets reviewed less frequently, and the clearing account line rarely triggers a question unless the balance is large enough to be flagged on a trial balance review. By the time it's large enough, months of drift have already stacked.
Payment processor float is money in transit between the processor and your bank. A card is charged today. Funds settle into the processor account, hold for the agreed period, and the net amount (gross minus refunds minus fees) hits the bank as a payout. Until the payout clears, those funds belong on the balance sheet as a clearing-account asset.
Hold periods vary. Stripe runs a rolling two-business-day payout (see the Stripe deposits breakdown). PayPal can hold up to 21 days for newer sellers. Square posts the next business day for accounts in good standing. Each processor creates a temporary asset equal to whatever has been charged but not yet paid out, a payment processor timing difference that should resolve within the next cycle.
Healthy float behaves predictably. A $4,200 Stripe balance at June 30 that becomes $0 by July 5 is doing exactly what it should. Accumulated drift is residue from un-reconciled prior cycles. It does not age out. It sits there. It grows. It survives every month-end close until somebody notices.
The audit later splits the clearing balance into these two buckets. If the balance shrinks to near zero within the first week of the new month, the float was healthy. If a chunk persists past the next payout, that chunk is drift and needs investigation.
A customer charged $89 in February asks for a refund in March. The refund reduces March's payout by $89. The original sale was booked in February. If the bookkeeper records the March refund against current-period revenue without matching it to the February charge, the clearing account holds an $89 variance until somebody reconciles the periods.
A SaaS business with 47 monthly transactions and a 3% refund rate has one to two refunds per cycle, $20 to $200 each. Across a year, that is 12–24 cross-period refunds. By December, several hundred dollars of unreconciled refund variance sit in clearing.
Processors calculate fees at the transaction level and round per-transaction. A $0.30 per-transaction fee across 47 transactions totals $14.10 exactly. The payout report shows $14.10. Your GL entry, built from a rounded line item, shows $14.00. The $0.10 is immaterial. Repeated across 30 payouts a month for 12 months, $0.10 becomes $36. Not catastrophic, but real, and cumulative.
A chargeback on a $400 charge freezes $400 plus the dispute fee. Funds disappear from the next payout and release weeks or months later, sometimes in partial amounts depending on the outcome. A full win returns everything. A loss returns nothing. A partial win returns a percentage. Each freeze and release creates an unexplained variance in clearing until the dispute lifecycle is traced to the exact payout events.
A $4 fee miscoded. A $0.50 refund variance from a transposed digit. A $14 sales tax line booked twice. Each immaterial. Cumulatively, a real balance sheet problem. These errors are almost impossible to catch at the transaction level. They surface only in aggregate, when clearing does not zero out.
Run the math across a year. January closes with $47 of unexplained drift. February adds $83. March pulls $34 back when a refund finally matches its prior-period charge but adds $112 from a new fee rounding gap. April: $29. May: $156 (chargeback timing). June through November: $40 to $90 a month. December: $1,247 in Stripe Clearing.
Every monthly variance felt immaterial in isolation. The pattern was invisible without a year-over-year trial-balance review. Now: where did $1,247 come from, and which period does it belong to?
The CPA pulls the trial balance and asks what the $1,847 in Stripe Clearing represents. The honest answer is "accumulated reconciliation drift across the year." That is not the answer the CPA wants. It is also the moment the bookkeeper realizes monthly cleanup beats year-end forensics by a wide margin.
If the drift is material, it has to be allocated to the periods it occurred in. If it touched revenue or fee expense in any non-trivial way, restating may be necessary. If it is write-off-grade immaterial, a single year-end adjustment works, but the documentation to justify it eats hours.
A five-minute fix at the time of variance becomes six or more hours of forensic accounting at year-end. Variances are no longer fresh. Payout reports may have rolled off processor dashboards. Sales tax periods are closed.
I have spent a Saturday on this exact problem: six months of payout CSVs, matched payout-by-payout, isolating disputes from refunds from fee rounding from manual errors. It works. It also costs a Saturday. The same work distributed across the year would have been twelve five-minute checks.
If your clearing account is already drifting, cleanup is mechanical. The steps below are sequential. Skipping any of them produces gaps that re-drift within the quarter.
For Stripe, export the payouts CSV. For PayPal, pull monthly statements. For Square, run the reconciliation export. Columns that matter per payout: gross sales, refunds, fees, net deposit, and payout date. This is the source of truth. Every reconciliation question downstream gets answered by these numbers, not by the GL.
For every payout, locate the corresponding JE in the GL. The four-line method produces one JE per payout: gross sales (credit revenue), refunds (debit refunds), fees (debit fees expense), net deposit (debit cash). If any line is missing, does not tie to the report, or the JE is missing entirely, flag it. A typical six-month review uncovers 10–30 flagged payouts. Most resolve in step 3.
Sort each flagged payout into three buckets. Timing: variance resolves in the next period, no action. Error: caused by a miscoded fee, bad refund entry, duplicate, or missing line; needs a correcting JE in the period it occurred (or current period with a note for closed periods). Mystery: needs investigation, usually a dispute timeline, processor adjustment, or partial release the bookkeeper did not track.
Distribution typically lands 70/20/10. Most variance is healthy float that has not aged out. A meaningful chunk is correctable error. A small slice is puzzling.
For most errors, materiality does not warrant a prior-period restatement. Book a clean correcting JE in the current period with a note: "$47 fee rounding drift, March 2026 Stripe payouts, see worksheet." For mysteries, an hour of investigation per item is reasonable; if it remains unexplained, write the residual to a P&L line (Other Expense, with disclosure to the CPA) and document the decision.
The goal is not perfection. The goal is a clearing account that ties to its source of truth and does not carry unexplained drift into the next year.
Once the account is clean, three habits keep the clearing balance honest.
Most clearing accounts get reconciled once a month. By then, 20–30 payouts have stacked up and any variance is buried in aggregate. Better cadence: reconcile per-payout, daily for Stripe, as each payout settles. Per-payout variance is $5 to $20, easy to catch. Wait for month-end and you are looking for $200+ aggregated across 30 events with no obvious source.
When the clearing balance exceeds $50 for more than one consecutive payout cycle, investigate immediately. The check takes five minutes when the payout is fresh. It takes six hours when the trail is six months cold.
A running log of open disputes per client — charge date, amount, filing date, expected resolution window — eliminates most mystery variances before they become clearing drift. When clearing does not zero, the dispute log is the first place to look.
The P&L is not the only signal. A clean income statement and a drifting balance sheet are the same problem dressed two ways, and the balance-sheet version surfaces at the worst time: in front of a CPA, with a tax filing on the calendar.
Pull one client's clearing account this week. Check the trend across six months. If the balance is growing instead of oscillating around zero, run the four-step audit before December. The cleanup compounds, and so does the cost of letting it sit.
Stop letting clearing-account drift turn into year-end forensics — start a free Growthy account and reconcile your processor payouts in minutes per cycle.
Free during alpha. Read-only access. You review every sync.
Growthy is dedicated to helping businesses of all sizes make informed decisions. We adhere to strict editorial guidelines to ensure that our content meets and maintains our high standards.
Stripe sends one deposit for 47 transactions. Learn the clearing account method to reconcile lump-sum payment processor deposits with step-by-step journal entries.
Where do Stripe, PayPal, and Square fees go on the P&L? Operating expense, contra-revenue, or COGS — explained with journal entries and a QBO account structure.
