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.
| When | Event | What disappears unless preserved | Who notices |
|---|---|---|---|
| Kickoff, about 3 months before go-live | Redesign project starts; drafts of version 8 circulate | Nothing yet; the inventory should happen here | Head of finance operations |
| 4 weeks before go-live | Audit rules and exception codes rebuilt for version 8 in a test environment | Nothing yet, but renamed codes are decided | Expense administrator |
| Go-live | Version 8 rules switched on; version 7 rules deleted or deactivated | Definitions behind past flags and codes | Expense administrator |
| Go-live | Intranet policy page replaced with version 8 | Version 7 text and its effective dates, unless archived | Intranet owner |
| Within months | Role changes and reorganization updates HRIS records | Past grade, cost center and manager, if fields are overwritten | HR systems team |
| About 12 months later | Expense platform contract ends; old tenant read access closes | Comments, approval history and attachments not migrated | Controller, IT |
| Years later | Ordinary retention schedule removes reports and receipts | The records themselves | Records 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.
- Policy versions. Every version still findable, with effective start and end dates, plus clarifications issued between versions.
- 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.
- Flagged volume. Years covered and rough counts of flagged lines, approved exceptions and rejections.
- Approval context. Where reviewer notes live: the expense system, email, or a ticket queue.
- HRIS history. Whether grade, cost center and manager are effective-dated, and since when.
- Deadlines. Go-live, the platform contract end date and any HRIS migration date.
- 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 type | Proposes keeping it | Must approve |
|---|---|---|
| Retired audit rules and exception codes | Expense administrator | Head of finance operations |
| Superseded policy versions | Head of finance operations | Controller or CFO |
| Reviewer comments and approval history | Head of finance operations | Counsel and HR |
| HRIS effective-dated history | HR systems team | HR leader and privacy lead |
| Old platform data at contract end | Controller | CFO 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.