# Expense policy exception records | SourceX

Canonical: https://refer.sourcex.si/guides/workflow-expense-policy-exception-review
Last updated: 2026-11-04

The records that explain an expense policy exception are the receipt, the policy version in force on the relevant date, the audit flag the expense system raised and the rule behind it, the employee's comment, the reviewer's note with the reasoning, the amount finally reimbursed, and any policy clarification that followed. Together they show a problem, an authorized decision and a checked result. A partner describes those record classes, systems and years at metadata level and introduces the finance leader who can authorize a licensing discussion.

Expense policy exception review is the finance work of deciding what to do with an expense the rules flagged. Most flags are simple: a missing receipt, a duplicate, a clear overspend. The informative cases are legitimate expenses that a rule flagged anyway, because they show judgment rather than enforcement. The [guide to assessing finance workflows without sharing sensitive records](/guides/how-to-assess-finance-workflows-without-sharing-sensitive-financial-records) explains the metadata-only approach used here.

## Which expense policy exception review records help a company explain how exceptions were handled?

The records that let someone re-check a decision: the receipt, the rule version in force, the flag the system raised, the reviewer's reasoning and what was finally paid. The hardest and most useful cases are legitimate expenses that a rule flagged anyway.

### Illustrative case: one stay, two policy versions

A 330-person engineering consultancy changes its travel policy on April 1. Version 6 allowed up to $240 a night for hotels in high-cost cities; version 7 lowers that to $200 and adds pre-approval for stays over four nights. A project engineer books a client-site hotel on March 10, for March 28 to April 3, at $228 a night: six nights, $1,368.00 in total.

| Step | Record | What it shows |
|---|---|---|
| Mar 10 | Travel booking confirmation | The stay was booked while version 6 was in force |
| Apr 3 | Hotel folio | Six nights at $228, $1,368.00: the receipt |
| Apr 7 | Expense report line and two audit flags | The system applied version 7 to the April 1 and April 2 nights: over the $200 cap and no pre-approval |
| Apr 8 | Employee comment | "Booked March 10 under the old policy; project schedule attached" |
| Apr 10 | Reviewer note from the finance operations head | Booking date governs; version 6 applies to the whole stay; approve in full |
| Apr 17 | Reimbursement record | $1,368.00 paid in the next expense run |
| May 2 | Policy clarification 7.1 | Stays booked before an effective date follow the prior version |

The case has an initial problem (two nights flagged, $56 over the new cap), an authorized action (the finance operations head applied a booking-date rule the policy had not written down), and a checked result (reimbursement, then a clarification that made the rule explicit). That last step is what makes it valuable: the exception changed the policy.

The documentation trail matches what tax rules already ask for. Under IRS guidance, travel expenses are generally substantiated with the date, place, amount and business purpose, usually backed by receipts ([IRS Publication 463](https://www.irs.gov/publications/p463)), and an accountable plan generally treats substantiation within 60 days as timely ([IRS Publication 15](https://www.irs.gov/publications/p15)). Companies therefore tend to hold the receipts. What they lose is the context around the decision.

## Why does the policy version decide whether a case can be re-checked?

Because every flag and every approval was made against the text in force at the time. In the case above, the reviewer's note says "version 6 applies". Without version 6's text and its effective dates, nobody can later confirm the $240 cap, and the note becomes an unsupported assertion. The same holds for the audit rules themselves. In SAP Concur Expense Standard Edition, compliance controls can flag transaction dates older than a set number of days, require attendees or comments on selected expense types, and set a random audit percentage. Those settings change over time, and a flag only makes sense next to the setting that produced it.

So the strongest exception histories keep three things side by side: the policy document with effective dates, the expense system's audit rule configuration over time, and the reviewer notes that cite them. Ask the finance operations head whether past versions of both still exist, and where.

## How do the records map to the exception?

The map below uses the worked case. It shows which record proves which part of the decision, and where each usually lives.

| Part of the case | Record | Typical system | What to ask |
|---|---|---|---|
| The rule | Policy version with effective dates | Policy library or intranet | Are superseded versions kept with their dates? |
| The control | Audit rule configuration | Expense system administration | Is there a history of rule changes, or only current settings? |
| The problem | Expense line with audit flags | Expense system | Do flags survive after the report is approved? |
| The evidence | Receipt and booking confirmation | Expense system attachments | Are attachments kept for closed reports, and for how long? |
| The argument | Employee comment | Expense report | Are comments exported with the line? |
| The decision | Reviewer note with reasoning | Approval workflow | Who wrote it, and is the reasoning written or just "approved"? |
| The result | Reimbursement record | Payroll or AP | Can the payment be tied back to the report? |
| The learning | Policy clarification | Policy library | Do clarifications reference the case that prompted them? |

Concur Expense administrators can create and download extract files of expense data; whether a given extract includes flags, comments and reviewer notes is a question for the company's administrator. The employee's grade, cost center and manager on the trip date also matter, because many policies vary by grade; how those fields join from the HRIS is a cross-system question covered on the child page below.

## Does the company qualify, and what stays unknown?

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Expense records contain personal data, so the company decides with counsel what is in scope and how it would be de-identified, and SourceX's rights review covers employee notices before any dataset is proposed. Also unknown until then: whether there is dataset demand, and any offer. Partners sign the Channel Partner Agreement before submitting, and the first valid introduction within the 90-day window is credited when the company submits a verified application. The [procurement approvals guide](/guides/how-to-assess-procurement-approvals-and-exception-workflows), [exception handling records for AI agents](/guides/exception-handling-ai-agents-data) and the [industries hub](/industries) cover related ground.

## Go deeper on expense policy exception review

- [Expense policy exception review records across systems](/guides/expense-policy-exception-review-records-across-systems): a system map of the keys joining expense system, HRIS, card feed and payroll.
- [Who can license expense policy exception review records](/questions/who-can-license-expense-policy-exception-review-records): a short answer on which decision-maker to introduce.
- [Preserve expense policy exception review records before a policy redesign](/guides/preserve-expense-policy-exception-review-records): an inventory checklist for a policy or platform change.
- [Expense policy exception review referral brief template](/resources/expense-policy-exception-review-referral-brief-template): a fill-in template for the introduction note.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's flagged expenses still carry the policy version, the reviewer's reasoning and the outcome, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce the CFO.

## Sources

- https://www.irs.gov/publications/p463
- https://www.irs.gov/publications/p15
- https://help.sap.com/docs/CONCUR_EXPENSE/1f13d54352684d6dba6e65c8c5d75ead/c45cdc5051c31015b92ddbec5a448aaa.html
- https://help.sap.com/docs/concur-expense/concur-expense-standard-edition-tools-guides/creating-and-downloading-extract-files
- https://refer.sourcex.si/terms
