Track an unmatched item that crosses reporting periods

Carry the case forward without resetting its history

Carry its evidence and next action forward so the close team can build on prior work instead of rediscovering it.

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.

An item can affect more than one period's work while remaining one unresolved investigation. Record the periods in which it is relevant and let the practitioner decide its accounting effect. Do not close the earlier case merely because a later month's tracker now contains a similar row.

Separate case history from period reporting

Use a master case register or an explicit link between monthly views. Suggested fields include original case ID, origin period, current reporting period, source references, cumulative investigation notes, latest action and reviewer condition for closure. Preserve the original detection date even if the case is reassigned or reopened.

Intuit: Reconcile an account describes period-based statement comparison. Microsoft: Refreshing filters describes refreshing filtered views after data changes. The proposed carry-forward control lets a monthly view show current work while the underlying case remains stable. Check that the filter includes relevant open cases from earlier periods, not only items created this month.

Follow one case across two months

This fictional example shows a September exception still unresolved in October. The history travels with the same case rather than being replaced by a fresh row with a new age.

The October view should link back to the original source and prior request. If the new evidence changes the hypothesis, record that change with its reason. Do not overwrite the earlier investigation as though the revised explanation was known from the beginning.

Reconcile the carry-forward population

At period rollover, compare the prior open case list with the new view. Every prior case should be present, closed with a documented decision or explicitly transferred to another controlled queue. Investigate missing cases and duplicate IDs before relying on the new report.

• Preserve the original case and detection date.
• Keep source links and prior actions accessible.
• Record the current next-action owner.
• Explain closures and transfers between views.
• Check that current filters include carried-forward work.

If a case is split into distinct issues, retain a parent relationship and explain the new case identities. If several cases are consolidated, record the surviving reference. Otherwise the rollover can appear to reduce or increase backlog simply because identifiers changed.

Review old cases for a new actionable step

Carrying a row forward is not progress by itself. At the next review, confirm that the previous action produced a result or define a different escalation. A case with a known wait still needs an owner and check date; a case with no viable next step needs practitioner attention.

Use the related workflow guide for the broader exception process and the workflow audit checklist to examine handoff continuity. A useful test is to roll a synthetic open case through two periods and verify that its age, evidence and next action remain visible.