Expense approval process map

A swimlane map of an expense claim from the moment a receipt exists to the moment the money is reimbursed and the claim is available for audit, across the employee, the line manager, finance/AP, payroll and an auditor. Seven decisions, most of them policy checks that a claim can fail.

Open this map in the editor

Opens a copy in the editor and saves it in this browser. No account, nothing sent anywhere.

What is in this map

20 steps across 5 swimlanes and 7 phases, with 7 decision points.

Swimlanes (who does the work): Employee, Line manager, Finance / AP, Payroll and Auditor
Phases (left to right): Capture, Submission, Validation, Approval, Finance review, Reimbursement and Assurance

Why map this process

Expenses are low value and high volume, which is the worst combination for an unmapped process: nobody can justify spending time on any individual claim, so the rules get applied inconsistently, and the inconsistency is what eventually costs real money in an audit finding. A single page that shows which check happens where, and who is allowed to waive what, does more for consistency than a policy document nobody opens.

The auditor lane is unusual on an operational map and it earns its place. Expense claims are sampled after the fact, and the sampling is only possible if the process left the right records behind, so drawing the assurance step as part of the process, rather than as something that happens to the process, makes the record-keeping steps upstream look necessary rather than bureaucratic.

Every step in the map

This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.

Every step in the Expense approval process process map, in the order the editor numbers them.
#	Step	Shape	Swimlane	Phase	Goes to
1	Expense incurred and receipt captured	Start	Employee	Capture	2
2	Submit claim with category and coding	Process	Employee	Submission	3
3	Receipt attached and within policy?	Decision	Line manager	Validation	5 (Compliant), 2 (Returned), 4 (Breach)
4	Exceptional approval granted?	Decision	Finance / AP	Validation	5 (Granted), 6 (Refused)
5	Line manager approves claim?	Decision	Line manager	Approval	7 (Approved), 6 (Rejected)
6	Claim rejected and closed	Reject	Employee	Approval	End
7	Value over approval threshold?	Decision	Line manager	Approval	8 (Over limit), 9 (Within limit)
8	Escalate to second approver	Process	Finance / AP	Approval	9
9	Duplicate claim detected?	Decision	Finance / AP	Finance review	10 (Duplicate), 11 (New claim)
10	Hold and query duplicate claim	Reject	Finance / AP	Finance review	End
11	Check evidence and code VAT	Process	Finance / AP	Finance review	12
12	Post claim to expense ledger	Registry	Finance / AP	Finance review	13 (Reimburse), 17 (Sampled)
13	Reimburse via payroll or payment run?	Decision	Finance / AP	Reimbursement	14 (Payroll), 15 (Payment run)
14	Add to next payroll cycle	Process	Payroll	Reimbursement	16
15	Include in weekly payment run	Process	Finance / AP	Reimbursement	16
16	Employee reimbursed and notified	Success	Employee	Reimbursement	End
17	Select claims for sample audit	Process	Auditor	Assurance	18
18	Claim supported by evidence?	Decision	Auditor	Assurance	20 (Supported), 19 (Exception)
19	Recover amount and log finding	Compensation	Finance / AP	Assurance	20
20	Audit findings reported	End	Auditor	Assurance	End

The decision points

Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.

3. Receipt attached and **within policy**?

Owned by Line manager · Validation
- Compliant → step 5
- Returned → step 2
- Breach → step 4
4. Exceptional approval granted?

Owned by Finance / AP · Validation
- Granted → step 5
- Refused → step 6
5. Line manager **approves** claim?

Owned by Line manager · Approval
- Approved → step 7
- Rejected → step 6
7. Value over **approval threshold**?

Owned by Line manager · Approval
- Over limit → step 8
- Within limit → step 9
9. **Duplicate claim** detected?

Owned by Finance / AP · Finance review
- Duplicate → step 10
- New claim → step 11
13. Reimburse via payroll or payment run?

Owned by Finance / AP · Reimbursement
- Payroll → step 14
- Payment run → step 15
18. Claim supported by evidence?

Owned by Auditor · Assurance
- Supported → step 20
- Exception → step 19

Notes on specific steps

These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.

3. Receipt attached and **within policy**?: Three exits, not two. A missing or illegible receipt is a correctable error and goes straight back to the claimant; a genuine policy breach is somebody else's decision and must never be fixed by resubmitting.
7. Value over **approval threshold**?: Decide whether the threshold reads the claim total or a single line: a week of hotel nights submitted as one claim behaves very differently from five separate ones. Fix the figure and the currency in policy, not in each approver's head.
9. **Duplicate claim** detected?: Match claimant, date, amount and merchant together, and look across claims as well as within one. A card transaction claimed again as cash, a re-photographed receipt, and a shared meal claimed by two attendees are the usual sources.
11. Check evidence and code *VAT*: Only a valid VAT receipt supports a reclaim, and mileage, per diems and tips usually follow separate rules. Code the irrecoverable portion here rather than leaving finance to unpick it at quarter end.

Making it yours

Your policy is the branch labels. Work through the validation phase and put the actual rule in the Line text column of each decision: the receipt threshold, the per-diem limit, the deadline for submitting after the expense date. Then use the Notes column on the manager approval step for the one thing managers always ask: what they are allowed to approve without finance, and what they are not.

What to watch out for

A rejected claim is almost never the end. It goes back to the employee for a corrected receipt or a better explanation and re-enters the process, so the rejection branch needs a line back into the submission phase, otherwise the map implies claims are refused rather than fixed.
Manager approval and finance review are different questions. The manager attests that the spend was legitimate business; finance checks it against policy and coding. Companies that merge them lose the business justification, which is the part an auditor actually asks for.
Reimbursement through payroll and reimbursement through AP have different timings and different tax treatment. If you run both, that is a decision row, not a footnote.

Frequently asked questions

Where should corporate card transactions enter this map?

At the capture phase, alongside out-of-pocket receipts, then through the same validation. The difference is that the money has already left the company, so a card transaction that fails policy leads to a recovery step rather than a non-payment: worth a branch of its own at the end rather than a separate map.

How do I map an approval that the claimant's manager cannot give?

Self-approval and approvals above a manager's limit both need a route to someone else. Add a decision immediately before the approval step that branches on claimant and amount, and send both exceptional cases to a second approver row in the finance lane. That branch is the single most useful thing on the map for an auditor.

Our expense tool already enforces the policy. What does the map add?

The tool enforces what happens inside it. The map covers what happens around it: the claim submitted after the deadline, the receipt that cannot be produced, the manager on leave, the disputed rejection. Those are handled by people, inconsistently, and they are exactly what a new starter asks about.

Open the map and start editing

The editor loads this chart with the spreadsheet underneath it. Change a cell and the diagram redraws — no drawing, no signup.

Open this map in the editor