Expense approvals on WhatsApp: how to stop losing track
A field worker asks for money to buy materials. A manager approves it in a chat. Finance sends the advance. Later, nobody can find the receipt or explain what happened to the unused balance.
WhatsApp can be a convenient way to communicate. The problem starts when the request, approval, transfer and receipt live in separate conversations with no agreed record linking them.
That can delay work and leave money unaccounted for. You can begin by making the steps clear.
Give every request a reference
Use a simple private register. Record the request reference, date, person, job, reason, amount and currency.
Attach or link the approved supporting information where staff have the right access. Do not collect more personal or financial information than the task requires.
If you use more than one currency, keep the amounts separate unless your finance person has agreed how to convert them. A total that mixes currencies will not help you make a sound decision.
Decide who can approve what
Write down who can request an expense, who approves it and who releases the money. Agree the spending limits and what needs further approval.
A request is not approval. Approval is not proof that money was sent. A payment notification is not proof that the expense has been fully accounted for.
Keep those events separate in the record. Where practical, have someone other than the requester review the expense and payment.
Track the advance until it is closed
For each approved advance, record:
- The amount authorised.
- The amount actually sent and its payment reference.
- The receipts or other evidence submitted.
- The spending accepted after review.
- Any balance that must be returned or additional cost that needs approval.
- Who checked the record and when it was closed.
Do not delete an original entry to hide a correction. Record the correction so the finance person can follow what changed.
For example, imagine a maintenance team receives an advance for a site visit. The worker buys the approved materials, submits the receipts and returns the unused balance. Finance checks the records and confirms the return before closing the request.
This is an illustration of the process, not evidence that a particular system has prevented fraud or saved money.
Test the rules before adding automatic actions
Start with a form and register if that is enough. Test a normal request, a missing receipt, a repeated submission and an amount above the approval limit.
A system can remind staff about an outstanding receipt or show which approvals are waiting. Keep payment release and unusual spending with the people authorised to decide. A receipt image alone should not automatically approve a payment.
Agree what happens when internet access is unavailable. Staff may need a safe temporary record that they enter and check later. They should not lose essential information because a form would not load.
Measure control and delay
Track how long approvals wait, how many advances remain open and the value of confirmed unused balances returned. Also record the time finance spends reconciling requests, payments and evidence.
Compare those figures before and after a trial. A returned balance is money recovered, not a new sale. Faster approvals may help work start sooner, but do not count that as extra profit unless the business can show the link.
Use your accountant's guidance for the records, tax treatment and retention rules your business needs. A request register is not a replacement for your accounts.
Explore the working example
TMG's Field Expense & Approval Control demo shows requests, approvals, simulated advances and closure with fictional data. Its records stay in your browser. It does not move real money or provide production security. Do not enter private information.
To discuss a similar process, use the enquiry link in the TMG demo section.