Explain an unresolved reconciliation item in a review note

Write the note around the decision the reviewer needs

State the difference, what has been checked and what remains needed so an unresolved item can still move through a clear handoff.

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.

The note should be concise but reproducible. It is not a transcript of every click or a substitute for source records. Focus on what another reviewer needs to verify the observation, understand unsuccessful checks and choose the next action.

Use a five-part note

Start with the case and scope, then the observation, completed checks, current hypothesis and next request. Label values with currencies and date meanings. Include links to the exact source versions used so a later change does not make the note impossible to reproduce. If no hypothesis is supported, say unresolved.

Intuit: Audit log describes recorded account activity. Intuit: Bank deposits describes grouped payment records. These sources can supply investigation evidence in relevant cases. The proposed note structure explains what staff learned from those records rather than merely listing that the audit log or deposit screen was opened.

Rewrite a fictional vague note

The example below concerns a net deposit. It demonstrates useful specificity without authorizing a balancing adjustment.

The EUR 15 difference remains unexplained. A note saying probably fees would be weaker unless supporting evidence exists. If the reviewer later confirms a documented deduction, append the source and decision rather than rewriting the original note to imply it was always known.

Record negative findings precisely

An unsuccessful search is useful when its scope is clear. No duplicate found among component IDs A1–A5 is more informative than no duplicates. State the period, account, view or source set checked, and avoid universal claims that the investigation did not support.

• Identify the source records and relevant versions.
• State values with units and date meanings.
• Describe checks and their actual results.
• Separate observations from hypotheses.
• Ask for one clear next decision or evidence item.

If a calculation is involved, show enough inputs for the reviewer to reproduce it. Do not paste a total without its component basis. If the note concerns unlike currencies or a disputed source relationship, state that limitation before presenting a numerical difference as meaningful.

Check whether the note enables continuation

Give the note and its links to a colleague unfamiliar with the case. Ask what they would do next and which checks they would avoid repeating. If their answer differs from the intended next action, clarify the request or missing context. A useful note reduces ambiguity while keeping the reviewer free to challenge the hypothesis.

Use the related workflow guide for the full exception process and the workflow audit checklist to assess investigation handoffs. Review a few notes that required repeated explanations and improve the common missing element, rather than creating a longer template that every case must fill unnecessarily.