In many companies there is someone who spends the first days of the month matching the bank against the system. Bank statement on one screen, ERP on the other, ticking off deposit after deposit. When something does not match, they go digging through the point of sale, emails or the sales rep’s WhatsApp.
Much of that work can be automated. But first you have to understand why it does not match, because it is almost never a software problem.
Why the three never match
The bank, the ERP and the point of sale record the same money at different times and in different amounts. The cases we see most:
- Card payments. The point of sale records each sale at its total. The bank receives a single deposit the next day, for the sum of several sales minus the terminal’s fee.
- Transfers without a reference. The customer pays by SPEI, Mexico’s instant transfer system, and writes “payment” or their name in the description. The money arrived, but nobody knows which invoice it belongs to.
- Cash. It is collected in a store or on a route and deposited days later, sometimes together with cash from other sales.
- Day cutoffs. A sale at 11:50 p.m. lands on one day in the point of sale and on another in the bank.
All of them are differences in timing and grouping, and automated reconciliation means teaching the system to recognize them.
The reference is half the job
What speeds up reconciliation the most is giving each payment something that identifies it uniquely before the money moves. With transfers that means giving each customer their own reference or account number, or sending a payment link that already carries the invoice number. When the deposit arrives with that reference, the system applies it on its own.
In Recaudo, for example, the payment link or the customer’s account number goes out in the same WhatsApp message that reminds them of their balance. And Banxico expects SPEI transfers to outnumber card payments in Mexico in 2026, so this point will only matter more.
Rules, not guesses
For whatever arrives without a reference, you write rules. Some we usually set up:
- Terminal deposits are compared with the sum of the previous day’s card sales, minus the agreed fee. If the difference is within a margin, it is reconciled and the fee is booked as an expense.
- A deposit without a reference that exactly matches a single open invoice from the same customer is proposed, not applied. A person confirms it with one click.
- Whatever fits no rule goes into a short list to review by hand.
The realistic goal is for that list to be short. Making it disappear is not realistic, and I distrust anyone who promises it.
Where reconciliation lives
Reconciliation should end up in the ERP, because that is where the accounting is. Nori, our ERP for small and midsize businesses, puts the point of sale, route sales and accounting in the same system, which removes one of the three sources. When the client already runs SAP Business One or NetSuite, we connect the point of sale and the bank to that ERP instead of creating a fourth place to reconcile.
One thing we learned to watch: zero amounts. In one integration we found quotes where the app sent add-on items with a $0 total, and the error went by without anyone noticing. A reconciliation that matches exactly because both sides are wrong is worse than one that does not match.
Where to start
If you reconcile by hand today, take one full month and sort every difference into the four categories above. You will see which one weighs the most. It almost always pays to tackle that one first, with references or a rule, before buying any tool.
That diagnosis is part of our process consulting work. How many days does it take your team to close the month today?