Manaz Afzal Book a consultation

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.

What a read-only review checks firstWeek 1
IDFindingEvidenceRisk if left
F1Payments recorded gross against invoices, payouts netEvery deposit unmatchedBank reconciliation cannot close
F2Fees not booked$1,296 of fees in the quarterMargin overstated
F3Refunds not reflected on invoices3 invoices still paidCustomer and ledger disagree
F4Clearing account used inconsistently$4,128.30 unexplained balanceHides missing or duplicate entries
F5One dispute recorded as income$310 held by StripeOverstated cash
F6Payout ids not stored anywhere in XeroNo audit linkEach 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

Stripe payout booking flowStripe payout events trigger Make, which reads balance transactions, builds a payout entry in Xero through a clearing account, logs it in Sheets, and the bank line matches the payout total.020040060080payout identryfees, refundsnet transferlog rowA · PROCESSORStripepayout.paid,balance reportB · PER PAYOUTMakeSum charges, fees,refunds, disputesC · CLEARINGStripe clearingCharges in, payoutout, back to 0.00D · COSTFees and refundsCard fees account,refunds to invoicesE · BANK FEEDXero bankOne line =one payoutF · AUDITPayout logPayout id, totals,check resultgross charges stay on the invoices;the payout entry carries the netclearing balance must be 0.00after every payoutPAYOUT FLOW · PER EVENTManaz Afzal
One payout, one entry, one bank line, clearing account back to zeroSolid: live data path · Dashed: exception path

The screens your team will use

The bookkeeper sees the bank rule, the payout breakdown, and the scenario that builds the entry.

Xero · Bank rule · Stripe payoutsLive
Conditions
PayeecontainsSTRIPE
Amountis greater than0.00
Then
Transfer toStripe clearing (1250)
ReferencePayout po_1Q8x… from description
Run
Apply toBusiness cheque accountAuto-suggest
CancelSave rule

The rule only suggests a transfer to clearing. The payout entry booked by the scenario must already be there to match.

Stripe · Payout po_1Q8x · breakdownLive

From charges to deposit

ItemCountAmount
Charges914,820.00
Refunds1(640.00)
Fees, charges9(432.48)
Fee on refunded charge keptincluded
Disputes00.00
Payout to bank13,747.52

Read from the balance transactions report for the payout id, not from the dashboard.

Make · Scenario · Stripe payout bookingLive
equaldiffersSTRWatch eventspayout.paidLISTBalance txnsby payout id11ΣAggregateby type=Checksum = payoutXXero entryvia clearing!Hold + alertsum differsROWPayout logSheets

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-level build6 modules
  1. Module AAccounts

    A Stripe clearing account, a card fees cost account, and a refunds treatment agreed in writing.

  2. Module BInvoice payments

    Invoices are paid into the clearing account at the gross charge, from the charge metadata.

  3. Module CPayout entry

    Make reads balance transactions for each payout and books fees, refunds and the net transfer.

  4. Module DCheck

    The rebuilt total must equal the payout amount to the cent, or the payout is held.

  5. Module EOpening balance

    The unexplained $4,128.30 is broken down by payout and cleared, item by item.

  6. 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 balance types to Xero
Stripe typeXero treatmentAccountNote
chargeInvoice payment at grossStripe clearingMatched by invoice number in metadata
stripe_fee / charge feeSpend in clearingCard feesOne line per payout
refundCredit note and refund from clearingStripe clearingOriginal invoice reopened then credited
disputeHeld, not incomeDisputes suspenseReleased when the dispute closes
payoutTransfer clearing to bankBankMatched by the bank rule
adjustmentHeld for a personNoneAdded to the list once understood
Fields read for each payout
Stripe fieldUsed for
payout.idReference on the entry and the log
balance_transaction.typeTreatment above
amount, fee, netTotals and the check
source.metadata.invoiceInvoice to pay
arrival_dateEntry date

Worked figures

Walkthrough arithmetic: one payout rebuilt, and the clearing account before and after the opening balance is cleared.

One payout, one bank lineWalkthrough figures
Charges$14,820.009 charges
Refund($640.00)1 credit
Fees($432.48)card fees
Bank line$13,747.52= payout entry
Clearing, before$4,128.30unexplained
Clearing, after$0.00every payout booked

Payout composition

Charges14,820.00
Refunds640.00
Fees432.48
Net payout13,747.52

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

AreaIncluded
ReviewThree months of Stripe reports, the bank feed and the last reconciliation, with findings
Accounts and rulesClearing, fees and refunds treatment, agreed in writing
ScenarioMake scenario booking one entry per payout, with the check and hold
Bank ruleSuggests the transfer to clearing for each payout
Opening positionOld clearing balance broken down and cleared
Payout logEvery payout id, totals and result
Not includedChanges to Stripe settings or pricing, or other payment providers

Milestones, week by week

  1. Week 1

    Review and rules

    • Three months reviewed
    • Accounts and treatments agreed
    25% of the fee
  2. Week 2

    Opening position

    • Old balance broken down
    • Items cleared with notes
    25% of the fee
  3. Week 3

    Scenario live

    • Payout booking on a copy
    • Live from the next payout
    • Bank rule on
    35% of the fee
  4. Week 4

    Handover

    • One full month at 0.00
    • SOP and walkthrough
    • 14 days of fixes
    15% of the fee

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.

Related work snippets

Next step

Bring me the work that repeats.

I scope it in writing, test it against your current process on your own data and hand over everything I build.

Book a consultation