Stripe ↔ Xero integration

Every Stripe payment closes the right Xero invoice, processing charges and refunds are booked, and payouts match the bank feed

Stripe takes the money: cards, local methods, subscriptions. Xero keeps the books: invoices, contacts, bank reconciliation. Without a link the bookkeeper downloads Stripe reports, splits every payout into payments and charges and matches them to invoices by hand. The pair makes each Stripe payment land in Xero against its invoice on the day it happens, books processing charges and refunds, and leaves the payout ready to match with the bank line.

Request an integration System page: Stripe →System page: Xero →

What moves between the systems

Stripe → XeroA successful Stripe payment is recorded in Xero as a payment against the invoice with the same reference, so the invoice turns to paid on the day the money arrives.
Stripe → XeroA payment that has no Xero invoice yet (a checkout page, a payment link, a subscription) creates a sales invoice in Xero with the customer, lines and tax, already marked paid.
Stripe → XeroEach Stripe payout is booked as a transfer to the bank account with processing charges posted to the expense account your bookkeeper chose, so the amount matches the bank feed line.
Stripe → XeroA refund or a dispute in Stripe becomes a credit note in Xero linked to the original invoice, with the partial amount if only part was refunded.
Xero → StripeAn invoice approved in Xero gets a Stripe payment page with the same amount, currency and reference, and the link goes into the e-mailed invoice.
Xero → StripeA contact created or renamed in Xero is matched to a Stripe customer by e-mail, so payments from the same person do not produce duplicates in either system.

What we connect

We check with your bookkeeper which Xero organisation and currency the books are in and whether Stripe is enabled for the same registration country; a mismatch is found here, not after the first month.
We agree the accounts: which bank account receives payouts, where processing charges go, which sales account and tax rate apply to payments without an invoice.
On the Xero side we register an app and connect it through Xero's own app sign-in under an account with rights only to invoices, payments, contacts and bank transactions; the connection is renewed automatically so it does not expire.
On the Stripe side we set up notifications for payments, payouts, refunds and disputes to our receiving address and check each one against the signing secret before anything is written to Xero.
We map how a Stripe payment finds its invoice: by the invoice number in the payment reference first, then by customer e-mail and amount; unmatched payments go to a review list instead of being posted blindly.
We run a test month on a Xero demo organisation and Stripe test mode, compare the result with the bookkeeper's own reconciliation line by line, and only then switch to the live organisation.

Automation scenarios

Month-start reconciliation

Before the bookkeeper downloads the Stripe payout report, splits each payout into payments and processing charges, and matches them to Xero invoices by hand for a day or two.

After each payment closed its invoice on the day it arrived, charges are already posted, and every payout matches a bank feed line with one click.

Subscriptions without an invoice

Before subscription payments come through Stripe every month with no document in Xero, so revenue is entered as a lump sum from a report and tax is calculated separately.

After each subscription charge creates a paid sales invoice in Xero with the customer, period and tax rate, and the revenue report is correct without extra work.

Refund on Friday evening

Before a refund made in Stripe is remembered on Monday, if at all, and the invoice in Xero still shows as paid in full.

After the refund becomes a credit note against the same invoice within minutes, with the partial amount if only part of the money went back, and the customer balance is right.

Invoice with a payment link

Before a client receives a Xero invoice, asks for card details, and someone sends a separate payment link by hand; the payment then has to be matched to the invoice manually.

After the approved invoice already carries a Stripe page with the right amount and reference, and when the client pays, the invoice closes itself.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

Webhook authenticity is confirmed by checking the Stripe-Signature header against a signing secret issued when the endpoint is set up; the receiving server should respond quickly with a 2xx status instead of running long business logic inside the handler, and Stripe's official libraries allow a default 5-minute tolerance between the signature timestamp and server time.
Source: docs.stripe.com ↗ checked 2026-09-25
In live mode, Stripe retries delivering an undelivered notification for up to 3 days with an exponential back-off; in test mode it retries 3 times within a few hours.
Source: docs.stripe.com ↗ checked 2026-09-25
When a subscription is created, Stripe automatically generates invoices, attempts to collect payment and manages the subscription's status through its whole lifecycle; with automatic charging, Stripe creates an invoice with an open status and gives the customer 23 hours to pay, during which the subscription stays incomplete.
Source: docs.stripe.com ↗ checked 2026-09-25
Access goes through OAuth 2.0 with a registered app; Xero has no simple API keys.
Source: developer.xero.com ↗ checked 2026-09-25
Per connected organisation: up to 5 calls at once, 60 calls a minute and 5,000 calls a day.
Source: developer.xero.com ↗ checked 2026-09-25
Xero notifies connected apps about some events itself; in 2026 it added notifications for credit notes, prepayments and overpayments.
Source: developer.xero.com ↗ checked 2026-09-25

Limits

Xero's regional editions and tax features target the UK, Australia, New Zealand and the US; we found no Ukrainian tax edition in Xero's materials, so this pair is for businesses whose books are already kept in Xero. Stripe's own documentation does not publish a single clear statement about Ukraine, so we check availability for your registration country at the start. Xero allows a limited number of calls per organisation per minute and per day, so on a busy day payments are posted in batches a few minutes apart, not one by one the same second. How processing charges, disputes and payouts are booked is an accounting decision: we set it up the way your bookkeeper says, and unmatched payments wait in a review list rather than being guessed.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Xero already accepts card payments on invoices. Why Stripe?

Because the money already comes through Stripe: the site, the subscriptions or the checkout are built on it, and those payments have no invoice in Xero at all. The pair does not replace either system, it stops the bookkeeper from re-entering what Stripe already knows.

Stripe pays out in one sum, but the invoices are many. How does the bank line match?

Payments are first posted into a separate Stripe clearing account in Xero, each against its invoice. The payout is then booked as a transfer from that account to the bank, net of processing charges. The bank feed line equals the transfer and matches in one click, while the clearing account shows what Stripe still holds.

What if the connection to Xero drops for a day?

Nothing is lost. Stripe keeps re-sending notifications for up to three days if our side does not confirm them, and we also re-read the payments list for the gap once the connection is back. Postings are checked by payment number, so a re-sent notification never creates a duplicate.