How to consolidate an add-on's accounting system without losing its history
To consolidate accounting systems after an acquisition, map the add-on's chart of accounts to the platform's, load opening balances and open items at a month-end cutover, reconcile one parallel close, then archive the legacy file read-only. Before the archive step, export the full transaction, attachment and audit history so it can be screened for data licensing.
What consolidating an add-on's accounting system involves
Consolidating accounting systems after an acquisition means moving the add-on onto the platform's ERP and chart of accounts, then retiring its old QuickBooks, Sage or Xero file. The platform takes mapped balances, open items and master data. The transaction detail, attachments and audit trail stay behind in the legacy file, which is then archived or cancelled.
That leftover history is the subject of this page. Finance teams treat it as a retention problem. It can also be an asset: years of vendor bills, approvals, collections notes and adjustments, tied to the email and tickets around them, are the kind of records AI developers license to train and test agents that do finance work. The decision on what to keep has to be made before the archive step, not after.
Which parts of the add-on's ledger move and which stay behind
Most integrations migrate what the platform needs to close the books and leave the detail in the legacy system. Decide each line deliberately rather than by default.
| Item | Treatment in the platform ERP | What happens to the detail |
|---|---|---|
| Chart of accounts | Mapped to the platform's accounts, departments, classes and locations | The legacy account structure and its change history stay in the old file |
| Opening trial balance | Loaded at the cutover date | Prior-period entries remain only in the legacy ledger |
| Open AR and AP | Loaded invoice by invoice so collections and payments continue | Closed invoices, credit memos and payment history stay behind |
| Vendors and customers | Deduplicated and merged into platform master data | Notes and terms history on inactive records tend to be dropped |
| Fixed assets | Register migrated with cost and accumulated depreciation | Disposal records and supporting invoices stay in the old system |
| Comparative history | Summarized monthly balances for the periods management reporting needs | Journal-line detail, memos and attachments stay behind |
| Approvals and audit trail | Not migrated; the platform starts a new trail | The only record of who approved what lives in the legacy file |
The last row matters most. Approval history, attachments and memos are what turn a ledger into a record of how finance work was actually done.
Timeline: what to do before the legacy file is archived
Run the records work alongside the finance integration so neither waits on the other.
| When | Finance integration task | Records task |
|---|---|---|
| First 30 days after closing | Take admin control of the legacy file, bank feeds and bill-pay tools; change approvers | Confirm who holds admin rights and switch off any auto-purge settings |
| Days 30 to 60 | Build the chart of accounts mapping and pick the cutover month | List every connected tool (AP automation, expense, payroll, CRM, ticketing) and the years each covers |
| Cutover month | Load opening balances, open items and master data | Take a full export of ledger detail, subledgers and attachments in native and open formats |
| First close on the platform ERP | Reconcile the parallel close and clear mapping exceptions | Check that the export opens outside the vendor's software and covers every year |
| Before cancelling the legacy subscription or server | Controller and auditor sign-off | Decide what is kept for retention, and whether the history deserves a licensing screen |
| After archive | Stub-period tax filings and audit requests | Store the archive under the platform's retention policy with a named owner |
Cloud accounting vendors differ in what they keep after a subscription ends, so read the vendor's current terms before cancelling. On-premise Sage or Dynamics servers carry the same risk when IT reimages the hardware. For retention periods, see how long to keep business records after closing.
Is the add-on's finance history worth screening for licensing?
Sometimes. A ledger on its own is rarely enough. The value sits in finance history that shows work being requested, reviewed and decided, linked to the conversations and documents around it.
| Signal | What to look for | Why AI buyers care |
|---|---|---|
| Depth | Five or more years of transaction detail, not only balances | Long histories show how decisions repeat and change |
| Attachments | Bills, receipts, contracts and statements attached to entries | Source documents paired with the entries they produced |
| Workflow traces | Approval chains, rejected bills, reversals, memo notes | Multi-step work with a visible result |
| Outcomes | Disputes resolved, write-offs, credit holds, collection results | Outcome labels make records useful for training and evaluation |
| Connected systems | Email, Slack or Teams, CRM, ticketing and project tools from the same years | Connected records show whole workflows, not fragments |
The company being introduced still has to meet the baseline: a US business with 50+ full-time employees at peak (contractors excluded), several years of documented operations, the right to license the records, and a sponsor with authority to sign. Finance history is stronger when it comes with the rest of the company's records. The who qualifies page sets out the full criteria.
Who can sign: the platform or the former owner?
Whoever holds the rights after closing can sign, and the purchase agreement decides who that is. Read it before anyone mentions licensing to the former owner or the platform board.
| Deal structure | Who holds the add-on's records | What to check first |
|---|---|---|
| Stock or membership-interest purchase | The acquired entity, now controlled by the platform | Platform board or sponsor approval; lender consents in the credit agreement |
| Asset purchase with books and records included | The buyer entity | The purchased-assets definition and any confidentiality covenants |
| Asset purchase with records excluded or copies retained | The former owner may hold rights to what it kept | The excluded assets schedule, purpose limits on retained copies, any license-back |
| Merger into the platform entity | The surviving entity | Whether the add-on's client contracts restrict reuse of client material |
When rights are split, both sides need to agree before anything is licensed, because SourceX deals are typically exclusive for AI training for an agreed term. The guide to excluded assets in an asset purchase agreement covers the clause questions in detail.
Who to talk to inside the platform
- Portfolio or platform CFO: owns the integration plan and the archive decision.
- Controller or integration lead: knows which legacy files, servers and subscriptions exist and when each is due to be shut off.
- Operating partner: decides whether a licensing screen belongs in the value creation plan and who at the platform would sponsor it.
- Former owner: relevant if they retained rights, rolled equity or still work in the business under a transition agreement.
- IT or managed service provider: holds the on-premise servers and backups that get wiped when hardware is retired.
- Auditors: sign off on what must be kept for the audit trail before anything is cancelled.
If you are new in the seat, the first 90 days plan for a new CFO shows where a records inventory fits alongside the close calendar. The add-on's customer history raises the same question; see what to do with old CRM data after a migration.
What to say to the platform CEO or sponsor
Raise it as a records decision first and a licensing question second.
Once the sponsor agrees to an introduction, the introduction email builder drafts an owner-approved version.
What to preserve before the legacy system is switched off
These exports stay inside the company. As a referrer you pass on basic fit information only, never the records themselves.
- General ledger detail for every year in the file, with memos
- AR and AP subledgers, including closed invoices, credit memos and payment applications
- Attachments: vendor bills, receipts, contracts and statements
- The audit trail or change log, with user names and timestamps
- Historical charts of accounts and the cutover mapping table
- Bank reconciliations and month-end close checklists
- Exports from connected tools such as AP automation, expense management and bill pay
- A native-format backup plus open-format copies (CSV for data, PDF for documents)
- A written note of who owns the archive and where it is stored
Payroll and employee files contain personal information. Keep them under HR's controls and out of any licensing discussion unless counsel advises otherwise.
Accounting and professional-rule points for the CFO
Two questions come up quickly once a license is on the table.
- Revenue recognition. How a license is structured affects when it is recognized. Under ASC 606 the analysis turns on whether the customer gets a right to use the IP as it exists when granted or a right to access it over the license period, as Deloitte's ASC 606 licensing roadmap explains. Take the specific answer to the company's auditors.
- Your own referral reward. If you are a CPA, the AICPA Commissions and Referral Fees Rule (ET 1.520) bars commissions where the member or firm also performs an audit, review, certain compilations or an examination of prospective financial information for that client, and permitted referral fees must be disclosed to the client; see the AICPA Code of Professional Conduct. State boards can be stricter.
This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.
How the introduction and reward work
- You confirm the sponsor is willing to talk, then send your referral link or submit the company through the referral form.
- SourceX checks size, history, breadth of records and rights with the sponsor, including which entity owns the add-on's history.
- The company builds a data inventory: each system, the years it covers and how it can be exported.
- Price and terms are agreed with the company before any buyer sees the opportunity.
- AI labs and data buyers review; the agreement is signed, the data is prepared under the agreed redaction rules and delivered, and the company is paid.
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It comes out of SourceX's fee, never out of the company's proceeds. The fractional CFO partner page covers the role in more depth.
When to skip the screen
- The add-on was a bookkeeping, payroll or outsourcing firm whose records mostly belong to its clients.
- The legacy file is already gone and nobody kept an export.
- The former owner kept the rights and will not engage, or the platform and former owner cannot agree who signs.
- The records are mainly consumer personal data or protected health information.
- The company being introduced does not meet the size and history baseline.
Next step
Put the records task in your integration plan before the cutover month. If the add-on's history passes the screen, register as a partner and make the introduction with the sponsor's approval.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Should we migrate the add-on's full transaction history into the platform ERP?
Usually not. Most teams load opening balances, open items and summarized monthly comparatives, and keep journal-line detail in an archived copy of the legacy file. Migrating every transaction is costly and forces old entries into a chart of accounts they were never coded to. Keep the archive complete and readable instead, with attachments and the audit trail, so auditors, tax advisers and any later licensing review can use it.
How do we merge two QuickBooks files after an acquisition?
Treat it as a migration rather than a merge. Pick the surviving ledger, either the platform ERP or one of the files, map the add-on's accounts to it, and import opening balances and open items as of a month-end cutover. Keep the add-on's original file as a read-only archive with its attachments. Check the vendor's current documentation for supported import tools before you start.
Can the add-on's former owner license the records after the sale?
Only if the purchase agreement left them the rights. In a stock purchase the acquired entity keeps its records, so the platform decides. In an asset purchase the records generally go to the buyer unless they were listed as excluded assets or the seller kept copies with permission to use them. Because AI-training licenses are typically exclusive for a term, both sides should agree in writing first.
Do license proceeds count toward the add-on seller's earnout?
It depends on how the earnout is defined in the purchase agreement. Earnouts tied to revenue or EBITDA may or may not capture one-time, non-operating income, and definitions often exclude items outside the ordinary course. Read the definitions with deal counsel before any license is signed, and tell the former owner early if it could affect their payment, so the question does not become a dispute.
Will a licensing screen delay the finance integration?
It should not. The screen runs in parallel and the only hard dependency is timing: take the full export before the legacy subscription or server is shut off. An initial screen needs only basic facts such as headcount, years of history and systems in use. The inventory, pricing and buyer review come later, with the company's sponsor, and never hold up the close or the cutover.
Related pages
- How long should you keep business records after closing a business?
- Which US businesses are a fit for a SourceX data licensing introduction
- Excluded assets in an asset purchase agreement: can the seller keep its data?
- A new CFO's first 90 days, with a data asset inventory built in
- What to do with old CRM data after a migration: keep, archive, delete or assess
- Prepare an owner-approved company introduction email
Free resources
- Client data licensing eligibility checker — A transparent preliminary screen for one company.
- Enterprise value calculator — Enterprise value from equity value, debt and cash.
- Earnout scenario calculator — Probability-weighted earnout value and its present value.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment