Employee spend management: one process for cards, reimbursements, petty cash and advances

When internal audit at a pharmaceutical distributor in Semarang reviews one area sales manager’s spend for October, two records stand out. The corporate card statement shows a client dinner on 8 October, Rp 2,350,000, matched to the card slip and approved by finance during the card reconciliation. The reimbursement claims for the same month show the same dinner, Rp 2,350,000, with the restaurant’s printed bill attached, approved by the regional manager and paid. The company paid for one dinner twice.

Nobody skipped a step. Finance reconciled the card, the regional manager approved the claim and the branch admin kept a tidy petty cash book. Each of them checked their own channel, and each channel was in order. Put side by side, the same month holds two more expenses paid twice: a hotel night settled against a cash advance and then claimed again, and a taxi paid from petty cash and then claimed again.

That’s the cost of running four ways to pay as four processes. Employee spend management brings them together: one policy, one approval matrix and one record per employee, whichever way the money left. This guide covers how the four methods differ, a worked example of that sales manager’s month, the gaps that separate processes leave and how to close them.

What is employee spend management?

Employee spend management is controlling all the money employees spend on the company’s behalf, through every route it can take: corporate cards, out-of-pocket reimbursements, cash advances and petty cash. It covers the same steps as expense management (capture, check, approve, pay and record), applied to every payment method at once rather than one at a time.

The idea behind it is simple. A client dinner is the same expense whether it was paid on a card, from the petty cash box or with the employee’s own money. It should meet the same policy, go to the same approver and be checked against everything else the same employee has spent. The payment method only changes who paid first, and who needs to be paid back.

Four ways to pay, four control points

Each method usually has its own control, run by its own people at its own time:

Method	Money leaves	Usually checked
Reimbursement	After approval, to the employee	By the manager, on the claim
Cash advance	Before the spend, to the employee	When the advance is settled
Corporate card	At the till, to the merchant	At month-end, against the statement
Petty cash	At the cash box, to whoever asks	By the custodian, when the box is topped up

Each control is reasonable on its own, and each answers its own question. Card reconciliation asks whether every card line has a receipt. The claim review asks whether every claim has one. The petty cash count asks whether cash and receipts add up to the float. None of them asks whether this expense has already been paid some other way, because none of them can see the others.

A worked example: one employee’s October

Here is the area sales manager’s October, gathered from the four places it was recorded:

Recorded in	Lines	Rp ’000
Corporate card statement	18	9,640
Reimbursement claims	11	4,215
Cash advance settlement	6	3,880
Branch petty cash book	4	620
Total	39	18,355

All four were reviewed and approved. Sorted by date and amount in one list, three expenses appear twice:

• The client dinner, Rp 2,350,000. On the card, matched to the card slip, and in a claim with the printed bill. Two different documents for one purchase, so a check that compares receipts finds nothing.
• A hotel night in Solo, Rp 740,000. In the settlement of a Rp 4,000,000 advance for the trip, with the hotel’s invoice, and in a claim with the booking app’s confirmation. The advance was settled with Rp 3,880,000 of receipts and Rp 120,000 returned, so it looked closed.
• A taxi to the airport, Rp 185,000. Paid from the branch petty cash on a handwritten receipt, and claimed again with the ride-hailing app’s e-receipt.

That’s Rp 3,275,000 paid twice in one month, for one employee. Most duplicates like these are honest mistakes by someone with four places to submit spend and two documents for many purchases. Either way the money has gone, and none of it was hidden: it sat in four files, each reviewed by someone who only had one of them.

Where separate processes leave gaps

• Each channel checks only itself. The duplicate check, if there is one, looks for the same receipt among claims, not against card lines, advance settlements or the petty cash book.
• Two documents for one purchase. A card slip and a printed bill, a hotel invoice and a booking confirmation, a handwritten receipt and an app’s e-receipt. Comparing receipt images or numbers misses them; comparing amount, date and merchant across every channel catches them.
• A different policy for each method. The meal cap is applied to claims, but nobody checks card lines against it, and petty cash has no receipt threshold at all.
• A different approver for each method. Claims go through the approval matrix, card lines are approved by finance at reconciliation and petty cash by whoever holds the box, so no manager sees the whole of their team’s spend.
• Different timing. Card statements arrive weeks later, petty cash is topped up when the box runs low and advances are settled after the trip, so one expense can reach two channels in different months.
• Budgets that only see part of the spend. A department’s travel budget shows approved claims as they come in, but card and petty cash spend only at month-end, so it looks under budget until it isn’t.
• Leavers settled one channel at a time. When someone resigns, the open advance is settled from the final pay, but nobody checks their unreconciled card lines or petty cash IOUs.

Employee spend in Indonesia

• Petty cash at every branch. Branch and site offices often run their own petty cash (kas kecil) for tolls, parking, couriers and small purchases, recorded in a book or spreadsheet that head office sees only when the box is topped up. Bring those payouts into the same record as the rest of the spend, line by line, not as one top-up total.
• Handwritten receipts and no receipts. A handwritten receipt (kuitansi) from a small shop, or no receipt at all for street parking, is common and easy to use twice. Set a small amount below which a signed declaration is accepted, and check those lines for duplicates like any other.
• Advances for trips and projects. Cash advances (kasbon) are common for travel and site work, and the receipts that settle them are the ones most likely to turn up again in a claim. Settle each advance against the same record as the employee’s claims.
• Tax documents don’t depend on the payment method. Input VAT (PPN masukan) can only be credited with a complete and correct faktur pajak, whether the purchase was paid by card, from petty cash or out of pocket. Ask for it when the purchase is made, since it’s hard to get afterwards.
• Final pay. When an employee leaves, settle everything they owe or are owed in one place before the final pay: open advances, card lines, personal charges, petty cash IOUs and unpaid claims. What can be deducted from final pay is regulated, so agree it in writing in advance and check the wording with HR and your legal adviser.

Signs your spend controls are split by payment method

You probably need to bring your spend controls together if any of these sound familiar:

• Card lines, claims, advances and petty cash are reviewed by different people, in different files.
• Nobody can say what one employee spent last month without opening three or four of them.
• The duplicate check covers claims, but not card lines, advances or petty cash.
• The meal cap is checked on claims, but not on card spend.
• Petty cash is approved by whoever holds the box.
• Budgets show card and petty cash spend only after month-end.
• Leavers’ advances are settled, but nobody checks their card or petty cash.

A dinner is a dinner, whichever way it was paid. The controls should follow the expense, not the payment method.

How to bring them into one process

1. List every way money leaves for employee spend. Cards, including the directors’, reimbursements, advances and every petty cash box, and the less obvious ones: e-money and fuel cards, or an account at a travel agent that staff book against.
2. Write one policy for all of them. The same limits, receipt rules and categories whichever way the expense is paid, with a short section for what’s specific to each method. It belongs in your expense policy.
3. Keep one record per employee. Card lines, claims, advance settlements and petty cash payouts in the same history, coded the same way, so anyone can sort one person’s month by date.
4. Check duplicates across all four, on what was bought. Match on amount, date and merchant, not only on the receipt image or number, so a card slip and a printed bill for the same dinner are caught. The expense fraud red flags apply across channels too.
5. Use one approval matrix. A card line goes to the same approver as a claim of the same amount, through your approval matrix, and nobody approves their own spend.
6. Run petty cash as a fixed float. The custodian holds a set amount (an imprest system), payouts are recorded as they happen and the box is topped up by exactly the approved receipts, so cash plus receipts always equals the float.
7. Settle in one place. Net advances against claims, recover personal card charges and clear petty cash IOUs per employee, every month and when someone leaves.

---

How Procapy helps

In Capy Expense, reimbursements, cash advances and card spend live in one place, per employee and per report, so an employee’s out-of-pocket, advance and card spend are in the same claim history. Card transactions are imported into Capy and matched to the receipts employees capture, then tagged, policy-checked and approved like any other expense. Advances are requested, approved and paid in the same flow, then settled automatically against the expense report that follows.

Before a report can be submitted, every line is checked against your expense policy: per-diem and meal caps, receipt thresholds, allowed categories and budget, by employee grade, entity or country. Duplicate receipts are caught across employees, reports and card feeds, and every claim is matched on vendor, amount, invoice number and date against everything already in the system, across entities and across expenses and AP, with the original shown to the approver alongside. ProcApprove routes every report through your approval matrix, and nobody can approve their own claim.

Approved claims are paid in one reimbursement run with open advances netted, and posted to Dynamics, SAP, Xero, QuickBooks or ABSS with the receipts attached. Before a period is locked, a close checklist lists unsubmitted card transactions and unapproved claims. The fraud and risk page covers the duplicate checks in more detail. Book a 30-minute walkthrough, bring a month of expense claims, and we’ll run them through the duplicate, mismatch and policy checks live.