GoCardless Xero integration

What a GoCardless to Xero integration actually does

GoCardless knows everything about a collection - the mandate it was taken under, the payment that cleared on Thursday, the per-transaction fee, the payout that lands net in your bank account next week, the Direct Debit that fails and is clawed back four days later. Xero, and whoever closes your books inside it, needs all of that as accounting: the invoice marked paid, the payment sitting in the right account, the payout reconciled against the real bank line, the fees booked as expense.

The gap between those two systems is where the manual work lives. A GoCardless to Xero integration closes it automatically. It reads each relevant event from GoCardless, applies your matching and posting rules, and keeps Xero in step so nobody has to reconcile a batched payout against a spreadsheet of individual payments at the end of the month.

What data moves

GoCardless object / event	Becomes in Xero	Notes
Confirmed payment	Payment applied to the matching sales invoice	Posted into a GoCardless clearing account, matched by reference, amount, and mandate
Customer / mandate	Contact	Mapped once, so every future payment ties to the same debtor
Payout	Bank transaction reconciled against the bank feed	Nets many payments minus fees, refunds, and failures in that batch
Provider fees	Expense booking on the payout	Per-transaction plus percentage, deducted before the money arrives
Failed / charged-back payment	Reversing payment, invoice reopened	Direct Debit can fail days after it was reported paid
Refund	Credit note against the contact	Reverses the original payment on the refund date
Subscription billed in GoCardless	Sales invoice raised in Xero	Only when the recurring billing lives in GoCardless, not Xero

The clearing account, fee account, and matching rules are agreed once and encoded in the pipeline. After that, nobody maps a payment by hand again.

The details that break naive syncs

A CSV import or a generic connector gets you most of the way and leaves the expensive part on your desk:

• The payout is not the sum of the payments. GoCardless pays out net of fees, days after collection, in a batch that spans many payments and sometimes more than one currency. Book the payout as income and nothing reconciles. The collection and the settlement have to be separate postings joined by a clearing account that returns to zero.
• Late failures and chargebacks. A SEPA or Bacs Direct Debit is reported paid and can still fail or be indemnity-claimed days later. If the reversal does not flow back into Xero, the invoice stays falsely paid and the payout no longer balances.
• Matching to the right invoice. GoCardless identifies a payment by mandate and reference, Xero by invoice and contact. Amount alone is ambiguous once two customers pay the same figure. Matching needs mandate, reference, and amount together.
• Multi-currency. GoCardless settles each currency in its own payout. Those have to land in the correct Xero organisation and currency, with FX handled rather than flattened to one number.
• Rate limits and tokens. Xero caps API calls per minute and per day and expires OAuth tokens on a schedule. A naive sync that ignores both stalls or drops records under load.
• Idempotency and ordering. GoCardless events must be applied in order - confirmed before paid out, paid out before failed - and never twice. Re-run a careless job and you double-post a month.

How we build and run it

We treat this as a pipeline, not a batch job. GoCardless payment, payout, fee, refund, and failure events are consumed by webhook or on a schedule, validated, matched to the right Xero contact and invoice, and posted through your agreed clearing and fee accounts. Payouts are reconciled against the bank feed so the numbers close themselves.

The pipeline is idempotent: every GoCardless event carries a stable identifier, so a retry or a re-run never produces a duplicate payment or a double-counted payout. Events are processed in order, so a late Direct Debit failure correctly reverses a payment that was already applied. It runs on cloud-native, fully EU-hosted AWS infrastructure, so payment and customer data never leaves the EU, which keeps your DPA / AVV and GDPR obligations clean.

And then we keep it running. Monitoring, alerting, incident response, and watching for GoCardless and Xero API changes, token rotation, and rate-limit shifts are our responsibility under contract. You get a named owner and an SLA. The close stops depending on anyone remembering to run a sync.

When this integration is worth building

If you collect a handful of Direct Debits a month against invoices you already raise in Xero, the native GoCardless connection is genuinely fine and we will tell you so. The pipeline earns its place when volume climbs, when subscriptions are billed in GoCardless rather than Xero, when payouts span currencies, or when fees, refunds, and late failures turn every payout into a manual reconciliation your finance team should not have to do by hand.