Work snippet
Stripe payouts, fees and refunds reconciled to the Xero bank feed
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
Card payments go through Stripe, and each payout nets many charges against fees, refunds and disputes, so the bank line never matches an invoice. Make rebuilds every payout from Stripe’s balance report and posts it via a Xero clearing account, which has to come back to 0.00.
The problemStripe pays out one lump that matches no invoice, and fees and refunds go unrecorded.
What changesEvery payout is rebuilt line by line in Xero, and the clearing account returns to 0.00.
- Area
- Payments and Xero
- Tools
- Stripe · Xero · Make · Google Sheets
- Typical scope
- US$250-600
- Timeline
- About 4 weeks · fixed milestones
The situation and what was breaking
The bank sees one lump sum. Inside it are nine separate charges, one refund and a fee taken from each, and the ledger recorded none of them.
Invoices were being marked paid from the Stripe dashboard, then the payout arrived in the bank as a single amount that matched nothing. Fees were never recorded as a cost, a refund left its invoice showing paid, and month-end meant opening the Stripe report and rebuilding each deposit by hand.
A clearing account had been set up once, but nobody booked into it consistently, so it carried a balance nobody could explain.
- Bank deposits that match no invoice
- Card fees missing from the cost lines
- Refunds leaving invoices marked paid
- A clearing account with $4,128.30 nobody could explain
- Days of rebuilding at month-end
What good looks likeEvery deposit reconciled to one entry, fees visible as a cost, and a check that tells me when something is missing.
Discovery findings
What a read-only review checks first: three months of Stripe payout and balance reports, the Xero bank feed, the clearing account and the last reconciliation.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | Payments recorded gross against invoices, payouts net | Every deposit unmatched | Bank reconciliation cannot close |
| F2 | Fees not booked | $1,296 of fees in the quarter | Margin overstated |
| F3 | Refunds not reflected on invoices | 3 invoices still paid | Customer and ledger disagree |
| F4 | Clearing account used inconsistently | $4,128.30 unexplained balance | Hides missing or duplicate entries |
| F5 | One dispute recorded as income | $310 held by Stripe | Overstated cash |
| F6 | Payout ids not stored anywhere in Xero | No audit link | Each check starts from scratch |
Architecture: Stripe Xero reconciliation
Stripe already knows exactly what is inside each payout. The scenario reads that, books one balanced entry per payout through the clearing account, and leaves only a single line to match on the bank feed.
Scroll sideways to see the full drawing
The screens your team will use
The bookkeeper sees the bank rule, the payout breakdown, and the scenario that builds the entry.
The rule only suggests a transfer to clearing. The payout entry booked by the scenario must already be there to match.
From charges to deposit
| Item | Count | Amount |
|---|---|---|
| Charges | 9 | 14,820.00 |
| Refunds | 1 | (640.00) |
| Fees, charges | 9 | (432.48) |
| Fee on refunded charge kept | included | |
| Disputes | 0 | 0.00 |
| Payout to bank | 13,747.52 |
Read from the balance transactions report for the payout id, not from the dashboard.
If the rebuilt total does not equal the payout, nothing is booked and the payout is held for a person.
How it is built
Accounts and rules first, then the opening balance is cleared, then payouts are booked by the scenario.
- Module AAccounts
A Stripe clearing account, a card fees cost account, and a refunds treatment agreed in writing.
- Module BInvoice payments
Invoices are paid into the clearing account at the gross charge, from the charge metadata.
- Module CPayout entry
Make reads balance transactions for each payout and books fees, refunds and the net transfer.
- Module DCheck
The rebuilt total must equal the payout amount to the cent, or the payout is held.
- Module EOpening balance
The unexplained $4,128.30 is broken down by payout and cleared, item by item.
- Module FLog
Every payout id, its totals and its check result are logged for the audit trail.
Field mapping and rules
Stripe types map to a short list of Xero treatments. Anything new from Stripe is held until it is on this list.
| Stripe type | Xero treatment | Account | Note |
|---|---|---|---|
| charge | Invoice payment at gross | Stripe clearing | Matched by invoice number in metadata |
| stripe_fee / charge fee | Spend in clearing | Card fees | One line per payout |
| refund | Credit note and refund from clearing | Stripe clearing | Original invoice reopened then credited |
| dispute | Held, not income | Disputes suspense | Released when the dispute closes |
| payout | Transfer clearing to bank | Bank | Matched by the bank rule |
| adjustment | Held for a person | None | Added to the list once understood |
| Stripe field | Used for |
|---|---|
| payout.id | Reference on the entry and the log |
| balance_transaction.type | Treatment above |
| amount, fee, net | Totals and the check |
| source.metadata.invoice | Invoice to pay |
| arrival_date | Entry date |
Worked figures
Walkthrough arithmetic: one payout rebuilt, and the clearing account before and after the opening balance is cleared.
Payout composition
QA and testing checklist
Every check runs in a copy or on test records first, and each one is ticked with evidence before go-live.
- T1TotalsA rebuilt payout equals the Stripe payout to the cent.
- T2FeesFees land in the card fees account, one line per payout.
- T3RefundA refunded charge credits its invoice and the fee stays as a cost.
- T4DisputeA dispute goes to suspense, not income.
- T5Unknown typeAn adjustment holds the payout and alerts.
- T6Duplicate eventThe same payout event twice books once.
- T7Bank matchThe bank rule finds exactly one entry for the payout.
- T8Zero checkClearing balance is 0.00 after a full month.
- T9Opening itemsEach item of the old balance has a payout id or a note.
Scope
| Area | Included |
|---|---|
| Review | Three months of Stripe reports, the bank feed and the last reconciliation, with findings |
| Accounts and rules | Clearing, fees and refunds treatment, agreed in writing |
| Scenario | Make scenario booking one entry per payout, with the check and hold |
| Bank rule | Suggests the transfer to clearing for each payout |
| Opening position | Old clearing balance broken down and cleared |
| Payout log | Every payout id, totals and result |
| Not included | Changes to Stripe settings or pricing, or other payment providers |
Milestones, week by week
- Week 1
Review and rules
- Three months reviewed
- Accounts and treatments agreed
- Week 2
Opening position
- Old balance broken down
- Items cleared with notes
- Week 3
Scenario live
- Payout booking on a copy
- Live from the next payout
- Bank rule on
- Week 4
Handover
- One full month at 0.00
- SOP and walkthrough
- 14 days of fixes
Handover and keeping it running
Handover pack
- One-page routine what to check after each payout and at month-end
- Treatment table every Stripe type and where it goes
- Payout log with a filter for held payouts
- Recorded walkthrough the scenario, the rule and the clearing account
- Ownership list Stripe and Xero connections in the business's name
- 14 days of fixes for defects in the agreed scope
Keep it running
The clearing account is the alarm. If it is not 0.00 after the last payout of the month, something was missed or booked twice, and the log shows which payout.
- Each payout: held payouts cleared the same day
- Month-end: clearing at 0.00 before reports
- When Stripe adds a product or currency: add its types to the treatment table
- Optional support hours at US$35 per hour, agreed in writing
Typical scope for this kind of project: US$250-600
About 4 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts. After handover, a set block of hours each month is available at the same rate, agreed in writing.
Discuss an engagement.
Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.