How to Connect Stripe to Xero: A UK Business Guide

If you take card payments through Stripe and keep your books in Xero, connecting the two should turn a tedious monthly job into a near-invisible one. Done well, your charges, fees, refunds and payouts land in Xero cleanly, and reconciliation is a few clicks. Done badly, you get a pile of unmatched bank lines, missing fees and VAT that doesn't add up.

This guide explains the realistic options for connecting Stripe to Xero in the UK, how each one handles fees, payouts and refunds, the way VAT should be treated, and the specific gotchas that catch people out.

The quickest answer: Xero's native Stripe feed

For most UK businesses that invoice customers, the simplest route is built into Xero. You add Stripe as a payment service under Settings → Payment Services, then attach it to your online invoice template. Customers can pay an emailed Xero invoice by card, and Xero records both the payment and the Stripe fee automatically.

Alongside this, Xero offers a Stripe bank feed. It's worth understanding how this works, because it shapes reconciliation:

• The feed imports your Stripe payouts (the net lump sums that hit your bank), not every individual charge.
• When an online invoice is paid, Xero matches it back to the underlying Stripe charge, so the payout line reconciles against the right invoices.
• The Stripe fee is posted automatically as an expense, so your sales stay at the gross amount and the fee sits separately.

That last point is the whole game. If you invoice a customer £500 and Stripe deducts a processing fee, your revenue should still read £500, with the fee recorded as a separate cost. The smaller amount that actually arrives in your bank simply clears the balance.

What the native feed needs to work smoothly

Auto-matching is reliable only when a few conditions are met:

• Stripe is on an automatic payout schedule, not manual payouts.
• The invoice was paid through Stripe on the Xero invoice itself. If Stripe is used as a gateway on your own website or inside another app, Xero often won't record the fee automatically, and you'll reconcile manually.
• One Stripe account maps to one Xero organisation. Several Stripe accounts feeding a single org isn't supported.

For a single-currency UK business that invoices customers and gets paid on those invoices, the native feed is usually all you need.

When the native feed isn't enough

The native approach assumes a clean "invoice → paid by card → reconcile" flow. Plenty of businesses don't fit that shape:

• You take payments on a website, checkout or app rather than on Xero invoices — subscriptions, e-commerce, donations, bookings.
• You process high volumes of charges that you don't want sitting in Xero as individual invoices.
• You charge in multiple currencies.
• You want summarised accounting rather than per-transaction detail.

In these cases, charges arrive in Stripe outside Xero's invoice flow, so Xero has no invoice to match the payout against. You then need something to reconstruct each payout: the gross charges in it, less Stripe fees, less refunds settled in that batch, to arrive at the net figure that matches your bank line. If you're running an online store specifically, our companion guide on how to sync Shopify and Xero covers the e-commerce version of this problem in more detail.

The four ways to connect Stripe and Xero

There's no single "best" method — it depends on volume, where payments happen, and how clean you need reconciliation to be. Here's an honest comparison.

Approach	Best for	Strengths	Weaknesses
Native Stripe feed in Xero	Invoicing businesses, single currency	Free; built in; auto-records fees; one-click match	Assumes payment on Xero invoices; weak for off-platform or high-volume charges
Dedicated apps	E-commerce, subscriptions, higher volume	Payout-level summaries; fees, refunds and multi-currency handled	Monthly fee; limited to supported scenarios
Zapier / Make	Light glue, edge workflows, alerts	Flexible; no code; connects many tools	Per-transaction by default; poor payout matching; cost climbs at volume
Custom integration	Complex, high-volume, bespoke logic	Exactly your rules; full control; scales	Build cost; needs maintenance; only worth it past real complexity

Option 1: Native Stripe feed

Covered above. Cheap, quick and right for the common invoicing case. Test it with one real invoice and one refund before you trust it.

Option 2: Dedicated apps

For businesses taking payments outside Xero — Stripe-powered checkouts, subscription billing, e-commerce — a purpose-built connector groups Stripe activity by payout and posts a summarised journal or invoice into Xero. Each entry breaks out gross charges, Stripe fees, refunds and tax, and the total matches the bank deposit, so reconciliation becomes a one-click match.

The trade-off is a monthly fee that usually scales with volume, and a ceiling on how much custom logic you can apply. If your revenue recognition or tax rules are unusual, you may hit the edges. When evaluating any app, ask specifically how it handles payouts, fees, refunds and multi-currency — that's where cheaper tools fall down.

Option 3: Zapier or Make

Zapier and Make are excellent for lightweight automation, and both connect to Stripe and Xero. They suit specific jobs: drafting an invoice when a particular Stripe charge succeeds, posting a Slack alert on large payments, or handling an edge case the main tool misses.

Where they struggle is the core accounting job. Out of the box they fire one action per charge, which doesn't reconcile against batched payouts and recreates the very mess you're trying to avoid. You can build payout-aware logic in Make, but you're effectively rebuilding what a dedicated app already does — and at volume, task pricing adds up. Use them as glue, not as your primary ledger sync. We dig into this trade-off in our guide to Zapier vs Make vs custom integration.

Option 4: Custom integration

A custom build talks directly to the Stripe and Xero APIs, applying exactly your rules: how to summarise, which clearing accounts to use, how to map tax, and how to handle refunds and FX. More on when that's worth it below.

Reconciling Stripe fees: get this right first

The most common mistake is letting fees quietly eat into recorded revenue. They shouldn't. The correct treatment is:

• Sales recorded at the gross amount the customer paid.
• Stripe fees recorded as a separate expense (a "Stripe fees" or "merchant fees" account).
• The net payout clearing both against your bank.

If a £500 charge is recorded as roughly £493 of revenue because the fee was netted off, your turnover is understated and your VAT can be wrong. The native feed gets this right automatically for invoice payments; for every other flow, your chosen tool must post the fee explicitly.

Payout grouping: why your bank balance never matches a single sale

Stripe doesn't pay you per transaction. It batches charges, deducts fees and any refunds, and pays out the net a day or several days later. A single payout might cover dozens of charges, partial refunds and fees, all netted together.

So a clean setup has to reconstruct each payout. A robust pattern is a Stripe clearing account in Xero: charges and fees post to the clearing account, and the payout moves money from clearing to your bank. The clearing account balance at any moment is money earned but not yet paid out. If it drifts to a strange number, something is wrong — which makes it a useful early-warning signal.

VAT: the UK details that matter

• VAT is on the gross sale, not the net payout. Account for VAT on what the customer paid, before Stripe's fee. Recording only the net would understate your output VAT.
• Stripe fees and VAT. Stripe's UK card-processing fees are generally treated as exempt from VAT, as a payment service, so there's usually no input VAT to reclaim on them. Check the treatment shown on your own Stripe invoices and confirm it with your accountant.
• Refunds reverse VAT. A refund isn't just negative revenue — it reverses the output VAT on the original sale too. Make sure your setup handles this rather than recording refunds as a plain expense.
• Tax mapping. If you sell zero-rated, exempt or mixed-rate items, summarised entries must split by the correct Xero tax rate rather than lumping everything into standard-rated.

Multi-currency gotchas

If you charge in more than one currency, watch for these:

• Decide whether you record in the charge currency or your settlement currency, and be consistent. Mixing them creates phantom gains and losses.
• Stripe applies its own FX rate, which won't match Xero's daily rate. The difference is a real realised FX gain or loss and needs an account to land in, not to be ignored.
• Xero's multi-currency feature lives on its higher-tier plans. Your sync must feed it consistent currency and exchange-rate data, or revaluation will be off.
• The native feed is designed around a straightforward single-currency flow. Multi-currency Stripe activity is usually a strong signal to use a dedicated app or a custom build.

When is a custom integration worth it?

Off-the-shelf options cover the common cases well. A custom build earns its keep when you outgrow them. Signs it's time:

• High volume, where per-transaction app pricing hurts or summarisation needs to be smarter than standard tools allow.
• Payments across several places (website checkout, subscriptions, in-app) that must post consistently into one Xero file.
• Unusual revenue recognition — subscriptions, deposits, deferred revenue — that standard summaries can't express.
• Bespoke tax or multi-currency logic that no single connector maps correctly.
• Operational coupling — you want the same pipeline to also update a CRM, trigger fulfilment, or feed a reporting warehouse.

A custom integration talks to the Stripe and Xero APIs directly and writes clean, payout-matched entries on your exact rules. The cost is real — design, build and ongoing maintenance — so it makes sense once the cost of getting it wrong (misstated VAT, hours of manual reconciliation, revenue you can't see clearly) exceeds the build. As an indicative UK market guide, a focused Stripe-to-Xero integration commonly sits in the low-to-mid five figures depending on flows and complexity — treat that as a range to sanity-check quotes against, not a price.

There's often a sensible middle path: use a dedicated app for the standard flow, and add a small custom piece only for the edge case it can't handle. That pragmatic, vendor-neutral call is the kind of thing we help with in our API integration work.

A practical rollout checklist

1. Map your accounts first — sales, Stripe fees, refunds, FX and a Stripe clearing account — before connecting anything.
2. Pick the lightest method that fits — the native feed if you're paid on Xero invoices, a dedicated app if payments happen elsewhere.
3. Confirm fees post separately and revenue stays gross.
4. Check a payout reconciles to the penny against your bank line.
5. Test a refund end to end, including the VAT reversal.
6. Run a parallel month alongside your old process before you trust it fully.
7. Document the setup so your accountant and the next person can follow it.

How APIwise can help

Connecting Stripe to Xero is rarely the hard part — getting it to reconcile cleanly, with fees split out, VAT correct and payouts matching your bank to the penny, is. As the UK's API and AI integration specialists, we're vendor-neutral: if the native feed or a dedicated app is the right answer for you, that's exactly what we'll say. If your volume, payment flows or multi-currency needs genuinely call for a custom build, we'll scope and price it up front, fixed.

The simplest next step is our fixed-price Integration Health Check — we review how your systems connect today, find the gaps and risks, and give you a clear, costed plan, all as part of our API integration work. Book your Integration Health Check and make your Stripe-to-Xero reconciliation something you never have to think about again.