Cash application exceptions retention timeline: what disappears first in a vendor switch

Short answer

Before a cash application vendor switch, inventory the record classes the outgoing tool holds that the ERP does not, the years they cover, who owns each one, and the exact date access ends. Match logs and applier notes usually disappear first, at cutover; remittance images and deduction cases go when read-only access ends. Bank statements and ERP settlements tend to survive. Work backward from the end date, and leave every keep-or-delete decision to the controller and counsel.

Visual briefFull-size diagram
A horizontal timeline from switch planned to tool decommissioned: match logs and user notes fade out at cutover, remittance images and deduction cases fade at the end of read-only access unless preserved, and ERP settlements and bank statements continue past the end.
Illustrative retention timeline for a fictional cash application vendor switch; real dates come from the contract and the company's policy.

This timeline is part of the cash application exceptions guide, which works through one short payment from bank credit to closed invoice. Here the question is narrower: when the tool that held that evidence is replaced, what fades out, in what order, and who has to say yes before anything is kept.

The retention timeline, stage by stage

A vendor switch has five dates that matter. Each one is a point where a record class can stop being reachable.

StageTypical date sourceWhat the company confirmsWho confirms it
1. Switch plannedProject charter or budget approvalRecord classes in the outgoing tool and the years they coverAR director
2. Contract noticeVendor agreementNotice period, read-only period after termination, and what the vendor returns on exitController or procurement
3. CutoverImplementation planWhich history migrates to the new tool, in what format, and what stays behindIT and the implementation lead
4. Read-only access endsVendor agreementThe last day anyone can open old remittances and casesController
5. DecommissioningIT asset planWhether any archive is kept, where, and for how long under policyController and counsel

The gap between stages 3 and 4 is where most history is quietly lost. During that window people can still look things up, so nobody feels the loss. On the morning after stage 4, the remittance behind a three-year-old deduction is simply gone.

For the general pattern of retiring a system, see application decommissioning. The SaaS inventory template gives a format for listing the tools themselves before you list their records.

What disappears first, and why

Records fade in a predictable order because migration plans are built around open items, not closed ones.

  1. Match suggestions and rule logs. The engine's proposed matches and confidence scores are rarely migrated, because the new tool has its own engine. They are the first to go, often at cutover.
  2. Applier notes and comments. Free-text notes on why a payment was split a certain way sit in the tool's own tables. If the new tool has no matching field, they stay behind.
  3. Parsed remittance lines. The structured lines extracted from a PDF or email (invoice, amount, deduction code) are tool-specific. The ERP usually keeps the settlement, not the parsed source.
  4. Remittance images and emails. Often attached inside the old tool rather than stored in a document system. They last until read-only access ends.
  5. Deduction cases. Closed cases with their routing, evidence and outcome usually stay in the old tool unless the project explicitly migrates closed history.
  6. ERP settlements and credit memos. These stay. The ERP is the system of record; in Dynamics 365 Finance, for example, a partial payment partially settles an invoice that stays open with a balance, so the arithmetic of the exception is in the ERP regardless.
  7. Bank statements. Banks and treasury systems hold these separately, commonly as camt.053 statement files reporting booked entries and balances. They outlast the tool switch.

The result is a common shape after a switch: the company can prove that a short payment happened and that a credit memo closed it, but no longer why. The evidence of judgment, items 1 to 5, is the part that disappears.

How long each record class tends to be kept

There is no single number. Each class is held for the longest of three things: the company's own retention policy, any legal or tax requirement that applies to it, and any contract term, such as a vendor's exit clause.

Record classWhat usually sets its lifeWhat to ask
Bank statementsTreasury and tax retention policyHow many years are kept, and where
ERP settlements, credit memosTax and audit retention policyWhether older years were archived out of the live ERP
Remittance images and emailsWherever they are stored; often only the old toolWhether a copy exists outside the tool
Deduction cases and notesThe old tool's contract and read-only periodWhether closed cases are in migration scope
Match logsThe old tool onlyWhether anyone has asked for them at all

On the tax side, the IRS's general rule is to keep records until the period of limitations runs out: generally three years from filing, six years in some cases of understated income, and seven years where a bad debt deduction is claimed. Receivable write-offs and deductions can touch that last category, which is one reason finance teams keep ERP records well beyond the life of a cash application tool. The IRS also notes that creditors or insurers may require records for longer. None of this tells a company to keep the tool's working evidence; it explains why the ERP side survives and the tool side often does not.

An Illustrative switch, worked backward from the end date

Illustrative. A 300-person industrial supplier replaces its cash application tool. The vendor agreement gives 90 days of read-only access after termination. The project team plans cutover for the end of the fiscal year.

DateEventRecord classes affectedStatus if nothing is decided
January 15Switch approvedNone yetAll reachable
March 1Notice given to vendorNone yetAll reachable
June 30Cutover; open items migrateMatch logs, applier notes, parsed linesNot migrated; readable only until September 28
September 28Read-only access endsRemittance images, closed deduction casesGone
October 31Old tool decommissionedAny residual exportsOnly what the company chose to archive

Working backward, the controller needs a decision on closed cases and remittance images before September 28, and a decision on migration scope before June 30. Eight years of deduction cases, by the AR director's estimate, ride on those two dates. A partner who notices this in March has done the useful part of the job by naming the dates to the right person.

Who must approve keeping anything

Keeping records past a planned deletion is a company decision, not a project task.

  • AR director: knows which record classes exist and which years matter. Raises the question; does not decide alone.
  • Controller: owns the retention policy for receivables and the vendor contract terms. Usually the decision-maker for what is archived.
  • Counsel: reviews whether customer contracts or privacy obligations limit keeping remittances, which name customers and sometimes contain personal data.
  • IT and the implementation lead: confirm what the tools can technically migrate or export. Technical ability is not authority.
  • CFO: approves any spend on archiving, and can prepare the case for a licensing discussion, which the CEO authorizes.

Do not advise the company to keep or copy records it has no authority or policy basis to retain. A partner gathers metadata only: record classes, years, rough volumes, systems, owners and dates. Never ask for a remittance, statement or export.

What qualifies, and what stays unknown

The 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. Partners sign the Channel Partner Agreement before submitting introductions.

What stays unknown until SourceX reviews it: buyer interest, how customer confidentiality terms affect remittances, which years are selected and whether an offer follows. To describe the systems involved, use the records across systems map; to hand the facts over, use the referral brief template. More sectors are on the industries hub.

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 cash application tool has a read-only end date and years of deduction cases behind it, register as a partner, check the company against who qualifies, and read the program terms before you name that date to the controller.

  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

Does the ERP not already hold everything the cash application tool held?

Usually it holds the result, the settlement and the open balance, but not the working evidence: the remittance image the applier read, the match suggestions the tool made, and the notes on why a deduction was accepted. Those tend to live only in the outgoing tool.

Should a partner ask the company to export the old tool before it closes?

No. A partner can point out the date and the record classes at risk. Whether anything is kept, copied or archived is a decision for the controller, counsel and IT under the company's own retention policy.

Sources

  1. irs.gov/businesses/small-businesses-self-employed/ho…
  2. learn.microsoft.com/en-us/dynamics365/finance/accounts-receivabl…
  3. iso20022.org/iso-20022-message-definitions
  4. 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