Separate timing differences from unexplained reconciliation gaps

Keep timing as a reviewed explanation

Label what is known and what remains uncertain so effort goes to the gaps that need evidence.

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 practical distinction is between a supported explanation that needs a follow-up check and an unknown cause that needs investigation. Both can remain open. A timing label should include the expected later event or review point, so the item does not disappear into a category that nobody revisits.

Record dates with their meanings

Capture source transaction date, bank posting date, reporting period and detection date separately. Add the evidence supporting the proposed relationship and the event expected to resolve it. Avoid compressing several dates into one field called date, especially when documents and imported records use different meanings.

Intuit: Reconcile an account describes statement comparison. Intuit: Find missing transactions explains that a transaction may appear in a different review state or account. Those checks matter before assigning a cause: a display or import issue can resemble a timing gap. The proposed classification retains unresolved when the available evidence does not distinguish them.

Compare two boundary cases

The fictional examples below share a similar date pattern but have different evidence. Only one has enough support for a proposed timing classification.

For X32, record the actual later source and the reviewer decision. For X33, assign the next search or evidence request and a check date. Do not copy X32's explanation merely because the amounts or dates look similar; each case needs its own supported relationship.

Keep the follow-up condition explicit

A supported timing item may require a subsequent-period check or another action under the firm's reconciliation process. Record that condition and who verifies it. If the expected event does not occur, reassess the classification rather than repeatedly extending the expected date without explanation.

• Preserve all relevant date types.
• Link evidence connecting the source records.
• Rule out simple view or account-location issues.
• Record the reviewer's classification and basis.
• Keep a next check for any unresolved condition.

Do not change posting dates or create adjustments solely to make the current period's difference disappear. Those actions belong to an authorized accounting decision. The exception register should show what is known and what needs deciding, not substitute an administrative label for professional judgment.

Review timing items at the next boundary

At the next review point, inspect whether the expected source appeared and whether it actually supports the original explanation. Retain rejected hypotheses as history so a later reviewer understands why the case changed category. Close only when the authorized process's conditions are satisfied.

Use the related workflow guide for the wider exception workflow and the workflow audit checklist to examine recurring period-boundary questions. A practical test should include both a supported timing case and an unresolved lookalike, ensuring that the workflow requires evidence rather than recognizing only a familiar date pattern.