One sale, several payments, several deposits
A shop with a card terminal has one processor paying one account. An online store has several providers paying you for the same baskets, each on a different cycle, each deducting a different fee.
So the revenue figure in your store dashboard is never the figure in your bank, and it is never wrong for only one reason. It is wrong for five reasons at once, spread across four deposits that arrived on four different days.
That is the specific problem this page is about. If you are reconciling one bank account or a set of card terminals, the bank reconciliation and POS reconciliation pages cover those directly.
Ese es justamente el problema que trata esta página. Si estás conciliando una sola cuenta bancaria o un conjunto de terminales de pago, las páginas de conciliación bancaria y conciliación de POS cubren cada una de esas situaciones directamente.
A shop with a card terminal
One processor, paying one account, on one schedule. There is a single relationship to check.
A single bank account
One statement against one ledger. The differences are timing, and they clear on their own.
An online store
Several providers paying you for the same orders, each on its own cycle, each deducting a different fee. Nothing lines up on its own.
Signs your store has outgrown reconciling by hand
Most finance teams do not decide to fix this. They notice one of these and realise it has been true for months.
You cannot say today how much of last month's sales actually reached the bank.
A payout went missing and you heard about it from your accountant, not from your own dashboard.
January payouts looked wrong after the Christmas rush and nobody could say exactly why.
Nobody checks the fee on a payout against the rate you agreed, because nobody has time to.
Someone spends the first week of every month working out what happened in the last one.
A refund was taken off twice and it took a quarter before anyone noticed.
If two or three of those are true, the issue is not that your team is careless. It is that the volume passed the point where a person can check it line by line, and nothing told you when that happened.
What ecommerce teams get with LedgerMatch
Built for online stores where the money for one order arrives from more than one place.
Rules that understand how stores get paid
Batched payouts, settlement lag by provider, returns landing weeks later, and a basket split across a gift card. The assistant proposes the rules from your own order data and nothing runs until your team approves them.
Every checkout option in one place
Card, wallet, buy now pay later and marketplace payouts reported together, so you read one picture instead of logging into four provider dashboards.
Exceptions that name the order behind them
Each payout that did not match comes back with the reason and the order, return or chargeback behind it, so you are not searching three dashboards to find out which basket caused it.
Daily matching instead of monthly
Order and payout data arrives on its own, so matching can run every night. During peak, the week is reconciled as it trades rather than becoming a backlog for January.
Read only on both sides
LedgerMatch can see transactions and holds no permission to move money, and nothing is written to your accounting software.
An audit package in one click
Reconciliation, summary, exceptions and adjustments, with every figure tracing back to an order or a bank line rather than starting inside the report.
The kinds of ecommerce stores this is built for
If more than one thing pays you, or you sell in more than one place, this is where reconciliation stops being a spreadsheet job.
Direct to consumer brands
One storefront, but card, wallet and buy now pay later all paying separately. Growth makes it worse, because every new checkout option adds another payout cycle to follow.
Stores selling on more than one channel
Your own site plus a marketplace, each with its own payout schedule, its own fee structure and its own way of describing the same order.
Subscription and repeat purchase stores
Renewals, failed payments and retries mean the same customer can produce three attempts and one payment. Volume is predictable, the money arriving is not.
Stores with a heavy peak season
A few weeks of trading that produce months of reconciliation afterwards, with returns from the peak still landing well into the new year.
Most stores start looking at this after one of these moments
Six reasons your store's sales report does not match your bank
None of these are mistakes. They are how online checkout and settlement work. The problem is that all six happen at once, on the same day's orders.
Each method pays on its own clock
Cards in two days, a wallet in three, buy now pay later in a week. A single day of trading on your storefront turns into several deposits.
Fees come out before the money moves
What reaches the account is already net, and it is a different amount for every provider you use.
One deposit covers hundreds of orders
Providers batch. One credit can cover a whole weekend of trading across every SKU you sell, which is why the amount alone never identifies it.
Refunds come out of a later payout
A refund on last Tuesday's order is netted out of next Friday's deposit, so a payout is short for something that happened weeks ago.
Chargebacks arrive long after the sale
The money is taken back weeks later, often with its own fee, and rarely with a reference pointing to the original order.
An order is not a payment
Authorised at checkout, captured on dispatch, part shipped, or split across a gift card. Only some of those ever become money in your account.
What one day of online sales looks like by the time it reaches your bank
A store takes $10,000 across 214 orders on a Monday. Here is what the bank actually shows over the following week.
$10,000
$6,214
Less $186 in fees
Menos $186 en comisiones
$2,039
Less $61 in fees
Menos $61 en comisiones
$268
Less $12 in fees and a $120 refund
Menos $12 en comisiones y un reembolso de $120
$1,034
Less $66 in fees
Menos $66 en comisiones
$9,555
By hand, that means opening four provider reports next to a bank statement and working out which deposit covers which orders. With LedgerMatch, all four are matched and the only thing that reaches you is the refund that needs a credit note.
The money that goes missing and nobody looks for
Reconciliation is usually sold as saving time. For an online store the bigger cost is the money that quietly never arrives, because the only way to spot it is to compare every payout against the orders behind it.
Fees higher than the rate you agreed
Rates change, tiers shift, and a transaction can be priced differently from how you expected it to be.
Invisible because the payout still arrives. It is just slightly smaller than it should have been, every single day.
Invisible porque el pago sigue llegando. Simplemente es un poco más pequeño de lo que debería ser, todos los días.
Payouts that never arrived at all
A settlement is issued, something fails on the way, and the deposit never lands in the account.
Invisible because nothing appears. A missing deposit leaves no row anywhere for anyone to notice.
Invisible porque no aparece nada. Un depósito faltante no deja ningún registro en ningún sitio para que alguien lo note.
Refunds taken off twice
The provider nets the refund out of a later payout, and the same refund is recorded again in your own books.
Invisible because both entries look correct on their own. Only putting them side by side shows the duplication.
Invisible porque ambos registros parecen correctos por separado. Solo al ponerlos uno junto al otro se ve la duplicación.
Chargebacks you paid for and never contested
The money is pulled back weeks after the sale, usually with a fee, and the window to respond is short.
Invisible because it arrives as a smaller payout, not as a notice, so the deadline passes before anyone looks.
Invisible porque llega como un pago menor, no como un aviso, así que el plazo vence antes de que alguien lo revise.
The three things LedgerMatch compares for an online store
Not your whole finance stack. Your storefront, your payment providers and your bank, read only, matched against each other.
What your store sold
Orders, their value, how they were paid, and whether they were refunded or cancelled.
What each provider paid
The payout reports from every provider sending you money, with the fees they deducted.
What reached your bank
The deposits that actually landed in the account, straight from your bank feed.
What peak season does to ecommerce reconciliation
Black Friday and the weeks around it are the clearest example, because everything that makes online reconciliation hard happens at once and at five times the volume.
- Steady order volume that one person can work through in a morning.
- The payment methods you always use, on cycles your team already knows.
- Returns trickling in against trading of roughly the same size.
- Differences get chased while the answers are still easy to find.
- Order volume multiplies, but payout cycles do not speed up, so the backlog lands after the rush.
- Extra checkout options get switched on for the season, each adding another payout to follow.
- Returns arrive in January, netted against a month of much lower trading, so payouts look wrong.
- Nobody has time to chase anything, so differences sit until the remittance trail has gone cold.
This is why the cost of reconciling by hand is not the hours it takes in a quiet week. It is the weeks after peak, when the volume that arrived in four days has to be unpicked by a team that is already behind.
How this is different from the accounting integration you already use
Most stores already sync payouts into their accounting software. That is a useful job, and it is not the same job as checking the money arrived.
An accounting integration
Tools that post your payouts into the books
- Takes the provider's payout report and turns it into entries in your ledger.
- Splits out the fees the provider says it charged.
- Takes the report at its word, because it has no view of your bank account.
- If the payout never arrived, your books still say it did.
LedgerMatch
Checks the money actually reached you
- Compares your orders, the provider's payout and the bank deposit against each other.
- Shows the fee as a difference you can see, not as a figure you have to accept.
- Catches the payout that was issued but never landed, which no ledger entry would reveal.
- Posts nothing to your books, so a wrong match is a line to correct, not a journal to reverse.
Put simply: your accounting integration records the payout. LedgerMatch checks the payout turned into money. They work alongside each other, and neither one replaces the other.
Reconciliation software by industry
Every industry gets paid differently. Each page covers the settlement patterns, the usual differences and the evidence that industry needs.
Reconciliation by where the money lands
Whatever you sell, the money arrives through one of these. These pages cover each side on its own.












