Which reconciliations show the original discrepancy and approved resolution?
Ask the question as written, because the distinction matters. Every company reconciles. What makes a reconciliation history useful outside the company is the full sequence for each exception: the discrepancy as first found, the investigation, the approval, and the correcting entry, linked together.
In this guide, the records are the company's vendor payment and correction histories: what it paid its own suppliers and contractors, where those payments went wrong, and how it fixed them. (This is unrelated to SourceX's own term, Actual Supplier Payout, which is only used to calculate a referral reward.)
Fractional CFOs are well placed to ask, because a finance stack redesign is usually theirs to lead: replacing an entry-level ledger with an ERP, adding AP automation, introducing a close management tool, or consolidating entities. In that project the CFO sees exactly which history will be carried over and which will remain in a system nobody logs into again.
A useful answer names reconciliation types, not a yes or no: "vendor statement and three-way match exceptions since 2018 have notes and approvals; bank reconciliations are signed off with no commentary; intercompany lives in spreadsheets." That sentence is metadata, and it is enough to judge whether an introduction makes sense.
Evidence asset: one vendor variance from discrepancy to correction
Illustrative. A 300-person regional distributor is moving from a legacy ledger and spreadsheets to a cloud ERP with AP automation. One vendor invoice shows what a complete case looks like and what the migration plan keeps.
| Stage | What was recorded | Where it lives today | Carried into the new stack? |
|---|---|---|---|
| Discrepancy found | Invoice billed at $12,400 against a purchase order of $10,560: a $1,840 price variance | Three-way match exception in the old AP module | No: only open items migrate |
| Investigation | Buyer's note: contract price not updated after a renegotiation; vendor confirmed by email | Note and attached email on the exception | No |
| Approved resolution | Controller approved a $1,840 credit memo request | Approval log in the old system | No |
| Correction | Credit memo applied; vendor statement reconciled for the month | Ledger entry and vendor reconciliation | Yes, inside the opening balance only |
| Follow-up control | Contract price table updated; similar variances checked for three months | Spreadsheet owned by the AP lead | Unknown |
The last column is the conversation. If most closed exceptions look like the first four rows and stay readable, the company holds discrepancy-to-resolution records. If they collapse into an opening balance, that history is effectively gone. The reconciliation exceptions data type page explains why this sequence matters to AI developers; this guide is about catching it at the redesign.
Why are vendor payment and correction histories easy to overlook?
Finance migrations are judged on whether the opening trial balance ties and whether open payables and receivables came across. Closed reconciliations are history, and history gets a read-only login or a folder of exported reports.
The trouble is that a corrected reconciliation looks clean afterward. Systems treat corrections as new events: in NetSuite, for example, changing the amount of a previously reconciled transaction makes it unreconciled, and someone has to open the right statement period and reconcile it again. The reasoning in between (the variance, the vendor call, the approved credit) lives in notes, attachments and approvals. A balance-forward migration keeps the result and drops the reasoning.
Retention rules do not close the gap. The IRS generally suggests keeping tax records for three years, seven years for a bad debt deduction, and employment tax records for at least four years. Those rules say how long records should exist, not whether the notes and approvals that explain each correction stay linked to them. A company can be fully compliant and still have lost every explanation.
Four metadata questions for the owner
Stay at metadata level: what exists, how much, how long, which system and who owns it.
- Which types keep the reasoning? Which reconciliation types are closed with notes, attachments and approvals, and which are only signed off?
- What does the migration carry? Will closed exceptions come across with their links, or only open items and opening balances, and how long will the old system stay readable?
- How much history? Roughly how many vendors, exceptions per month and years of history, across which systems?
- Who controls it? Do outsourced bookkeepers, a parent company or payment platforms hold any of these records under their own terms, and who can authorize a licensing discussion?
Record answers by reconciliation type, with ranges. You never send ledgers, workpapers or vendor files, even as a sample; the company shares anything further directly with SourceX after it applies. The finance tech stack inventory template helps you map systems first, the tech stack questions cover broader discovery, and ERP implementers will recognize the pattern from the NetSuite projects guide.
How do you disclose the reward and get the owner's permission?
Ask permission before raising SourceX, and disclose your interest at the same time. Check your engagement letter and any professional rules that apply to you, and put the disclosure in writing before any introduction.
If the owner wants to hear more, explain that SourceX licenses approved operating records directly from companies for AI training and evaluation and handles the agreement, rights review, data preparation and delivery. SourceX funds any referral reward separately, so it does not reduce the company's payment. If the owner says no, the redesign carries on and the records decision is still documented.
Describe the reward exactly: on a company's first qualifying transaction the default is 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%. Illustrative arithmetic only, not a promise of earnings: a $400,000 payout to the company for a qualifying completed handoff would produce a USD 70,000 reward (USD 50,000 plus 5% of USD 400,000, which is more than 15% of it). 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. The rewards page lists every condition. If you are weighing how a referral reward compares with other fee conventions, the Lehman formula comparison sets them side by side.
Does the company qualify, and what stays unknown?
Check who qualifies first. The introduced company needs 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.
| What you can know at metadata level | Who usually confirms it | What stays unknown until SourceX reviews it |
|---|---|---|
| Old and new systems, reconciliation types documented | Controller or finance lead | Demand for these records |
| Approximate volumes and years | Controller or IT | What must be de-identified |
| Who controls each record set | CEO, owner or counsel | The rights review, including vendor confidentiality terms |
| Who can authorize a discussion | CEO or owner | Any offer, and any reward |
Sign the Channel Partner Agreement before submitting an introduction, and introduce only with the decision-maker's agreement. 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. To find other clients in a similar project, use the network opportunity finder; more playbooks sit under /for, including fractional CFOs and the partner program for fractional CFO firms.
Go deeper on finance stack redesign records
- Finance stack redesign introduction email: a ready-to-adapt email for introducing an opted-in owner to SourceX before the old ledger retires.
- Finance stack redesign meeting agenda: a timed agenda for the owner conversation about reconciliation history and the referral option.
- Finance stack redesign archive context checklist: a checklist, by owner, of the cutover, export and attachment questions to settle before the redesign.
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 client's closed reconciliations keep the discrepancy, the approval and the fix, and the owner wants to talk before cutover, register as a partner, check the company on who qualifies, and keep the program terms in front of you when you write.