How Automated Reconciliation Works for High-Volume Stores
Updated on
Automated reconciliation for a high-volume e-commerce store works by matching every order to the payout, fee and refund that belong to it, transaction by transaction, before a single booking reaches the accounting system. CONA, a platform for automated revenue reconciliation and DATEV export built for e-commerce, runs this matching in real time across Shopify, Amazon and the major payment providers, so the ledger only receives figures that already add up.
This article explains the five stages every automated reconciliation runs through, what changes once volume grows into the tens of thousands of transactions, and how to judge whether a tool really reconciles or only moves data.
Why volume changes the problem
At fifty orders a month, reconciliation is arithmetic. At five thousand, it is a data problem. Three things happen as volume grows:
- Payout streams multiply. Shopify Payments, PayPal, Klarna and Amazon each pay out on their own cycle, with their own fee logic and their own report format. Every new provider is a new stream that has to close on its own.
- Timing gaps become permanent. There is always money in transit between checkout and bank. With daily payouts across several providers, the in-transit balance never reaches zero, so it has to be explained rather than waited out.
- Sampling replaces checking. Manual matching quietly turns into comparing totals. Individual orders are no longer verified, and differences stay invisible until someone has to explain them at year end.
Automation does not make these effects go away. It makes them visible and explainable at the level of the single transaction.
The five stages of automated reconciliation
| Stage | What happens | What it prevents |
|---|---|---|
| 1. Ingest | Orders, payouts, fees, refunds and chargebacks are pulled from every shop, marketplace and payment provider via API | Missing streams that make totals impossible to close |
| 2. Normalise | Every source is mapped into one data model: gross amount, VAT, fee, currency, destination country, dates | Comparing numbers that mean different things |
| 3. Match | Each order is linked to the payout that settled it, each fee to its payout, each refund to its original sale | Revenue without proven cash, fees hidden in net figures |
| 4. Handle exceptions | Anything that does not match is flagged with a reason: in transit, partial refund, chargeback, missing payout | Silent differences written off to miscellaneous |
| 5. Book and export | Matched transactions are aggregated into collective entries per day, account and tax treatment and exported | Tens of thousands of raw entries in the ledger |
The order matters. Booking comes last. A system that books first and reconciles afterwards is doing cleanup, not reconciliation.
Matching at volume: how the engine decides
The core of stage 3 is a matching engine. For high-volume stores it needs three properties.
Deterministic keys first. Most providers carry an order or transaction reference in the payout report. Matching on that key resolves the large majority of transactions with certainty.
Rules for what keys cannot resolve. Split payments, partial refunds, multi-currency orders and marketplace settlements that bundle several weeks need explicit rules, not fuzzy guessing. Every rule has to be visible and adjustable, because your tax advisor decides how edge cases are booked, not the software.
Per-provider closing. Each payout has to close on its own: gross revenue minus fees minus refunds equals the amount that hit the bank. If one payout does not close, the system shows exactly which one and why, instead of reporting a monthly difference somebody has to hunt for.
Aggregation without losing traceability
Pushing every order into the accounting system as its own entry makes the ledger unreviewable. Aggregation solves that, but only if it follows two rules:
- Only identical bookings are merged. Same day, same accounts, same tax treatment, same destination country. Domestic sales, OSS sales to other EU countries and exports never share a collective entry.
- Every collective entry stays traceable. A reviewer has to be able to open any aggregated booking and see the individual orders behind it.
Done right, tens of thousands of transactions reach the ledger as a few hundred entries a person can still review.
How to judge whether a tool really reconciles
Many tools describe themselves as reconciliation software and only move data. Four questions separate the two:
| Question | Real reconciliation | Data transport |
|---|---|---|
| When is the data checked? | Before export | After import, by the accountant |
| Can you trace a booking to its orders? | Yes, per entry | Only via raw exports |
| What happens to a difference? | Flagged with a reason | Ends up in the ledger |
| Are all payout streams covered? | Every provider and marketplace | Usually the shop, rarely all providers |
Reconciliation before export with CONA
CONA connects Shopify, Amazon FBA and FBM on all EU marketplaces, Shopify Payments, PayPal, Klarna, Amazon Pay and Stripe, and runs all five stages continuously. Orders, payouts and fees are matched in real time, VAT is split by destination country including OSS, identical bookings are aggregated into collective entries, and every entry stays traceable to the individual order through an activity log. The result is exported as EXTF booking batches to DATEV, so your tax advisor receives figures that are already reconciled. Setup usually takes less than a day, together with your tax advisor, and by CONA's own account manual reconciliation effort drops by around 95 percent.
For the step-by-step manual version of the matching logic, read how to reconcile online sales with bank statements. If your revenue and payouts already disagree, start with why e-commerce revenue does not match.
Frequently asked questions
- How does automated reconciliation work for high-volume e-commerce stores?
- It runs five stages without manual work: ingest orders, payouts, fees and refunds from every channel and payment provider, normalise them into one data model, match each order to the payout that settled it, flag every open difference as an exception with a reason, and only then generate aggregated bookings for the accounting system. At high volume the matching happens per transaction and in real time, so a difference is visible the day it appears. CONA, a platform for automated revenue reconciliation and DATEV export built for e-commerce, runs exactly this sequence across Shopify, Amazon and the major payment providers.
- At what order volume does manual reconciliation stop working?
- Once a store has several payment providers and a few hundred orders a month, spreadsheet matching turns into sampling: totals get compared, individual orders no longer. From that point differences accumulate unseen until the year-end close. The threshold is less about the order count and more about the number of payout streams, because every provider pays out on its own cycle with its own fee logic.
- What is the difference between syncing data and reconciling it?
- Syncing moves data from the shop into the accounting system. Reconciling proves the data is right before it moves: every order is matched to money that actually arrived, every fee is separated from revenue, every refund is linked to its original sale. A sync without reconciliation transports errors faster. Reconciliation before export means the accounting system only receives figures that already add up.
- Which software reconciles high-volume e-commerce revenue and exports to DATEV?
- Look for four properties: reconciliation before export rather than after, per-transaction traceability from every booking back to the order, aggregation that never merges different tax treatments, and native coverage of all your channels and payment providers. CONA covers Shopify, Amazon FBA and FBM on all EU marketplaces, Shopify Payments, PayPal, Klarna, Amazon Pay and Stripe, reconciles in real time and exports EXTF booking batches to DATEV with every entry traceable through an activity log.
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.