How to Reconcile Online Sales With Bank Statements
Updated on
To reconcile online sales with bank statements, stop comparing the two directly. There is a layer in between, the provider payout, and that is where reconciliation actually happens. Your shop reports gross revenue at checkout; your bank shows a net payout days later; the payout report is the only document that explains how one became the other.
This article gives you the step-by-step process per payment provider, the clearing account setup that makes it close, and the point at which it makes sense to automate.
The three-layer model
Every reconciliation problem in e-commerce becomes tractable once you stop treating it as two numbers and start treating it as three layers.
| Layer | What it records | When |
|---|---|---|
| Orders | Gross revenue per order, including VAT, before any deduction | At checkout |
| Payouts | Batches of orders, net of fees, refunds and chargebacks | Days later, on the provider cycle |
| Bank | The net amount actually received | On value date |
Reconciliation is two matches, not one: orders to payout, then payout to bank. Almost everyone attempts the shortcut of orders to bank, which cannot work, because the deductions that happen in the middle layer are invisible from either end.
The process, per payment provider
Do this separately for each provider. Shopify Payments, PayPal, Klarna and Amazon Pay run their own cycles, formats and fee logic, and combining them before reconciling is the fastest way to lose the thread.
- Pull the payout report at payout level. Individual payouts, not a monthly summary. The summary hides exactly the detail you need.
- Decompose each payout. Gross revenue of the included orders, minus fees, minus refunds and chargebacks, equals the net amount. This must balance exactly for each payout. If it does not, the missing piece is nearly always a fee type you have not accounted for or a reserve the provider withheld.
- Match the net amount to the bank entry. By amount and value date. Across a month end, this step determines which period the revenue belongs to, which is a decision, not a rounding issue.
- Move unpaid-out orders to the clearing account. Orders paid by the customer but not yet paid out to you sit here. This is the structural reason shop revenue and bank deposits never match at month end.
- Book the fees as expense. Each fee type with its own classification and input VAT treatment. Fees netted off inside a payout and never booked separately are the most expensive single error in e-commerce accounting, because you lose both the expense and its input VAT deduction.
- Name every residual difference. A fee, a chargeback, a reserve, a timing effect. If a residual has no name, it is not reconciled, and writing it off to miscellaneous expense destroys the only signal that something upstream is wrong.
The clearing account, in practice
This is the piece most manual setups are missing, and adding it resolves a surprising share of what looked like chaos.
When a customer pays, the money is yours economically but is not in your bank yet. Book the gross order value against a clearing account rather than straight to the bank. When the payout arrives, clear the relevant orders out of that account, book the fees as expense, and post the net amount to the bank.
The balance on that account at any moment is money in transit: paid by customers, not yet paid out to you. At month end this balance should equal the sum of orders paid but not yet settled. If it does, your reconciliation closes. If it drifts upward month over month, something is being booked into the account and never cleared out, which is a specific, findable problem rather than a vague mismatch.
Where returns and chargebacks break the pattern
Two cases do not follow the clean flow above, and both need explicit handling.
Returns and refunds reduce a later payout, not the original one. The correction has to carry the tax treatment and destination country of the original sale, not of the payout it happens to be netted against. Getting this wrong shifts your VAT base quietly, and it only surfaces at filing.
Chargebacks arrive weeks after the sale, with their own fee, and sometimes after the original payout has long been reconciled. They need to be matched back to the original order rather than treated as a fresh negative transaction, otherwise the original sale stays overstated and the difference sits in your books indefinitely.
For marketplace payouts the same logic applies with more components. Amazon in particular nets commissions, fulfilment fees, advertising costs, refunds and security reserves out of a single fortnightly transfer, which means the gross revenue has to be reconstructed before anything can be booked.
When to automate
Below roughly 100 orders a month through one dominant payment method, the manual process is genuinely fine. A few hours monthly and a clean spreadsheet will hold, and there is no reason to buy anything.
The threshold is an effort number, not a revenue number. Once monthly reconciliation costs more than a working day, or a month-end difference can no longer be explained, the volume has outgrown the method. Multiple payment providers pull that threshold sharply lower, because each one adds a full parallel reconciliation track rather than incremental work.
What automation should take over is precisely the six steps above: pulling payout reports, decomposing them, matching to orders, maintaining the clearing account, classifying fees, and flagging residuals. What it must not do is skip straight to producing bookings from raw data, which relocates the problem into your accounting system instead of solving it.
CONA automates that sequence and keeps the order of operations intact: reconcile first, export second. Orders, payments, fees, returns and VAT are reconciled in real time, identical bookings are aggregated into collective entries so the accounting system receives a few hundred entries rather than tens of thousands, and each one remains traceable back to the individual order through an activity log. Pricing is public and usage based, from 19.99 euros per month plus VAT with all features in every tier, and the first month is free without a credit card.
If your numbers are currently not matching and you want to understand why before changing anything, start with Why your e-commerce revenue does not match. To compare the tooling categories, see Accounting automation software for e-commerce in Germany. More guides are in the knowledge hub, and you can walk the full path from order to booking with your own data in a free demo.
Frequently asked questions
- How do I reconcile online sales with bank statements?
- Never compare shop revenue directly to bank deposits. Work through the payout layer in between: pull each provider payout report, break every payout into gross revenue, fees, refunds and chargebacks, match the resulting net figure to the bank entry by date and amount, and hold orders that are paid but not yet paid out on a clearing account. Do this per payment provider, because each pays out on its own cycle. The arithmetic has to close per payout, not approximately across the month.
- What is a clearing account and why do I need one?
- A clearing account holds the value of orders that customers have paid but the provider has not yet paid out to you. Without it, shop revenue and bank deposits can never agree at month end, because there is always money in transit. With it, the gap becomes a number you can point at and explain. This single account resolves most of what looks like an unexplained difference in an online store, and it is the first thing to set up before automating anything.
- How do I streamline e-commerce accounting reconciliation?
- Three levers, in order of impact. Reconcile at payout level rather than monthly totals, because only payout level lets you trace a difference to a cause. Reconcile before data enters the accounting system rather than after, because raw data is never cleaned up later. And aggregate identical bookings so the accounting system receives a few hundred entries instead of tens of thousands. Everything else is optimisation on top of those three.
- What are best practices for the e-commerce financial close?
- Close monthly rather than annually, reconcile per payment provider, keep every open item on a clearing account with a documented reason, and split VAT by destination country before the close rather than after. Never write a residual difference off to miscellaneous expense: it removes the only signal that something upstream is broken. If a month cannot be closed within a few days, the problem is almost always data quality, not the schedule.
- Can I automate the reconciliation of sales and bank statements?
- Yes, and this is the part worth automating first. Reconciliation software pulls the payout reports itself, decomposes each payout into its components, matches them against the underlying orders and only then produces bookings. CONA does this in real time across Shopify, Amazon FBA and FBM on all EU marketplaces, plus Shopify Payments, PayPal, Klarna and Amazon Pay, and every resulting entry stays traceable to the individual order.
- How do I automate expense tracking for an online store?
- Start with the expenses that are already inside your payouts, because those are the ones most often missed entirely: payment fees, marketplace commissions, fulfilment fees and advertising costs netted off before the money arrives. Automating these means having each fee type extracted from the payout, classified consistently and booked as expense with its input VAT, rather than disappearing into a net figure. Card and invoice expenses outside the payout flow are the easier half of the problem.
Want reconciliation and DATEV export automated?
CONA reconciles orders, payments, fees and VAT from Shopify in real time, then exports clean, aggregated booking batches to DATEV. Every entry stays traceable down to the individual order, no black box. Setup in under a day, first month free, no credit card required. Book a 15 minute demo.