Expense policy exception review across systems: a map of the records and the keys that join them

Short answer

Reconstructing an expense policy exception takes five joins: the expense report to the travel booking by booking reference, to the corporate card feed by transaction ID, to the HRIS by employee ID as of the trip date, to the policy library by version and effective date, and to payroll or AP by payment batch. The HRIS join breaks most often, because grade, cost center and manager are frequently overwritten when people change roles.

Visual briefFull-size diagram
A hub-and-spoke map with the expense report at the center and five systems around it (travel booking, card feed, HRIS, policy library, payroll), each joined by its linking key: booking reference, transaction ID, employee ID with effective date, policy version and payment batch.
Illustrative: the five joins that rebuild one flagged business-class fare. The HRIS join is the one most often lost.

This system map is part of the expense policy exception review guide. That page explains which records tell the story of one decision; this one shows where each record sits and which identifier carries the case from one system to the next.

The systems and what each one holds

An exception case is never stored in one place. The expense platform is the center of gravity, but the facts a reviewer relied on come from at least five neighbors.

  • Expense system. The report, each line, the audit flags, the exception codes, the employee's comment, the receipt image and the approval history. In SAP Concur Expense Standard Edition, compliance controls can flag transaction dates older than a set number of days, require comments or attendees on chosen expense types and set a random audit percentage, so the flag itself is produced by configuration that changes over time.
  • Travel booking tool. The itinerary, booking date, fare class and any pre-trip approval. The booking date often decides which rule applied.
  • Corporate card feed. The posted transaction with merchant, amount, currency and posting date, matched to the expense line.
  • HRIS. Grade, job title, cost center, manager and location, ideally effective-dated so each value has a start and end.
  • Policy library or intranet. Each policy version with its effective dates and any clarifications issued between versions.
  • Payroll or accounts payable. The reimbursement, the run it was paid in and any recovery from the employee.

Receipts are the part companies usually keep, because tax and audit rules already push them to. What gets lost is the context in the neighboring systems.

The linking keys, system by system

The table is the map in compact form: one row per join, the key that makes it, and who owns each side.

SystemRecord it contributesLinking key to the expense reportOwner
Expense systemReport, line, flag, exception code, comment, approvalReport ID and line ID (the anchor)Finance operations, administered by the expense admin
Travel booking toolItinerary, booking date, fare class, pre-trip approvalBooking reference or trip ID copied onto the lineTravel manager
Corporate card feedPosted transaction, merchant, amountCard transaction ID matched to the lineTreasury or AP
HRISGrade, cost center, manager, locationEmployee ID plus the trip date as an effective dateHR or people operations
Policy libraryPolicy version, clause, effective datesPolicy version cited by the exception code, chosen by dateHead of finance operations
Payroll or APReimbursement and recoveryPayment batch or run ID referencing the report IDController or payroll lead

Two of these keys are not stored identifiers but rules. The HRIS join needs a date as well as an employee ID, and the policy join needs a date to pick the right version. If either system keeps only today's state, the key still resolves, but to the wrong answer.

One fully joined case (Illustrative)

Illustrative. A 410-person medical device distributor allows business-class airfare for grade 9 and above on flights over six hours, under policy version 7, clause 4.2. A regional sales manager is promoted to director, grade 9, effective May 15. The HRIS feed to the expense system runs weekly, so on May 20, when the manager books a June 3 flight to a customer site at a $3,140 business-class fare, the expense system still shows grade 7.

StepRecordSystemKey that joins it
May 15Promotion to grade 9, effective-datedHRISEmployee ID, effective date
May 20Booking, business class, $3,140Travel booking toolBooking reference
May 21Card charge posts for $3,140Card feedTransaction ID
Jun 9Expense line flagged: fare class above grade 7 limitExpense systemReport ID, line ID, exception code
Jun 10Employee comment: promoted May 15Expense systemLine ID
Jun 12Reviewer checks HRIS as of May 20, finds grade 9; approves under clause 4.2Expense system and HRISEmployee ID plus booking date; policy version 7
Jun 20Reimbursement settled against the cardPayroll or APPayment batch referencing report ID

Two years later the same person moves to grade 10. Anyone reading the case with a current-state HRIS sees grade 10 and concludes the flag was wrong for a different reason, or cannot tell why it fired at all. Only the effective-dated record shows the real sequence: the grade changed five days before the booking, and the sync lag produced the exception. That is why the reviewer's note, the flag and the HRIS history have to stay joined.

Where the joins usually break

The weak points are predictable, and an expense administrator can usually say which apply from memory.

  1. Overwritten HRIS fields. If grade or manager is stored as a single current value, the as-of-date join fails. Workday's auditing records old and new values with a timestamp and the person who made a user-made change, which is the kind of trail that can rebuild history; whether a given tenant's reports cover the needed fields and years is for the company's HR systems team to confirm.
  2. Booking reference not copied. If the travel tool and the expense line share no reference, the join falls back to matching on name, date and amount, which is fragile.
  3. Policy version not cited. Exception codes often point at a rule name, not a version. The version is then inferred from the date, which works only if past versions and their dates were kept.
  4. Retired audit rules. When a rule is deleted from configuration, old flags lose their definition.
  5. Extract scope. Concur Expense administrators can create and download extract files, but whether a particular extract includes comments, exception codes and approval history together is a configuration question. Treat it as unknown until the administrator confirms.

For how other finance platforms expose transactions and receipts, see the Ramp transactions and receipts page. The broader case for joined records over single exports is in why cross-system data is worth more.

Questions to ask, and what stays unknown

Keep the conversation at metadata level: system names, field names, years and owners. A partner never asks for a report, a receipt or an employee list.

  • Does the HRIS store grade, cost center and manager with effective dates, and since which year?
  • Does each expense line carry the booking reference and card transaction ID?
  • Are past policy versions kept with start and end dates, and do exception codes cite them?
  • Who owns each system, and who could authorize a licensing discussion? The who-can-license decision tree covers that step.

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. What stays unknown until SourceX reviews it: which joins actually hold, what employee data counsel allows in scope and how it is de-identified, whether there is dataset demand, and any offer. The accounting data licensing question covers the general rights picture, and the referral brief template turns this map into a one-page introduction.

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 the expense administrator confirms that the HRIS keeps effective-dated history and the lines carry their booking and card keys, register as a partner, check the company against who qualifies, and read the program terms before you introduce the finance leader.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is an expense system export enough on its own?

Rarely. The export holds the line, the flag and usually the approval, but the employee's grade on the trip date sits in the HRIS and the rule text sits in a policy library. Without those two joins a reviewer's decision cannot be re-checked.

Does the partner need to see the keys or the records to build this map?

No. The map is built from field names and system names that an expense administrator can describe from the configuration screens. No report, receipt or employee name changes hands.

What if the HRIS only stores current values?

Then the grade, cost center and manager on past trip dates may be unrecoverable from the HRIS itself, though an audit trail or old payroll extracts sometimes fill the gap. Record it as unknown and let the company's administrators confirm.

Sources

  1. help.sap.com/docs/CONCUR_EXPENSE/1f13d54352684d6dba6e65c8…
  2. help.sap.com/docs/concur-expense/concur-expense-standard-…
  3. doc.workday.com/admin-guide/en-us/manage-workday/tenant-conf…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment