Skip to main content
All Articles
POSAug 27, 2026

How to reconcile Stripe payouts with your sales records

To reconcile Stripe payouts with your sales records, work in two steps. First, match the amount that lands in your bank to the balance transactions Stripe included in that payout: payments, refunds, disputes, fees and adjustments. Then match those payments to the orders, bookings and invoices in your POS or booking system. A payout is a net figure that follows Stripe's settlement timing, so it seldom equals a single day's sales report.

For automatic payouts, Stripe's reports and API handle the first step. The second depends on how well your sales system and your payment records share references.

Why doesn't my Stripe payout match my sales?

  • Fees come off before the money reaches you, so a payout is net of processing fees.
  • Settlement takes time. Stripe's default for UK accounts is three business days, and payouts due on a weekend or bank holiday arrive the next business day.
  • Refunds and disputes are deducted when they happen, often in a later payout than the original sale.
  • Cash, house accounts, and voucher or gift card redemptions appear in your sales report but never pass through Stripe.
  • Payments forwarded after an internet outage are processed later than the sales they belong to.
  • If you run several connected accounts or legal entities, each has its own payouts.

What is a Stripe balance transaction?

Stripe creates a balance transaction for every movement of funds into or out of your Stripe balance. Card payments, refunds, payouts and some Stripe fees each have one, recording a gross amount, a fee and a net amount; the processing fee on a card payment sits on that payment's own balance transaction. Automatic payouts are the easiest to reconcile, because Stripe records which balance transactions each one contains.

Manual and Instant Payouts work differently. You choose their timing and amount, so Stripe cannot say which transactions they include, and reconciling them against your transaction history is your job.

If you reconcile through the API, pass the payout ID to the request that lists balance transactions and Stripe returns only the transactions in that payout. Stripe also sends a payout.reconciliation_completed webhook event, which a finance system can use to start matching automatically.

Stripe's payout reconciliation report covers automatic payouts and groups the transactions in each one by reporting category, such as charges, refunds and fees. Its itemised download lists every transaction with gross, fee and net amounts, and you can include custom metadata, such as an order reference, to match transactions to your own records.

How do you reconcile a Stripe payout step by step?

  • Start from the bank statement. Note the payout amount and date, then find the matching payout in Stripe.
  • List the balance transactions in that payout from the Dashboard, the itemised report or the API.
  • Check the arithmetic: gross payments, minus fees, refunds, disputes and other adjustments, should equal the payout.
  • Match each payment to an order or booking using a shared reference, such as an order ID stored in the payment's metadata.
  • Investigate what is left: refunds against older sales, disputes, payments without an order, and card sales in your POS that have not settled yet.
  • Post the result to your accounts, recording sales at gross and fees as a cost, so the payout clears your Stripe clearing account.

Here is a hypothetical payout broken down by reporting category, with net equal to gross minus fees:

Reporting categoryGrossFeeNet
Charges£5,000.00£97.60£4,902.40
Refunds-£90.00£0.00-£90.00
Total paid out£4,910.00£97.60£4,812.40

The £4,812.40 in the bank is £5,000 of card sales, less £97.60 of fees and a £90 refund for an earlier sale. A sales report for the same period can show a higher figure because it includes cash and vouchers that never pass through Stripe.

How should Stripe payouts appear in your accounts?

A Stripe clearing account keeps the books tidy. Post card sales to it at their gross value, post Stripe fees out of it as a cost, and post refunds and disputes against it when they happen. Each payout then moves money from the clearing account to your bank account. At any point, the balance left on the clearing account should equal the funds Stripe is holding for you that have not yet been paid out, so a difference tells you something is missing.

Recording fees separately also shows what card acceptance costs you each month, which a net payout figure hides. Reconcile payouts at least weekly. A short list of unexplained items is easy to clear, and a dispute or an unmatched refund is much easier to trace a few days after it happens than at the month-end close.

How does Tiquo help with payout reconciliation?

In Tiquo, card payments are processed through Stripe and each payment stays linked to the order or booking it belongs to, so the second step of the method above starts from records that already share a reference. The Payments area in Tiquo's settings embeds the connected Stripe account's balances, payouts and disputes, so finance staff can look up a payout without leaving Tiquo.

For the files your accountant needs, Tiquo's Import & Export page includes Stripe payment and accounting exports for connected payment accounts. Order exports can list one row per order or one row per item sold, which covers the cash, voucher and free orders that never reach a payout, and the end-of-day export gives one summary row per trading day for a sublocation. Tiquo's integrations directory lists accounting tools including Xero, QuickBooks and Sage.

© 2026 Tiquo. "Tiquo" and the Tiquo logo are registered trademarks of Tiquo Ltd.

GDPR · CCPA · PCI DSS · ICO · Cyber Essentials Certified · EU–US DPF · SOC 2 Type II (in progress) · ISO 27001 (in progress)

Security & Operational

  • 99.99% SLA Uptime
  • AES-256 encryption at rest
  • TLS 1.3 in transit
  • AES-256 / TLS 1.3
  • Perfect Forward Secrecy (PFS)
  • HTTP Strict Transport Security (HSTS)
  • 99.999999999% (11 nines) data durability
  • Automated backups
  • DDoS protection
  • Web Application Firewall (WAF)
  • Zero Trust posture
  • Role-Based Access Control (RBAC)
  • Principle of Least Privilege
  • Secret scanning in CI
  • SBOM generation
  • Dependency supply-chain controls
  • 24/7 infrastructure monitoring
  • GDPR Article 22 safeguards
  • Data Protection Impact Assessments (DPIAs)
  • Records of Processing Activities (ROPA)
  • SAML 2.0 SSO
  • EASIE SSO
  • OAuth 2.0 / OpenID Connect (OIDC)
  • SCIM 2.0 provisioning
  • MFA / 2FA enforcement
  • Responsible disclosure / bug bounty programme

Privacy, Data Protection & Statutory Obligations

  • ICO Registered
  • UK Modern Slavery Act 2015 compliant
  • UK Public Interest Disclosure Act 1998 compliant
  • EU Article 27 Representative appointed (Paris, France)
  • Swiss FADP Article 14 Representative appointed
  • UK GDPR compliant
  • EU GDPR/DSGVO compliant
  • UK Data Protection Act 2018 compliant
  • Swiss revFADP compliant
  • CCPA / CPRA compliant (California)
  • VCDPA compliant (Virginia)
  • CPA compliant (Colorado)
  • CTDPA compliant (Connecticut)
  • TDPSA compliant (Texas)
  • OCPA compliant (Oregon)
  • MCDPA compliant (Montana)
  • FDBR compliant (Florida)
  • ICDPA compliant (Iowa)
  • ICDPA compliant (Indiana)
  • TIPA compliant (Tennessee)
  • DPDPA compliant (Delaware)
  • NJDPA compliant (New Jersey)
  • NHDPA compliant (New Hampshire)
  • NDPA compliant (Nebraska)
  • MCDPA compliant (Minnesota)
  • MODPA compliant (Maryland)
  • KCDPA compliant (Kentucky)
  • RIDTPPA compliant (Rhode Island)
  • Canada PIPEDA compliant
  • Quebec Law 25 compliant
  • Alberta PIPA compliant
  • British Columbia PIPA compliant
  • Singapore PDPA compliant
  • Hong Kong PDPO compliant
  • Brazil LGPD compliant
  • Japan APPI compliant
  • Australia Privacy Act / APPs compliant
  • India DPDPA 2023 compliant
  • Thailand PDPA compliant
  • Malaysia PDPA 2010 (as amended 2024) compliant
  • New Zealand Privacy Act 2020 compliant
  • South Africa POPIA compliant
  • UAE PDPL compliant
  • Mexico LFPDPPP compliant
  • Kenya Data Protection Act 2019 compliant
  • Ghana Data Protection Act 2012 compliant
  • Nigeria NDPA 2023 compliant
  • Indonesia PDP Law 2022 compliant
  • Philippines Data Privacy Act 2012 compliant

Global Fiscal & E-Invoicing

  • EN 16931 - EU e-invoicing core standard
  • UBL 2.1 - Universal Business Language
  • Austria - RKSV
  • Belgium - Peppol BIS 3.0 (B2B)
  • Czechia - fiscalization
  • Croatia - Fiscalization 2.0
  • Denmark - Peppol BIS 3.0 (B2B)
  • France - NF525 / LNE / Infocert, Factur-X / PDP, E-Reporting
  • Germany - KassenSichV / TSE, DSFinV-K, GoBD, E-Rechnung B2B (XRechnung / ZUGFeRD)
  • Hungary - Online Szamla
  • Italy - Scontrino, FatturaPA (via SDI)
  • Lithuania - i.SAF / i.MAS
  • Norway - Peppol BIS 3.0 (B2B), SAF-T
  • Poland - KSeF
  • Portugal - ATCUD/QR, SAF-T PT
  • Slovakia - eKasa
  • Slovenia - fiscalization (davcno potrjevanje)
  • Spain - FacturaE, SII, VeriFactu, TicketBAI
  • Sweden - SKVFS (certified cash registers)
  • Argentina - ARCA (Q4 2026)
  • Australia - Peppol PINT A-NZ (Q4 2026)
  • Brazil - NFe, NFCe, NFSe (Q4 2026)
  • Chile - SII Chile (Q4 2026)
  • Colombia - DIAN (Q4 2026)
  • Finland - Finvoice, TEAPPSXML (Q4 2026)
  • Japan - JP PINT (Peppol) (Q3 2026)
  • Malaysia - Peppol Malaysia (Q4 2026)
  • Mexico - CFDI (Q4 2026)
  • New Zealand - Peppol PINT A-NZ (Q4 2026)
  • Peru - SUNAT (Q4 2026)
  • Romania - Peppol (RO e-invoice) (Q4 2026)
  • Saudi Arabia - ZATCA (Q4 2026)
  • Singapore - Peppol BIS 3.0 (Q4 2026)
  • United Arab Emirates - Peppol (5C) (Q4 2026)

Standards & Frameworks

  • Cyber Essentials Certified
  • SOC 2 Type II - audit in progress
  • ISO/IEC 27001 - audit in progress
  • NIST Cybersecurity Framework - aligned
  • NIST Privacy Framework - aligned
  • NIST SP 800-53 / 800-63 / 800-63B - aligned
  • NIST AI Risk Management Framework - aligned
  • CIS Critical Security Controls / CIS Benchmarks - aligned
  • OWASP ASVS & OWASP Top Ten - aligned
  • ISO 25010 (quality) - aligned
  • ISO 31000 (risk) - aligned
  • ITIL - aligned
  • W3C Web Standards - aligned
  • OpenAPI Standard - aligned
  • DevSecOps practices - aligned
  • ePrivacy Directive - aligned
  • EU Whistleblowing Directive (2019/1937) - aligned

Payments Compliance

  • PCI DSS Level 1
  • PSD2 / Strong Customer Authentication
  • 3D Secure (3DS)
  • EMVCo Level 1 & 2
  • AML / KYC controls
  • Sanctions screening (OFAC, UN, EU, HMT)

International Data Transfer Mechanisms

  • EU-US Data Privacy Framework
  • EU Standard Contractual Clauses (Decision 2021/914) - Modules 2 & 3
  • UK International Data Transfer Agreement (IDTA) + ICO Addendum
  • Swiss FDPIC-recognised transfer mechanisms
  • APEC Cross-Border Privacy Rules (CBPR)

Accessibility Compliance

  • ADA (Americans with Disabilities Act) - aligned
  • European Accessibility Act (EAA) 2025 - aligned
  • WCAG 2.2 - aligned
  • EN 301 549 - aligned
  • WAI-ARIA - aligned

A single platform for hotels, spas, classes, events, restaurants, and more.

Tiquo Ltd
London, UK

LinkedInTop Performer Spring

We use cookies

Choose whether to allow cookies for analytics and advertising. You can accept or decline them. Closing this notice declines them.

Learn more