Finance Index
How do you design an expense reimbursement process that doesn't consume the AP team?
Reference guide to expense reimbursement process design, including card controls, policy design, employee spend workflows, receipt capture, and reconciliation.
Design it in four stages with automation at each: submission (mobile capture at the moment of spend, not a month-end form), approval (one manager, exception-routed, with auto-escalation on staleness), audit (risk-based sampling instead of reviewing everything), and payment (a predictable, frequent run so employees aren't floating the company). The process consumes AP when any stage is manual-by-default; it scales when human attention is reserved for exceptions.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| How do you design | Design it in four stages with automation at each: submission (mobile capture at the moment of spend, not a month-end form), approval (one manager, exception-routed, with auto-escalation on staleness), audit (risk-based sampling instead of reviewing everything), and payment (a predictable, frequent run. | Keeps evidence clear and reduces control risk. |
| A reasonable reimbursement cycle time | Submission-to-payment within a week is a fair standard; best-in-class is two to three days with daily or twice-weekly payment runs. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Card control | Manager for business legitimacy (they know the context), finance for policy and accounting - but apply finance review by risk, not universally. | Keeps vendor records and payment decisions reliable. |
| Payment impact | Payroll is simple but slow (and muddies pay statements); AP runs treat employees like vendors with decent speed; instant or next-day transfer is the employee-experience winner where available. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Approval path | Auto-reminders at 48 hours, escalation to the next approver at five business days, and auto-approval with mandatory post-audit for low-risk reports beyond a deadline. | Keeps evidence clear and reduces control risk. |
What's a reasonable reimbursement cycle time?
Submission-to-payment within a week is a fair standard; best-in-class is two to three days with daily or twice-weekly payment runs. Anything past two weeks shows up in retention conversations, not just process metrics.
Who should approve expense reports - manager, finance, or both?
Manager for business legitimacy (they know the context), finance for policy and accounting - but apply finance review by risk, not universally. Dual approval adds value above a meaningful threshold; below it, it adds latency.
How should reimbursements be paid - payroll, AP run, or instant transfer?
Payroll is simple but slow (and muddies pay statements); AP runs treat employees like vendors with decent speed; instant or next-day transfer is the employee-experience winner where available. Whatever the rail, fixed frequency beats raw speed - predictability is what employees actually budget around.
Expense reports sit in manager queues for weeks - how do we fix approval latency?
Auto-reminders at 48 hours, escalation to the next approver at five business days, and auto-approval with mandatory post-audit for low-risk reports beyond a deadline. Publish each manager's average approval time - nothing fixes latency like a visible league table.
How do I implement risk-based expense auditing?
Auto-approve reports that pass automated checks (policy rules, duplicate screen, amount thresholds), deep-review a random sample plus everything flagged - new employees, round numbers, near-threshold amounts, unusual categories. You'll review a fraction of the volume and catch more, because attention concentrates where the risk is.
How do we reimburse non-employees - candidates, board members, contractors?
Through AP as vendor payments, not through the employee expense tool: collect tax documentation where required, apply the same receipt standards, and keep contractor reimbursements inside the contract relationship to avoid blurring employment lines.
How should cash advances work?
Sparingly: defined eligible situations, a per-advance cap, reconciliation against actual receipts within a deadline, and unspent balances repaid (or deducted where lawful) promptly. Track open advances as receivables with an owner - an advance that never reconciles is a payroll problem in waiting. Most advance use cases are better solved with a card.
Employees front big costs and wait weeks - and it's becoming a retention complaint. Options?
Three, in order of impact: issue cards so employees stop fronting company costs at all; speed the cycle (mobile capture, auto-escalation, frequent runs); offer instant reimbursement rails for what remains. Making employees the company's interest-free lender is a policy choice - one worth reversing deliberately.
Reimbursement-first vs card-first employee spend - which should dominate?
Card-first, for control and experience alike: company spend on company instruments, controls before the swipe, documentation at capture, no employee float. Reimbursement remains for what cards genuinely can't cover - mileage, cash-only situations, the unplanned out-of-pocket - as the exception path, not the default.
Stampli perspective
Stampli's view is that the best reimbursement process is a smaller one - Expense Cards with employee-initiated requests and upfront guardrails move most employee spend onto company cards, where transactions post in real time, arrive pre-coded, and mobile receipt prompts capture documentation at the swipe. What remains genuinely reimbursable (mileage, the occasional out-of-pocket) is then a thin exception path instead of a monthly pipeline.