Who can say yes to licensing expense policy exception records? An approval tree for partners

Short answer

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.

Visual briefFull-size diagram
A top-down approval tree starting at the head of finance operations as sponsor, branching past the expense administrator and controller, through HR and counsel review of employee data, to the CEO as authorized signer, with SourceX rights review as the final gate.
The usual path at a mid-sized company. The CFO can prepare the case; the CEO signs.

This approval tree belongs to the expense policy exception review guide. 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 classDay-to-day ownerMust be consultedCan authorize a licensing discussion
Expense lines, flags and exception codesHead of finance operationsExpense administratorCEO
Reviewer comments and approval historyHead of finance operationsHR, counselCEO, after HR and counsel
Receipt imagesControllerCounsel, for third-party details on receiptsCEO
Policy versions and clarificationsHead of finance operationsNone usuallyCEO
HRIS grade, cost center, manager historyHR or people operationsPrivacy lead, counselCEO with the HR leader
Reimbursements and recoveriesController or payroll leadPayroll provider termsCEO

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 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 covers the general rights test, and the accounting data licensing question 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 shapeSponsorAuthorized contactRequired consults
Founder-led professional services firm, 180 staffFinance operations managerFounder-CEOOutside counsel, HR lead
Sponsor-backed distributor, 520 staffHead of finance operationsCEOGeneral counsel, CHRO, board visibility
Subsidiary of a listed group, 1,400 staffShared services expense leadSubsidiary CEO with group approvalGroup 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 helps the sponsor describe what exists, and the preservation timeline 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, confirm the company on who qualifies and read the program terms before you make the introduction.

  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

Can the expense administrator approve the discussion if they hold the admin rights?

No. Administrator rights let someone run extracts and change audit rules; they do not carry authority over whether company data is licensed. The administrator is a good source of facts about what exists and a poor choice as the person to introduce.

Do employees have to agree before their expense records are discussed?

That is a legal question for the company's counsel and HR, and the answer depends on jurisdiction, the employee privacy notice and the form the data would take. A partner does not answer it; the rights review with SourceX works through it with the company.

What if the CFO is also the person who runs expense review?

Then the CFO is a natural sponsor and can prepare the case, but the CEO still authorizes the discussion and signs. The other branches of the tree still apply: HR and counsel still need to weigh in on employee data before anything is decided.

Sources

  1. delcode.delaware.gov/title8/title8.pdf
  2. eur-lex.europa.eu/eli/reg/2016/679/oj/eng
  3. help.sap.com/docs/concur-expense/concur-expense-standard-…
  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