Intercompany Reconciliations for Multi-Entity SaaS

Why intercompany reconciliations matter

When one entity bills another in the same group, both sides have to record the same transaction, in the same month, for the same amount. If they don't, the group accounts won't eliminate cleanly, and someone ends up with an "intercompany difference" line that grows every quarter until an auditor asks about it.

It is also the place where two teams, two ledgers and often two currencies meet. Nobody is wrong on purpose; it just takes a process to stay agreed.

Key terms

• Intercompany (IC) transaction: a sale, recharge, loan or payment between two companies in the same group.
• Intercompany receivable and payable: the balances each entity holds with the other. One side's receivable should equal the other side's payable.
• Recharge (or management fee): one entity charging another for shared costs, such as staff, hosting or software, often with a markup.
• Transfer pricing: the rules that intercompany charges should be priced as if the companies were independent (the "arm's length" principle). Tax authorities, including HMRC, can adjust charges that aren't.
• Elimination: the consolidation journal that removes intercompany balances and transactions, so the group accounts only show dealings with outsiders.
• Functional currency: the main currency each entity operates in. A US subsidiary usually keeps its books in US dollars.
• Cash in transit: money sent by one entity that hasn't arrived in the other's bank account by month-end.

The monthly intercompany checklist

AI shortcut: give an approved AI assistant the intercompany ledger exports from both entities and ask it to match invoices by number, amount and date, then list the unmatched items on each side. You go straight to the exceptions instead of building the lookup.

Agreeing balances across currencies

The most common source of IC differences in multi-entity SaaS is currency. A simple rule makes most of it go away: agree balances in the currency of the invoice, not each entity's own currency.

• If the UK parent invoices the US subsidiary in pounds, the UK side has no FX exposure. The US side holds a pound payable and revalues it into dollars each month.
• Both sides then compare the pound balance. They should agree exactly, apart from timing and cash in transit.
• The FX gain or loss is real and stays in the US entity's P&L. It is not an intercompany difference.

Under IFRS (IAS 21) and FRS 102 (Section 30), monetary balances in a foreign currency are retranslated at the closing rate, with differences going to profit or loss. There is a special case for long-term loans that are effectively part of the parent's investment in the subsidiary, where exchange differences can go through other comprehensive income in the group accounts. That treatment depends on settlement not being planned or likely in the foreseeable future, so it is worth documenting the decision.

Worked example: recharge, reconciliation and elimination

MonthEndClub Co Ltd (the UK parent, books in pounds) employs the engineering team that builds the product. Its US subsidiary, MonthEndClub Inc (books in US dollars), sells to US customers. The intercompany agreement says the UK recharges a share of engineering costs to the US at cost plus 5%, invoiced in pounds.

Step 1: calculate and book the recharge

October engineering costs allocated to the US are £40,000. Markup: £40,000 × 5% = £2,000. Recharge invoice: £42,000. A service supplied by a UK business to an overseas business customer is typically outside the scope of UK VAT under the general business-to-business place-of-supply rule, so no VAT is charged here. Check HMRC's guidance on place of supply for your own facts.

UK books (in £):

US books (in $), invoice dated 31 October, booked at that day's rate of $1.25 per £1. £42,000 × 1.25 = $52,500.

Step 2: reconcile the balance

At 30 September, the US owed the UK £20,000 for September's recharge. MonthEndClub Inc paid it on 30 October. The money arrived in the UK bank on 3 November.

The £20,000 difference is cash in transit. Neither side is wrong, but for the group accounts it needs dealing with. A common approach is to book it in the receiving entity at month-end as cash in transit, then reverse when the money lands:

After that journal, both sides show £42,000 and agree.

Step 3: revalue the US payable

The month-end rate on 31 October is $1.25, the same as the invoice date, so there is no FX difference on the new invoice this month. In November, if the rate moves to $1.27 before payment, the US revalues: £42,000 × 1.27 = $53,340. The payable rises by $840, which is an FX loss in the US books. The pound balance still agrees with the UK side.

Step 4: eliminate on consolidation

The group reports in pounds. The US payable of $52,500 translated at the closing rate of $1.25 is £42,000, which matches the UK receivable. The October recharge income and cost both translate to £42,000 at the rate used (here the same $1.25). The elimination journals, in the consolidation workbook only:

Everything eliminates to nil. If it didn't, the leftover would show up as an unexplained difference, which is exactly what the monthly reconciliation is there to prevent. In practice, income and cost are often translated at an average rate, which can leave a small translation difference. That is a currency effect, not a booking error, and it goes to the translation reserve under the group's policy.

If you report under US GAAP (ASC 606 and related standards): the mechanics are broadly the same. Consolidation and elimination follow ASC 810 and foreign currency follows ASC 830, which also has a long-term investment exception for intercompany balances. Terminology differs (for example "cumulative translation adjustment" rather than "translation reserve").

Common mistakes and audit watch-outs

• Booking in different months. One entity books the recharge on 31 October, the other on 2 November. A shared cut-off date fixes it.
• Comparing balances in different currencies. Comparing a dollar balance to a pound balance always "differs". Compare in invoice currency.
• Forcing differences. Posting the gap to "IC suspense" to make it agree hides the real issue. Auditors look for these.
• No intercompany agreement. Without a written agreement, recharges have no agreed basis, and transfer pricing questions get harder to answer.
• Balances that never settle. Large, growing IC balances can create tax, currency and solvency questions. Many groups settle monthly or quarterly.
• Missing VAT or withholding tax analysis. Cross-border recharges can have VAT and tax effects. Check the treatment when a new flow starts, not at year-end.
• Taking an AI match on trust. AI matching by amount can pair the wrong invoices when amounts repeat each month. Check the invoice numbers on matched items too.
• Sharing both entities' ledgers with an unapproved tool. Only use AI tools your company has approved for financial data, including subsidiaries' data.

Tools that can help

Xero and QuickBooks each handle one entity per file, so IC reconciliations are often done in Excel or Google Sheets, or with a consolidation add-on. NetSuite (with its multi-subsidiary setup) and Sage Intacct can automate intercompany invoices and eliminations. Reporting tools such as Fathom and Syft can consolidate multiple entities. Tools don't replace the process; agreed cut-offs and two-sided sign-off still do the heavy lifting.

Key takeaways

• Both sides book the same IC transaction, in the same month, for the same amount.
• Agree balances in the invoice currency; FX revaluation is a real P&L item, not a difference.
• Explain every difference as timing, cash in transit, FX or error, then fix errors in the right entity.
• Get sign-off from both sides, then eliminate on consolidation.
• Let AI do the first match; people check invoice-level detail and sign off.

FAQs

Who is responsible for fixing an intercompany difference?

Typically the entity that made the error. Many groups give the group financial controller the final say when the two sides disagree.

How often should intercompany balances be settled in cash?

It varies. Monthly or quarterly settlement is common in SaaS groups. The agreed schedule is usually set out in the intercompany agreement.

What markup should a recharge use?

That is a transfer pricing question with tax consequences, and it depends on the functions each entity performs. Groups usually take specialist input and document the basis. HMRC publishes guidance on transfer pricing on gov.uk.

Can AI do our intercompany reconciliation?

It can do most of the matching and draft the explanations. A person still confirms the causes, approves corrections and signs off, and the data only goes into AI tools your company has approved.

Do dormant or small entities need reconciling every month?

If there are no transactions, a quick check that the balance hasn't moved is often enough. Many teams still confirm the balance with the other side at each quarter-end.

Related guides

• Month-End FX Revaluation, Step by Step
• Balance Sheet Reconciliations: What Good Looks Like
• Journal Review and Approval: Simple Controls That Work
• The SaaS Month-End Close Checklist

More in Reconciliations and Controls guides.

From the Club

Same mug, both sides of the Atlantic. Balances agreed in pounds. The Team Mug · The Washed Cap

Join the Club. New guides, early access and members-only batches. Join here.

This guide is general information about common practice. It isn't tailored to any business, and standards, tax rules and figures change. Check your own circumstances, the latest rules and, where needed, a qualified professional before acting.

Last reviewed: October 2026.