Decompose Stripe, Square, Shopify, and PayPal deposits into the right accounts. No more month-end clearing-account spirals.
What is payment reconciliation in bookkeeping?
Payment reconciliation is the process of matching a processor's lump-sum bank deposit back to the individual transactions that created it. A $4,237.18 Stripe transfer isn't revenue. It's gross sales minus processing fees, minus refunds, minus chargebacks, minus any reserve hold. Reconciliation maps each component to the right account: revenue, contra-revenue, bank fees, or balance-sheet float. Done correctly, your P&L shows actual gross revenue, fees sit in the right expense line, and the clearing account zeros every month.
Every payment processor sends money the same way: one lump sum to your client's bank account, covering all individual transactions in the period. Stripe doesn't send a $47.00 deposit for each sale. It aggregates everything (sales, refunds, disputes, processing fees, reserve holds) and wires the net balance, sometimes daily, sometimes weekly, sometimes on a custom schedule. That $4,237.18 ACH credit in the bank feed is not revenue. It's a bundle.
Most books break at this exact point. The bookkeeper books the deposit to Sales or Income, moves on, and by month-end has a P&L that understates gross revenue and hides fees somewhere they don't belong. Or they know the net method is wrong, try to decompose by hand, and spend 4-8 hours per client pulling Stripe dashboard exports, cross-referencing payout reports, and building journal entries that still don't agree to the bank statement.
The problem isn't effort. It's method. Payment reconciliation has a framework that most bookkeepers were never formally taught, because accounting programs don't cover it and the processors don't explain it. Once you learn the three-row structure, it clicks for every processor you'll ever encounter.
Every payment processor follows the same three-layer structure, regardless of whether it's Stripe, Square, Shopify Payments, PayPal, or anything else:
Row 1: Gross transactional activity. This is the total of all sales processed in the period, before anything is deducted. It belongs in your revenue account (Sales, Service Revenue, or whatever your chart of accounts calls it). This is the number that flows to the income statement as top-line revenue.
Row 2: Processor deductions. Everything the processor keeps before sending the wire: processing fees (usually 2.9% + $0.30, or similar), refunds issued to customers, chargebacks lost, and reserve holds. Fees are an operating expense. Refunds typically offset revenue as contra-revenue. Reserves park on the balance sheet as a current asset until released. Each item has a different accounting home.
Row 3: Net payout to bank. This is the actual deposit that hits the bank account. Row 1 minus Row 2 equals Row 3. If your journal entry doesn't reconcile Row 1 to Row 3 via Row 2, it's not done.
For lump-sum deposit reconciliation, the processor's payout report is your source document. Every processor has one. Stripe calls it the Payouts report; Square calls it the Balance report. That report shows gross activity and all deductions, and it ties to the bank deposit amount. If yours doesn't tie, something is in the wrong period or missing from the reconciliation.
The three-row framework applies universally, but the reports, terminology, and quirks differ by processor. Here's how each major processor fits:
Stripe is the most complex processor for bookkeepers. Stripe has payout timing that can span multiple days, Connect platform splits, dispute windows, and a Balance transaction report that separates every fee line. For Stripe-connected clients, the reconciliation method builds on this hub's framework but requires processor-specific handling. See the Stripe Bookkeeping hub for complete Stripe-specific reconciliation, payout matching, and fee classification.
Square settles daily by default. Square's transaction reports are more readable than Stripe's, but multi-location businesses create complexity when each location has its own settlement. The QuickBooks Integrations hub covers Square-to-QBO sync for firms keeping clients on QBO.
Shopify Payments deposits on a rolling 3-business-day cycle and combines Shopify POS and online sales in the same payout. The Shopify Balance report separates sales from fees and refunds. For Shopify clients on QBO, the QuickBooks Integrations hub covers the Shopify Payments sync workflow and how to handle multichannel deposits.
PayPal and others (Venmo Business, Cash App Business, Afterpay, Klarna) follow the same three-row structure but offer less detailed reporting. PayPal's Transaction Activity report is the source document. Most newer BNPL processors are roadmap items as Growthy expands processor coverage in Phase 5.
These are the five mistakes that show up most often when reconciliation breaks down. Each maps to a spoke article with the full fix.
The clearing account that never zeros. A bookkeeper sets up a Stripe Clearing account as a holding account, posts deposits there, and plans to decompose later. "Later" becomes three months of unreconciled transactions and a balance sheet line that looks like a current asset but isn't. The fix is a strict month-end rule: the clearing account closes to zero every period. Balance-sheet float covers how to identify and unwind reserve holds, outstanding payouts, and processor float that legitimately belongs on the balance sheet versus clearing-account buildup from skipped reconciliation.
The net method hiding revenue. A bookkeeper books the $4,237.18 deposit directly to Sales. The P&L shows $4,237.18 in revenue when gross sales were actually $4,612.44, and $375.26 in processing fees just vanished. For any client where you need to know gross revenue (which is most clients), the net method makes the income statement wrong. The gross vs. net accounting guide walks through when net is technically acceptable and when it's a problem.
Fee categorization dumped into "Bank Charges." Processing fees, dispute fees, reserve fees, and chargeback losses are different economic events. Lumping them into one Bank Charges line loses the ability to benchmark fee rates, track dispute costs, or reclassify fees as contra-revenue. Payment processor fee classification covers when fees belong in operating expenses, contra-revenue, or cost of goods sold depending on the business model.
Float on the balance sheet nobody investigates. Processors hold reserves against potential future chargebacks. Stripe Standard holds nothing; Stripe for Platforms holds up to 25%. PayPal holds up to 30 days on newer accounts. These reserves are real money sitting at the processor, and they're a balance-sheet asset until released. If your client's books don't show this balance, you're missing an asset.
Multi-currency timing differences. Clients with USD and CAD (or EUR) payment streams get payouts in each currency on different cycles. FX conversion happens at the processor's rate, not the bank's, creating timing differences that don't resolve cleanly. This is an advanced reconciliation problem that most single-currency clients won't hit.
Reconciliation tools like A2X, Synder, Bookkeep, and Acodei connect directly to processor APIs and pull the payout report automatically. They build the journal entry for you (Row 1 to Row 3 via Row 2) and post it to QuickBooks or Xero without manual work. For clients with high transaction volume (100+ sales per day), automation is the right call. Doing it by hand takes 30-60 minutes per payout period; automation takes seconds.
But automation isn't unconditional. It breaks on Connect platforms (Stripe Connect with multiple subaccounts), marketplace splits (where a platform takes a percentage before remitting to the client), and custom fee structures that don't map cleanly to the tool's schema. Automated vs. manual payment reconciliation covers the decision criteria: when automation earns its cost, when it needs manual overrides, and how to audit automation output so you're not trusting a journal entry you didn't build.
Growthy doesn't replace reconciliation tools. Growthy's categorization layer runs on the already-decomposed transactions, after A2X or Synder have done the split. Growthy classifies each line item to the right account. The two tools work in sequence, not competition.
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice. Full disclaimer.
Related: Stripe Bookkeeping, QuickBooks Integrations, AI Bookkeeping
Free during alpha. Read-only access. You review every sync.
CPA firm partner who got tired of watching bookkeepers click categorize 500 times a day. Built Growthy to fix it.
View all articles →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.
Learn exactly how payment reconciliation works, from decomposing processor payouts to building journal entries, with step-by-step guidance for Stripe, PayPal, Square, and Shopify Payments.
Clover, Square, and Shopify integrations that land transactions in the right QBO accounts. Tool comparisons, sales tax sync, and multi-location setups for bookkeepers.
When QBO stops scaling for bookkeepers running 15+ client portfolios. 5 breakpoints past 15 clients, honest comparison vs Growthy, Xero, Puzzle, FreshBooks, plus a 30-day migration overview.