Build a reconciliation exception register with a next action

Give every exception a next action and an owner

Give each reconciliation gap an owner, the evidence still needed and the decision it blocks so the team can move individual items toward closure.

When an exception needs a supplier invoice schedule, ParseMill can extract the invoice PDFs into Excel and keep source references available for checking. That gives the reviewer a concrete starting point. Bank reconciliation, accounting judgments and posting stay in your accounting system.

Start from observations rather than diagnoses. Record bank amount differs from component schedule, for example, before labeling the cause a fee. An unsupported cause label can steer later reviewers toward a convenient explanation and hide the need to inspect the underlying sources.

Define the register around decisions

Suggested fields are case ID, account reference, relevant period, source records, observed discrepancy, current hypothesis, evidence request, action owner, review owner, next check date and closure basis. Keep financial amounts in their original currencies and distinguish transaction dates from the date the exception was detected.

Intuit: Reconcile an account describes comparing recorded transactions with statements. Microsoft: Data validation describes restricting worksheet values. The proposed register can use consistent states such as investigation, awaiting evidence, review required and closed with decision, while preserving the detailed reason in a separate field. The state should describe the current work, not imply a conclusion unsupported by evidence.

Turn a vague exception into a task

This fictional example starts with a note that says deposit does not match. The revised row gives the next person a specific investigation to perform.

The EUR 30 difference remains unexplained until evidence supports a cause. The coordinator can complete the evidence-gathering action while the case stays open for review. This prevents a successful document request from being confused with resolution of the reconciliation issue.

Keep actions distinct from cases

One exception may require several messages, checks and decisions. Record those as activity under the same case rather than creating a new exception every time someone acts. Conversely, unrelated discrepancies should not share a single case merely because they concern the same account or month.

• Describe the observed discrepancy precisely.
• Link the source records and their versions.
• Name the next-action and review owners.
• Record a check date for waiting dependencies.
• Require a closure decision and supporting evidence.

If an action produces no useful evidence, record that result and the next proposed step. A note saying checked is insufficient without what was checked and what was found. If the case is transferred, preserve prior attempts so the new owner does not repeat them unnecessarily.

Test the register with a handoff

Give another staff member three open cases and ask them to identify the next action, evidence location and decision owner for each. If they need an oral explanation, improve the row rather than adding another status label. The register should carry the work across ordinary staff changes.

Use the related workflow guide for the broader reconciliation-exception process and the workflow audit checklist to assess missing ownership. A useful software evaluation should test a case that moves from client evidence collection to internal review without losing its identity or closure conditions.