Petty Cash and Operational Cash Advances with ERP: Controls, Receipts, and Reconciliation

Petty cash looks trivial next to large purchases or customer receivables. Each transaction is small: parking fees, photocopies, water gallons, fuel for a courier's motorbike, or emergency supplies. But because it happens every day, across many branches, and is handled by many people, petty cash is often the area with the messiest receipts, unexplained differences, and the most tiring reconciliation work at month-end close.

The same applies to operational cash advances, money given to employees before an activity, such as buying project materials, business travel, or events. Without a system, advances are easily forgotten and sit as unsettled balances for months. This article covers how to manage both properly with an ERP: from policy, digital receipts, and approvals to replenishment, reconciliation, and automatic journal posting.

Summary

• Use an imprest system: a fixed petty cash balance, replenished by the amount of spending already accounted for
• Set per-transaction limits, spending categories, and a responsible custodian for each location
• Require digital receipts, a photo uploaded at the time of the transaction, not collected at month-end
• Advances must have a purpose, a settlement deadline, and a visible status
• Count cash regularly and reconcile physical balances with system records
• The ERP creates journals automatically so costs go straight to the right accounts and cost centers

Common petty cash problems

• Receipts lost, damaged, or illegible when collected at month-end
• Personal spending mixed with business spending
• Physical balance does not match records and nobody knows why
• Replenishment done without complete supporting documents
• Employee advances left unsettled for months
• Cost categories filled in carelessly, so branch expense reports cannot be trusted
• The finance team spends days consolidating spreadsheets from every branch

The imprest system: a simple, strong foundation

In an imprest system, each location receives a fixed petty cash balance, for example IDR 5 million. The custodian pays small expenses and keeps the receipts. When the balance runs low, the custodian requests replenishment equal to the total of documented spending. After replenishment, the balance returns to IDR 5 million.

The advantage is that a simple equation holds at all times: cash on hand plus receipts not yet reimbursed equals the imprest balance. Any difference is immediately visible.

Setting the balance

Calculate the average petty cash spending per week or two weeks at that location, and set a balance that covers that period. A balance that is too large increases risk; one that is too small makes replenishment too frequent.

The custodian

One person is responsible per cash box, with a backup for leave periods. Handover between custodians is done with a cash count and a record in the system.

Policies to write down

• Types of spending that may and may not be paid from petty cash
• A value limit per transaction; above it, the normal purchasing process applies, as explained in [purchase approval workflows](/blog/alur-approval-pembelian)
• A list of cost categories linked to accounts and cost centers
• Accepted evidence: receipts, invoices, or transfer proof, and what to do when there is none
• A deadline for submitting evidence after the transaction
• The cash count procedure and consequences of differences

A clear policy makes it easier for custodians to refuse inappropriate requests without looking unhelpful to colleagues.

Digital receipts and recording at the point of transaction

The key to tidy petty cash is recording when the transaction happens, not at month-end.

• The custodian photographs the receipt in a mobile or web app and enters the amount, date, category, and a short description
• OCR can read the amount and date from the receipt photo to speed up input; see [automating data entry from documents](/blog/otomatisasi-input-data-dari-dokumen)
• The system warns when the same receipt appears to have been uploaded before
• Physical receipts are still kept according to the archive policy, but day-to-day checks use the digital copy

This way, the petty cash balance in the system is always current, and finance can review spending at any time without waiting for envelopes of receipts from branches.

Approvals and replenishment

Transaction approval

For transactions below a certain limit, approval can be given after the fact by the location supervisor. For certain categories or larger amounts, approval is requested before payment.

Replenishment request

The custodian submits a replenishment request from the system. It lists the approved transactions with their evidence.

Finance review

Finance checks categories, evidence, and the reasonableness of amounts. Rejected transactions are returned with a reason.

Payment

Once approved, funds are transferred to the custodian or taken from the main cash. The system records expense journals by category and the reduction in the bank balance.

Operational cash advances

Advances differ from petty cash because they are given before an activity and must be settled afterward.

Request

The employee requests an advance with a purpose, an estimated cost breakdown, the activity date, and the related project or cost center.

Disbursement

After approval, money is disbursed and recorded as an employee receivable or advance on the balance sheet, not directly as an expense.

Settlement

After the activity, the employee uploads proof of spending. The system compares the total evidence with the advance.

• If evidence is less, the remaining money is returned or deducted according to policy
• If evidence is more, the difference is paid to the employee after approval

Deadlines and reminders

Set a settlement deadline, such as seven working days after the activity. The system sends automatic reminders and shows a list of overdue advances to supervisors and finance. Employees with unsettled advances can be restricted from requesting new ones.

The process is similar to employee expense reimbursement; the differences are covered in reimbursement and employee travel expense management.

Cash counts and reconciliation

Regular cash counts

Count the physical cash in the box regularly and by surprise, for example monthly and occasionally without notice. The count is recorded in the system by someone other than the custodian.

Reconciliation

• Physical cash plus transactions not yet replenished must equal the imprest balance
• Bank movements for replenishment must match approved requests; automatic bank matching is covered in [automatic bank reconciliation with ERP](/blog/rekonsiliasi-bank-otomatis-dengan-erp)
• The advance balance per employee on the balance sheet must match the list of open advances in the system

Handling differences

Differences are recorded with an explanation, approved by a supervisor, and posted to a cash difference account. Repeated differences at a particular location need investigation.

Automatic posting to the ERP

The biggest benefit of using an ERP is that journals do not have to be created by hand.

• Each spending category is linked to an expense account
• Location, department, or project is filled in automatically as the cost center
• Input tax is recorded when the receipt qualifies as a tax invoice
• Replenishment creates a journal from bank to petty cash
• Advances are recorded in an advance account and moved to expenses when settled

Every step has a record of who created, approved, and changed it, following the principles in audit trails and internal controls in ERP systems. As a result, petty cash no longer holds things up during month-end close.

Useful reports

• Petty cash spending by location, category, and month
• Replenishment frequency per location, to judge whether the imprest balance is right
• Open advances and how overdue they are
• Cash count differences per location and per custodian
• Categories with unusual spending growth

Per-location reports also help multi-branch companies compare operating costs; see multi-branch report consolidation.

Alternatives that reduce cash

Petty cash does not always have to be physical cash.

• Prepaid cards or company debit cards with per-card limits
• A company e-wallet for QR payments at small shops
• Direct payment by head office for regular suppliers

Cashless payments leave an automatic transaction trail but still need evidence and categories. Many companies use a combination: a small amount of cash for needs that are truly cash-only, and cards or e-wallets for the rest.

An illustration in a multi-branch company

Imagine a distribution company with eight branches, each holding petty cash. Before using a system, every branch sent a spreadsheet summary and an envelope of receipts to head office at month-end, and finance spent several days checking and journaling them.

After adopting the flow above, the first step is to standardize the list of cost categories and set an imprest balance per branch based on two weeks of average spending. Custodians photograph receipts at the time of the transaction, branch supervisors approve daily, and replenishment is requested when the balance falls to a third. Head-office finance only needs to review requests and exceptions, not every receipt. The results to monitor are the number of entries without evidence, cash count differences, and the time needed to close the petty cash accounts at month-end.

Common mistakes

• A petty cash balance that is too large, increasing the risk of loss and misuse
• Collecting receipts at month-end, so many are lost
• No deadline for settling advances
• Recording advances directly as expenses, making expense reports inaccurate
• Cash counts done only by the custodian
• Too many cost categories, or categories that are too general

Frequently asked questions

Do we still need petty cash if the company already uses digital payments?

Often yes, because some small expenses only accept cash. But the amount can be reduced sharply with company cards or e-wallets.

What if there is spending without a receipt?

Set a policy, such as a spending declaration form with supervisor approval up to a certain value. Limit the amount and frequency so it does not become a habit.

Do we need a special ERP module?

Many ERPs already have petty cash and advance features. What often needs adding is a mobile app for uploading evidence and an approval flow that matches the company structure.

Who should do the cash count?

Someone other than the custodian, such as finance staff or the location supervisor, with the custodian present during the count.

Conclusion

Petty cash and operational advances are small per transaction, but their impact on report quality and leakage risk is significant. With an imprest system, written policy, digital receipts at the time of the transaction, tiered approvals, settlement deadlines, regular cash counts, and automatic ERP journals, a company gains strong control without burdening employees. Start with one or two branches, measure differences and reconciliation time, then expand.