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.
| Date | Why it matters for reconciliation history | Usually set by |
|---|---|---|
| Announcement of the new system | Migration scope is still open; full history can still be added | CFO and owner |
| Cutover to the new ledger | Open items move; closed exceptions stay behind unless someone planned otherwise | Controller and implementation partner |
| Old ledger read-only end or retirement | Notes, attachments and approval logs in the old system stop being reachable | Owner, 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 item | Finding | Effect on discrepancy-to-resolution history |
|---|---|---|
| Migration approach | Each clinic's ledger arrives as a single opening balance per account | Every closed clinic-level fix depends on 14 separate old files |
| Close tasks with a written trail | Intercompany charges between clinics and the management company carry memos and approvals since 2019; card tie-outs are ticked only | Intercompany is the one area holding the full sequence |
| Where reasoning lives | Explanations sit in two bookkeeping firms' client portals | Context survives only while those engagements and portals continue |
| Read-only end | Bookkeeper portal access ends when each engagement letter is terminated | The decision window differs clinic by clinic |
| Who controls each record set | Engagement letters are silent on who owns portal content | Counsel needs to answer before any discussion |
| Owner's decision | Revisit after the first six clinics migrate, with the fractional CFO leading | The 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.