Expense software should turn a business purchase into an evidenced, policy-checked, approved, reimbursed and reconciled transaction. Faster receipt capture is useful only when identity, purpose, tax, duplicate, approval and accounting remain controlled.
Map the full journey and its exceptions. Automate objective rules, keep judgement with accountable people and show employees current status and correction.
Define expense scope
List employee, contractor, card and mileage expenses; countries, currencies, entities, tax, projects and payment methods. State what belongs in purchasing instead.
Publish policy in usable categories and examples with specialist review where obligations apply.
Map the transaction
| Stage | Required evidence | Owner |
|---|---|---|
| Capture | merchant, date, amount, currency and receipt | employee/card feed |
| Explain | business purpose, category, project and attendees | claimant |
| Check | policy, duplicate, tax and limits | system/control owner |
| Approve | authority, exception decision and evidence | manager/finance |
| Pay/post | accepted reimbursement and accounting | payroll/AP/finance |
Design receipt capture
Test image, email, card feed and manual entry. Validate extracted values and preserve original evidence. Show confidence and require correction where needed.
Handle missing receipt through approved exception rather than a fabricated attachment.
Apply policy at the right time
Warn before submission where possible and distinguish block, justification and review. Define thresholds, per diem, mileage and category rules with effective dates.
Do not encode ambiguous policy without an owner. Record why an exception was accepted.
Detect duplicates
Compare employee, date, amount, merchant, card transaction and receipt signals. Test split, foreign currency, resubmission and shared receipt.
Use human review for uncertain matches and preserve the decision.
Design approval authority
Map manager, project, cost centre, amount and exception routes. Test delegation, absence, self-approval conflict and changed manager.
Escalation must reach someone able to decide, not repeatedly alert the same queue.
Protect sensitive data
Minimise personal details and restrict receipts, travel and attendees. Control administrator and support access, retention, export and deletion according to policy.
Notifications should not expose receipt detail unnecessarily.
Connect reimbursement and accounting
Define approved event, payee identity, bank authority, payment batch, posting, tax, project and reconciliation. Test rejection after approval and failed payment.
Reconcile claims, approved amounts, payments and ledger entries by period.
Measure the process
Track submit-to-first-review, return rate, exception cause, approval age, payment time, duplicate prevention, missing evidence and manual posting. Pair speed with audit and employee experience.
Fix repeated policy or data causes before adding reminders.
Pilot and govern
Run ordinary, foreign, mileage, card, missing receipt, duplicate and policy-exception cases. Keep rollback and manual pay control.
Name policy, process, system, data and accounting owners. The service succeeds when employees understand status and finance can explain every reimbursement from evidence to ledger.
Separate roles and conflicts of interest
Define who may submit, edit, approve, pay, administer policy and change bank details. Prevent self-approval and make delegation time-bound. An executive exception still needs an independent route. Test an approver on leave, a user changing department and an administrator attempting to alter their own claim.
Where finance performs a final check, state whether it validates policy, tax, coding or payment authority. Avoid an undefined final approval that merely repeats earlier work.
Handle tax, currency and accounting explicitly
Specify receipt tax evidence, recoverability, merchant location, transaction currency, reimbursement currency, rate source, rounding and personal portions. Define coding for department, project, client, grant or cost centre and who may override suggested values. Test a mixed-purpose receipt, foreign-currency refund and a corrected tax amount.
Reconcile approved expenses to the accounting import and payment file. The control should identify missing, duplicated and rejected records rather than assume a successful transfer is complete.
Include cards, advances and out-of-pocket spend
Corporate-card matching, cash advances and personal reimbursement have different evidence and settlement paths. Define how card feeds are matched, how unmatched transactions age and how personal card use is recovered. For advances, reconcile issued, spent and returned amounts before closure.
Do not force all spend into one status model if that obscures who owes money to whom.
Design exception handling before automation
List missing receipt, policy breach, duplicate suspicion, disputed merchant, cancelled trip, departed employee, failed payment and returned reimbursement. For each, define owner, permitted action, evidence, escalation and closure. A rejection should explain what can be corrected; a compliance hold should not be bypassed by resubmission.
Measure exception reasons and recurrence. Repeated late submissions may point to a poor capture process, while repeated coding corrections may indicate unclear master data.
Protect sensitive information
Receipts can expose health, travel, location and personal purchasing information. Define necessary fields, redaction, access by role, audit access, retention and deletion. Limit what managers see when only amount, purpose and policy status are needed. Test downloaded files and support access, not only the application screen.
Confirm current legal and tax obligations with qualified advisers in each operating jurisdiction.
Pilot with a complete reimbursement cycle
Use employees, managers and finance across several expense types. Start at receipt or card transaction and finish with bank settlement, ledger reconciliation and employee confirmation. Include one clean claim, one policy exception, one duplicate, one foreign-currency item and one failed payment. Observe workarounds and administrative effort.
Release only when the team can prove that an approved amount is paid once, posted correctly and supported by accessible evidence. After launch, track cycle time by stage, first-time acceptance, unresolved card items, duplicate alerts, late claims and manual accounting corrections. These measures show where the process—not merely the user—needs improvement.