This agenda is part of the hub guide on reconciliation history, which explains why variance-to-fix history matters. Use this page for the conversation itself; a separate checklist, linked in the decision section below, covers the dates and owners to confirm around it.
Who to invite and how to frame it
Keep the room small. Three people can answer every block, and the owner must be present for the last one.
| Attendee | What they know | Blocks |
|---|---|---|
| Controller or finance lead | How reconciliations are closed, documented and approved today | 1, 2 and 3 |
| AP lead or outsourced bookkeeper | Where exception notes, vendor emails and credit approvals actually live | 2 and 4 |
| Owner or CEO | Who controls the records and who can authorize a licensing discussion | 4 and 5 |
Frame the invite in one line: "Twenty minutes on which closed reconciliations keep their notes and approvals before we switch systems. Description only; nobody sends files." That sentence matters to finance teams in particular, because the instinct is to prepare a sample workpaper. Say clearly that nothing will be shared.
Schedule it after the target system is chosen but before the data migration approach is signed off, when "balance forward or full history" is still an open question.
The 20-minute run sheet
Illustrative. A 210-person specialty food distributor is moving from an entry-level ledger and spreadsheets to a mid-market ERP with AP automation. The part-time CFO leading the project runs this agenda.
| Minutes | Question for the block | Who answers | A useful answer sounds like |
|---|---|---|---|
| 0-3 | What will the new system carry over: open items and balances, or closed history too, and how long will the old one stay readable? | Controller | "Open AP and AR plus opening balances. Read-only access to the old system for a year." |
| 3-8 | Which reconciliation types are closed with notes, attachments and approvals, and which are only signed off? | Controller and AP lead | "Vendor statements and three-way match exceptions have notes since 2019. Bank recs are sign-off only." |
| 8-12 | Can you describe one corrected exception from discovery to correcting entry without opening it? | AP lead | "Price variance, buyer note, controller approval, credit memo. All four are linked in the old AP module." |
| 12-16 | Who controls these records: the company, an outsourced bookkeeper, a parent company or a payment platform? | Owner and AP lead | "Ours, but the bookkeeper's portal holds 2018 to 2020 attachments." |
| 16-20 | Does the company want to hear how licensing approved records works, and who would lead that conversation? | Owner | "Yes, I would lead it; leave payroll out entirely." |
What block 2 is really testing
Every company reconciles, so "do you reconcile?" tells you nothing. The useful distinction is whether each exception keeps its whole sequence: the mismatch as first found, the investigation, the approval and the correcting entry. A reconciliation marked complete with no commentary has the result without the reasoning.
Why block 3 asks for a description, not a sample
A described case shows the controller understands where each piece lives. It also avoids a common mistake in these meetings: someone opening the old system and sharing a screen. Keep the room at metadata level; the company shares anything further directly with SourceX if it applies.
Reading the answers
Some answers should change what you write in your notes, and a few should end the conversation early.
| What you hear | What it usually means | Your note |
|---|---|---|
| "Corrections just show as the final balance." | The redesign is balance-forward and the reasoning sits in the old system | Record how long the old ledger stays readable |
| "We fix it and re-reconcile." | Corrections were treated as new events | Ask whether the original variance and approval are kept anywhere |
| "The notes are in the bookkeeper's email." | Reasoning exists but is outside company systems | Record who holds it and under what terms |
| "Our retention policy covers that." | Records exist, but links between them may not | Note the policy name; retention is not the same as context |
| "Vendor contracts are confidential." | Rights may limit what can be licensed | Flag for counsel; do not debate it in the meeting |
Two documented facts help with the second and fourth rows. In NetSuite, for example, changing the amount of a previously reconciled transaction makes it unreconciled, and someone opens the right statement period and reconciles it again, so the corrected state can overwrite the visible story. And the IRS generally suggests keeping tax records for three years, seven for a bad debt deduction and at least four for employment tax records: rules about how long records exist, not whether each correction stays linked to its explanation.
What the owner needs to hear before block five
Say three things plainly before asking for the decision.
What SourceX does. SourceX licenses approved business data directly from companies for AI training and evaluation, and handles the agreement, rights review, data preparation, delivery and payout. Nothing is shared unless the company agrees to terms.
Your interest, in writing. You are a SourceX referral partner and may receive a reward if a qualifying license completes and every condition in the terms is met. SourceX funds it separately; the rewards page confirms it never reduces the company's payment. Check your engagement letter and any professional rules that apply to you, and follow up the meeting with the disclosure in writing.
The term that sounds like their records. The company's own vendor payouts are its records. SourceX's Actual Supplier Payout is a separate term: what SourceX pays the company, used only to calculate a reward. Illustrative only: a $250,000 payout to the company would mean a $62,500 reward.
The decision this meeting produces
Record one of three outcomes, in the owner's words, in your notes and in the follow-up email.
- Introduce now. Confirm the company looks like a fit: 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. Sign the Channel Partner Agreement, then use the finance stack redesign introduction email.
- Revisit after go-live. Note the date the old ledger's read-only access ends, because that is when the choice closes, and track it on the finance stack redesign archive context checklist.
- Stop. Note that the question was raised and declined, and continue the redesign.
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. What stays unknown until SourceX reviews it: SourceX's current data needs for reconciliation histories, the rights review result, what must be de-identified, and any offer.
Before the meeting, the finance tech stack inventory template helps map which systems hold what. If the redesign also changes the account structure, the chart of accounts redesign guide explains why old and new codes need a map. For another finance meeting built on the same timed format, see the portfolio review meeting agenda, and the fractional CFO partner page covers the role more broadly.
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 owner chooses an introduction at minute 20 and the old ledger is still readable, register as a partner, check the company against who qualifies, and read the program terms before you write the follow-up.