Review lag is a useful measure because a reconciliation that is not reviewed is not a control. It is also easy to misread. A fast review can be a rubber stamp, and a slow review can reflect a complex account rather than a slow reviewer.
Cash & Treasury
Measuring bank reconciliation review lag without overclaiming
A research brief on timing the review of bank reconciliations, separating preparation, review, and correction from the quality of the reconciliation.
Published · 3 listed sources
Table of contents
Key takeaways
- Review lag measures the time to a reviewer's sign-off, not the accuracy of the reconciliation.
- Split the lag into preparation, queue, review, and correction so the delay has a stage.
- Report the share reviewed before the close and the open items with no reviewer.
- Pair the timing with a sample quality check before drawing a conclusion.
A bank reconciliation is prepared, then reviewed. The preparation takes time, the reviewer has a queue, and a question can send the reconciliation back for correction. The review lag is the time from ready-for-review to sign-off.
What the measure can show
The measure can show when the reconciliation was ready, when the reviewer picked it up, when it was signed off, and how many times it was returned. It can show the share reviewed before the close.
Those facts support a review of the queue and the review capacity. A queue that builds at month end may need a different schedule. A high return rate may need a clearer template.
What the measure cannot show
The measure cannot show whether the reconciliation is accurate. It cannot show whether the reviewer checked the supporting documents or simply approved the balance.
It also cannot show whether the preparer had the information needed. A slow review may be a missing document, not a slow reviewer.
Methodology
This brief reviews public guidance on internal control, records, and time measurement, and maps it to a private reconciliation review. The sources support documentation and review discipline. They do not prescribe a review target or measure reconciliation quality. The proposed stages are an operating design.
Define the stages
Record four times: ready, picked up, reviewed, and corrected. The gap from ready to picked up is the queue. The gap from picked up to reviewed is the review. The correction time is the rework.
Report the stages separately. A single average hides whether the problem is the queue, the review, or the corrections.
Separate the account types
A simple operating account and a complex trust account have different review needs. Group the reconciliations by type and risk before measuring. A single average will be dominated by the easy accounts.
Report the count and the distribution by type. A small number of complex accounts with long lag may matter more than a large number of simple ones.
Check the reviewer and the independence
Record who prepared and who reviewed. If the same person did both, note it. A review by the preparer is a self-check, which may be acceptable in a small team but should be visible.
The measure should show the share of reconciliations with an independent reviewer. That share is a control indicator, not a performance score.
Pair timing with a quality sample
Take a small sample of reviewed reconciliations and check the support: the statement, the outstanding items, the adjustments, and the reviewer's notes. A fast sign-off with no notes is a question.
Record the sample size and the findings. Do not present the sample as a full audit.
Review the pattern monthly
Look at the lag by account, preparer, and reviewer. A recurring delay at one stage may need a schedule change or a clearer template. A recurring correction may need a training or a data fix.
The review should produce one or two changes. A new cutoff or a different reviewer rotation is enough.
Protect the reconciliation data
Reconciliations contain bank balances, account numbers, and adjustments. Keep them in the approved system and limit access. Do not share a reconciliation in a broad channel.
Set a retention period with the client's records policy.
Check the close calendar
Review lag should be measured against the close calendar, not the calendar month. A reconciliation due on the third business day is late on the fourth, even if the month has just ended.
Record the due date and the sign-off date. The difference is the useful measure.
Separate the preparer from the reviewer
If the preparer is also the reviewer, the lag is shorter but the control is weaker. Record the arrangement and review a sample for evidence.
The goal is not to force a separation that the team cannot support. It is to make the arrangement visible.
Decide what the review will change
Before the review, name two changes the team would make depending on the result. If the queue is the problem, the schedule may change. If corrections are frequent, the template may need a fix.
Share the summary with the preparers and reviewers.
Keep the sample comparable
If the measure is repeated, keep the account types, the stages, and the close calendar. A change in lag may reflect a new template or a different reviewer. Record the context.
Date any change in the definition.
Write the outcome down
End the review with a short note: the month, the account type, the stage with the largest delay, and the one or two changes the team will try. A written outcome gives the next review a starting point.
Keep the queue visible
A review queue that is hidden in an inbox is hard to measure and easy to ignore. Use a shared list with the account, the due date, the reviewer, and the status. The list is the source for the measure.
A simple list is enough. The point is to make the wait visible before it becomes a close problem.
Keep the process proportionate
A small account set does not need a formal review metric every month. A quarterly check with a clear close calendar may be enough. Match the measurement to the volume and the risk.
Keep the record ready for the close
If the close is questioned later, the review record should show the account, the due date, the reviewer, and the sign-off. A short note is enough.
A later reviewer should not have to rebuild the timeline from messages. The record is the evidence that the review happened.
Bounded pilot
Measure one month of reconciliations for one account type. Record the four times, the reviewer, and the corrections. Report the distribution by stage and the share reviewed before the close. Ask a reviewer who did not prepare them to explain what the measure shows and what it does not.
Limitations
This brief describes an operating measurement model. It does not establish a review benchmark, a legal standard, or a measure of reconciliation accuracy. The cited sources support general control and records principles. Results depend on the sample and the completeness of the records.
Sources
- Standards for Internal Control in the Federal Government; U.S. Government Accountability Office; checked November 11, 2026.
- Security and Privacy Controls for Information Systems and Organizations; National Institute of Standards and Technology; checked November 11, 2026.
- Recordkeeping; Internal Revenue Service; checked November 11, 2026.
Conclusion
Bank reconciliation review lag is useful when it is split into queue, review, and correction stages and paired with a quality sample. The measure cannot prove that a reconciliation is accurate. It can show where the review process waits and what to fix.
For related workflows, see the vendor aging reconciliation brief and the bank reconciliation services overview.