Monday, October 19, 2026

How to speed up employee reimbursements: where the weeks go, and how to get them back

Procapy Team

On a Thursday in early September, a sales manager in Bandung pays for a client dinner on a personal credit card: Rp 1,850,000. The money comes back on 28 October, 55 days later. In between, the card bill falls due, the manager asks finance four times whether the claim has been paid, and new colleagues get some advice: never pay for anything you can’t afford to wait for.

Nobody in the process was slow on purpose. The claim spent less than half an hour, in total, in anyone’s hands. The rest of the 55 days was waiting: for a receipt to turn up, for a manager to get back from a trip, for a rejection to be fixed and for the next monthly payout.

This guide explains the reimbursement process, a worked example of where one claim’s 55 days went, why reimbursements stall and how to get a claim that’s in order paid within a week.

What is the reimbursement process?

The reimbursement process is how an employee who pays for a business cost with their own money gets it back: from the purchase, through the claim, the checks and the approvals, to the transfer into their account. The number that matters is the reimbursement cycle time: the days from the purchase, or from submission, to the money arriving.

It’s one of four ways employees spend company money, and each has its own process:

Reimbursement: the employee pays, claims and is paid back.
Cash advance: the company pays first, and the employee settles the advance with receipts afterwards.
Corporate card: the company’s card pays, and the employee attaches the receipt to each transaction.
Allowance or per diem: a fixed amount set by policy, with no receipt for each purchase.

Reimbursement is the one where the employee carries the cost while the company decides, which is why its speed matters more than the others’.

The reimbursement process, step by step

Spend. The employee pays with their own money, often on a personal credit card or a mobile wallet.
Capture. The receipt is photographed or forwarded, ideally on the spot, before it’s lost or fades.
Submit. The employee completes the claim with the category, the business purpose and anything else the policy requires, such as attendees for a client meal.
Approve. The manager, or whoever the approval rules name, checks that the cost was for the business and signs it off.
Check. Finance checks the claim against the receipt and the expense policy, and codes it for the ledger.
Pay. Approved claims are paid into the employee’s account, usually in a batch on a fixed day.
Record. The claim is posted to the accounting system, with its receipt and approvals attached.

A worked example: one claim, 55 days

Here is the client dinner from the opening. The company pays reimbursements with salaries on the 28th, for claims approved by finance by the 25th:

Date	What happened	Days
3 Sep	Client dinner, Rp 1,850,000 on a personal card
10 Sep	Employee finds the receipt and submits the claim	7
17 Sep	Manager approves, back from a week of travel	7
22 Sep	Finance rejects it: “not in line with policy”	5
24 Sep	Employee works out why and adds the attendees	2
28 Sep	Manager approves again	4
30 Sep	Finance approves, five days after the cut-off	2
28 Oct	Paid with October’s salaries	28
Total		55

Where the time went:

Seven days before the claim existed. The receipt was in a jacket pocket. Every day between spending and submitting is a day nobody else can act on.
Seven days with an approver who was away. The manager was travelling and didn’t approve from their phone. Nobody else was allowed to.
A rejection that cost a month. The policy requires attendees for client meals, but nothing asked for them when the claim was submitted, and the rejection didn’t say what was missing. Fixing it took eight days, from 22 to 30 September, but it also pushed the claim past the cut-off. Without the rejection, finance would have approved on 22 September and the claim would have been paid on 28 September, after 25 days instead of 55.
Half the time was the payout calendar. 28 of the 55 days were spent waiting for the next monthly run, after the claim was fully approved.

Now the same claim with four changes: the receipt is photographed and submitted from the restaurant on 3 September, the policy check asks for attendees before the claim can be sent, the manager approves on their phone on Friday 4 September, and finance approves on Monday 7 September, in time for a weekly payout on Wednesday 9 September. Six days instead of 55, and nobody worked any harder.

Why reimbursements are slow

Receipts captured late. Employees collect receipts in a wallet and submit monthly, so the clock starts weeks after the spend.
Approvals that wait for one person. The approver is travelling, on leave or busy, with no reminders, no mobile approval and no delegate.
Rejections that teach nothing. “Not in line with policy” with no rule, no missing item and no fix. The employee guesses, resubmits and the approvals start again.
Checks after approval, not before submission. Missing attendees, receipts or business purposes are found by finance after the manager has approved, instead of by the system while the employee is still filling in the claim.
A monthly payout. Reimbursements ride with payroll, so a claim approved a day after the cut-off waits a month.
A cut-off nobody knows. Employees don’t know when they need to submit by, so they can’t plan for it.
Payments made one by one. Finance transfers each claim by hand from the bank portal, so payouts happen when someone has time.
No status. The employee can’t see where the claim is, so they ask, and finance spends time answering instead of processing.

Reimbursements in Indonesia

“Kapan cair?” In many companies, the most common question finance hears about reimbursements is when the money will arrive. A published payout day and a visible status on each claim answer it before it’s asked.
Payroll or a separate run. Many companies pay reimbursements with the monthly salary, which keeps transfers down but makes every late claim wait a month. A weekly or twice-monthly reimbursement run costs a few more transfers and removes most of the wait.
Reimbursement isn’t salary. Paying back an actual business cost backed by a receipt is generally treated differently for income tax from a fixed allowance, which is usually part of the employee’s income. Keep the two separate on the payslip and in the ledger, and agree the treatment with your tax adviser.
Personal cards and paylater. Employees often front business costs on a personal credit card or a paylater account. When reimbursement takes longer than the billing cycle, the employee pays the interest, and the company’s slow process becomes their debt.
Employees’ bank details. Pay into the account on the employee’s own profile, and treat a change to it like a change to a vendor’s bank account: logged, and confirmed with the employee. Bank details are also personal data under UU PDP, so limit who can see them.

Signs your reimbursement process is too slow

You probably need to look at your reimbursement process if any of these sound familiar:

Employees ask finance, by chat or in the corridor, whether their claim has been paid.
Reimbursements are paid once a month, with salaries.
Nobody outside finance knows the cut-off date.
Claims are rejected with “not in line with policy” and nothing else.
A claim waits until the approver is back from leave.
New joiners are warned to avoid paying for anything themselves.
Finance transfers reimbursements one at a time from the bank portal.

Most of a reimbursement’s life isn’t spent being processed. It’s spent waiting.

How to speed up reimbursements

Capture receipts on the spot. Let employees photograph, forward or send a receipt the moment they get it, and have the claim pre-filled from it.
Check against the policy before submission. Ask for attendees, receipts and business purposes while the employee is still filling in the claim, so a claim that reaches the approver is complete.
Make approvals easy to do, and hard to forget. Approval from a phone, automatic reminders, escalation after a set number of days and a delegate when the approver is on leave. Write the delegate into your approval matrix.
Reject with a reason someone can act on. Name the rule, say what’s missing and let the employee fix the claim in place, without starting the approvals again for a missing attachment.
Pay weekly, on a fixed day. Collect approved claims into one payout batch each week, and publish the cut-off on every claim.
Show the status. Let employees see where each claim is and when it will be paid, and notify them at each step.
Measure the cycle time. Track the days from submission to payment each month, and where they go: submission, approval, finance or payout.

How Procapy helps

In Capy Expense, employees take a photo, forward an email or send the receipt over WhatsApp, and ProcAI reads the merchant, date, amount and tax, suggests the category and pre-fills the claim. Limits, eligible categories and required evidence are checked as the claim is built: soft rules show a warning with the rule in plain language, and hard rules block the submission and say what to change.

Managers approve from their phone with the policy check already done, and ProcApprove sends reminders, escalates past the SLA and delegates around leave. A rejected claim states the rule it failed, what’s missing and what to change, and can be corrected and resubmitted in place, with the approver choosing a reason rather than typing “see policy”.

Approved claims are collected into a payout batch on a fixed cadence, weekly or whatever you choose, and paid to the bank details on the employee’s own profile, in the currency of the claim or of payroll. The cut-off is shown on the claim itself, and each claim shows its stage, from submitted to paid, with the expected payment date and a notification at every step. The employee experience page covers the rest. Book a 30-minute walkthrough, bring your expense policy and allowance rules, and we’ll set up your first claim flow live.

Back to blog