Stripe Direct Debit, Xero, QuickBooks and Sage: a UK finance integration map

For two and a half years we have been building a UK telecom billing and revenue-assurance platform that collects by card and Direct Debit through Stripe, syncs to Xero, QuickBooks Online and Sage Accounting, and produces a daily journal file for Sage 50 and 200. Most of our work is delivered under NDA, so many projects cannot be named. So the client stays unnamed, and the vendor facts below come from public documentation you can check.

Note that “Sage” covers different products. Sage Accounting is a cloud service with a REST API. Sage 50 and 200 are products usually found on a local or hosted server, and they are integrated differently. Confirm the exact product and edition with the customer’s finance team before you estimate anything.

Most finance integration problems start here: two systems both think they own a record. Write this table for your project and get finance to sign it before anyone writes code.

The most common reconciliation mistake is treating money arriving in the bank as a single customer payment. Stripe automatic payouts bundle many transactions, net of refunds, fees and disputes. Here is a made-up example, for the arithmetic only:

The usual pattern is a clearing account for Stripe in your books. Payments and fees post to it, the payout moves the balance to the bank, and that account should return to zero, apart from timing. Stripe’s payout reconciliation guide gives the mechanism for automatic payouts: listen for payout.reconciliation_completed, then list balance transactions filtered by that payout. Stripe can’t do this for manual payouts, so stick with automatic ones if you can.

Your own system also has to record what Stripe can’t know: which invoices a single charge paid. The platform we built for a UK client handles part payments and one charge covering several invoices. That needs an allocation table of its own, with the rule for what gets paid first agreed with finance. See the Stripe Bacs guide for how pending states and failures fit in.

1. Every sync must be safe to repeat. Store the other system’s ID against each of your records, and check before creating. Timeouts happen after the other side has acted, so a blind retry creates a duplicate invoice.
2. Use a queue, one connection at a time. Xero allows 5 concurrent calls and 60 a minute per organisation. Throttle per connection, not globally, so one large customer doesn’t use up everyone’s time. Read the response headers instead of guessing.
3. Failures go to a person who can act. “Tax code missing for product X” should reach finance in plain language, with a retry button. A log file that only developers read means finance finds out at month end.
4. Mapping is data, not code. Ledger and tax codes differ per customer and change over time, so keep them in a table that finance can see, with a safe default of stopping when a code is unmapped.
5. Post once, then correct. Don’t edit what has been posted. Send a credit note or a reversal, and the trail remains clear.
6. Check balances every night. The platform we built for a UK client runs nightly balance checks and has a month-end checklist. A difference found the next morning is one day’s entries to search. A difference found in the year-end audit is much harder.
7. Plan for lost connections. Accounting connections expire or get revoked when someone leaves the company. Detect it, stop posting, keep the queue, and ask a named person to reconnect.

Cards tell you the result straight away, but Bacs doesn’t. Stripe takes 4 business days to confirm a payment on an existing mandate, and 7 with a new one. So a receipt can spend a week in a pending state, and that state has to be represented somewhere finance can see. Don’t post it as received too early, or your customer balances will be overstated, and your credit controller will stop chasing someone whose payment later fails.

The harder case comes later. A bank can reverse a Bacs payment as a dispute, with no time limit for the customer to file and no appeal for you. That reversal may land in a period you have already closed, so decide in advance how it posts: usually dated today and clearly linked to the original invoice, which goes back to unpaid. Have your accountant agree this before go-live, since it will happen on a day when nobody remembers the design.

If you sell software to many businesses, each connects their own Stripe, Xero or QuickBooks account. That adds four jobs. Tokens must be encrypted and stored per customer. Limits count per connection, so one customer’s bulk import must not delay another’s. Xero also limits connections by your app’s tier, with Starter capped at 5 and Core at 50, so check the current tier table and its fees before you set your prices. Finally, customers arrive with history, so migrating opening balances needs its own tool and sign-off.

• Stripe: a sandbox with test bank accounts for success, insufficient funds, cancelled mandates and disputes. Use the three-minute delayed ones, which behave more like real life.
• QuickBooks: Intuit provides a sandbox company, with the same throttling figures as production.
• Xero: a demo company, so you can post freely without touching real books.
• Sage 50: a test company or a backup, and your accountant’s eye on the import result before it goes near live data.
• Your own suite: keep sample API responses, including failures, so the rules above run on every change. The automated suite on the platform we built for a UK client runs on every change, for this reason.

Then have finance reconcile one complete test month by hand. If it won’t reconcile on paper, it won’t reconcile in production.

A finance integration quote is only as good as the answers behind it. Get these from the people who run the numbers, not just from whoever manages the software. If you are briefing a supplier, send them this list with your answers filled in.

The most valuable answer is often the last one. A sync with a named owner and a short daily list of exceptions stays healthy. One where failures go to a shared inbox gets switched off a year later, when people stop trusting it.

Our integration service covers these and other business systems. Detailed notes: what to sync with Xero and the Sage 50 journal file.