Cash controls

Review a petty cash reconciliation with receipts

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

Review a petty cash reconciliation with receipts workflow illustration

Review a petty cash reconciliation with receipts

Name the decision and the queue owner

The petty cash reconciliation note should separate the request, the decision that is still open, and the person who can close it. Separate the request from the decision, because a complete request is not an approval. Record the requester and the promised response time. Write the decision in one sentence so the reviewer knows what would count as an answer. Apply the same petty cash reconciliation test to the custodian note and to the value that survives in the petty cash log.

A case that moves between owners should keep both owner periods visible. Name the person who can close the question and the date by which the answer is needed. Name the trigger that brought the case into the queue. Separate the request from the decision, because a complete request is not an approval. The petty cash reconciliation record should let a second reviewer rebuild the decision from the receipts and the custodian note.

Use the same definition across the queue and the review so the counts agree. A clean-looking status is not evidence that the underlying work is correct. Distinguish a new request from a correction to an earlier one. Write the decision in one sentence so the reviewer knows what would count as an answer. A sample petty cash reconciliation review checks the cash count, the receipts, and the surviving value in the petty cash log.

Map the source and the evidence trail

Attach the cash count and the receipts to the case, label their versions, and record the time each was observed. The next reviewer should not have to ask which document is authoritative. Preserve a conflicting value instead of overwriting the first one. Name the repository where sensitive evidence is held. The petty cash reconciliation close note cites the petty cash log, the approver, and the time of the final check.

If the team cannot reproduce the result from the record, the control is not finished. A case that moves between owners should keep both owner periods visible. Keep a version label on every file that can change. Record who supplied each document and when it arrived. The petty cash reconciliation case note should show what the petty cash log held at the time and who reviewed it.

Keep the original document and the working copy in separate states. Compare the source and the destination values before drawing a conclusion. State whether the evidence is confirmed, inferred, or unavailable. A short written rule is easier to test than an unwritten habit. For petty cash reconciliation, compare the cash count with the destination value rather than relying on a status label.

Set the authority boundary

The office manager owns the decision in petty cash reconciliation; the preparer may compare, label, and route but may not approve the outcome. A clean-looking status is not evidence that the underlying work is correct. Name the owner for every open item, including items waiting on someone else. A complete packet is not an approval; the decision needs a person and a timestamp. Every petty cash reconciliation handoff names the office manager and the field in the petty cash log that will confirm the change.

A short written rule is easier to test than an unwritten habit. Do not let a familiar requester bypass the approval boundary. A role change should trigger a review of queue access. Write the authority limit into the case template. In the petty cash reconciliation queue, an item without a next action is treated as an exception.

Record rejected and deferred requests as well as approvals. The next reviewer should not have to ask which document is authoritative. Do not let a deadline expand a role beyond its written limit. Approval, payment, records disposition, and policy exceptions stay with the named owner. For petty cash reconciliation, the working file keeps the cash count and the receipts beside the decision note.

Run the daily handoff

End the petty cash reconciliation shift with an owner, a next action, and a due time on every open case. Open the day with a queue pass by age, owner, and missing evidence. A case that moves between owners should keep both owner periods visible. Keep the queue view readable on one screen. In this petty cash reconciliation case, the record points to the petty cash log and names the office manager as the decision owner.

A case with no next action is an exception even if it says in progress. Leave the next shift a queue that needs no chat history. Do not let a status update stand in for a verified event. Open the day with a queue pass by age, owner, and missing evidence. The petty cash reconciliation reviewer records the reviewer, the owner, and the next action in one place.

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. The record should show the source, the decision, and the surviving value in one place. A clean-looking status is not evidence that the underlying work is correct. A petty cash reconciliation exception keeps the reviewer attached and routes the question to the office manager.

Handle exceptions without rewriting history

If the count differs from the receipts with no explanation, stop the dependent action and log the conflict in the petty cash log rather than choosing the more convenient value. When access blocks the work, name the system, role, and approver. The next reviewer should not have to ask which document is authoritative. A short written rule is easier to test than an unwritten habit. The petty cash reconciliation record should let a second reviewer rebuild the decision from the receipts and the custodian note.

If the exception repeats, give it a reason code. When access blocks the work, name the system, role, and approver. Preserve both values and the time each was observed. The record should show the source, the decision, and the surviving value in one place. A sample petty cash reconciliation review checks the cash count, the receipts, and the surviving value in the petty cash log.

A short written rule is easier to test than an unwritten habit. If the exception repeats, give it a reason code. Do not rewrite the earlier record to match the later answer. Do not close a case just because the requester stopped asking. Apply the same petty cash reconciliation test to the custodian note and to the value that survives in the petty cash log.

Close with a verified destination value

The final petty cash reconciliation check compares the reviewer with the surviving value in the petty cash log; a status label alone is not a close. Do not mark complete until the check is repeatable by another reviewer. Do not let a deadline expand a role beyond its written limit. Keep the original request so a later correction does not erase the reason for the work. The petty cash reconciliation case note should show what the petty cash log held at the time and who reviewed it.

Record the approximate value, the approver, and the final check time. Tie the close note to the original request and the final evidence. Test one closed case by rebuilding it from the evidence map. Keep the prior value so the change can be explained. For petty cash reconciliation, compare the cash count with the destination value rather than relying on a status label.

If the team cannot reproduce the result from the record, the control is not finished. Do not mark complete until the check is repeatable by another reviewer. Keep the prior value so the change can be explained. The next reviewer should not have to ask which document is authoritative. The petty cash reconciliation close note cites the petty cash log, the approver, and the time of the final check.

Review the pattern, not only the case

Review petty cash reconciliation with a sample drawn from the queue export before the meeting, so the discussion cannot drift to memorable cases. Set the next review date before the action begins. Separate what was observed from what the team believes caused it. Keep the prior procedure available for comparison. In the petty cash reconciliation queue, an item without a next action is treated as an exception.

Use case-level review to explain an outlier before calling it a trend. If the team cannot reproduce the result from the record, the control is not finished. Keep the prior procedure available for comparison. Report a null result as clearly as a positive one. For petty cash reconciliation, the working file keeps the cash count and the receipts beside the decision note.

End the review with one change and one measure. Choose the sample from the export before the meeting. A stable total can hide a growing tail. Name the owner for every open item, including items waiting on someone else. Every petty cash reconciliation handoff names the office manager and the field in the petty cash log that will confirm the change.

Keep the record ready for the next reviewer

Store sensitive petty cash reconciliation evidence in the approved repository and keep only the reference and access path in the analysis note. Name the owner for every open item, including items waiting on someone else. Do not store credentials or unnecessary personal data in the case. A case that moves between owners should keep both owner periods visible. The petty cash reconciliation reviewer records the reviewer, the owner, and the next action in one place.

Do not let a deadline expand a role beyond its written limit. Keep the source reference and the coded value in the same row. Use the approved repository for sensitive content. The next reviewer should not have to ask which document is authoritative. A petty cash reconciliation exception keeps the reviewer attached and routes the question to the office manager.

Avoid a private second version in a personal document. Do not let a deadline expand a role beyond its written limit. Keep the note short enough to read with the case. Make the handoff readable by the next shift and the next auditor. In this petty cash reconciliation case, the record points to the petty cash log and names the office manager as the decision owner.

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.