Stripe and Adyen Settlement Accounting in 2026: Clearing Accounts, Reconciliation, and the Three-Way Match
Executive Summary
- Payment processor settlement accounting is the discipline of recording the full lifecycle of card and wallet payments, from gross customer charge through processor fees, refunds, chargebacks, reserves, and net bank payout. Done correctly, it produces a clean three-way match between processor data, general ledger, and bank statement.
- A clearing account (also called a settlement account or a “Due from Stripe” account) is the centerpiece of any clean setup. It separates gross revenue from net deposits, tracks funds in transit, and makes month-end reconciliation possible without reverse-engineering payouts.
- Stripe, Adyen, Square, PayPal, and Braintree all follow the same pattern: gross charge collected, fees deducted, refunds and chargebacks netted, reserves potentially withheld, lump-sum payout deposited. Your bank shows only the final net result. GAAP requires you to show the gross.
- The most common settlement accounting failures are booking net payouts as revenue, missing chargeback reversals, ignoring FX timing differences on cross-border payments, and letting clearing account balances drift away from processor-reported balances.
- According to Ridgeway Financial Services, the inflection point where manual reconciliation breaks is usually somewhere between 200 and 500 transactions per month, sooner if disputes or FX are part of the picture. Beyond that, automation through tools like Synder, LedgerUp, or Acodei pays for itself within a quarter.
- Settlement accounting is also a control function. Auditors testing revenue under ASC 606 want to see a documented bridge from processor data to the GL to the bank. Companies that cannot produce this bridge in under an hour will pay for the gap during their audit.
Why Settlement Accounting Matters
If your company collects customer payments through Stripe, Adyen, Square, PayPal, or any other processor, your bank deposits rarely equal “sales.” The processor routes funds, deducts fees, nets refunds and chargebacks, sometimes withholds reserves, and then pays you out on a delayed schedule. Between the customer payment and the bank deposit sit several days of timing, multiple fee categories, and a meaningful possibility of dispute or reversal.
The accounting risk is real. If you record only the net deposit as revenue, you understate revenue and hide processing fees inside the net figure. If you book revenue when cash hits the bank, you create cutoff errors at every month-end. If you do not reconcile to processor detail, you can leave revenue overstated, miss chargebacks, and fail your first audit.
This guide covers how settlement flows actually work, why clearing accounts are the right pattern, the journal entries and reconciliation workflow that make the system function, and the specific issues that break in real-world implementations.
How Settlement Flows Actually Work
The mechanical pattern is consistent across processors:
- Customer charge. A customer pays by card, ACH, or wallet. The processor authorizes and captures the funds.
- Settlement window. The charge moves from “pending” to “available” after the processor’s settlement window, typically two business days for cards in the U.S.
- Fees deducted. Processing fees, interchange, network costs, and platform fees are deducted from the amount due to you.
- Adjustments netted. Refunds, chargebacks, dispute fees, and any other adjustments are netted against the next payout.
- Reserves applied. If the processor holds a rolling reserve (common for higher-risk verticals or new accounts), a percentage is withheld from each payout.
- Payout deposited. The net amount is deposited to your bank as a lump sum representing many underlying transactions.
Stripe documents this explicitly in their reporting architecture. Every dollar moving in or out of your Stripe balance creates a BalanceTransaction object: charges, refunds, fees, disputes, dispute reversals, payouts, and partial captures. These balance transactions are immutable and serve as the authoritative ledger of what happened. Your accounting system has to reconcile to that ledger.
The accounting challenge is that your bank only shows the final net result, while GAAP reporting requires gross presentation, accurate timing, and proper classification of each component.
Clearing Accounts: What They Are and Why They Matter
A clearing account is a temporary balance sheet account used to hold activity until it settles and is fully matched. For payment processors, it functions as a “virtual bank account” that mirrors the processor’s reported balance.
What a clearing account accomplishes
It separates gross revenue from net deposits. Without a clearing account, the only way to record processor activity is to book the net bank deposit as revenue, which understates revenue and hides fees. With a clearing account, you record revenue gross at the transaction date and fees as a separate expense.
It tracks funds in transit. Between the sale date and the payout date, the processor owes you money. The clearing account balance represents that receivable, so your balance sheet reflects economic reality rather than the lag in cash movement.
It makes reconciliation possible at speed. Instead of trying to reverse-engineer payouts from bank activity, you reconcile processor activity to the clearing account, then tie payouts to the bank as simple transfers.
It supports clean month-end cutoffs. With a clearing account, you can recognize revenue based on transaction dates while keeping cash timing separate. This eliminates most of the cutoff errors that surface in first audits.
Naming convention
Create one clearing account per processor. Use clear, scannable names:
- Stripe Clearing (Other Current Asset)
- Adyen Clearing (Other Current Asset)
- Square Clearing (Other Current Asset)
If the processor holds a meaningful reserve, create a separate sub-account so the reserve is visible on the balance sheet:
- Stripe Reserve (Due from Processor) (Other Current Asset)
For audit cleanliness, do not use QuickBooks’ default “Undeposited Funds” account as your clearing account if you have multiple payment sources. It comingles activity from different processors and makes reconciliation harder, not easier. Create dedicated clearing accounts.
Who Needs This (and When)
Not every early-stage company needs a formal settlement workflow on day one. But most fintech and transaction-heavy startups hit a point where it becomes unavoidable.
Common company profiles that need clearing accounts
- Fintech and payments companies: marketplaces, wallets, payfac-like models, lending platforms collecting repayments, embedded finance products
- SaaS or platforms with high transaction volume, especially usage-based billing, subscription plus add-ons, or freemium with paid conversion
- E-commerce and digital businesses with refunds and disputes as a normal operating reality
- Cross-border businesses that charge in one currency and settle in another
- Teams using multiple processors or payment methods (cards, ACH, wallets, BNPL)
Trigger points
The clearest signal that you have outgrown manual reconciliation is operational pain. If month-end close consistently slips because of payment reconciliation, if your books and Stripe Dashboard do not agree, or if your auditor is asking for documentation you cannot produce, you are past the point where a clearing account workflow would have helped.
Other typical inflection points:
- Transaction volume. Manual reconciliation breaks somewhere between 200 and 500 transactions per month. Sooner if you have FX or disputes.
- First audit. Reviewed or audited financials require clean traceability from gross to net.
- Investor or board reporting. Sophisticated investors ask for gross transaction volume, take rate, fee percentages, and reserve balances. Without a clearing account, you cannot produce these without manual extraction.
- Regulatory posture. Money transmitter license applications, partner bank reviews, and BSA/AML examinations all expect documented controls over funds flow.
The Journal Entry Workflow
This is the core of settlement accounting. Three journal entries cover the standard flow. Two more cover the edge cases.
The three core entries
Entry 1: Record gross sales into the clearing account
When a transaction occurs (or daily in batch):
| Account | Debit | Credit |
|---|---|---|
| Stripe Clearing | $100.00 | |
| Revenue | $100.00 |
This recognizes revenue at the gross amount and treats the processor’s holding of those funds as a receivable.
Entry 2: Record processor fees
When fees are known (daily, or at payout):
| Account | Debit | Credit |
|---|---|---|
| Payment Processing Fees | $2.90 | |
| Stripe Clearing | $2.90 |
Fees can be classified either as an operating expense or as cost of revenue, depending on your policy. For transaction-driven businesses (payments fintechs, marketplaces, payfacs), fees are typically cost of revenue because they scale directly with revenue and affect gross margin. For SaaS and other businesses where payments are incidental to the product, fees are typically operating expenses. The key is consistency, not which bucket you choose.
Entry 3: Record the payout from clearing to bank
When the net payout arrives in the bank:
| Account | Debit | Credit |
|---|---|---|
| Bank | $97.10 | |
| Stripe Clearing | $97.10 |
After all three entries, the Stripe Clearing balance should match Stripe’s reported “available balance” at any point in time. If they do not match, something is missing from the GL or has not yet been recorded.
Edge case 1: Refunds
When a customer is refunded:
| Account | Debit | Credit |
|---|---|---|
| Refunds (contra-revenue) | $100.00 | |
| Stripe Clearing | $100.00 |
Refunds reduce revenue (or hit a contra-revenue account, which is preferable for clean reporting) and reduce what the processor owes you. The refund will then net against the next payout from Stripe automatically.
Edge case 2: Chargebacks and dispute fees
A chargeback has two pieces: the reversal of the original charge and the dispute fee charged by the processor. Treat them separately.
Chargeback reversal:
| Account | Debit | Credit |
|---|---|---|
| Chargebacks (contra-revenue) | $100.00 | |
| Stripe Clearing | $100.00 |
Dispute fee:
| Account | Debit | Credit |
|---|---|---|
| Dispute Fees Expense | $15.00 | |
| Stripe Clearing | $15.00 |
If you later win the dispute, Stripe credits your balance with the original charge amount (the dispute fee is generally not refunded). Reverse the chargeback entry but leave the dispute fee in place.
This is the most error-prone area in settlement accounting. The most common mistake is failing to reverse chargebacks when disputes are won, which leaves phantom contra-revenue on the books and understates current-period revenue.
Edge case 3: Reserves
If the processor withholds a rolling reserve (often 5 to 15 percent for higher-risk merchants), the reserve sits in a separate processor-controlled balance.
When the reserve is created:
| Account | Debit | Credit |
|---|---|---|
| Stripe Reserve (Due from Processor) | $5,000.00 | |
| Stripe Clearing | $5,000.00 |
When the reserve is released (typically on a 90 or 180 day rolling basis):
| Account | Debit | Credit |
|---|---|---|
| Bank | $5,000.00 | |
| Stripe Reserve (Due from Processor) | $5,000.00 |
Tracking reserves separately keeps them visible on the balance sheet. Companies that forget about reserves often discover them years later, which is its own kind of audit problem.
FX, Cross-Border, and Multi-Currency Settlement
For companies charging in one currency and settling in another, settlement accounting gets harder. Stripe, Adyen, and other processors apply their own FX conversion at settlement, often at a rate that differs from your accounting system’s spot rate at the transaction date.
The cleanest approach:
- Record the customer payment in the original transaction currency
- Let the processor’s settlement rate determine the home-currency value at payout
- Book the FX gain or loss to a dedicated FX Gain/Loss account
- Review FX gain/loss monthly, not at year-end. Cumulative drift is hard to investigate after the fact.
If your processor charges in EUR but settles in USD, the EUR balance in clearing should be tracked at the original rate, and the USD payout creates the FX adjustment. NetSuite handles this natively if configured correctly. QuickBooks Online requires manual workflow.
The other FX-related risk is that processors typically convert at unfavorable rates compared to spot. Companies handling significant cross-border volume often use a multi-currency setup (separate clearing accounts per currency) and only convert when they need to.
Reserves and Negative Balances: When Things Go Wrong
A surge of refunds, chargebacks, or fraud can push your processor balance negative. When that happens, the processor may reduce or skip a payout, or in extreme cases, withdraw funds from your bank to cover the deficit.
In your books, a negative clearing account balance means you have recorded payments that have not yet (and may never) result in a bank deposit. This is a legitimate liability situation and should be investigated immediately.
Common causes:
- A spike in chargebacks that exceeds incoming charges
- A fraud event where the processor is recovering disputed funds
- A processor freeze pending investigation
In any of these scenarios, your accounting system is showing you something real. Do not “fix” the negative balance by writing it off. Investigate, document, and disclose if material.
Month-End Reconciliation: The Three-Way Match
A clean month-end reconciliation is a three-way match: processor balance activity, general ledger, and bank statement. If those three do not agree, the close is not complete.
Step 1: Reconcile the clearing account to the processor balance
Pull the processor’s end-of-period balance report. For Stripe, this is the Balance Summary report. For Adyen, the equivalent payout report.
Compare the closing balance of the processor’s report to the closing balance of your Stripe Clearing account in the GL.
If they do not match, work through this checklist:
- Are all charges from the period recorded in the GL?
- Are all fees recorded?
- Are all refunds, chargebacks, and dispute events recorded?
- Are all payouts recorded?
- Are there any timing differences (charges in Stripe but not yet in GL, or vice versa)?
- Are there any FX adjustments that have not posted?
Step 2: Reconcile payouts to the bank
Every processor payout should match a corresponding bank deposit by amount and date (allowing for one or two business days of bank posting delay). Investigate any unmatched deposits the same day.
This is the easiest of the three matches but also the one most often left unfinished. A missing match here can hide weeks of unrecorded activity.
Step 3: Tie revenue to the GL
The total gross revenue recorded in the GL for the period should reconcile to:
- Sum of all processor charges in the period
- Less refunds and chargeback reversals
- Plus any non-processor revenue (wires, ACH, manual invoices)
If reported ARR or recognized revenue diverges from processor activity by more than expected timing differences, something is wrong somewhere in the workflow.
Documentation
Maintain a monthly reconciliation file with:
- The processor reports used
- The GL trial balance for the clearing account
- The bank statement for the payout account
- A tie-out schedule showing the three-way match
- Any reconciling items and their resolutions
This is what makes the process audit-ready. If your auditor asks for the reconciliation in year three and you cannot produce it for year one, that is a finding.
When Manual Reconciliation Breaks: Automation Options
Below a few hundred transactions per month, manual reconciliation works fine if the team is disciplined. Above that, automation pays for itself.
The 2026 landscape includes several solid options:
Synder for QuickBooks and NetSuite integrations, with summary or detail sync modes. Best for SMB and mid-market.
Acodei for QuickBooks-only integrations. Good free tier for very small companies.
LedgerUp for NetSuite-focused companies needing detailed transaction sync, dispute automation, and FX handling. Targets B2B SaaS finance teams.
Puzzle for startups wanting an all-in-one accounting platform with native Stripe integration.
Native Stripe Revenue Recognition for companies using Stripe as their primary processor and willing to live within Stripe’s reporting framework.
Common automation triggers:
- Transaction volume above 200 to 500 per month
- Close consistently takes more than a day of dedicated reconciliation time
- Multiple processors creating mapping complexity
- FX exposure creating manual rate-tracking work
- Approaching first audit and need clean traceability
The build-versus-buy calculation almost always favors buying. The internal cost of building reliable reconciliation infrastructure typically exceeds the annual cost of automation tools by 5 to 10x.
Common Pitfalls and How to Avoid Them
After working through settlement accounting with dozens of fintech and SaaS companies, the same handful of issues recur.
Booking net payouts as revenue. Understates revenue, hides fees, distorts gross margin, breaks ASC 606 compliance.
Recognizing revenue when cash hits the bank. Creates cutoff errors at every month-end. Revenue should be recognized at the transaction date (when the performance obligation is satisfied), not at the payout date.
Missing chargeback reversals when disputes are won. Leaves phantom contra-revenue on the books. Build a control where every dispute outcome is reviewed and the corresponding reversal posted.
Ignoring FX gains and losses. They compound silently. Review monthly, not annually.
No documented bridge from gross to net. Auditors will spend hours building one if you do not. Build it once, maintain it monthly.
Using “Undeposited Funds” as the clearing account in QuickBooks. Comingles processor activity with other payment sources. Create dedicated clearing accounts per processor.
Letting clearing account balances drift. If your Stripe Clearing GL balance no longer matches Stripe’s reported balance, you have an unreconciled gap that grows every period. Reconcile monthly without exception.
These are not exotic problems. They are the cost of growing transaction volume without investing in reconciliation infrastructure.
How Ridgeway Financial Services Helps
Ridgeway Financial Services is a CPA-led firm specializing in fintech, technology, and crypto companies. Settlement accounting is one of the most common areas where high-growth companies need help, because the systems get complex faster than internal finance teams can scale.
We support companies with settlement accounting in four ways.
Initial buildout. Designing the chart of accounts, clearing account structure, fee classification policy, and journal entry templates that fit your specific processor mix and transaction patterns. Done correctly the first time, this saves months of cleanup later.
Cleanup of existing books. Restating prior periods where revenue was booked net, fees were missed, or chargebacks were not properly reversed. This is common when a company is preparing for a first audit or fundraise and discovers the books do not tell a clean story.
Ongoing monthly reconciliation. Running the three-way match every month as part of monthly accounting and bookkeeping services. For companies past the manual reconciliation point, we operate the automation tools and own the close.
Audit readiness and technical accounting memos. Documenting the settlement accounting policy, ASC 606 revenue recognition treatment, fee classification rationale, and FX methodology. These are the technical accounting memos auditors expect to see, and the documents that turn a painful first audit into a routine one.
If your transaction volume is growing, you are heading toward an audit, or stakeholders are asking tougher questions about gross revenue, fees, and reserves, getting settlement accounting right is one of the highest-leverage finance upgrades you can make.
Talk to Ridgeway Financial Services if you want to design or fix your settlement accounting workflow. We work with companies running Stripe, Adyen, Square, PayPal, Braintree, Checkout.com, and most major processors.
Frequently Asked Questions
Do I need a clearing account if I am small?
If transaction volume is low and you are running cash basis, you can survive without one. As soon as you need GAAP reporting, are approaching an audit, have frequent refunds or disputes, or use multiple processors, a clearing account becomes the safer default. Setting one up early is materially cheaper than restating later.
Should processing fees be revenue contra or operating expense?
Both treatments are acceptable depending on your business model. For transaction-driven businesses (payments, marketplaces, payfacs), fees are typically cost of revenue because they scale directly with revenue and affect gross margin. For SaaS and other businesses where payments are incidental, fees are typically operating expenses. The key is consistency and clear gross-versus-net presentation.
How long does a Stripe payout take to clear?
In the U.S., a typical card charge moves from pending to available after 2 business days. Once available, it gets included in the next automatic payout, which takes another 1 to 2 days to clear your bank. Total time from charge to bank: 2 to 4 business days. International payouts take longer.
What is the right reconciliation frequency?
Monthly is the minimum for close. Weekly is standard for growing teams. Daily is common in higher-volume or higher-risk environments where reserves and disputes move quickly. Anything less frequent than monthly creates cumulative drift that becomes hard to investigate.
My payout includes multiple days of transactions. How do I handle that?
This is normal. The clearing account accumulates daily activity (charges minus fees minus refunds minus chargebacks) and is reduced when the payout transfers to your bank. Match the payout amount to the corresponding period of activity in the clearing account using Stripe’s Payout Reconciliation report or the equivalent for your processor.
How do I handle FX when I charge in EUR but settle in USD?
Record the customer payment in the original transaction currency (EUR). The processor’s settlement converts to USD at the payout rate. Book the FX gain or loss to a dedicated account. Review monthly. NetSuite handles multi-currency natively. QuickBooks Online requires manual workflow.
What is a three-way match in settlement accounting?
The three-way match reconciles three sources: the processor’s reported balance and activity, your general ledger (specifically the clearing account and revenue), and your bank statement. All three should tie to the same activity for the period. If they do not, the close is not complete.
At what transaction volume should I automate reconciliation?
The breaking point is usually 200 to 500 transactions per month, sooner if you have disputes or FX. Above that volume, manual reconciliation becomes unreliable and time-consuming. Tools like Synder, LedgerUp, Acodei, or Puzzle automate 90 to 95 percent of the workflow and typically pay for themselves within a quarter.
Can I just use the Stripe Dashboard for reconciliation?
The Dashboard is your source data, not your reconciliation system. You still need to reconcile Stripe activity to your general ledger and your bank statement. Stripe’s Payout Reconciliation report is the bridge document that makes that reconciliation possible.
Reviewed by YR, CPA, Senior Financial Advisor, Ridgeway Financial Services
Ridgeway Financial Services is a CPA-led fractional CFO and accounting firm serving technology, fintech, and digital asset companies. We help high-growth companies build audit-ready financial systems, navigate complex revenue and settlement accounting, and prepare for fundraising, audits, and IPO.