# Duplicate payment records: retention timeline | SourceX

Canonical: https://refer.sourcex.si/guides/preserve-duplicate-payment-recovery-records
Last updated: 2026-11-04

Before an AP automation rollout, inventory five record classes behind duplicate payment recovery: captured invoices with their rejected and resubmitted versions, match results, supplier correspondence, credits and refunds, and close notes. For each, note the years covered, the system, the owner and the date access actually ends. The explanatory records disappear first, usually at contract end or when staff accounts are removed, while posted payments stay in the ERP. Keeping anything is the company's decision under its own retention policy.

This retention timeline is part of the [duplicate payment recovery guide](/guides/workflow-duplicate-payment-recovery). The main guide explains what a useful recovery history contains; this page puts those records on a clock, so the people who own them can decide what to keep before a system change removes it.

## What disappears first after a cutover

The table orders record classes by how early they tend to be lost. Where a vendor documents a deletion point, it is cited; otherwise the trigger is the company's own contract or setting.

| Order lost | Record class | Where it usually lives | What ends it | Who approves keeping it |
|---|---|---|---|---|
| 1 | Recovery spreadsheets and personal notes | A staff member's OneDrive or desktop | Account deletion when the person leaves; Microsoft allows a deleted user account to be restored within 30 days, after which it is permanently deleted | Controller, with IT |
| 2 | Rejected and resubmitted invoice versions, images | The old AP capture platform | Subscription end or migration that moves posted invoices only | AP director and controller |
| 3 | Supplier threads in personal mailboxes | Individual Exchange Online mailboxes | License removal; default 30-day grace, plus 30 more with Delicensing Resiliency, then deletion | AP director, with IT and counsel |
| 4 | Match results and match rules | Capture platform, audit tool or an outside firm's system | Platform retirement or end of the audit contract | Controller, with counsel for firm papers |
| 5 | Shared AP mailbox threads | Shared mailbox under a retention policy | The company's retention policy | AP director, IT and counsel |
| 6 | Posted invoices, payments and credit memos | ERP | Usually years later, under tax and audit retention | Controller and finance leadership |

The last row is the reassuring one. The IRS generally suggests keeping records for three years from filing, with longer periods in some situations, and notes that insurers or creditors may require more. Payments and credits therefore tend to outlast the rollout. What does not is the material that explains why a credit was issued.

## A cutover timeline, day by day (Illustrative)

A fictional 300-person building products distributor is replacing its AP capture platform. The old contract ends on March 31; cutover is March 1. Dates are invented to show the sequence.

| Date | Event | Record classes affected | Decision needed |
|---|---|---|---|
| December 1 | Planning call; partner asks the inventory questions | None yet | AP director agrees to list record classes and dates |
| December 15 | Inventory complete at metadata level | All | Controller reviews against the retention policy |
| January 10 | Migration scope fixed: open invoices and two years of posted headers | Rejected versions and images out of scope | Finance leadership decides whether to archive out-of-scope items |
| February 1 | Two AP specialists leave in the reorganization | Personal mailboxes and spreadsheets | IT and the AP director decide what moves to the shared mailbox first |
| March 1 | Cutover to the new platform | Old platform becomes read-only | None, if earlier decisions were made |
| March 31 | Old platform contract ends | Anything not archived from the old platform | Too late to decide |
| Early April | Leavers' mailboxes, delicensed February 1, pass the end of the 30-day grace plus 30 days of Delicensing Resiliency | Leavers' mailboxes | Too late to decide |

Every decision row sits before the access deadline. That is the point of the timeline: the inventory has value only while the owners can still act on it.

## Inventory fields to capture before the deadline

Use this checklist in the planning conversation. It produces a list the company can act on, not a copy of anything.

- [ ] **Record classes:** invoice images and versions, approval history, payment runs, match or audit results, supplier correspondence, credit memos and refunds, close notes.
- [ ] **Coverage:** first and last year for each class, and gaps such as a prior system, an acquisition or a mailbox purge.
- [ ] **Volume:** rough counts of invoices per year, duplicate cases found and recoveries closed, each marked estimate or report-based.
- [ ] **System and administrator:** the tool name as plain text and who holds admin rights.
- [ ] **Access deadline:** the contract end or cutover date after which the old tool is read-only or gone, from the contract itself.
- [ ] **Staff changes:** planned departures in AP, and whose mailboxes or spreadsheets hold recovery work.
- [ ] **Retention policy:** what the company's own policy already requires for each class.
- [ ] **Third-party work papers:** whether an outside recovery audit firm holds findings, and under what contract.

The [system map of recovery records](/guides/duplicate-payment-recovery-records-across-systems) shows which joins depend on the records in rows 1 to 4, so the owners can see what would break if those classes were lost.

## Who must approve keeping each record

Keeping records is not free or automatic. It costs money, it may conflict with policy, and where records hold personal data it has to be justified. The UK ICO's storage limitation principle says personal data must not be kept longer than needed and that organizations should be able to justify retention periods, ideally in a retention policy or schedule.

| Decision | Approver | Advisor |
|---|---|---|
| Archive out-of-scope capture platform data before contract end | Controller or CFO | IT, AP director |
| Move leavers' recovery threads into the shared mailbox | AP director | IT, counsel on personal data |
| Keep personal spreadsheets as company records | Controller | IT |
| Request outside audit firm working papers | CFO | Counsel |
| Extend any retention period beyond policy | Finance leadership | Counsel |

A [data retention policy template](/resources/data-retention-policy-template) shows how companies write these rules down, and the guide to [inactive mailboxes for former employees](/guides/inactive-mailbox-microsoft-365-former-employees-license-cost) covers the mailbox options and their cost.

## What a partner does, and does not, recommend

A partner raises the deadline with the person who owns it and lets finance leadership, counsel and IT decide. A partner does not recommend keeping data beyond what the company's policy allows, extending a subscription, or exporting anything on the strength of a possible license. Those same decision-makers would later decide whether any of the records can be licensed. For portfolio-level reviews, the [special situations data assets guide](/for/special-situations-investor-data-assets) applies the same deadline logic across several companies, and [day 1 readiness](/guides/day-1-readiness-m) covers the equivalent problem in a transaction.

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. Unknown until SourceX reviews it with the company: what supplier contracts allow, whether audit firm papers are in scope, what must be de-identified, whether there is dataset demand and any offer. When the inventory is done, the [referral brief template](/resources/duplicate-payment-recovery-referral-brief-template) turns it into an introduction. Partners sign the Channel Partner Agreement before submitting.

## 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 AP platform contract has a fixed end date and the recovery history sits partly outside the ERP, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before the introduction.

## Sources

- https://www.irs.gov/businesses/small-businesses-self-employed/how-long-should-i-keep-records
- https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-user-mailboxes/exchange-online-delicensing-resiliency
- https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/restore-user?view=o365-worldwide
- https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles/storage-limitation/
- https://refer.sourcex.si/terms
