Before AP automation goes live: a retention timeline for duplicate payment recovery records

Short answer

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.

Visual briefFull-size diagram
A horizontal timeline from inventory to cutover and beyond, with five record lanes: recovery spreadsheets end first, rejected invoice versions end at the capture platform's contract end, leavers' mailboxes end when license grace runs out, while the shared mailbox and ERP payments continue.
Illustrative timeline. Real deletion points come from the company's own contracts, settings and retention policy.

This retention timeline is part of the duplicate payment recovery guide. 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 lostRecord classWhere it usually livesWhat ends itWho approves keeping it
1Recovery spreadsheets and personal notesA staff member's OneDrive or desktopAccount deletion when the person leaves; Microsoft allows a deleted user account to be restored within 30 days, after which it is permanently deletedController, with IT
2Rejected and resubmitted invoice versions, imagesThe old AP capture platformSubscription end or migration that moves posted invoices onlyAP director and controller
3Supplier threads in personal mailboxesIndividual Exchange Online mailboxesLicense removal; default 30-day grace, plus 30 more with Delicensing Resiliency, then deletionAP director, with IT and counsel
4Match results and match rulesCapture platform, audit tool or an outside firm's systemPlatform retirement or end of the audit contractController, with counsel for firm papers
5Shared AP mailbox threadsShared mailbox under a retention policyThe company's retention policyAP director, IT and counsel
6Posted invoices, payments and credit memosERPUsually years later, under tax and audit retentionController 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.

DateEventRecord classes affectedDecision needed
December 1Planning call; partner asks the inventory questionsNone yetAP director agrees to list record classes and dates
December 15Inventory complete at metadata levelAllController reviews against the retention policy
January 10Migration scope fixed: open invoices and two years of posted headersRejected versions and images out of scopeFinance leadership decides whether to archive out-of-scope items
February 1Two AP specialists leave in the reorganizationPersonal mailboxes and spreadsheetsIT and the AP director decide what moves to the shared mailbox first
March 1Cutover to the new platformOld platform becomes read-onlyNone, if earlier decisions were made
March 31Old platform contract endsAnything not archived from the old platformToo late to decide
Early AprilLeavers' mailboxes, delicensed February 1, pass the end of the 30-day grace plus 30 days of Delicensing ResiliencyLeavers' mailboxesToo 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 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.

DecisionApproverAdvisor
Archive out-of-scope capture platform data before contract endController or CFOIT, AP director
Move leavers' recovery threads into the shared mailboxAP directorIT, counsel on personal data
Keep personal spreadsheets as company recordsControllerIT
Request outside audit firm working papersCFOCounsel
Extend any retention period beyond policyFinance leadershipCounsel

A data retention policy template shows how companies write these rules down, and the guide to inactive mailboxes for former employees 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 applies the same deadline logic across several companies, and day 1 readiness 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 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, check the company on who qualifies and read the program terms before 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

Should the company extend the old AP platform contract to protect the history?

That is a business decision for finance leadership, counsel and IT, weighed against cost and the company's retention policy. A partner should point out the date and what sits only in the old platform, then step back. Never recommend an extension on the strength of a possible license.

Are invoices and payments at risk at all, given tax retention rules?

Posted invoices and payments usually stay in the ERP for years because of tax and audit needs. The records at risk are the ones that explain recoveries: rejected versions, match logic, correspondence and close notes, which often sit outside the ERP.

Sources

  1. irs.gov/businesses/small-businesses-self-employed/ho…
  2. learn.microsoft.com/en-us/exchange/recipients-in-exchange-online…
  3. learn.microsoft.com/en-us/microsoft-365/admin/add-users/restore-…
  4. ico.org.uk/for-organisations/uk-gdpr-guidance-and-resou…
  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