Petty Cash Replenishment: Is Your App Restoring a Fund or Paying the Same Receipts Again?

A petty cash tool should distinguish the authorised fund amount from the cash currently in the box. Replenishment restores money already used for reviewed expenses; it does not automatically increase the fund or create another payment to each original recipient. Before commissioning an internal app, agree how receipts move into a replenishment request and stop being available for a second request.

This is workflow planning, not an accounting policy. Your accountant must approve permitted spending, supporting evidence, postings, reconciliation and differences for your business. The institutional example below is not a rule for private companies or another jurisdiction.

Define the fund before designing the receipt screen

Identify the fund, currency, authorised amount and responsible custodian. Keep a change in the authorised amount separate from an ordinary replenishment. Otherwise a manager may appear to increase the permanent fund whenever staff ask for money to replace expenditure.

The University System of New Hampshire petty cash procedure describes an imprest fund as a fixed amount restored to its authorised level by replenishing expenditure. Its page displays a last-updated date of 22 June 2015. Use it as a concrete institutional control example, not as current tax advice or proof that its spending limits suit your company.

For a custom application, ask for distinct actions for establishing, replenishing, changing and closing a fund. Have finance decide which supporting approvals each action requires. A photograph of a receipt should not change the authorised amount.

Follow a receipt into exactly one replenishment

Record an actual cash disbursement with its recipient, purpose, amount and evidence. Then distinguish evidence awaiting review, accepted expenditure not yet included in a request, expenditure included in an outstanding request, and expenditure whose replenishment has arrived.

These are proposed design states, not documented software features of USNH. Their purpose is to stop an accepted receipt from being treated as fresh spending every time a new request is prepared.

If two staff members prepare requests together, the same expenditure must not become part of both. Specify what happens when a request is returned for correction: are its items still reserved, or explicitly released? Preserve the relationship between the original item and the replacement request rather than copying the receipt into an apparently unrelated expense.

Also distinguish replenishing the custodian's fund from reimbursing an employee. The person who originally received cash is not necessarily the recipient of the replenishment. Reusing an ordinary expenses payment screen without this distinction can send money to the wrong destination.

Show money in transit without counting it twice

The USNH procedure says cash on hand, receipts and replenishment requests in process should together equal the authorised fund amount. It also requires reconciliation before a replenishment request. This matters because sending a receipt to finance does not put cash back in the box.

In your app, show how each expenditure is represented while its request is outstanding. Do not count it both as an unsubmitted receipt and again as part of the pending request. Equally, an approved request must not immediately appear as physical cash received.

When replenishment arrives, record its confirmed receipt against that request and update the corresponding representation. A partial receipt should leave an explainable amount in transit. A missing confirmation needs investigation, not a new request that unknowingly duplicates the first. These partial-payment and reconciliation controls are requirements to agree and test, not claims about the university's systems.

Do not replenish an unexplained shortage into invisibility

Cash may be missing even when every recorded receipt is genuine. Keep a discrepancy separate from supported expenditure and send it to the person authorised to investigate. The USNH example directs an unbalanced fund to Accounting Services for assistance; its institutional contacts and procedures are not your escalation policy.

Agree with finance how unresolved differences affect a request. Do not create a fictitious receipt or silently increase the authorised fund to make the screen balance. A replenishment approval is not evidence explaining why cash disappeared.

Ask for a complete cycle in the demonstration

Use fictional records in your acceptance criteria. Demonstrate a disbursement, review, inclusion in one request, approval, actual receipt and the next replenishment cycle. The old receipt must remain traceable without becoming spendable evidence again.

Then try concurrent requests, a returned request, a partial replenishment and an unexplained shortage. Show a fund increase through its separate authorisation path. Bring your reviewed fund procedure to an internal workflow discussion. The useful deliverable is a continuing accountable fund, not merely a tidy receipt folder or a button labelled top up.