Explain why a reconciliation exception backlog changed

Explain the backlog with a movement bridge

Show what actually changed so the team knows whether the process improved and where effort is still needed.

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 bridge explains movement; it does not by itself explain quality or cause. Keep the definitions and population constant, and report transfers, mergers or scope changes explicitly when they affect the count. Do not force those events into new or closed categories without stating the rule.

Define the counting unit and boundary

Specify the accounts or workstreams included, period start and end, case state rules and cutoff time. Use one case ID for each exception, with activity recorded beneath it. A case reopened and closed in the same period can contribute to both movement categories while leaving no closing balance, provided that rule is applied consistently.

Microsoft: Excel tables describes structured worksheet tables. Microsoft: Refreshing filters describes refreshing filtered data views. These mechanics can support a movement register, while the proposed bridge makes the population and transitions explicit. Recheck filters before counting so a current view does not omit cases that closed earlier in the period.

Reconcile a fictional week's movement

The following synthetic example counts distinct cases and state transitions under a stated weekly rule. It illustrates arithmetic, not a claimed customer result.

The check is 40 + 12 + 3 - 18 = 37. Eighteen closures do not mean eighteen fewer open cases because fifteen cases entered the queue. If staff sent sixty messages during the week, report that as activity separately; it is not another case movement in this bridge.

Investigate a bridge that does not balance

Compare the opening and closing ID sets and inspect cases that entered, left or changed identity. Common questions include whether a case was deleted, merged, transferred outside scope or created twice. Record the actual adjustment and its reason instead of changing the closure count to make the equation work.

• Keep stable case IDs across periods and owners.
• Count actions separately from exceptions.
• Define reopened and same-period reclosed cases.
• Record transfers and scope changes explicitly.
• Reconcile the bridge to actual opening and closing lists.

If several component tasks sit under one exception, closing a component does not close the parent case. Likewise, splitting one case into two can change the count without introducing two new underlying problems. Preserve those relationships so the report can distinguish real demand from administrative restructuring.

Interpret movement alongside ageing and cause

After the bridge balances, inspect which cases remain old, which causes are recurring and which closures have review evidence. A lower backlog with unsupported closure decisions is not a meaningful improvement. A temporary increase may reflect better detection, but that explanation needs evidence rather than a convenient narrative.

Use the related workflow guide for the wider exception process and the workflow audit checklist to examine queue movement. A useful test includes a reopen, a transfer and several actions on one case, ensuring the report counts the work population accurately rather than rewarding message volume.