Finance stack redesign archive context checklist: saving reconciliation reasoning before the old ledger retires

Short answer

Check a handful of facts at three points: before the new finance system is announced, before cutover, and before the old system goes read-only and then retires. Each item names what to confirm, who on the finance team owns it, and what is lost if it is skipped. The test throughout is one question: which reconciliations still show the original discrepancy and the approved resolution, and will they after the move?

Visual briefFull-size diagram
A stepped countdown descending toward the date the old ledger goes read-only and then retires, with checklist items ticking at announcement, cutover and retirement.
The checklist as a countdown. Each date comes from the company's own plan or license terms.

This checklist belongs to the hub guide on reconciliation history. It sets no deadlines of its own. Each date comes from the company: go-live from the project plan, the read-only window from the outgoing vendor, the license end from the contract.

The three dates to get in writing

Ask for these at the start, and write them at the top of the checklist exactly as given.

DateWhy it matters for reconciliation historyUsually set by
Announcement of the new systemMigration scope is still open; full history can still be addedCFO and owner
Cutover to the new ledgerOpen items move; closed exceptions stay behind unless someone planned otherwiseController and implementation partner
Old ledger read-only end or retirementNotes, attachments and approval logs in the old system stop being reachableOwner, through the old vendor's contract

The third date is the real one. A read-only login delays the loss; it does not prevent it.

Before the change is announced

Nothing has moved yet. The aim is to make sure the migration plan is not balance-forward by default without anyone choosing that.

  • ☐
    Migration approach. Confirm whether the plan carries closed history or only open items and opening balances. Owner of the answer: CFO with the implementation partner. If skipped: closed exceptions stay in a system nobody plans to keep.
  • ☐
    Which close tasks leave a written trail. Go through the month-end task list (supplier statement tie-outs, PO match exceptions, cash, corporate cards, intercompany) and mark each one: explained with comments, files and a named approver, or merely ticked as done. Owner: controller. If skipped: nobody knows which history is worth keeping.
  • ☐
    Where the reasoning lives. Confirm whether investigation notes and vendor emails sit inside the ledger, in a shared mailbox, in spreadsheets or in a bookkeeper's portal. Owner: AP lead or outsourced bookkeeper. If skipped: the explanation is spread across systems with different end dates.
  • ☐
    Who controls each record set. Note whether a parent company, outsourced bookkeeper or payment platform holds records under its own terms. Owner: owner and counsel. If skipped: rights questions surface late.

Before cutover

Cutover is when corrections in the old system stop being the live record. This is a stage where context easily detaches from the numbers.

  • ☐
    What happens to closed exceptions. Confirm whether they migrate with their notes and approval links, migrate as bare entries, or stay behind. Owner: controller. If skipped: the new system shows clean history with no story.
  • ☐
    Whether fixes overwrote the original. Ask if a corrected period still displays the first variance or only the redone result. Oracle's NetSuite help is a useful illustration: edit the amount on a transaction that was already reconciled and it drops back to unreconciled, so the statement period has to be worked again and the surviving view may show only the end state. Owner: controller. If skipped: you cannot tell which periods still hold the discrepancy.
  • ☐
    Approval logs. Confirm whether approval logs from the old AP module or close tool are exported, archived or left in place. Owner: AP lead. If skipped: the "approved resolution" half of the sequence is lost first.
  • ☐
    Rough scale. Note years of history, number of active vendors and exceptions per month, in ranges. Owner: controller. If skipped: the owner cannot judge whether the question is worth their time.
  • ☐
    Owner briefed. Confirm the owner has heard, with your disclosure, that the history may have value outside the company. Owner: you, with the owner. If skipped: the choice is made by default.

Before the old ledger goes read-only and retires

This is where the decision closes. Retention rules continue, but the links between entries and their explanations may not.

  • ☐
    Read-only end date and what remains reachable. Confirm which notes, attachments and approval logs a read-only login can still open, and until when. Owner: owner, through the old vendor's contract. If skipped: the loss happens on a renewal date nobody tied to this question.
  • ☐
    Retention versus context. IRS guidance points to a three-year baseline for tax records, stretching to seven for a bad debt deduction and at least four for employment tax records. Those periods govern how long entries must exist; check separately whether the archive keeps each entry tied to its explanation. Owner: controller. If skipped: the company stays compliant but loses every reason.
  • ☐
    Owner's decision recorded. Introduce, revisit before retirement, or stop. Owner: you, with the owner. If skipped: the question ends unanswered.

Illustrative: what the checklist caught

Illustrative. A fictional 460-person dental services organization is folding 14 clinic ledgers, each kept by a different bookkeeping firm, into one cloud ERP. The dates and findings below are invented.

Checklist itemFindingEffect on discrepancy-to-resolution history
Migration approachEach clinic's ledger arrives as a single opening balance per accountEvery closed clinic-level fix depends on 14 separate old files
Close tasks with a written trailIntercompany charges between clinics and the management company carry memos and approvals since 2019; card tie-outs are ticked onlyIntercompany is the one area holding the full sequence
Where reasoning livesExplanations sit in two bookkeeping firms' client portalsContext survives only while those engagements and portals continue
Read-only endBookkeeper portal access ends when each engagement letter is terminatedThe decision window differs clinic by clinic
Who controls each record setEngagement letters are silent on who owns portal contentCounsel needs to answer before any discussion
Owner's decisionRevisit after the first six clinics migrate, with the fractional CFO leadingThe choice stayed with the owner

The reconciliation exceptions data type page explains why a full exception sequence matters to AI developers. For the owner conversation itself, use the finance stack redesign meeting agenda.

Who decides, what you can share, and what stays unknown

Whether to discuss licensing is the owner's or CEO's call. Whether supplier confidentiality clauses, bookkeeper engagement letters or other obligations narrow it is counsel's. Your role is to ask and record; ledgers, close workpapers and supplier files never pass through you, not even an example.

Check fit before introducing: 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.

Open until SourceX looks: whether buyers want this history, what de-identification it needs, how the rights review comes out, and what the company might be offered. SourceX licenses approved business data directly from companies for AI training and evaluation, and pays any referral reward from its own funds, never out of the company's payment. For scale only, an Illustrative $250,000 payout to the company would mean a $62,500 reward under the default the greater of $50,000 plus 5% and 15% rate; the rewards page lists every condition. Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. If the owner opts in, the finance stack redesign introduction email is the next document.

Related tools: the NetSuite implementation checklist for the project side, the tech stack audit template and questions to ask about a company's tech stack for discovery, and the Lehman formula comparison if you are weighing fee conventions.

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 the checklist shows closed reconciliations that still carry the discrepancy, the approval and the fix, and the owner wants to talk before the old ledger retires, register as a partner, confirm fit on who qualifies, and keep the program terms close.

  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 IRS retention period mean the reasoning is safe?

No. The IRS guidance says how long records should be kept, not whether the notes and approvals that explain each correction stay linked to the entries. A company can keep every record and still lose every explanation in a balance-forward migration.

Who should keep this checklist during the redesign?

Usually the fractional CFO, since the redesign is theirs to lead. The controller and AP lead answer most rows; the owner answers the rights and decision rows.

What if the old ledger is a desktop file rather than a cloud system?

The same three milestones apply. Note where the file and its attachments are stored, who can open them, and whether the software license that reads them will lapse, because that can end access as surely as a subscription.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/rewards
  3. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  4. irs.gov/businesses/small-businesses-self-employed/ho…

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