Private equity and portfolios
Intercompany reconciliation histories in multi-entity groups: AI value
By SourceX Editorial · Updated
Short answer
Intercompany reconciliation records show how a multi-entity group finds, explains and clears mismatches between its entities' books, which makes them useful to AI developers building finance agents. Their value sits in the resolution trail: mismatch type, evidence, adjusting entry and approver. Balances that matched automatically carry little signal; documented exceptions carry most of it.
Key takeaways
- Intercompany records gain value from the resolution trail, not from balances that matched on the first pass.
- Each exception record is most useful when it names the mismatch type, the evidence, the adjusting entry and the approver role.
- Entity names, bank details, employee names and tax positions are removed or held back before any review outside the group.
- ERP consolidations are when reconciliation history is most often lost, so export close-tool history and entity mappings first.
What counts as an intercompany reconciliation record?#
An intercompany reconciliation record is any document that shows two entities' views of the same transaction being compared, explained and brought into agreement. In most groups that trail is split across the ERP, a close-management tool, spreadsheets and email.
The multi-entity accounting records that matter most are the ones where a person had to decide something. A balance that matched automatically shows a rule working. An exception that took several emails, a corrected allocation and a controller's approval shows a professional reasoning through a problem.
- Intercompany receivable and payable entries, by entity pair and period.
- Due-to and due-from balance reports, plus matching and exception reports.
- Recharge and allocation invoices for shared services, management fees and cost sharing.
- Intercompany loan schedules, interest calculations and settlement records.
- Reconciliation workpapers with preparer and reviewer sign-offs.
- Adjusting and elimination journal entries with their supporting memos.
- Dispute threads by email or ticket where one entity challenged a charge.
- Close checklists and task histories showing who did what, and when.
Intercompany mismatch types, resolutions and approvers#
Intercompany mismatch types give the records their structure, because each type has a typical cause, a typical fix and a typical approver. Groups that tag exceptions by type, even loosely, produce far more usable histories than groups that leave the reason in an unlabeled spreadsheet comment.
The approver field is often the weakest part of the record. Close tools capture a reviewer sign-off, but escalations to the group controller or tax lead frequently happen by email and never reach the workpaper. Linking those approvals back, even as a role and a date, turns an unexplained adjustment into a documented decision.
| Mismatch type | Typical cause | Resolution recorded | Usual approver |
|---|---|---|---|
| Timing difference | One entity books in the period, the other in the next | Accrual or cut-off adjustment with dates | Entity controller |
| Foreign exchange difference | Different rates or revaluation timing | FX adjustment and rate source | Group controller |
| Missing counterpart entry | One side never recorded the charge or receipt | Entry posted by the missing side, with reference | Entity controller |
| Amount dispute | Disagreement over an allocation or recharge basis | Corrected invoice or allocation memo | Both entity controllers, escalated to group |
| Wrong counterparty | Transaction coded to the wrong entity | Reclassification entry | Preparer with reviewer sign-off |
| Classification difference | Expense for one side, inventory or asset for the other | Reclassification citing the group policy | Group controller |
| Duplicate posting | Same invoice entered twice or by both sides | Reversal entry | Preparer with reviewer sign-off |
| Pricing true-up | Year-end adjustment to intercompany pricing | True-up entry with its calculation | Group controller and tax lead |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Why AI developers value the resolution trail#
AI developers value the resolution trail because it records multi-step financial judgment: two inconsistent records, a search for evidence, a decision under a policy and a documented approval. That is the sequence finance agents attempt during month-end close, and real exceptions are hard to simulate convincingly.
Under the SourceX Enterprise Data Value Framework, intercompany histories draw on domain expertise, human-generated signal and data cleanliness, and they resist reproducibility because synthetic examples miss the untidy causes real groups face. Privacy burden and preparation cost reduce net value when records are thick with names and bank details.
| Signal | Raises value | Lowers value |
|---|---|---|
| Linkage | Exception linked to entries, evidence and approval | Balances with no explanation attached |
| Narrative | Written reasons in memo fields and workpapers | Blank memo fields and bare codes |
| History | Many closes in one consistent system | History lost in an ERP migration |
| Labels | Mismatch type and resolution recorded | Reason buried in unstructured comments |
| Approvals | Reviewer and approver roles captured | No evidence of sign-off |
What has to be removed or held back?#
Entity names, bank account details, employee names and tax positions have to be removed or held back before intercompany records are reviewed outside the group. Approvals usually keep their meaning when names are replaced with roles, such as entity controller or group controller.
Some material should stay out entirely: transfer pricing studies and tax planning memos, legal advice in dispute threads, lender reporting packages and anything covered by confidentiality terms in credit agreements or investor documents. Auditors' own working papers generally belong to the audit firm, so only the company's workpapers are in scope.
Customer and vendor names also appear in recharge detail when shared costs are allocated by account. Those names are confidential details to remove, not context to keep.
Illustrative: a distribution group consolidating its ERP#
Illustrative: a fictional industrial distribution group, Orvale Industrial Holdings, owns several US subsidiaries that sell to each other, share a central warehouse and pay management fees to the holdco. Each subsidiary ran its own ERP before acquisition; the group is moving everyone onto NetSuite and uses a close-management tool for reconciliations.
Before the legacy ERPs are retired, the controller exports intercompany ledgers, the close tool's reconciliation history with attachments, dispute threads from the shared intercompany mailbox and a table mapping old entity codes to new ones. Entity names become codes, approvers become roles, and the transfer pricing file and lender packages are excluded.
The group first uses the history to write a close playbook that lists each mismatch type and its fix. Later, the CFO takes the same inventory into a metadata-only fit check to see whether a licensable set exists.
How to keep reconciliation history through an ERP consolidation#
Reconciliation history survives an ERP consolidation only if the team exports it deliberately, because new systems usually import opening balances rather than the trail behind them. The close team, not the implementation partner, is best placed to say which history matters.
Start before the legacy system's license ends, since reconciliation attachments and reviewer comments often live in the close tool rather than in the ERP, and they disappear with the subscription.
- Export intercompany subledgers by entity pair for every closed period still accessible.
- Export the close tool's reconciliations with workpapers, comments and sign-off timestamps.
- Keep the entity and account mapping between old and new charts of accounts.
- Archive dispute threads and tag them with period and entity pair.
- Record which entities merged, dissolved or changed codes, and when.
- Store everything read-only with a provenance note naming systems and periods.
How SourceX looks at finance close records#
SourceX looks at finance close records through the SourceX five-step transaction, starting with metadata such as systems, periods and record types. Finance records usually carry a heavier privacy burden than operational records, so the Rights and Preparation steps get more attention, and the CFO and each entity's signer approve what is released.
The SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization. How any license income is recognized or taxed is a question for the group's accountants and tax advisers.
Frequently asked questions
Should auditors be involved before close records are reviewed?
Tell them early if the records include audit-related workpapers. The company's own reconciliations and entries are its records, but auditors' working papers generally belong to the audit firm and stay out of scope. Engagement letters and confidentiality terms are worth checking with the auditors and counsel.
Are intercompany records less sensitive than customer records?
In some ways. They often contain fewer consumer personal details, but they hold bank information, employee names, pricing between entities and tax positions. Preparation removes those details, and some documents, such as tax memos and lender reports, are excluded entirely.
Can a group with only a few entities still have useful history?
Yes, if the history is documented. A group with a handful of entities that records mismatch types, reasons and approvals across many closes can be more useful than a large group with blank memo fields. Linkage and narrative matter more than entity count.
Should we tidy up old reconciliations before anyone reviews them?
No. Rewriting history destroys the signal and can create audit questions. Preparation should remove identifiers and confidential details, not correct past entries or fill in missing reasons. Unresolved or incomplete items can simply be labeled as such.
Does licensing finance records require board approval?
That depends on the group's governance, credit agreements and investor documents. Many groups take any data license to the board or sponsor, and lender consent may apply to IP licenses. Counsel and the CFO should check those documents before scoping begins.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.