Operated function · reconciliation
Reconciliation exists to catch differences, and it is very good at it. What it does not do is notice that a difference is the eleventh occurrence of the same cause — so a process defect gets cleared, correctly, every month, forever.
Two systems that should agree do not. That is normal and expected — timing differences, in-transit items, a fee posted on one side, a currency rate applied differently. The exercise is separating the differences that will resolve themselves from the ones that will not.
Matching is mostly mechanical and mostly done by hand, or by a rule set that catches the easy cases and leaves an exception list. The exception list is where the time goes and it is worked by whoever has the deepest knowledge of both systems, which is usually one or two people.
That knowledge is undocumented. Why a particular counterparty always posts two days late, why one product line reconciles differently, which differences are safe to carry and which are not — it lives in a head, and when that person is on leave, month-end takes longer and everybody knows why.
Adjustments get made to close. Some are correct. Some are a judgement made at eight in the evening on the last day, and the reason is recorded as a reference nobody can interpret three months later.
And the recurrence is invisible. The same cause produces a break every period, and because each period is worked as a fresh exercise, nobody accumulates the evidence that would justify fixing the upstream process instead.
Breaks are cleared individually and their causes are not recorded in a comparable form, so recurrence is invisible — and a process defect that generates a difference every month is indistinguishable from a one-off.
That is why reconciliation effort never falls. The work is genuinely being done well; it is simply being done against a population that regenerates itself, and nothing in the process is designed to notice.
Recording cause in a comparable form is the whole change, and it is cheap. Not a free-text note — a classification from a written list your controllers own: timing, fee, rate, missing posting, duplicate, cut-off, counterparty error, our error. Once a cause is a value rather than a sentence, recurrence becomes a count.
A count changes the conversation. "This counterparty has produced a cut-off difference in nine of the last twelve periods" is a business case for changing something upstream. "We had some breaks again" is not, and it is what a free-text note supports.
Matching itself is the bounded, delegable part: applying your rules, working the exception list against your written cause list, and preparing what remains for a controller. It is high volume, repetitive, and the place where a person’s attention is worth least.
What is never delegated is the adjustment. Posting an entry, writing something off, and signing a reconciliation are acts with accounting and control consequence, and they belong to your controllers under your delegation of authority.
Breaks carrying a classified cause — measured by exceptions with a cause value from your written list, against a baseline of free-text notes or nothing.
Recurrence, visible for the first time — measured by the count of periods each cause and counterparty combination has produced a break.
Time to close the period — measured by elapsed days from data availability to sign-off, and the variance between periods.
Dependence on specific individuals — measured by close duration when the most experienced reconciler is unavailable, compared against when they are.
Adjustments with an interpretable reason — measured by entries carrying a classified cause and history, as a share of all adjustments.
Upstream defects actually fixed — measured by recurring causes closed at source, and the break volume that stops being generated.
any accounting judgement, adjustment, write-off or certification. Nothing here posts an entry, decides materiality, or signs a reconciliation. It matches, classifies against your list, and prepares — the accounting decisions belong to your controllers, and a system making them would be operating inside your financial control framework without authority.
Data is read from each system of record rather than from an extract somebody prepared, because an extract is a third version and its preparation is itself a source of difference.
The cause list and the matching rules are yours: written, versioned, owned by your controllers. They encode your accounting policy and your knowledge of your counterparties, and they are the asset that stops the operation depending on one person’s memory.
Adjustments are prepared for your team to post in your own system. Nothing writes an accounting entry, which is a boundary rather than a configuration.
No entry is posted and no reconciliation is certified. The operation prepares; your controllers decide and sign. That separation is what allows any of this to happen inside a control framework at all, and it is structural rather than a setting.
Every classification records who or what applied it, against which version of the cause list, and with what evidence. A classification with no basis is the finding an auditor writes up, and this is designed to eliminate that rather than create more of it.
Segregation of duties is preserved by scope: the operation cannot both prepare and approve, because approval is not a capability it has.
Operational access is not permission to train. Your financial data does not become material improving anything serving another organisation.
Internal audit will ask about segregation of duties, and the answer is that approval is not a capability rather than a permission that has been withheld. That distinction matters to them and it should be examined rather than accepted.
Your external auditor should confirm that the classification record improves rather than complicates the evidence they examine. In practice it usually improves it substantially — a classified, versioned cause with a recurrence history is stronger than a free-text note.
Where an obligation attaches through your control framework or a regulator, it is marked applicability-gated rather than presented as standing.
Twelve trailing periods of already-cleared breaks — read-only, nothing posted — reclassified against a written cause list to establish which causes recur.
The retrospective pass is the whole argument and it touches no live period. It takes breaks that were already cleared and classifies them, which produces the number nobody has: what share of last year’s reconciliation effort went into causes that appeared in most periods.
Where that share is large, the case is not for faster reconciliation — it is for fixing a handful of upstream processes, and the evidence for that case is now in hand. Several finance teams should stop there and spend the effort on the fix.
If you continue, the first delegation is matching and classification on one reconciliation, with adjustments and sign-off untouched and the cause list written by your controllers before anything runs.
Most of it matches well and leaves an exception list, which is the correct division of labour. The gap this addresses is what happens to the exceptions: whether their causes are recorded as comparable values and whether anybody can see that the same cause returned nine periods running. If your tool already reports recurrence by cause and counterparty, this is a duplicate.
The retrospective pass measures that directly against twelve periods you have already closed, and it costs read access to data you already hold. Some books genuinely are irregular. More commonly a handful of causes account for most of the volume and nobody could see it, because each period was worked as its own exercise and the notes were free text.
Nothing posts, writes off or certifies — those are not permissions that have been withheld, they are capabilities the operation does not have, which is what preserves segregation of duties by scope. What is delegated is matching and classifying against a list your controllers wrote. If your control framework holds that even classification is a finance act, the retrospective pass alone still produces the recurrence evidence.
Frequently true, and it changes who the evidence is for rather than whether it is worth having. A counterparty producing a cut-off difference in nine of twelve periods is a conversation with that counterparty, and it goes considerably better with a count than with an impression. Where the upstream system is genuinely immovable, classifying the cause at least stops it consuming investigation time every period.