Capture that never becomes evidence
A photo is attached. The handbook still asks for an SST invoice or an e-invoice QR. Sampled claims show a thumbnail and a paid status. A claim-path audit starts with closed items, not the policy PDF.
Claim path
Six places a receipt can quietly leave the policy
A working reference we use to frame trail audits and walkthroughs—not a generic controls catalogue.
Path entries
Each point names the usual story, the evidence we look for, and the engagement that clarifies it.
Displayed limit, live send
The help screen shows meal caps and mileage rates. The submitter can save past the banner. Policy-rule testing asks whether the engine stops, or only colours the row.
The same night, two claims
A hotel or taxi can sit on the card feed and again as cash. Duplicate examinations look at the period, not only identical merchant strings.
Card line still open after payout
Reimbursement can close while the bank file is unmatched. Card-feed walkthroughs follow ageing, forced matches, and write-off rights.
A click in someone else’s name
Delegates and admin impersonation keep work moving. The failure is an unlogged actor. Delegate reviews sample who clicked, not who the org chart names.
Exception path without a reader
Force-approve buttons are not the scandal. Unreviewed logs are. Trail packs attach the exception to a named claim and ask who last opened the report.
How teams use the path
Pick the point closest to the debate in your next sitting, then request the matching engagement. The path frames the sample; it does not replace your application data.
Name the platform and the sitting
Which expense application runs claims, and which committee paper you are preparing.
Match a path entry
We confirm whether the usual story fits, or whether a different point better explains the documents.
Book the engagement
Trail audit, rule testing, duplicate examination, card walkthrough, or delegate review—scoped to the decision you need to table.
