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.
| System | Record it contributes | Linking key to the expense report | Owner |
|---|---|---|---|
| Expense system | Report, line, flag, exception code, comment, approval | Report ID and line ID (the anchor) | Finance operations, administered by the expense admin |
| Travel booking tool | Itinerary, booking date, fare class, pre-trip approval | Booking reference or trip ID copied onto the line | Travel manager |
| Corporate card feed | Posted transaction, merchant, amount | Card transaction ID matched to the line | Treasury or AP |
| HRIS | Grade, cost center, manager, location | Employee ID plus the trip date as an effective date | HR or people operations |
| Policy library | Policy version, clause, effective dates | Policy version cited by the exception code, chosen by date | Head of finance operations |
| Payroll or AP | Reimbursement and recovery | Payment batch or run ID referencing the report ID | Controller 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.
| Step | Record | System | Key that joins it |
|---|---|---|---|
| May 15 | Promotion to grade 9, effective-dated | HRIS | Employee ID, effective date |
| May 20 | Booking, business class, $3,140 | Travel booking tool | Booking reference |
| May 21 | Card charge posts for $3,140 | Card feed | Transaction ID |
| Jun 9 | Expense line flagged: fare class above grade 7 limit | Expense system | Report ID, line ID, exception code |
| Jun 10 | Employee comment: promoted May 15 | Expense system | Line ID |
| Jun 12 | Reviewer checks HRIS as of May 20, finds grade 9; approves under clause 4.2 | Expense system and HRIS | Employee ID plus booking date; policy version 7 |
| Jun 20 | Reimbursement settled against the card | Payroll or AP | Payment 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.
- 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.
- 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.
- 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.
- Retired audit rules. When a rule is deleted from configuration, old flags lose their definition.
- 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.