# Expense exception referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/expense-policy-exception-review-referral-brief-template
Last updated: 2026-11-04

A company introduction about expense policy exception review should fit on one page and contain only metadata: company size, the business task, record classes, systems, years of history, rough volumes, the access deadline, the open question, who owns the records and who can authorize a licensing discussion. No receipt, report, export or employee name belongs in it. The template below gives each line with guidance, then one completed Illustrative brief.

This template is part of the [expense policy exception review guide](/guides/workflow-expense-policy-exception-review). It turns what the sponsor has told you into a page the CEO can read in two minutes.

## The blank template

Copy the left two columns into a document and fill in the right column with the sponsor. Every line is a description, never a record.

| Line | What to write | Your entry |
|---|---|---|
| Company size | Full-time employees at peak, contractors excluded | Write the figure |
| Location and language | Country of operation; share of records in English | Write the country and share |
| Business task | One sentence on the review work | Write one sentence |
| Record classes | Names only: flags, codes, comments, receipts, policy versions, reimbursements | List the classes |
| Systems | Plain-text names: expense platform, travel tool, card feed, HRIS, policy library | List the systems |
| Years of history | First and last year per system, and any gap | Write the years |
| Volumes | Rough counts of reports, flagged lines and approved exceptions, marked verified or not | Write the estimates |
| People-data history | Effective-dated or overwritten, and since when | Write what is known |
| Access deadline | The date context disappears and why | Write the date and event |
| Unresolved question | What nobody can answer yet | Write the question |
| Record owners | Who owns each class day to day | Name the roles |
| Authorized contact | Name and title of the person who can authorize a discussion | Write the name and title |
| Consulted | HR, counsel, privacy lead | Name the roles |
| Not shared | A plain statement that no records were shared | Confirm it |

## How to fill in the hard lines

Four lines cause most of the back-and-forth. Get them right and the rest is quick.

- **Volumes.** Ask the expense administrator for counts from report filters, not exports. Receipts are usually plentiful, because travel expenses generally must be substantiated with date, place, amount and business purpose, typically with receipts. A figure such as "about 40,000 flagged lines, unverified" is enough. Precision comes later.
- **People-data history.** Ask the HR systems team whether grade, cost center and manager carry effective dates, or whether each change overwrites the last value. If nobody knows, write unknown.
- **Access deadline.** Name the event: deletion of old audit rules at go-live of a new policy, the end of the expense platform contract, an HRIS migration. A kickoff date is not a deadline.
- **Authorized contact.** The CEO, not the expense administrator. In SAP Concur Expense, administrators can create and download extract files, but that is technical access, not authority. The [who-can-license approval tree](/questions/who-can-license-expense-policy-exception-review-records) explains the other roles.

## A completed brief (Illustrative)

Illustrative. A fictional 330-person engineering consultancy, prepared with its head of finance operations. No real company is described.

| Line | Entry |
|---|---|
| Company size | 330 full-time employees at peak, contractors excluded |
| Location and language | United States; all records in English |
| Business task | Reviewing expense lines flagged by policy rules, including legitimate expenses that cross policy versions |
| Record classes | Audit flags and exception codes, employee comments, reviewer notes, receipts, policy versions 3 to 7 with clarifications, reimbursements |
| Systems | Expense platform, travel booking tool, corporate card feed, HRIS, intranet policy library |
| Years of history | 2019 to 2026 in the expense platform; policy library complete from version 3 |
| Volumes | About 41,000 flagged lines and 9,000 approved exceptions, unverified |
| People-data history | Effective-dated since a 2022 migration; overwritten before that |
| Access deadline | Version 7 audit rules deleted when version 8 goes live next quarter |
| Unresolved question | Whether pre-2022 grade history survives in old payroll extracts |
| Record owners | Head of finance operations (flags, notes, policy); controller (receipts, reimbursements); HR (HRIS) |
| Authorized contact | CEO |
| Consulted | HR director, general counsel |
| Not shared | No receipt, report, export or employee name was shared |

The brief is short on purpose. It tells the CEO what exists, where, for how long, what may disappear and who decides, and it does so without moving any personal data. Under the GDPR, personal data covers any information relating to an identifiable person, including by name or ID number, which is why names and IDs stay out of the brief entirely.

## Check before you send it

Run through these with the sponsor before the brief leaves their hands.

1. Every entry is a description, a count or a role. No row contains a record.
2. Unverified figures are marked as such.
3. The authorized contact is the CEO, not a system administrator.
4. The company meets the basics: 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.
5. The sponsor has read and approved the page.

What the brief cannot settle: rights, the privacy review outcome, which records would be selected, dataset demand and any offer. Those stay unknown until SourceX reviews the opportunity with the company. A covering note for the owner is in the [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner), and the [client opportunity brief generator](/tools/client-opportunity-brief-generator) can draft a first version. If you implemented the client's expense platform, read [whether referring clients hurts the relationship](/questions/does-referring-clients-hurt-relationship) first. For where the joins behind each line live, see the [system map](/guides/expense-policy-exception-review-records-across-systems); for why exception records interest AI developers, see [exception handling data for AI agents](/guides/exception-handling-ai-agents-data).

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

When the sponsor has approved the completed brief and named the CEO, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you send it.

## Sources

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