The checklist is part of the invoice processing rollout guide. The conversation that starts it is the 30-minute meeting agenda; this page is the follow-through that keeps those answers current until the old system goes dark.
Pinning the three dates before any item
A countdown is only useful if its clock is real. Write down each milestone as the company documented it and who set it.
| Milestone | Where the date usually comes from | If nobody has set it |
|---|---|---|
| Announcement | The AP automation business case or the project charter | Treat the checklist as early and work through milestone one calmly |
| Cutover | The go-live plan for the new capture and approval tool | Record who owns the go-live decision |
| Switch-off | The old capture subscription end, an ERP module retirement ticket or an IT plan | Leave it open; the item becomes "find out who decides" |
Mark each item confirmed (someone with authority said so), unknown (with a name for who will find out) or at risk (the current plan drops it). A dashboard that shows paid invoices is not confirmation that rejected ones are kept. Keep the sheet yourself, one row per item, and record configuration and ownership only: no invoice images, vendor names or amounts.
Milestone one: before the rollout is announced
Nothing about the old history has been decided yet, so this is the cheapest moment to ask.
| Confirm | Owner | If it is skipped |
|---|---|---|
| Whether rejected and held invoices stay on record with the approver's reason, date and user | AP lead | The team discovers after go-live that only posted invoices exist |
| Which system raises duplicate alerts: the capture tool, the ERP or both | AP systems admin | Flags held by the scanning vendor vanish with the subscription |
| Where price and quantity mismatches and their approvals are recorded | AP lead | Match decisions survive only as a corrected invoice with no reason |
| Who owns AP history, and whether a shared services provider or vendor contract limits reuse | Controller | Rights questions surface after an introduction is made |
The capture tool deserves a separate look. Microsoft's invoice capture, for example, detects duplicate files by checksum but has no built-in validation for an invoice with the same number, so companies often add their own check. Where that custom rule logs its result is a question only the systems admin can answer.
Milestone two: before cutover to the new tool
Here the data load scope is being written, and anything outside it is at risk by default.
| Confirm | Owner | If it is skipped |
|---|---|---|
| Whether the data load covers closed and stopped invoices or only open ones | Rollout project lead | Rejected history is left in the old system without anyone deciding to |
| Whether workflow history tables, including rejection reasons, are inside the agreed archive scope | AP systems admin | Reason text stays in a table no standard report exposes |
| Where AP clerks wrote resolution notes: ERP notes, a shared mailbox or a ticket queue | AP lead | The explanation splits from the credit memo it explains |
| How many years and roughly how many exceptions per month the old system holds | AP lead or systems admin | Nobody can describe the archive when it matters |
A Workflow rejected status in Dynamics 365 Finance, for instance, carries the approver's reason, while a Workflow failed status records a validation error. The two mean different things, and an archive plan should keep them apart.
Milestone three: before the old system is switched off
This is the last point at which the company can still choose what to keep.
| Confirm | Owner | If it is skipped |
|---|---|---|
| Whether the old capture tool is going read-only, exported or deleted, and on what documented date | Controller and IT | Duplicate alerts and capture metadata are deleted with the account |
| Whether retention rules are being read as a full archive policy | Controller | Tax-compliant records remain while the decision trail is lost |
| Who signs off the final archive and where it will live | Controller or CFO | Nobody is accountable for what was dropped |
| Whether the owner wants to hear about licensing before deletion | Owner | The question is never asked while the history still exists |
Retention rules do not answer the question for you. The IRS default record-keeping period is three years, with seven for certain bad-debt deductions, and creditors can require longer. Those periods describe records that support a tax return, not every rejected invoice or clerk note.
Turning a finished checklist into an introduction
A complete sheet describes what the company holds. It does not decide whether the company qualifies. Check fit before you raise SourceX: 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.
| Known from the checklist | Unknown until SourceX reviews it |
|---|---|
| Record types, systems and years, as the company described them | Whether there is current demand for AP exception records |
| Who owns AP history and who signs off the archive | The rights review result, including vendor and provider contracts |
| The documented cutover and switch-off dates | Any offer to the company |
| That the reward was disclosed | Whether any referral reward becomes payable |
Ask permission before mentioning SourceX and disclose your interest at the same time. SourceX licenses approved business data directly from companies for AI training and evaluation, and pays any eligible reward separately under its terms, never from the company's payout. Illustrative only: a $400,000 payout to the company for a qualifying completed handoff would mean a $70,000 default reward. Sign the Channel Partner Agreement first; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. When the owner opts in, use the introduction email. The CRM migration handoff checklist, the system decommissioning guide and the Bill.com invoice history page cover neighboring switch-off moments.
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 milestone three is still ahead and the owner wants to talk before the old AP system is switched off, register as a partner, confirm the company against who qualifies, and read the program terms first.