Intercompany Reconciliation Software: A Practical Guide

Intercompany reconciliation software helps a finance team compare both sides of activity between related entities, keep the open items visible, and carry a documented result into the report. A useful tool shows the entity pair, the period, the source record, and the person who still owns the difference. It does not ask the team to rebuild that trail in a spreadsheet every month.

Request information about your reporting setup

This guide is for controllers, family-office finance leads, and acquisition-led teams who already run more than one ledger. It covers what the software should do, which evidence to ask for in a demo. And how a read-only reporting layer differs from a close suite or an ERP. The seven-step process itself lives in the intercompany reconciliation process improvement guide. Use that page for the operating sequence, and use this one to judge the tool.

What intercompany reconciliation software should do

Start with the job, not the feature list. The software has to answer four questions about every material balance: which entities are involved. Which period the entry belongs to, which source record supports it, and who must clear the exception.

Both sides of the pair should be visible together. If Entity A records an amount due from Entity B, Entity B should show the matching amount due to Entity A. A total that nets to zero is not enough when the reviewer cannot see the transactions behind it.

IAS 24 requires an entity to identify related-party relationships, transactions, and outstanding balances, including commitments, and to disclose them where the standard requires it. The IFRS Foundation sets that objective in IAS 24 Related Party Disclosures. Software does not replace the accounting policy. It should make the outstanding items easier to find and explain.

A practical tool also keeps matching separate from resolution. A match can clear an obvious pair. An exception still needs a reason, an owner, and a next action. Forcing the difference to zero hides the item the reviewer most needs to see.

Which problems should the software remove?

Most teams do not buy intercompany reconciliation software because they lack a definition of the work. They buy it because the same problems return at every close.

• Mixed ledgers. QuickBooks, Sage, Yardi, MRI, AppFolio, and Rent Manager files do not share one counterparty list.
• One-sided entries. A management fee, allocation, or reimbursement is recorded in one entity and missed in the other.
• Cutoff and currency gaps. The same invoice lands in different months, or two books use different rates.
• Spreadsheet work-ups. Someone exports both sides, then loses the link back to the source transaction.
• Late eliminations. The consolidated report still includes amounts the group owes itself.

Helix Reports is built for that mixed-system case. It imports full general-ledger data as a read-only reporting layer, so the source books stay in place. The intercompany reconciliation product page shows the investigation path: entity pair, period, amount, source record, and a schedule for report-time elimination.

Ask whether the product writes back to the ledger. Helix does not. It does not replace bookkeeping, an ERP, or fund administration, and it does not post automated accounting entries into the source system. Corrections stay in the books of record. The reporting layer keeps the history of what was matched, what stayed open, and what was eliminated in the report.

How to evaluate intercompany reconciliation software

Score the product against work you already do. A polished dashboard that cannot find a $200 due-to/due-from difference is not a fit, even if the demo looks complete.

Use a short scorecard. Weight the factors before the demo, then score each vendor from 1 to 5. Keep the list under ten items so the comparison stays usable.

Bring one closed month to the demo. Include a reconciled pair, an open difference, a currency item if you have one, and a balance that should be eliminated. If the vendor cannot run that sample, treat the rest of the pitch as unproven.

What should a demo prove?

Ask the presenter to follow one open item from the source record to the report. The path should be short enough that a reviewer who did not prepare the file can repeat it.

1. Import the period from each source system without editing those books.
2. Filter to one entity pair, one account type, and one amount.
3. Open the source record, including system, entity, counterparty, and date.
4. Show why the item is matched, open, or needs review.
5. Record the status change and keep that history on the item.
6. Place the cleared amount on an elimination schedule for the report.
7. Leave the unresolved amount visible, with an owner and an age.

The useful test is reproduction. Hand the pack to someone who did not build it. They should name the account, the period, the open items, and the next action without a verbal tour.

On the Helix page, that path is concrete. A reviewer starts with transaction type, entity pair, month, and amount, then inspects the source line. The history can show a read-only import, a counterparty match, and a later status change when a difference is identified. The open amount stays open until the source entry is corrected. The report can still eliminate the matched activity and show the schedule.

Also test search. A global search by amount, name, or account matters when the matching entry sits in another file. Summary totals do not replace that search. An open difference needs the corresponding entry.

How do reporting layers, close suites, and ERPs differ?

Intercompany reconciliation software is not one product category. Teams usually meet three shapes, and they solve different problems.

A read-only reporting layer sits on top of the ledgers you already run. It standardizes entity, account, counterparty, and period, then reconciles and reports without changing the source system. Helix is this shape. Mapping rules are configured once and reused, and the how it works page explains the metadata approach behind that reuse. Consolidated balance sheet, profit and loss, and cash-flow reports can apply multi-level elimination after the extra setup those reports require.

A financial close suite is broader. It often manages the close calendar, account certifications, and journal workflows across the whole ledger, not only related-party pairs. That scope helps a large controllership team. It is more software than a multi-entity group needs when the pain is mismatched balances and manual report work-ups. The financial close software comparison covers that wider buying question.

An ERP or a new core ledger can own intercompany if every entity moves onto it. Many family offices and acquisition-led teams cannot do that quickly. Their entities stay on the systems operators already use. A reporting layer lets the group report across those systems while the books remain where the transactions start.

Do not treat a consolidation module as proof of reconciliation quality. Consolidation can add up entities. Reconciliation has to show whether the amounts between them agree, and which items still do not.

Which intercompany items should the software track?

A demo built on one due-from account can hide the items that actually delay the close. List the flows before you score any product. The software should identify each flow by entity pair, not only by a company-wide total.

• Due-to and due-from balances. These are the pairs that should net, and the usual source of a small difference that blocks the report.
• Management fees and cost allocations. One entity records income while another must record the same amount as expense.
• Shared-service charges and reimbursements. The support entry often lands in a different month from the original cost.
• Loans between entities. Principal, interest, and the repayment need separate matches so a payment is not paired with a new advance.
• Inventory, rent, or cost transfers. The receiving entity and the sending entity can use different accounts for the same event.

Ask the vendor to show one example of each flow you use. A match rule that works for equal amounts can fail on a partial payment, a split invoice, or a charge booked to two accounts. The exception view should show the residual, not only the original total.

Also ask how eliminated and open amounts stay distinct. A cleared fee can leave the report. An unpaid residual should stay on the schedule with its age. If both disappear into one net number, the reviewer has lost the item that still needs a source correction.

What should you confirm before you choose?

A scorecard can look strong while the operating boundary is wrong. Confirm these points in writing before you treat a product as the reporting standard.

• Source systems. Name every ledger, including the odd one acquired last year.
• Write access. Confirm whether the tool changes source transactions or only reads them.
• Entity growth. Ask how a new company, partnership, or property is added.
• Report set. Separate ready reports from reports that need one-time setup.
• Elimination level. Ask how nested ownership and multi-level pairs are handled.
• Reviewers. Decide who can see the exception, the schedule, and the final report.
• Evidence. Keep the import, match, and approval history with the period.

Pricing should follow that scope. Helix scopes the work to entity count, source systems, report set, and configuration, and publishes the starting point on the pricing page. Compare scope, not a single monthly number taken out of context.

Family offices can use the same test. A single family group may hold operating companies, partnerships, and properties in separate files. The family offices page describes that reporting need. The software decision is still about pairs, exceptions, and report-time elimination, not about a generic control framework.

Where should the software stop?

Good intercompany reconciliation software is explicit about its edge. If a vendor claims to replace the ledger, the close, the audit. And the management report in one step, ask which of those jobs the current product actually does.

Helix stops at the reporting layer. Source-ledger records remain read-only. The team corrects the books in the accounting system, then refreshes the report. There is no automated posting of accounting entries from the reconciliation screen. Eliminations happen at report time and stay attached to a schedule.

That boundary is a feature for teams that need one reporting view and many source systems. It is the wrong fit if you need the tool to become the book of record. Say that early. A short qualification conversation is more useful than a long demo of reports you cannot produce from the files you have.

After you choose, pilot one material flow for a full close. Watch open-item age, the number of items matched on the first pass, and how long a reviewer needs to trace one exception. Expand only after that pack can be reproduced without the person who built it.

Frequently asked questions

What is intercompany reconciliation software?

It is software that compares transactions and balances between related entities, shows what still does not match, and keeps the evidence a reviewer needs. Strong tools also place cleared intercompany amounts onto a report-time elimination schedule.

How is this different from account reconciliation software?

Account reconciliation covers many balance-sheet accounts, such as banks, credit cards, and clearing accounts. Intercompany reconciliation software focuses on both sides of related-party activity, including due-to and due-from balances, fees, allocations, and reimbursements.

Does the software have to replace our accounting system?

No. A read-only reporting layer can import from the ledgers you already use and leave those books unchanged. An ERP replacement is a different project, and it is only necessary if you want one system of record for every entity.

What should we bring to a demo?

Bring one closed month with a matched pair, an open difference, and any currency or cutoff issue you actually see. Ask the vendor to trace one item from the source record to the elimination schedule.

Can the same tool produce the consolidated report?

Sometimes. Confirm whether consolidated balance sheet, profit and loss, and cash-flow reports are included or require separate setup. Also confirm that eliminations stay documented rather than disappearing into a plug.

Request information about a reporting-layer fit