Job payout-stripe-deposit-matches-bank-line · revised 11 October 2026
Make every Stripe payout match one bank deposit line in Xero or QuickBooks Online
Each automatic Stripe payout in an agreed test period becomes one ledger entry equal to the bank deposit, with its gross, fees and refunds explained and a clearing balance that returns to zero.
You might be seeing
- A bank deposit equals the sum of many sales minus fees and refunds, so nothing in the ledger equals it
- A clearing or Stripe account in the ledger never returns to zero
- Fees and refunds are missing from the ledger or posted on a different date from the payout
No passwords, keys, card details or admin invites needed to start.
What usually happened
The ledger records each sale at its gross amount against a Stripe account, while the bank receives a batched net amount on a different date. Nothing links the ledger entries to the payout they were paid in, so no single entry matches the bank line and fees, refunds and disputes inside the payout are unexplained.
Who it’s for: A bookkeeper, finance manager or shop owner who receives one net Stripe deposit but records every sale as a gross payment, so each bank line has to be matched by hand.
Usually starts when: The bank shows one deposit per payout that matches no single ledger entry, and the month-end bank reconciliation takes hours of manual splitting.
The result: For the agreed test payouts, one ledger entry per payout equals the bank deposit amount, its composition by category (gross, fees, refunds, disputes and any others) adds up from Stripe's own transaction list for that payout, and the clearing balance after the payouts equals only the transactions not yet paid out.
Check whether this job fits
Answer these from what you can see without sending logins, invoices or customer data. Nothing is submitted unless you choose to contact us; this is a fit check, not permission for us to touch your systems.
Checks you can run yourself
Break one payout into its parts
In the Stripe Dashboard open one payout and download its itemised transaction list, or open the payout reconciliation report. Do not share the export.
Look for: Whether the gross charges, fees and refunds in that list add up to the payout amount, and whether the payout date matches the bank line date.
What you get
- The job as a pull request or exported configuration, with the matching rule and the account roles described
- A reconciliation sheet per test payout: bank amount, ledger entry, composition and the clearing balance
- A list of exceptions the rule could not place, such as a payout in a second currency or a manual payout
Included
- Automatic Stripe payouts in one settlement currency for one Stripe account and one Xero organisation or QuickBooks Online company
- A payout-level ledger entry that moves the net amount from a clearing account to the bank account, matching the deposit
- A breakdown of each payout by gross, fees, refunds and disputes from Stripe's per-payout transaction list, recorded against the clearing account
- A repeat-safe job: running it again for the same payout creates no second entry
- Tests on Stripe test-mode data or an invented export and a demo or sandbox ledger
Not included
- Manual and instant payouts, which Stripe says it cannot tie to specific transactions, and payouts in several currencies
- Subscription or invoice access rules, covered by other offers
- Choosing the chart of accounts, fee expense accounts or tax treatment of fees and refunds: your accountant decides
- Historic payouts already reconciled by hand, unless agreed as a backfill
- Bookkeeping, tax, audit or any accounting advice, including deciding how a transaction should be treated in your accounts
- Changing posted, reconciled or locked-period transactions: your accountant or account holder decides and performs those
- Live changes: your authorised account holder applies any agreed change and holds the production keys
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
For three test payouts, each produces exactly one ledger entry whose amount equals the payout amount.
Evidence: The payout list, the ledger entries and a per-payout amount comparison.
For each payout, gross charges less fees, refunds, disputes and every other balance transaction category in Stripe's per-payout list equals the payout amount, shown per category.
Evidence: The per-payout composition table with totals.
After the three payouts, the clearing balance equals the net of the test transactions not yet paid out, and that list is shown.
Evidence: The clearing balance and the list of unpaid transactions.
Running the job again for the same payout creates no second entry and changes no amount.
Evidence: Entry counts before and after the repeat run.
Sign-off. You inspect the named test evidence and sign off before payment. Your authorised account holder performs and verifies any live change, and decides what happens to records already posted.
If it fails. If an agreed check does not pass, you do not pay for this fixed scope. We hand over the findings and agree whether to stop or re-quote; no surprise work and no change to your live records.
When it fits, and when we stop
It fits when
- You use automatic Stripe payouts and can export test-mode or synthetic payout data
- A clearing account that can receive payments exists or can be agreed in a demo organisation or sandbox company
- The bank feed or bank statement lines are visible to your bookkeeper, who can say what a matching line should look like
- A person on your side can approve the account roles and the date rule (arrival date versus bank posting date)
- Real financial records, customer data and keys are handled only after written agreement, through a secure handoff we agree with you; the first enquiry and the fit check use invented or redacted examples
We stop and tell you if
- Payouts are manual or instant only, or span several settlement currencies
- Stripe is not the only processor feeding the same clearing account and the sources cannot be separated
- The ledger cannot hold a clearing account for the agreed period
What could go wrong
Before switch-over, nothing in your live ledger is changed. After the switch, your accountant can reverse the entries the job created for a payout, which the repeat-safe design lists by payout id. Entries in the demo or sandbox file are disposable.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A payout total is matched to the bank line while its composition is wrong, hiding a missing refund or fee. | The composition is totalled from Stripe's own per-payout list and checked against the payout amount; a mismatch is an exception, not a posted entry. |
| Report timing differs from bank timing, so a payout is matched on the wrong date. | The date rule is agreed in writing; Stripe groups payouts by estimated arrival date, which may differ from the bank's posting date, and the sheets show both. |
| The job posts into a closed period or a reconciled bank line. | It posts only to the demo or sandbox file; live posting is performed by your account holder under their own controls. |
An independent reviewer recomputes each payout total from the transaction list, checks that fees and refunds are not double counted, and confirms the evidence uses only test or invented amounts. Your accountant approves the account roles.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the account roles, the date rule and the matching rule for a payout in writing with your accountant
- Recreate the problem with test-mode or synthetic payouts and record the unmatched bank line and the clearing balance
- Fetch the transactions for one payout and total gross, fees, refunds and disputes by category
- Post one entry per payout from clearing to bank and the breakdown against clearing, repeat-safe by payout id
- Run three payouts including one with a refund and one with a dispute, and compute the clearing balance
- Independent review of the sums and the sheets, then hand over for your accountant to approve and your developer to switch live
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access, any licences and necessary permissions are in place. Platform and supplier charges are excluded unless the written quote includes them. No charge or booking is created by an enquiry.
Need to keep it working?
If payouts keep arriving, discuss a monthly check that every payout has its entry as a separate standing agreement.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Stripe's payout reconciliation report groups each automatic payout by reporting category and can be downloaded itemised; many small businesses reconcile from it by hand. docs.stripe.com
- Stripe documents listing the balance transactions for one payout through its API; your developer can build the same lookup. docs.stripe.com
Questions
Does this reconcile my bank for me?
No. It makes the ledger entry for each payout match the deposit so that your bookkeeper's own reconciliation step becomes a simple match. Accepting a match in the accounting system remains a person's decision.
What about disputes and fees?
They are read from Stripe's per-payout transaction list and shown separately. How they are expensed or treated for tax is your accountant's decision.
I use manual payouts.
Stripe says it cannot identify which transactions a manual payout contains, so this per-payout match does not apply. Reconciling those needs a different design and its own quote.
Send an enquiry
Send us
- Whether payouts are automatic, the payout schedule and the settlement currency
- One invented payout showing a sale, a fee and a refund, with amounts that add up to a deposit
- Which accounting system you use and how sales are recorded today (gross or net)
- Do not send credentials, bank details, invoices, customer records or confidential code in the first enquiry
Later, once you agree
- Test-mode payout data or a synthetic export, shared through the agreed route; live Stripe keys are not part of this job
- A demo organisation or sandbox company created by you for the job
- Your accountant's written account roles for clearing, fees, refunds and the bank account
- A secure, company-controlled handoff route agreed in writing before any access; no passwords, keys or customer records by ordinary email
You keep the live accounting organisation, payment accounts, production keys and every customer and financial record. We work on an authorised demo, sandbox or synthetic copy through a company-controlled handoff, never a personal login. Your authorised account holder approves and performs any live change and checks the result under their own keys.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “payout-stripe-deposit-matches-bank-line” as the subject.