Build or buy: reconciling Stripe payouts and bank lines with your ledger
What is inside a Stripe payout, why matching it by hand takes days at month end, and the three routes, with who runs each one after.
A Stripe payout is one bank line made of many payments, minus fees, refunds and disputes. You can buy a product, build a matcher in-house, or have us build one you own. Our Proof on your real payouts is from 1,500 euro, takes 5 working days and writes nothing while it runs.
What is inside a Stripe payout
Stripe's docs say an automatic payout can include funds from multiple transactions. Each movement of money creates a balance transaction with a gross amount, a fee and a net amount. Stripe's payout reconciliation report lists every payment, refund, dispute and fee inside a payout.
Stripe's own docs add three snags:
- The report groups a payout by its estimated arrival date, not the date your bank posts it.
- A payout can arrive before its reconciliation data is ready.
- For manual and instant payouts, Stripe cannot tell which transactions each payout holds, so you reconcile those yourself.
Why the match takes days at month end
The bank shows one amount. The ledger shows open invoices at full value. In between sit fees, refunds netted against later sales, and disputes. Someone splits each payout, finds the invoice each payment pays, posts the fees and chases the rest. Whatever does not fit moves to next month.
The three routes
Buy a product. Synder's site describes it as accounting automation for ecommerce, retail and SaaS businesses, names Stripe among its sources and QuickBooks Online, Xero, NetSuite and Sage Intacct among its ledgers, and its pricing page lists prices for most of its plans, with Premium through sales. Xero's app store listing says Xero automatically matches payments as they come through your Stripe bank feed. Stripe's own payout reconciliation report gives the itemised breakdown for automatic payouts. A product fits well when your rules are its rules.
Build it in-house. Your developers read the balance transactions API, map each transaction's reporting category to a ledger account (Stripe's API reference suggests reporting_category over type for accounting) and write the matching rules with finance. That time comes from the team that ships your product, and the matcher stays theirs to run. Stripe's API reference lists a long set of transaction types, and its docs give each report type a version number. A field that moves can break a home-made matcher quietly.
A fixed-price build you own. We build the matcher on your rules and your real data. The Proof is one workflow, fixed scope, with 3 to 5 pass/fail tests written on day 1. It runs in shadow mode: it reads and reports, and writes nothing. The Pilot, from 6,000 euro, runs it live in your systems for 30 days against a baseline you agree. Care, from 500 euro a month per live system, covers monitoring, fixes and small changes. You own the code.
| Route | Who runs it after | What you own | How long until it runs | When Stripe changes a field |
|---|---|---|---|---|
| A product | The vendor | Your subscription and your entries | As long as setup and mapping take | The vendor updates its connector, on its timeline |
| In-house | Your developers | The code | As long as your developers can spare | Your developers fix it, once they notice |
| Fixed-price build | Our engineers under Care, or your team | The code, the tests and the runbook | Proof in 5 working days, then a 30-day Pilot | Covered by Care, or your team edits code it owns |
A worked example, on synthetic data
Our sample hold list, from the duplicate invoice check, shows what a person gets on day 5. Every row is synthetic: 20 sample invoices, 4 held, each next to its evidence, with 3 confirmed duplicates, 1 false alarm released. A reconciliation leftover list works the same way: each unmatched payout line sits next to its reason, such as "no open invoice with this amount", and nothing posts until a person decides. The bank reconciliation write-up has the full scope.
Half up front, the other half when it passes the tests. If it fails and we can't fix it within 5 working days, the first half comes back. The Proof is credited in full against a Pilot booked within 30 days.
Send us the job in the form below and a plan with a fixed price comes back within 24 hours.
Contact
Send us the problem or email jayron@geurs.com