A supermarket's fortnightly payment won't reconcile straight against your open invoices, and Xero refuses to balance it. The deposit is right, your open AR is right, and sitting between them is a column of deductions the retailer applied on its own terms. One payment covers a hundred invoices net of charges you never chose line by line, and there are two jobs tangled up inside it, matching the clean invoice lines and accounting for the deductions. The matching is repetitive enough that a machine should be doing it, and the deductions are an accounting decision that stays with you.
The steps below assume you sell into one or more major grocery chains, you raise sales invoices in Xero, and you reconcile AR against a bank feed. If your customers pay one invoice at a time and never deduct anything, none of this applies and you can stop reading. We're working through the fortnightly grocery remittance, which is long, multi-page, net of deductions, with reason codes that change per retailer.
Why supermarket remittances are the hardest to reconcile
Most remittances are awkward because they cover more than one invoice, and supermarket remittances are awkward at a different scale entirely. A single fortnightly payment routinely covers well over a hundred invoices, runs across multiple pages, and arrives net of a deduction column the retailer has applied on its own terms, and reading it is closer to auditing a payment advice than to receiving one.
The volume is high, which makes manual matching slow and error-prone before you've even started. The document is long and runs to multiple pages, with the header total at the top and the net figure that hits your bank sitting pages apart. Deduction lines sit among the invoice lines and reduce the net, so the payment never equals the sum of your open invoices, and because the reason codes attached to those deductions differ by retailer, a supplier dealing with Tesco, Sainsbury's and Asda is reconciling three coding schemes at once. Add the fortnightly cadence and you've got a job that lands like clockwork, never gets smaller, and always seems to fall on the busiest day of the period.
Take your largest grocery customer's last remittance and count the lines. If it's more than a hundred, and your team keys those matches by hand every fortnight, you're spending most of a day on work that's identical from one period to the next, apart from the handful of deductions that need a decision.
The anatomy of a major-retailer remittance
Strip the branding away and every major-retailer remittance has the same skeleton, with a header total at the top, then a long list of invoice lines, one row per invoice, each carrying an invoice number and a gross amount, then a set of deduction lines, each with its own reason code and a negative value, and at the bottom the net, the figure that lands on your bank feed. Whether it comes from Tesco, Sainsbury's, Asda, Morrisons, Waitrose or any other major chain, the shape holds, and only the layout and the codes move around.
Take a worked example in round numbers. Your remittance lists 118 invoices totalling £96,400 of goods supplied over the period, and below them sit three deductions, a shortage line of £1,900 where fewer cases were received than billed, a promotional allowance of £1,700 funding an agreed deal, and a settlement discount of £800 for paying to terms. That's £4,400 of deductions, and the net payment that hits your bank is £92,000.
Your Xero bank feed shows a single £92,000 credit, your open AR for this customer is £96,400, and reconciling the bank line straight against the invoices leaves you £4,400 short, which Xero won't let balance. Both figures are correct, and that £4,400 gap is the deduction column doing what it was designed to do, so there's nothing there for anyone to hunt down.
The deduction lines, and where they actually go
The clean invoice lines are the easy 95 percent, mapping one row to one open invoice, with the numbers agreeing, and they can be matched and posted without a human looking at them. The deduction lines are the other 5 percent, and they're where the time goes, because each one is a question about which general-ledger account it belongs in, and that's a policy decision every business charts differently. The categories you'll meet again and again:
- Shortages. Fewer cases received than billed. Often a real revenue reduction, sometimes a claim you'll dispute, so how you code it depends on whether you accept it.
- Promotional and co-op advertising allowances. Funding you owe for an agreed deal or for in-store and circular advertising. This is contracted spend rather than a pricing error, so it usually belongs in a marketing or trade-spend account rather than against sales.
- Retrospective promotion rebates. A volume or period rebate clawed back after the fact, which may need accruing across the period rather than booking in full on the day it appears.
- Spoilage and unsaleables. Stock written off at the retailer's end and charged back to you.
- Compliance and service-level charges. Late-delivery fines, fill-rate penalties and other service-level deductions, typically coded as a cost rather than a sales adjustment.
- Invoice price or quantity mismatches and post-audit claims. The retailer's records disagree with yours, sometimes months later. These often warrant a dispute before you code anything.
- Settlement or early-payment discounts. The discount you offered for prompt payment, taken as agreed.
None of these point at a specific open invoice the way an ordinary payment line does, so they reduce the net without retiring anything, and there's nothing for a matcher to match them against. They have to be coded, and the right account differs from one supplier to the next, which is why this part stays with a person while the clean matching doesn't need one. For the coding deep dive on how to treat each category in Xero, see our piece on handling remittance deductions in Xero.
Some retailer deductions don't arrive as adjustment lines on the sales remittance at all, they come as separate debit notes. In Xero a debit note can land on your purchase ledger (accounts payable) instead of as a sales credit, so it'll never match against your AR invoices and has to be picked up and handled on its own. If your net doesn't reconcile even after you've accounted for every line on the remittance itself, a debit note sitting on the purchase ledger is the usual culprit.
When one remittance runs past Xero's batch limit
Xero caps a single batch payment at 200 invoices, which is academic for most businesses. For a large grocery supplier, a single fortnightly remittance can carry more than 200 clean invoice lines, so the payment won't post as one batch however you slice it. You have to split it, and splitting by hand while keeping the totals straight is its own headache on top of the deductions.
If you're anywhere near that volume, it's a constraint to plan around rather than discover at month-end. We wrote up the limit and how to work within it in Xero's 200-invoice batch payment limit.
Getting the clean lines off your plate
The vast majority of a supermarket remittance is clean invoice matches, where a row points at an invoice, the amounts agree, and it can be posted. That's repetitive, rules-based and identical every fortnight, which is the kind of work a machine should get through in seconds, and what's left once it has run is the short list of deduction lines that need your judgement.
RemitClear's Xero remittance matching reads the remittance, matches the clean invoice lines against your open AR in Xero, and splits the posting across batches when the count runs past 200. The deductions come out as a short flagged list you work through and code, instead of being buried among a hundred rows you'd otherwise eyeball one at a time. That's what grocery and retail remittance matching is for.
Summary
Next fortnight, split the remittance into its two piles before you touch Xero. Run a highlighter down the page and separate the clean invoice lines, which map one-to-one and can be matched and posted in bulk, from the deduction column, which can't. Match the clean pile first, even past the 200-invoice batch ceiling, then work only the deductions, shortages, promotional and co-op allowances, retro rebates, spoilage, compliance charges, settlement discounts, coding each to the account your chart of accounts calls for. And keep half an eye out for the debit notes that slip onto the purchase ledger.
