# Who can license expense exception records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-expense-policy-exception-review-records
Last updated: 2026-11-04

Start with the head of finance operations, who runs the exception queue and knows where the history sits. The person who can say yes to a licensing discussion is the CEO, often with the CFO preparing the case and HR and counsel consulted because expense records describe employees. The expense administrator and the controller hold or control the records but cannot authorize their use. What can actually be licensed stays unknown until SourceX's rights review.

This approval tree belongs to the [expense policy exception review guide](/guides/workflow-expense-policy-exception-review). It answers one question: who needs to be in the room, and in what order, before a company decides to talk about its expense exception history.

## Walk the tree from sponsor to signer

Follow the branches in order. Each one names a role and tells you whether to stop or keep going.

1. **Who owns the exception queue?** Usually the head of finance operations or an expense and travel manager. They know the years covered, the policy versions and the systems. Treat them as sponsor, not signer. Next branch.
2. **Who can describe the system configuration?** The expense administrator knows audit rules, exception codes and what an extract can contain. Concur Expense administrators, for example, can create and download extract files. That capability tells you what is technically possible; it confers no decision right. Next branch.
3. **Who owns the money side?** The controller owns reimbursement accounting, card reconciliation and retention schedules for finance records. The controller describes these records but does not authorize their use. Next branch.
4. **Does the history describe identifiable employees?** Almost always yes: names, employee IDs, travel locations, grades. Under the GDPR, personal data is any information relating to an identified or identifiable natural person, including by a name or an identification number, and other jurisdictions use similar tests. If yes, HR and counsel join the path. Next branch.
5. **Who decides on licensing a company data asset?** The CEO, who can authorize the discussion and sign for the company; the CFO often prepares the case. Under Delaware law, for example, a corporation's business and affairs are managed by or under the direction of its board, and the CEO acts within that authority. A sponsor-backed company may want board visibility. Final branch.
6. **SourceX's rights review.** No one at the company can commit a specific dataset before it. The review settles scope, form and conditions.

## Authority by record class

Different record classes sit with different owners, and that changes who must agree. The matrix is the core of this page.

| Record class | Day-to-day owner | Must be consulted | Can authorize a licensing discussion |
|---|---|---|---|
| Expense lines, flags and exception codes | Head of finance operations | Expense administrator | CEO |
| Reviewer comments and approval history | Head of finance operations | HR, counsel | CEO, after HR and counsel |
| Receipt images | Controller | Counsel, for third-party details on receipts | CEO |
| Policy versions and clarifications | Head of finance operations | None usually | CEO |
| HRIS grade, cost center, manager history | HR or people operations | Privacy lead, counsel | CEO with the HR leader |
| Reimbursements and recoveries | Controller or payroll lead | Payroll provider terms | CEO |

Policy text is the least sensitive row and HRIS history the most. That ordering is useful when the company wants to scope a first conversation narrowly.

## Why employee data adds branches

Accounts payable or vendor records mostly describe companies. Expense records describe people: where they traveled, what they ate, who they met, what grade they held. Three consequences follow.

- **HR has a seat, not just a vote.** HR owns the HRIS fields and usually the employee privacy notice. A discussion that ignores HR tends to stop later at a worse moment.
- **Counsel decides the personal-data scope.** Whether names, IDs, locations or attendee lists can stay, in what form, and under which notice is a legal call. The [PII versus personal data comparison](/compare/pii-vs-personal-data) explains why the definitions differ across regimes.
- **Works councils or employee representatives may matter.** In some EU countries employee data changes involve them. Counsel will know; a partner should only flag that the question exists.

The licensable value in most cases is the decision pattern (rule, flag, reasoning, outcome) rather than who traveled where. The [data rights explainer](/proof/why-data-rights-matter) covers the general rights test, and the [accounting data licensing question](/questions/license-accounting-data-for-ai-training) covers finance records more broadly.

## Who to introduce, by company shape (Illustrative)

Illustrative shapes, not real companies. The tree lands on different people depending on structure.

| Company shape | Sponsor | Authorized contact | Required consults |
|---|---|---|---|
| Founder-led professional services firm, 180 staff | Finance operations manager | Founder-CEO | Outside counsel, HR lead |
| Sponsor-backed distributor, 520 staff | Head of finance operations | CEO | General counsel, CHRO, board visibility |
| Subsidiary of a listed group, 1,400 staff | Shared services expense lead | Subsidiary CEO with group approval | Group privacy office, group legal |

## What remains unknown after the right people agree

Even with the CEO engaged and HR and counsel involved, these stay open until SourceX reviews the opportunity with the company: whether the employee privacy notice permits the use, which record classes are in scope, what must be removed or de-identified, whether there is dataset demand, and the company's offer.

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. 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.

Before the introduction, the [system map of expense exception records](/guides/expense-policy-exception-review-records-across-systems) helps the sponsor describe what exists, and the [preservation timeline](/guides/preserve-expense-policy-exception-review-records) shows which records may disappear first.

## 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.

Once the head of finance operations has named the CEO and confirmed HR and counsel will be involved, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you make the introduction.

## Sources

- https://delcode.delaware.gov/title8/title8.pdf
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- https://help.sap.com/docs/concur-expense/concur-expense-standard-edition-tools-guides/creating-and-downloading-extract-files
- https://refer.sourcex.si/terms
