Account matching: the process and essential checks

Quick answer. Matching reconciles, on a third-party account, the entries that offset each other: an invoice and its payment of the same amount. What stays unmatched becomes the useful information, the unpaid customer receivables and the unsettled supplier payables. The process combines automatic matching for the bulk of the flow and manual matching for special cases, then the analysis of unmatched entries and the treatment of discrepancies.

Matching is a basic operation, but decisive for the reliability of third-party accounts (class 4 of the French general accounting plan). Done poorly, it leaves false balances, masks the real receivables and payables, and distorts both cash-flow follow-up and the year-end close. Done well, it turns an unreadable balance into a clear list of invoices remaining due. Here is the process, the checks that matter, and the pitfalls we keep seeing in client files.

Matching gives meaning to a third-party account balance. A customer or supplier account records, in chronological disorder, invoices and payments. Matching consists of linking the entries that cancel out, an invoice and the corresponding payment, by assigning them the same marker (a letter, hence the French term). Once these entries are paired, what stays unmatched is precisely the information to exploit: invoices not yet paid on the customer side, invoices not yet settled on the supplier side.

The French general accounting plan (ANC regulation no. 2014-03) requires third-party accounting that justifies each individual balance. Without matching, this global balance says nothing: it is impossible to know which invoices remain due, or for how long. Matching is therefore a prerequisite for any analysis of third-party accounts, for dunning follow-up and for the accounting close. It also underpins the justification of balances expected during an audit, knowing that accounting records are kept for ten years (article L123-22 of the French Commercial Code).

The process combines two complementary modes, which must not be confused.

Automatic matching reconciles in bulk the entries with identical amounts: most invoices paid to the cent are matched without intervention. It is the tool that absorbs the volume, fast. Manual matching takes over for what automation cannot handle: down payments, credit notes, partial payments, grouped payments covering several invoices, payment discrepancies. These situations require reconciling entries of different but linked amounts, which is analysis, not mechanical pairing.

A third mode exists in most software: approximate matching (or by reconciliation), which proposes matches with a slightly different amount (typically a discount or a rounding) and leaves the accountant to validate. It is a real time-saver, provided you keep a low tolerance threshold and always justify the residual gap.

The key is not to choose a mode, but to chain the three in the right order: automatic for speed, approximate under control, manual for accuracy on the risk cases, which are precisely those that reveal anomalies.

Matching is not limited to pairing amounts: it calls for controls, without which it gives a false impression of cleanliness.

First, you must analyse unmatched entries by age: a customer invoice left unmatched for several months is a receivable to chase, sometimes a dispute, sometimes an invoice already paid but wrongly allocated. Then you must handle payment discrepancies: an invoice paid at a slightly different amount may reveal a discount granted, a retention guarantee, bank fees, an exchange difference or a simple input error. You must also spot duplicates (the same invoice posted twice) and unallocated payments (collected but linked to no invoice). Finally, matching can be undone, or unmatched, to re-link entries that were paired by error.

The best support for these checks is the aged trial balance: it sorts receivables and payables by age bracket (not yet due, due 0 to 30 days, 30 to 60, 60 to 90, over 90). Up-to-date matching is the condition for it to be reliable: an aged balance built on poorly matched accounts shows phantom overdues and masks the real ones. Once matching is reliable, the physical stock count completes the work of justifying balance-sheet items ahead of the close.

The table below summarises the action to trigger by the age of an unmatched customer receivable. It is this reading by bracket that turns the aged balance into a collection plan.

Our view#

Matching is an operation that automation has greatly eased, but which keeps an irreplaceable share of analysis. The frequent mistake is to believe that automatic matching is enough: it handles the simple, but leaves aside the risk cases. Yet those are the ones that carry the management information.

Our approach is to let automation absorb the ordinary flow, to frame approximate matching with a low tolerance threshold, then to focus human analysis on the old unmatched entries and on the discrepancies. That is where the receivables to chase, the payables to settle, the forgotten credit notes and the errors to correct are found. Rigorous matching makes third-party accounts reliable, secures the close and directly feeds the customer line of the cash-flow follow-up. Botched matching does the opposite: it makes the accounts unreadable and installs a false sense of security.

The underestimated risk: a matched account is not a correct account#

An account can be fully matched and still be wrong. If an invoice has been matched with the wrong payment (two operations of the same amount but unrelated), the global balance stays correct while the detail is wrong: the true unpaid invoice disappears from the radar, and a payment already collected is still treated as due. Matching by amount does not guarantee reconciliation by operation. This is why we check the consistency invoice by invoice on sensitive accounts, and not just the overall matching rate.

A services SME relied solely on automatic matching. Over the months, unmatched entries had piled up on the customer account: around 28,000 euros of unpaired entries, a balance that had become unreadable. Resuming it, entry by entry, revealed three things. First, nearly 9,000 euros of invoices already paid but matched by error with other operations, so collections counted twice in the follow-up. Second, around 6,000 euros of genuinely unpaid receivables never chased, two of them beyond 90 days. Finally, discount gaps never posted as an expense, which left residuals of a few euros on dozens of invoices.

After unmatching the wrong links, posting the discount gaps and chasing the real receivables, the account became readable again. The aged balance then showed the true customer exposure, and the owner could chase what needed chasing. The gap between the displayed balance and reality came entirely from the quality of the matching.

In practice: securing your matching#

• Run automatic matching first to absorb the identical-amount flow.
• Use approximate matching with a low tolerance threshold, and always justify the residual gap with an entry (discount, fees, exchange). In practice, a threshold of 0.50 euro, or 0.1% of the amount for large invoices, is enough to absorb rounding without masking a real error; adjust it to your volume.
• Then handle manually down payments, credit notes, partial payments and grouped payments, reconciling invoice by invoice.
• Issue the aged trial balance after matching, at least once a month, and weekly if your flow of payments is significant: it is what reveals old receivables and feeds the chasing.
• Unmatch any doubtful link rather than leaving it: a traced unmatching is better than a false balance.
• Make matching a monthly routine, not a year-end project: done regularly, it clears in minutes; accumulated over the year, it becomes an audit.

Most modern software tools support this sequence. In Pennylane, for example, you combine automatic and approximate matching with a low threshold (around 0.50 euro), then issue the monthly ageing report to drive the chasing. The logic stays the same whatever the tool: let automation absorb the volume, and keep human analysis on the gaps and the old entries.

To make these accounts reliable over time, it is better to rely on a firm that keeps a consistent method from one year to the next. Our accounting and tax engagements include this control of third-party accounts, and the subject takes on a particular dimension in groups, where the matching of shareholder current accounts and intragroup balances is a matter of genuine holding taxation. Understanding the role of the chartered accountant on this point shows that, beyond data entry, it is the justification of balances that creates the value.

• Too wide an approximate-matching threshold matches real errors as if they were discounts: keep it low and check the gaps.
• A fully matched account is not necessarily correct: check reconciliation by operation, not just the balance.
• Grouped payments covering several invoices are matched by hand: automation often leaves them aside.
• Unmatched credit notes artificially inflate the supplier balance or wrongly credit the customer account: treat them as entries to pair.
• Unmatching must be traced and justified; done blindly at year-end, it loses an account's history.
• Matching postponed to the close turns a routine of a few minutes into a project of several days, at the worst moment in the accounting calendar.

• Matching links, on a third-party account, the entries that offset each other (invoice and payment); what stays unmatched corresponds to the real receivables and payables to follow.
• Three modes chain together: automatic for speed, approximate under a low tolerance threshold (around 0.50 euro), manual for the risk cases (down payments, credit notes, partial or grouped payments).
• The aged trial balance is reliable only if matching is up to date: issue it at least once a month, more often if the flow of payments is significant.
• Read the aged balance by age bracket to trigger the right action: check, reminder, formal notice, or dispute analysis beyond 90 days.
• A fully matched account can be wrong: check reconciliation invoice by invoice, not just the overall balance.
• Make matching a monthly routine, never a year-end project, and trace every unmatching.