The Stripe Reconciliation Problem Every UK Business Ignores

If your business accepts card payments through Stripe, there is a good chance your accounts are wrong. Not dramatically wrong — but subtly, persistently wrong in a way that compounds over time and can cause real problems when HMRC comes knocking or when you try to reconcile your year-end accounts.

The root of the problem is simple: Stripe does not send you the money your customers pay. It sends you the money your customers pay, minus its fees, batched together across multiple transactions, deposited days later. And most accounting software — including Xero, QuickBooks, and FreeAgent — has no native way to handle this correctly.

The Three-Way Split

When a customer pays you £100 through Stripe, three things happen financially:

1. Gross revenue of £100 — this is what your customer paid and what should appear on your invoice and in your sales ledger
2. Stripe fee of approximately £2.20 (1.4% + 20p for UK cards) — this is a business expense that should be recorded in your profit and loss account
3. Net deposit of £97.80 — this is what actually arrives in your bank account, usually 2-7 days later, often batched with other transactions

If you simply match the bank deposit to the invoice, you are understating your revenue by the fee amount and not recording the expense at all. Over a year of trading, this can mean thousands of pounds of unrecorded expenses and understated turnover. Your profit figure might end up roughly correct by accident, but your financial statements are wrong — and that matters for VAT, Corporation Tax, and any due diligence.

Why Batched Payouts Make It Worse

Stripe does not pay out each charge individually. By default, it batches all charges from a rolling period and sends a single payout to your bank. A typical payout might contain 15 charges, 2 refunds, and the associated fees — all netted into one bank deposit. Trying to match this single deposit against 15 individual invoices manually is a nightmare.

Many businesses give up and simply record the payout as miscellaneous income or dump it into a suspense account. Others create a single "Stripe sales" invoice for the payout amount, which destroys the link between individual customer payments and their invoices. Both approaches make VAT reporting unreliable and bank reconciliation a guessing game.

The VAT Complication

For VAT-registered businesses, getting this wrong has direct tax consequences. Your VAT return should be based on the gross invoice amounts, not the net bank deposits. If you are reporting VAT based on bank deposits, you are under-reporting your output VAT. HMRC can (and does) identify this discrepancy during VAT inspections.

Additionally, Stripe processing fees are a supply from Stripe (an Irish entity for EU/UK merchants). This means the fee is subject to reverse charge VAT — you need to account for VAT on the fee and reclaim it simultaneously. Most businesses simply ignore this, but it should appear in Box 1 and Box 4 of your VAT return.

How Businesses Currently Cope

The most common approaches we see are:

• Ignore the problem — match bank deposits to invoices and accept the discrepancy. This is the most common approach and the least correct.
• Manual journal entries — create monthly journal entries to account for Stripe fees based on downloaded Stripe reports. Better, but time-consuming and error-prone.
• Third-party sync apps — use tools like Stripe’s Xero integration or third-party connectors. These vary in quality, often create duplicate entries, and rarely handle the three-way split correctly.
• Accountant fixes at year-end — leave it messy all year and let the accountant sort it out. Expensive, reactive, and means your management accounts are unreliable throughout the year.

The TaxStats Approach: Automatic Three-Way Reconciliation

TaxStats connects directly to your Stripe account via the Stripe API. When a charge is received, we automatically:

1. Record the gross amount against the matched sales invoice, debiting Trade Debtors and crediting Sales
2. Record the Stripe fee as a business expense, debiting Stripe Fees and crediting Trade Debtors
3. Track the net amount due from Stripe, holding it in a Stripe Settlement account until the payout arrives
4. Match the payout to the bank deposit when it arrives, clearing the settlement account

This means your revenue is always stated at the correct gross amount, your Stripe fees are recorded as they occur (not estimated at year-end), your bank reconciliation works because you are matching the actual payout amount, and your VAT return includes the correct figures for both output tax and the reverse charge on Stripe fees.

Handling Refunds and Disputes

Refunds add another layer of complexity. When you refund a customer through Stripe, the refund amount is deducted from your next payout — meaning the bank deposit is reduced but there is no separate bank transaction for the refund. TaxStats handles this automatically by creating reversal entries when a refund is processed, adjusting the settlement account, and ensuring the reduced payout still reconciles correctly.

Disputes (chargebacks) are handled similarly. When a dispute is opened, the charge is flagged and the disputed amount is held back from payouts. When a dispute is resolved — whether in your favour or the customer’s — TaxStats creates the appropriate accounting entries.

What You Should Do Now

If you are a UK business accepting Stripe payments, review your current accounting process. Ask yourself:

• Are your sales invoices recorded at the gross amount the customer paid?
• Are Stripe fees recorded as a business expense?
• Can you reconcile each Stripe payout to your bank statement?
• Is your VAT return based on invoice amounts, not bank deposits?

If you answered no to any of these, your Stripe accounting needs attention. TaxStats automates the entire process — connect your Stripe account, and we handle the rest. No manual journals, no third-party sync apps, no year-end cleanup. Just accurate, real-time accounting from day one.