Reconciliation controls

Verify a bank reconciliation item before the close

A bank reconciliation item guide that names the evidence, the approver, and the close condition Revisit the rule with one current example before the next cycle.

Verify a bank reconciliation item before the close workflow illustration

Verify a bank reconciliation item before the close

Name the decision and the queue owner

For bank reconciliation item, the first step is to write the open decision, the requesting role, and the queue owner before anyone touches the bank reconciliation. Keep the original request so a later correction does not erase the reason for the work. The record should show the source, the decision, and the surviving value in one place. A short written rule is easier to test than an unwritten habit. In the bank reconciliation item queue, an item without a next action is treated as an exception.

State explicitly what is in scope and what is out of scope for the case. Name the trigger that brought the case into the queue. A clean-looking status is not evidence that the underlying work is correct. Do not let a deadline expand a role beyond its written limit. For bank reconciliation item, the working file keeps the bank statement and the ledger balance beside the decision note.

Separate the request from the decision, because a complete request is not an approval. Note the observation window; a case without a period cannot be compared later. Record the queue and the entity so the case cannot drift into another team's work. Record the requester and the promised response time. Every bank reconciliation item handoff names the controller and the field in the bank reconciliation that will confirm the change.

Map the source and the evidence trail

Map each bank reconciliation item value to its source: the bank statement for the request, the ledger balance for the check, and the bank reconciliation for the surviving destination value. Do not treat a screenshot as a substitute for the system record. A clean-looking status is not evidence that the underlying work is correct. The record should show the source, the decision, and the surviving value in one place. The bank reconciliation item reviewer records the reviewer sign-off, the owner, and the next action in one place.

Link each value to the field or page that supports it. A short written rule is easier to test than an unwritten habit. Preserve a conflicting value instead of overwriting the first one. State whether the evidence is confirmed, inferred, or unavailable. A bank reconciliation item exception keeps the reviewer sign-off attached and routes the question to the controller.

The next reviewer should not have to ask which document is authoritative. If the team cannot reproduce the result from the record, the control is not finished. Preserve a conflicting value instead of overwriting the first one. Keep the original document and the working copy in separate states. In this bank reconciliation item case, the record points to the bank reconciliation and names the controller as the decision owner.

Set the authority boundary

When bank reconciliation item changes a record in the bank reconciliation, the controller approves and the preparer records the action; the two roles stay separate. When urgency presses against the limit, pause and route the decision. A complete packet is not an approval; the decision needs a person and a timestamp. Name the owner for every open item, including items waiting on someone else. A sample bank reconciliation item review checks the bank statement, the ledger balance, and the surviving value in the bank reconciliation.

A short written rule is easier to test than an unwritten habit. Keep emergency authority narrow and followed by a review note. When urgency presses against the limit, pause and route the decision. The next reviewer should not have to ask which document is authoritative. Apply the same bank reconciliation item test to the reconciling item and to the value that survives in the bank reconciliation.

Keep the original request so a later correction does not erase the reason for the work. Approval, payment, records disposition, and policy exceptions stay with the named owner. Use the same definition across the queue and the review so the counts agree. If two roles share a queue, mark which one decides each item. The bank reconciliation item record should let a second reviewer rebuild the decision from the ledger balance and the reconciling item.

Run the daily handoff

Each morning the team reviews bank reconciliation item arrivals, items waiting on the controller, and items ready for a verified close. The record should show the source, the decision, and the surviving value in one place. The next reviewer should not have to ask which document is authoritative. A handoff is complete only when the receiver acknowledges it. For bank reconciliation item, compare the bank statement with the destination value rather than relying on a status label.

Leave the next shift a queue that needs no chat history. Log the handoff time when a case crosses a shift. Escalate an item that has waited past the written threshold. Do not let a deadline expand a role beyond its written limit. The bank reconciliation item close note cites the bank reconciliation, the approver, and the time of the final check.

Keep the original request so a later correction does not erase the reason for the work. Assign every unowned case before new work begins. Keep the queue view readable on one screen. Record one next action and one due time per open item. The bank reconciliation item case note should show what the bank reconciliation held at the time and who reviewed it.

Handle exceptions without rewriting history

When an unreconciled item carries into the next period, preserve both versions, record the observation times, and route one answerable question to the controller. A case that moves between owners should keep both owner periods visible. Use the same definition across the queue and the review so the counts agree. A short written rule is easier to test than an unwritten habit. For bank reconciliation item, the working file keeps the bank statement and the ledger balance beside the decision note.

Keep the original request so a later correction does not erase the reason for the work. A case that moves between owners should keep both owner periods visible. Keep the failed attempt and the correction in the same history. Check whether the exception came from a form, a rule, or a permission. Every bank reconciliation item handoff names the controller and the field in the bank reconciliation that will confirm the change.

A case that moves between owners should keep both owner periods visible. Separate a data conflict from a policy conflict. Preserve both values and the time each was observed. A short written rule is easier to test than an unwritten habit. In the bank reconciliation item queue, an item without a next action is treated as an exception.

Close with a verified destination value

Record the bank reconciliation item close reason, the approver, and the surviving evidence reference in the same case note. Tie the close note to the original request and the final evidence. A closed status is not proof that the destination changed. Do not mark complete until the check is repeatable by another reviewer. A bank reconciliation item exception keeps the reviewer sign-off attached and routes the question to the controller.

Record the close reason with the same codes used in the exception queue. Reopen the case when the destination value is disputed. Record the approximate value, the approver, and the final check time. Keep the original request so a later correction does not erase the reason for the work. In this bank reconciliation item case, the record points to the bank reconciliation and names the controller as the decision owner.

Compare the destination field, not only the activity log. A closed status is not proof that the destination changed. Name the owner for every open item, including items waiting on someone else. Tie the close note to the original request and the final evidence. The bank reconciliation item reviewer records the reviewer sign-off, the owner, and the next action in one place.

Review the pattern, not only the case

Report bank reconciliation item open cases by age and dependency, not only the total, because a stable total can hide an aging tail. Do not let a deadline expand a role beyond its written limit. Use the same definition across the queue and the review so the counts agree. Keep the prior procedure available for comparison. Apply the same bank reconciliation item test to the reconciling item and to the value that survives in the bank reconciliation.

Choose the sample from the export before the meeting. Separate what was observed from what the team believes caused it. Keep the prior procedure available for comparison. Check whether the definition changed during the period. The bank reconciliation item record should let a second reviewer rebuild the decision from the ledger balance and the reconciling item.

If the team cannot reproduce the result from the record, the control is not finished. Name the owner for every open item, including items waiting on someone else. Keep the original request so a later correction does not erase the reason for the work. Use case-level review to explain an outlier before calling it a trend. A sample bank reconciliation item review checks the bank statement, the ledger balance, and the surviving value in the bank reconciliation.

Keep the record ready for the next reviewer

The bank reconciliation item working paper should show the request, the source, the decision, the action, and the surviving value without a private inbox. A clean-looking status is not evidence that the underlying work is correct. Keep the source reference and the coded value in the same row. Name the owner for every open item, including items waiting on someone else. The bank reconciliation item close note cites the bank reconciliation, the approver, and the time of the final check.

Use the same definition across the queue and the review so the counts agree. Label the version of every file that can change. Archive the extract with the study so it can be repeated. The next reviewer should not have to ask which document is authoritative. The bank reconciliation item case note should show what the bank reconciliation held at the time and who reviewed it.

Write the note so a reviewer can reconstruct the decision without a meeting. A short written rule is easier to test than an unwritten habit. Avoid a private second version in a personal document. Keep the source reference and the coded value in the same row. For bank reconciliation item, compare the bank statement with the destination value rather than relying on a status label.

This note is operational guidance, not accounting, tax, legal, or security advice. Use the back office support service and read the GAO Green Book before turning the routine into policy.