The Hollow Sign-Off: When a Reconciliation Control Stops Working

A frequent failure is the hollow sign-off. A reconciliation gets prepared and approved on schedule while unexplained differences quietly roll forward inside it. Control testing finds a signature and passes it. Reading the open items exposes the problem. Repair means clearing the backlog, naming owners and changing what reviewers must check.

How it starts

It rarely begins with negligence. A reconciliation between the ledger and an outside record, such as cash held at the bank, an asset register or a payroll summary, produces a difference nobody can explain before the close deadline. The preparer labels it a timing item and carries it forward. The reviewer accepts the label because the close is late and the amount looks small.

Next period the item is still there. Now it has company. A new system interface posts some transactions under a different account attribute. A payment adjustment lands in the wrong period. Each new difference gets the same treatment, because the template has a line for carried items and nothing forces anyone to resolve them.

Staff turnover finishes the job. The person who knew why the first item existed moves on. The successor inherits a schedule full of old entries with vague descriptions and treats them as permanent fixtures.

Why testing misses it

Most control tests ask whether the reconciliation was done, whether it was done on time and whether someone independent approved it. A hollow sign-off satisfies all of that. The evidence pack looks complete. Auditors requesting documentation receive a tidy schedule with signatures.

The weakness sits in the content. A test that never asks how old the reconciling items are, or whether each one has a documented cause, will keep passing a control that has stopped doing its job.

How it gets spotted

Usually someone outside the routine notices first. A financial statement preparer tries to trace a balance back to the ledger and finds a stubborn variance. An auditor pulls a sample and asks for support on an item that turns out to predate everyone in the team. A budget holder sees available funds that do not match what was spent.

Inside the finance team, the clearest signal is a reconciling items list that only grows. Descriptions like "under review" or "timing" appearing on the same entries across several periods tell the story. Another warning is a reviewer who signs within moments of receiving the file. Manual journal entries posted to force the reconciliation to zero, with no supporting document, are the most serious sign of all.

Questions to ask the people who run it

What staff actually do often departs from the written procedure, so ask the preparers and reviewers directly.

• When an item cannot be explained before the deadline, what happens to it?
• Who decides that something is a timing difference, and what evidence do they need?
• Which items on the current schedule were there when the preparer took over the work?
• What does the reviewer look at before signing, and what do they skip when time is short?
• Has anyone ever posted an entry just to make the reconciliation balance?
• If a difference is traced to another team or system, who chases it, and does anyone follow up?
• Does the written procedure say anything about how long an item may stay open, and is that followed?

The answers to the last two questions tend to reveal the gap between policy and habit.

Fixing it

Start by treating the problem as a control deficiency and recording it formally. That gives the remediation an owner, a target and visibility with management.

Then clear the backlog. Sort the open items by origin. Some will trace to a known cause, such as a misclassified ledger attribute or a payment posted to the wrong account, and can be corrected with a properly supported adjustment. Others will need research in source systems or with the counterparty. A few may never be explained. Those need a documented decision from someone with authority to write them off or escalate them, not another quiet carry forward.

Fix the upstream causes while the research is fresh. If an interface keeps posting under the wrong segment, correct the mapping. If a tolerance setting lets mismatches through without a hold, tighten it.

Finally, redesign the review. Require every reconciling item to carry a cause, an owner and the date it first appeared. Set an ageing threshold that triggers escalation automatically. Ask the reviewer to evidence what they examined, such as a sample of items traced to support, instead of a bare signature.

Keeping it fixed

Update the monitoring test so it examines item age and support, not only completion. Have someone outside the preparing team read the reconciling items list periodically. Retest the remediated control over more than one cycle before closing the deficiency, because a clean first period after a backlog cleanup proves little on its own.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.