Run a weekly quality sample on bank reconciliation

Published October 27, 2026

The operational risk around bank reconciliation

The risk around bank reconciliation is not that staff forget a task; it is that the record can look complete even when the bill image was never checked against the receipt inbox. When the record cannot show what changed, small business bookkeeping teams cannot separate a process problem from a person problem, so coaching becomes guesswork. The operating standard should distinguish preparation from approval and show both in the same bank reconciliation trail. The operator should be able to point to the exact field in the receipt inbox that will change, not only to the message that requested the change.

When QuickBooks support work scales, bank reconciliation becomes a coordination problem: several people can touch the same request without anyone seeing the full sequence of source, decision, action, and confirmation. That gap creates rework, weakens correction rate, and makes it hard to tell whether the outcome was authorized or merely convenient. The control should make the bank reconciliation path readable from the request, the vendor W-9, the named owner, the decision, and the confirmation in the vendor master. When the team reviews correction rate, it should ask which cases are excluded from the count and why.

Evidence map for bank reconciliation

Start the evidence map by naming the field in the vendor master that the bank reconciliation action is supposed to change. The reviewer should be able to open the vendor W-9 from the case without searching a personal drive or asking for a screenshot. Resolve the conflict by naming the authoritative source, the owner who decided, and the correction applied to the vendor master. A source that cannot be opened by the reviewer is not a usable source, even if the operator can see it on their screen.

For bank reconciliation, the governing source is the close checklist; a note in the queue is only a pointer to that source. When two approval email versions conflict, preserve both and route the conflict to business owner; do not silently choose the cleaner-looking value. A conflict is not a reason to rewrite history; it is a reason to show the reviewer exactly where the bank reconciliation record stopped agreeing with itself. The evidence map should show which fields are required, which are conditional, and which may be marked unavailable.

Start the evidence map by naming the field in QuickBooks Online that the bank reconciliation action is supposed to change. The reviewer should be able to open the reconciliation report from the case without searching a personal drive or asking for a screenshot. If the reconciliation report is incomplete, the safest next step may be to pause bank reconciliation rather than fill the gap with a plausible assumption. If the reconciliation report contains personal or confidential data, use the approved access path and record only the reference in the queue.

Decision rights for bank reconciliation

Write the bank reconciliation boundary in plain language: which systems the operator may touch, which fields may change, and which questions must go back to bookkeeper. A complete packet is not an approval; the decision needs a named person, a time, and a scope that matches the approval email. Review a sample of approvals each month to confirm that the named role still matches the current QuickBooks support process. A standing approval should have a limit, a review date, and a clear description of the bank reconciliation work it covers.

Name the role that can approve bank reconciliation before the work begins; a shared inbox can receive the request, but it cannot own the decision. A decision right is not the same as system access; the operator may be able to edit a field without being authorized to decide its value. If the approval arrives after the action, mark the sequence honestly and route the late approval to the owner for a correction decision. If controller delegates approval, record the delegate, the scope, the start time, and the end time.

Daily workflow for bank reconciliation

If the queue cannot be reconciled in the morning, record the gap and assign an owner before starting new bank reconciliation work. Keep the bank reconciliation case note short enough to read during the day and specific enough to survive a weekly review. The end-of-day review should show what was completed, what is blocked, who owns the next step, and which reconciliation report is still missing. A daily stand-up should review exceptions and aging items, not read every completed ticket aloud.

Open the bank reconciliation queue in the bank feed and mark every item with the current owner, the next action, and the time it is due. Keep the bank reconciliation case note short enough to read during the day and specific enough to survive a weekly review. Close the day by checking that each completed bank reconciliation has a destination update in the bank feed and a confirmation for the requester. A daily stand-up should review exceptions and aging items, not read every completed ticket aloud.

The daily bank reconciliation routine should begin with a queue count by owner and age, not with the easiest request in the inbox. A status update should describe a verifiable event, not a feeling about progress; link the event to the bill pay system or the missing receipt note. The end-of-day review should show what was completed, what is blocked, who owns the next step, and which missing receipt note is still missing. Use the same bank reconciliation status values across owners so the daily count means the same thing to everyone.

Exception handling for bank reconciliation

Classify exceptions by whether the work can continue, must pause, or needs an immediate owner decision. Send the exception to the named owner with the journal memo attached and a specific question, not a general request to review. If the exception affects unreconciled line, pause the dependent action until bookkeeper decides and the decision is recorded. If the same exception appears in three cases, review the intake form or the journal memo requirement.

When wrong vendor is involved, use the highest escalation path even if the bank reconciliation request looks routine. The packet should state what the operator did not do and why, so the owner can see the boundary that was preserved. When the request conflicts with policy or the approved scope, the operator should route it rather than negotiate a workaround in the queue. If the same exception appears in three cases, review the intake form or the missing receipt note requirement.

When missing receipt is involved, use the highest escalation path even if the bank reconciliation request looks routine. The packet should state what the operator did not do and why, so the owner can see the boundary that was preserved. A stop is not a failure of service; it is the control working before the error reaches vendor. When a case is blocked by access, record the system, the role requested, and the person who can grant it.

Close and verify bank reconciliation

The close condition should name the field, the expected value, the approver, and the time of the final check. If the destination value differs from the approved value, keep the case open and route the variance. When the same bank reconciliation reopens repeatedly, review the intake, the missing receipt note, and the approval boundary rather than only the final step. If the final value differs from the approved value, record the variance and the person who accepted it.

Use the same close definition for routine and exception cases so the missing receipt rate does not improve by redefining completion. The reviewer should be able to trace the bank reconciliation from the original request to the final field without opening a personal inbox. Track reopen rate with a denominator; a raw count without the number of closures overstates or hides the problem. Use a consistent close reason so the monthly review can separate completed work from cancelled or duplicate requests.

Review cadence for bank reconciliation

For QuickBooks support work, review the oldest open bank reconciliation and the most recently closed one side by side. Use the correction log to estimate rework, and separate corrections caused by source errors from those caused by judgment. If the gap is caused by an unavailable bookkeeper, add a backup decision path rather than letting the bank reconciliation queue wait indefinitely. Keep a short action log with the decision, the owner, the due date, and the next sample that will test it.

Record the sample frame, the reviewer, the criteria, and the result before discussing the cause. Review the exception mix each month; a rising missing-evidence count may be an intake problem rather than an operator problem. If the gap is caused by an unavailable controller, add a backup decision path rather than letting the bank reconciliation queue wait indefinitely. Keep a short action log with the decision, the owner, the due date, and the next sample that will test it.