How to Reconcile Stripe, PayPal, and Amazon Payments in One Accounting Workflow
Key takeaways
- Multi channel reconciliation breaks when you treat every processor like Stripe. Each one has a different cash cycle, fee structure, and settlement cadence.
- Separate clearing accounts per settlement source. One combined clearing account is a black box.
- Reconcile each channel independently first. Consolidate only after channel level tie outs are done.
- No single tool handles all three at depth. The stack that works: Finlens for Stripe (payout decomposition), A2X for Amazon (settlement parsing), QBO bank feed or Synder for PayPal.
You don't have a reconciliation problem. You have a source problem.
If you're dumping Stripe payouts, Amazon settlements, and PayPal transfers into one Undeposited Funds account and trying to "tie month," you'll get one of two outcomes: it won't tie, or it ties because errors net each other out, wrong but lucky.
A bookkeeper on r/Bookkeeping asked about clearing data from multiple payment processors, replies showed exactly how this goes wrong.
Another thread on r/Bookkeeping about QBO AR clearing payments confirmed same trap from receivables side.
The fix is structural, not procedural: reconcile each cash cycle independently, then consolidate at reporting layer.
Step zero: sort channels by cash cycle
Multi channel closes break when teams apply same reconciliation logic to every source. They're not same.
Settlement channels: Stripe, PayPal, Amazon, Square, Shopify Payments. These pay you net via payouts or settlements. Reconcile using clearing accounts.
Invoice channels : wholesale, B2B, retail partners, distributors. You invoice and collect later. Reconcile using AR and AR aging.
Don't mix them. Clearing accounts are for settlement sources. AR is for invoiced sources. Mixing creates "mystery money" that nobody can trace.
The chart of accounts that prevents drift
The control is point: one clearing per settlement source, AR for invoices, holds tracked separately. If your Undeposited Funds contains Shopify + PayPal + Amazon + "other," you've built a black box.
The reconciliation pattern (every settlement channel, same structure)
Every settlement source follows same four step flow:
- Record gross activity: don't book net deposits as revenue. Gross charges to income, fees to expense, refunds as reversals. Net deposits are cash, not revenue.
- Post fees, refunds, and adjustments from payout/settlement detail to clearing: each component needs its own entry, not a net of everything lump.
- Match payout/settlement IDs to bank deposits : if you can't match, you don't reconcile yet.
- Clearing balance = open items only: pending payouts, documented holds, and nothing else. If clearing balance includes unexplained amounts, something is mis posted.
Wholesale is different: invoices → AR → cash receipts. Don't force it through a settlement model.
What's different by channel
Same pattern, different gotchas.
Stripe
- Payouts batch charges, fees, refunds, disputes, and FX into one deposit. The bank sees one number. Your books need decomposition.
- Payout date ≠ charge date. A Friday charge settles in Monday's payout. The offset varies by country and risk review.
- Refunds deduct from future payouts, not as separate bank withdrawals. The next deposit is lower than expected, and refund is against a charge from weeks ago.
- Disputes create three adjustments across 60 days : initial deduction + fee, evidence hold, reversal (if won).
- Deferred revenue on annual subscriptions needs monthly recognition entries, not lump sum booking at charge time.
Automation: Finlens decomposes every Stripe payout into individual charges, posts fees as separate expense entries, handles dispute tracking across payout periods, and splits annual subscriptions into monthly recognition entries. Clearing account balance matches Stripe's balance report at all times. This is deepest Stripe to QBO integration available detailed walkthrough here.

Amazon
- Settlements are bi weekly and bundle everything: product sales, FBA fees, referral fees, storage fees, refunds, reimbursements, and sometimes advertising debits. One deposit, dozens of fee categories.
- Reserves and holds create timing items. Amazon holds a percentage for risk. Track holdbacks separately so clearing doesn't look "broken" forever.
- Sales tax is often marketplace facilitated. In most US jurisdictions, Amazon collects and remits. Don't record marketplace collected tax as your revenue or a liability you must remit unless you're actually remitter.
- Reimbursements and fee reversals exist. If you don't map them, they show up as "random credits" in your clearing account.
A seller on r/FulfillmentByAmazon asked how others handle accounting for FBA responses showed how many sellers can't map Amazon's fee categories to their chart of accounts.
Another thread on r/FulfillmentByAmazon debated direct bank integration vs. a dedicated parser most landed on needing a tool between Amazon and GL.
Automation: A2X parses each settlement report and posts a summary journal entry to QBO product sales to revenue, each fee type to its designated expense account, refunds and reimbursements as separate line items. Per settlement normalization, not per order. At Amazon's volume, that's right trade off.
PayPal
- Two step cash is common. PayPal pays to a wallet, then you transfer to bank. That's two reconciliation points — wallet balance and bank deposit; not one.
- Holds happen unpredictably. PayPal holds funds longer and less transparently than Stripe. Track holds as holds, not as "timing."
- Fee rates vary by transaction type, country, and volume tier. Don't use a blended percent in workpapers. Tie fees to transaction detail.
Automation: Under 200 transactions/month, QBO bank feed with PayPal connected directly approve matches, categorize fees manually. Over 200 transactions/month, Synder for automated per transaction sync with fee separation.
Wholesale / B2B
- Run it through AR. Invoices create AR, collections reduce AR. Reconcile with AR aging and open invoices.
- Expect deductions. Returns, allowances, compliance chargebacks may reduce cash receipts without changing original invoice. Track and document them.
- Revenue recognition ≠ cash arrival. Cash timing and revenue timing are different. Don't book revenue "when check clears."
The tool stack
No single tool handles all three settlement processors at depth each requires. The tools that claim to (Synder across all channels, Dext Commerce) do breadth, not depth; rule based matching across many sources, not payout decomposition for any one of them.

The consolidated bridge
After each channel is reconciled independently, roll up to a consolidated view. This is what leadership and auditors care about.
Illustrative. Your fee rates, refund volumes, and timing will differ.
That "Open timing" column should be supportable by pending payouts (per processor dashboards), documented holds/reserves (tracked and aged), and wholesale AR (open invoices net of credits). If total can't be supported, something is mis posted.
Month end close checklist
- Pull source reports. Payout/settlement exports per processor + bank statements for same window. One folder per month.
- Match deposits to payout/settlement IDs. If you can't match a deposit, you don't reconcile yet — you investigate.
- Reconcile each settlement channel. Clearing ties to pending payouts + documented holds. Fees, refunds, and disputes mapped to correct GL accounts.
- Reconcile wholesale AR. AR aging ties to open invoices. Cash receipts applied. Deductions documented.
- Build consolidated bridge. Roll up from reconciled channels, not from dashboards. The bridge is an output of reconciliation, not an input.
- Investigate variances above threshold. Set a real threshold (dollar amount or %) and enforce it. "Close enough" is not a close.
- File workpapers. Bank statements, payout/settlement exports, clearing reconciliations, AR aging, consolidated bridge, variance notes. Another competent person should be able to follow trail without calling you.
Common mistakes
One giant clearing account. If everything hits Undeposited Funds, you can't isolate which processor caused mismatch. Separate clearing by settlement source.
Net deposits booked as revenue. Net deposits are cash. Revenue is gross activity per your recognition policy. If you book deposits as revenue, you've thrown away information needed to reconcile.
Blended fee % in workpapers. Fee rates vary by payment method, plan, country, and transaction mix. Tie to payout/settlement detail, not a guessed average.
Holds treated as normal timing. Reserves and risk holds are not "it'll clear next week." Track them separately, age them, and follow up.
FAQ
Can I reconcile all three processors in QuickBooks Online?
Yes, QBO handles accounting entries. What it can't do is decompose Stripe payouts or parse Amazon settlements. That's what Finlens (Stripe), A2X (Amazon), and direct feeds or Synder (PayPal) handle before data reaches QBO.
How many clearing accounts do I need?
One per settlement source, minimum. Stripe Clearing, Amazon Clearing, PayPal Clearing. Wholesale goes through AR, not clearing.
What's biggest mistake in multi channel reconciliation?
Booking net deposits as revenue. It removes detail needed to map fees, refunds, and disputes, and makes every subsequent reconciliation harder.
Can one tool handle Stripe, Amazon, and PayPal?
Tools like Synder and Dext Commerce connect to multiple processors. They handle breadth, syncing across many sources with rule based matching. They don't handle depth that Stripe's payout decomposition or Amazon's settlement parsing requires. The tool per channel approach gives you both.
How often should multi channel businesses reconcile?
Monthly at minimum. Weekly clearing account reviews if volume is high. The longer you wait, harder it is to trace a mismatch to its source.
How do I handle wholesale alongside e commerce channels?
AR with aging tied to open invoices. Document deductions and credits that affect collections. Don't run wholesale through clearing accounts, that's for settlement sources only.
What does "done" look like?
Each channel reconciled to its own support before consolidation. Every deposit matched to a payout/settlement or AR receipt. Clearing and AR aged with owners and follow up. Fees, refunds, and disputes mapped consistently across channels.
