Cash controls

Check a petty cash replenishment against the receipt pack

A practical petty cash replenishment guide that names the evidence, the approver, and the close condition for the current close cycle.

Check a petty cash replenishment against the receipt pack workflow illustration

Check a petty cash replenishment against the receipt pack

Name the decision and the queue owner

The petty cash replenishment note should separate the request, the decision that is still open, and the person who can close it. 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. Name the trigger that brought the case into the queue. The petty cash replenishment record should let a second reviewer rebuild the decision from the receipt pack and the custodian count.

Confirm that the request belongs in this queue before assigning an owner. Use the same definition across the queue and the review so the counts agree. Do not let a deadline expand a role beyond its written limit. Say which system of record governs if two sources disagree. A sample petty cash replenishment review checks the replenishment request, the receipt pack, and the surviving value in the petty cash log.

A clean-looking status is not evidence that the underlying work is correct. Record the requester and the promised response time. A short written rule is easier to test than an unwritten habit. If the team cannot reproduce the result from the record, the control is not finished. Apply the same petty cash replenishment test to the custodian count and to the value that survives in the petty cash log.

Map the source and the evidence trail

Attach the replenishment request and the receipt pack to the case, label their versions, and record the time each was observed. Record who supplied each document and when it arrived. Keep the original request so a later correction does not erase the reason for the work. If the team cannot reproduce the result from the record, the control is not finished. The petty cash replenishment case note should show what the petty cash log held at the time and who reviewed it.

Do not let a deadline expand a role beyond its written limit. Do not treat a screenshot as a substitute for the system record. Use the same definition across the queue and the review so the counts agree. Record who supplied each document and when it arrived. For petty cash replenishment, compare the replenishment request with the destination value rather than relying on a status label.

Use the same definition across the queue and the review so the counts agree. Mark missing evidence as missing, with a reason, rather than leaving a blank. The record should show the source, the decision, and the surviving value in one place. Keep the original request so a later correction does not erase the reason for the work. The petty cash replenishment close note cites the petty cash log, the approver, and the time of the final check.

Set the authority boundary

The controller owns the decision in petty cash replenishment; the preparer may compare, label, and route but may not approve the outcome. Write the authority limit into the case template. Preparation, comparison, and follow-up may sit with the assistant. A delegation needs a scope, a limit, an end date, and a named backup. In the petty cash replenishment queue, an item without a next action is treated as an exception.

A role change should trigger a review of queue access. Use the same definition across the queue and the review so the counts agree. A case that moves between owners should keep both owner periods visible. Do not let a deadline expand a role beyond its written limit. For petty cash replenishment, the working file keeps the replenishment request and the receipt pack beside the decision note.

If the team cannot reproduce the result from the record, the control is not finished. Name the backup owner and the coverage window in advance. A case that moves between owners should keep both owner periods visible. Keep the original request so a later correction does not erase the reason for the work. Every petty cash replenishment handoff names the controller and the field in the petty cash log that will confirm the change.

Run the daily handoff

End the petty cash replenishment shift with an owner, a next action, and a due time on every open case. If the team cannot reproduce the result from the record, the control is not finished. Use the same definition across the queue and the review so the counts agree. A handoff is complete only when the receiver acknowledges it. The petty cash replenishment reviewer records the approver sign-off, the owner, and the next action in one place.

Keep the queue view readable on one screen. Compare arrivals and completions, not only the backlog total. Check that the owner is actually available before assigning. Leave the next shift a queue that needs no chat history. A petty cash replenishment exception keeps the approver sign-off attached and routes the question to the controller.

Name the owner for every open item, including items waiting on someone else. Open the day with a queue pass by age, owner, and missing evidence. Assign every unowned case before new work begins. Use the same definition across the queue and the review so the counts agree. In this petty cash replenishment case, the record points to the petty cash log and names the controller as the decision owner.

Handle exceptions without rewriting history

If the receipt pack total differs from the replenishment amount, stop the dependent action and log the conflict in the petty cash log rather than choosing the more convenient value. Keep the original request so a later correction does not erase the reason for the work. Do not close a case just because the requester stopped asking. Name the owner for every open item, including items waiting on someone else. A sample petty cash replenishment review checks the replenishment request, the receipt pack, and the surviving value in the petty cash log.

If the team cannot reproduce the result from the record, the control is not finished. 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. Name the owner for every open item, including items waiting on someone else. Apply the same petty cash replenishment test to the custodian count and to the value that survives in the petty cash log.

Do not close a case just because the requester stopped asking. Check whether the exception came from a form, a rule, or a permission. Separate a data conflict from a policy conflict. A short written rule is easier to test than an unwritten habit. The petty cash replenishment record should let a second reviewer rebuild the decision from the receipt pack and the custodian count.

Close with a verified destination value

The final petty cash replenishment check compares the approver sign-off with the surviving value in the petty cash log; a status label alone is not a close. If the destination is another team, require an acknowledgment. A clean-looking status is not evidence that the underlying work is correct. Keep the prior value so the change can be explained. For petty cash replenishment, compare the replenishment request with the destination value rather than relying on a status label.

Do not mark complete until the check is repeatable by another reviewer. If the destination is another team, require an acknowledgment. If the team cannot reproduce the result from the record, the control is not finished. A closed status is not proof that the destination changed. The petty cash replenishment close note cites the petty cash log, the approver, and the time of the final check.

A case that moves between owners should keep both owner periods visible. If the team cannot reproduce the result from the record, the control is not finished. Compare the destination field, not only the activity log. Keep the original request so a later correction does not erase the reason for the work. The petty cash replenishment case note should show what the petty cash log held at the time and who reviewed it.

Review the pattern, not only the case

Review petty cash replenishment with a sample drawn from the queue export before the meeting, so the discussion cannot drift to memorable cases. Report age and dependency, not only the total count. Separate what was observed from what the team believes caused it. The record should show the source, the decision, and the surviving value in one place. For petty cash replenishment, the working file keeps the replenishment request and the receipt pack beside the decision note.

Report age and dependency, not only the total count. End the review with one change and one measure. A stable total can hide a growing tail. Set the next review date before the action begins. Every petty cash replenishment handoff names the controller and the field in the petty cash log that will confirm the change.

Report a null result as clearly as a positive one. Record the sample frame, the reviewer, and the criteria. Separate what was observed from what the team believes caused it. Set the next review date before the action begins. In the petty cash replenishment queue, an item without a next action is treated as an exception.

Keep the record ready for the next reviewer

Store sensitive petty cash replenishment evidence in the approved repository and keep only the reference and access path in the analysis note. A short written rule is easier to test than an unwritten habit. Use the same definition across the queue and the review so the counts agree. The record should show the source, the decision, and the surviving value in one place. A petty cash replenishment exception keeps the approver sign-off attached and routes the question to the controller.

Name the owner and the date beside each decision. Label the version of every file that can change. Use the same definition across the queue and the review so the counts agree. Keep the original request so a later correction does not erase the reason for the work. In this petty cash replenishment case, the record points to the petty cash log and names the controller as the decision owner.

If the team cannot reproduce the result from the record, the control is not finished. A short written rule is easier to test than an unwritten habit. 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. The petty cash replenishment reviewer records the approver sign-off, the owner, and the next action in one place.

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.