Finance stack redesign referral meeting agenda: a 20-minute owner conversation on reconciliation history

Short answer

Hold a 20-minute conversation in five blocks: what the new system carries over, which reconciliation types keep their reasoning, what one complete case looks like, who controls the records, and the owner's decision. Each block has its question, the person who should answer, and what a useful answer sounds like. The meeting closes with one recorded outcome: introduce the company to SourceX, revisit after go-live, or stop.

Visual briefFull-size diagram
A meeting clock whose outer ring is split into five timed segments that light up in turn, each with its agenda question on a leader line, ending at the owner's decision.
The 20-minute owner conversation as a clock. The questions are fixed; block lengths can flex.

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.

AttendeeWhat they knowBlocks
Controller or finance leadHow reconciliations are closed, documented and approved today1, 2 and 3
AP lead or outsourced bookkeeperWhere exception notes, vendor emails and credit approvals actually live2 and 4
Owner or CEOWho controls the records and who can authorize a licensing discussion4 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.

MinutesQuestion for the blockWho answersA useful answer sounds like
0-3What 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-8Which 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-12Can 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-16Who 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-20Does 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 hearWhat it usually meansYour note
"Corrections just show as the final balance."The redesign is balance-forward and the reasoning sits in the old systemRecord how long the old ledger stays readable
"We fix it and re-reconcile."Corrections were treated as new eventsAsk whether the original variance and approval are kept anywhere
"The notes are in the bookkeeper's email."Reasoning exists but is outside company systemsRecord who holds it and under what terms
"Our retention policy covers that."Records exist, but links between them may notNote the policy name; retention is not the same as context
"Vendor contracts are confidential."Rights may limit what can be licensedFlag 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.

  1. 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.
  2. 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.
  3. 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.

  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

Why 20 minutes rather than a full workshop?

The meeting only needs descriptions, not analysis. A 20-minute slot is easier for an owner to give, and it keeps the conversation from drifting into the redesign itself, which has its own meetings.

Should the outsourced bookkeeper attend?

If the bookkeeper closes reconciliations, yes, for blocks 2 and 4. They often know better than anyone which exceptions carry notes and which are only signed off, and whose systems hold the files.

Is this the same meeting as the redesign kickoff?

No. Keep it separate. The kickoff is about the future stack; this conversation is about which closed history the redesign leaves behind, and it needs the owner present for the last block.

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