Before an expense policy redesign: a retention timeline for exception review history

Short answer

Before an expense policy redesign, inventory the context that disappears first: retired audit rules and exception codes, the superseded policy text with its effective dates, and HRIS grade and manager history if those fields are overwritten. Receipts and reimbursements usually sit under longer tax and payroll retention and are rarely the first loss. Note each record type's owner and the date it becomes unrecoverable, and leave any decision to keep it to finance, HR and counsel.

Visual briefFull-size diagram
A horizontal timeline from kickoff to go-live, contract end and years later, with five record rows: audit rules and policy text end at go-live, HRIS history soon after, reviewer comments at contract end, while receipts continue under existing retention; a dashed line marks context kept only if the company's owners approve.
Illustrative sequence. Actual retention is set by each company's policy, counsel and HR.

This timeline is part of the expense policy exception review guide. It does one job: show, in order, what a redesign removes and when, so the company's owners can decide what to keep before it is gone.

The timeline, from kickoff to contract end

Illustrative sequence for a company replacing policy version 7 with version 8 and moving expense platforms a year later. Dates are relative to go-live of the new policy.

WhenEventWhat disappears unless preservedWho notices
Kickoff, about 3 months before go-liveRedesign project starts; drafts of version 8 circulateNothing yet; the inventory should happen hereHead of finance operations
4 weeks before go-liveAudit rules and exception codes rebuilt for version 8 in a test environmentNothing yet, but renamed codes are decidedExpense administrator
Go-liveVersion 8 rules switched on; version 7 rules deleted or deactivatedDefinitions behind past flags and codesExpense administrator
Go-liveIntranet policy page replaced with version 8Version 7 text and its effective dates, unless archivedIntranet owner
Within monthsRole changes and reorganization updates HRIS recordsPast grade, cost center and manager, if fields are overwrittenHR systems team
About 12 months laterExpense platform contract ends; old tenant read access closesComments, approval history and attachments not migratedController, IT
Years laterOrdinary retention schedule removes reports and receiptsThe records themselvesRecords owner

The pattern is consistent: the definitions and the context go first, at go-live, and the transactional records go last. A history with receipts but no rule definitions shows that money was spent and approved, but not why a flag fired or why a reviewer overruled it.

Typical minimum retention by record type

These are reference points, not advice. Each company sets its own schedule with counsel.

  • Receipts and expense reports supporting tax positions. The IRS generally suggests keeping tax records for three years, longer in listed cases, and employment tax records for at least four years (IRS). Many finance teams keep expense records longer as policy.
  • Reimbursements processed through payroll. U.S. payroll records must be kept for at least three years under the Fair Labor Standards Act, and records on which wage computations are based for two years (DOL Fact Sheet 21).
  • Substantiation timing. Under an accountable plan, substantiation within 60 days and return of excess within 120 days are generally treated as reasonable (IRS Publication 15), which is why comments and receipts cluster in the weeks after a trip.
  • Personal data in employee records. In the UK, the storage limitation principle says personal data should not be kept longer than needed and retention periods should be justified, ideally in a schedule (ICO). That principle can cut against keeping context indefinitely, which is exactly why the decision belongs to counsel.
  • Audit rule configuration and policy text. No general rule requires keeping these. They survive only if someone archives them.

What to inventory at kickoff

The inventory is a list of record types, years and owners, not a copy of anything.

  1. Policy versions. Every version still findable, with effective start and end dates, plus clarifications issued between versions.
  2. Rule configuration. Whether the expense system keeps a history of audit rules, limits and exception codes, or only the current set. Screenshots or a configuration export are the company's choice.
  3. Flagged volume. Years covered and rough counts of flagged lines, approved exceptions and rejections.
  4. Approval context. Where reviewer notes live: the expense system, email, or a ticket queue.
  5. HRIS history. Whether grade, cost center and manager are effective-dated, and since when.
  6. Deadlines. Go-live, the platform contract end date and any HRIS migration date.
  7. Retention schedule. What the company's current policy already requires for each record type.

Who must approve keeping anything

Keeping context past its normal life is a decision with legal weight, especially for employee data.

Record typeProposes keeping itMust approve
Retired audit rules and exception codesExpense administratorHead of finance operations
Superseded policy versionsHead of finance operationsController or CFO
Reviewer comments and approval historyHead of finance operationsCounsel and HR
HRIS effective-dated historyHR systems teamHR leader and privacy lead
Old platform data at contract endControllerCFO and counsel

A partner points out the deadline and the potential value, then steps back. Advising a company to retain or export data for a licensing conversation is not the partner's role. The same metadata-only approach appears in the portfolio handoff checklist and in assessing finance workflows without sharing sensitive records. Redesigns elsewhere in finance raise the same timing issue; see the chart of accounts redesign guide.

Qualification, and what stays unknown

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 preserved record types have value, the outcome of the rights and privacy review, which records would be selected, whether there is dataset demand, and any offer. For the joins that make preserved records usable, see the system map; to hand the inventory to a decision-maker, use the referral brief template.

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 a client's go-live date will delete the rules behind years of exception decisions, register as a partner, check the company against who qualifies, and read the program terms before you raise it with 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

Should a partner advise the company to keep its old audit rules?

No. Retention is the company's decision under its own policy, made with counsel and HR. A partner can point out the date when context will disappear and why it may matter, then let the record owners decide.

Are receipts at risk during a policy redesign?

Usually not in the short term. Receipts and reimbursements sit under tax and payroll retention rules that a redesign does not change. The context around them, such as the rule that fired and the policy text in force, is what tends to go first.

What counts as the real deadline?

The earliest date on which a piece of context becomes unrecoverable: deletion of old audit rules at go-live, replacement of the policy page, an HRIS migration, or the end of an expense platform contract. The redesign kickoff date is not the deadline.

Sources

  1. irs.gov/businesses/small-businesses-self-employed/ho…
  2. dol.gov/agencies/whd/fact-sheets/21-flsa-recordkeeping
  3. ico.org.uk/for-organisations/uk-gdpr-guidance-and-resou…
  4. irs.gov/publications/p15
  5. 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