Key takeaways
- Intercompany reconciliation is the check that two companies in the same group record every balance between them at the same amount, so the group total eliminates to zero on consolidation.
- In a payment group, intercompany balances arise from payout funding, fee recharges, intragroup loans and collections made by one entity for another entity's customers.
- Customer funds safeguarded by one licensed entity can never be used to settle or offset another entity's balance: UK, EU and US state rules all ring-fence them for that entity's own customers.
- Under IAS 21 paragraph 45, an intragroup monetary balance cannot be eliminated without showing the effect of currency movements, so FX gains and losses on intercompany balances stay in group profit or loss.
- The strongest process matches intercompany flows daily, in the transaction currency, and leaves month end for revaluation, eliminations and sign-off.
What are the key facts on intercompany reconciliation for payment groups?
Each pair of group companies must agree what one owes the other, in the same currency, at the same date, and no agreed balance may draw on customer funds.
| Item | Position |
|---|---|
| What it is | Matching the receivable in one group company to the payable in another, item by item and in total |
| Who does it | Group finance or the international controller, with each entity's finance lead and group treasury |
| Frequency | Daily for cash flows between entities; monthly for revaluation, eliminations and sign-off |
| Accounting rule | Intragroup balances are eliminated on consolidation; FX differences on intragroup monetary items remain (IAS 21 paragraph 45) |
| UK rule | Electronic Money Regulations 2011 regs 20 and 21; Payment Services Regulations 2017 reg 23 |
| EU rule | Directive (EU) 2015/2366 Article 10, applied to e-money institutions by Directive 2009/110/EC Article 7 |
| US rule | State permissible investment rules, for example Minnesota Statutes sections 53B.61 and 53B.62 |
| The hard line | Intercompany positions are never netted against safeguarded or trust funds |
What is intercompany reconciliation?
It is the routine check that every amount one group company says it is owed by another is recorded, at the same value, as owed by that other company.
An intercompany balance is money owed between two companies (legal entities) owned by the same group. The company that is owed records a receivable, often called a "due from" balance. The company that owes records a payable, a "due to" balance. The two companies are each other's counterparty. If the books are right, the receivable in one equals the payable in the other.
In consolidated accounts, meaning one set of accounts for the whole group, these balances are removed, because a group cannot owe money to itself. That removal is called an elimination. If the two sides disagree, the elimination leaves a difference that reconciliation must explain first.
In a group of licensed payment or e-money companies it is also a regulatory control, because the same balances affect whether each company holds enough protected money for its own customers. Our guide to multi-entity reconciliation explains why each licensed entity must be reconciled on its own.
Why is intercompany reconciliation harder in a payment group?
Because money moves between entities every day in several currencies, and some of it belongs to customers rather than to the group.
Take a group with a US money transmitter, a UK e-money institution (EMI) and an EU EMI. When a US sender pays a UK recipient, the UK company pays out and the US company owes it. The UK company recharges shared technology, the EU company lends spare capital, and one company may collect card payments for another's customers. Each creates a different kind of balance.
| Flow | Typical booking | Customer funds involved? | How it is settled |
|---|---|---|---|
| Payout funding | Paying entity: receivable; originating entity: payable | The underlying transfer is customer money until the payout completes | Cash from the originating entity's own funds once its obligation is discharged |
| Fee and cost recharges | Provider: receivable; user: payable | No, these are the group's own revenue and costs | Operating account to operating account |
| Intragroup loans and capital | Lender: loan receivable; borrower: loan payable | No, but the lender must stay above its capital and buffer levels | Operating account to operating account, with approval |
| Collections for another entity | Collector: payable; issuing entity: receivable | Yes, these are the issuing entity's customer funds | Gross, in cash, into the issuing entity's safeguarding or trust account |
The last row is where most regulatory risk sits. Approvals and source-of-funds checks for the cash movements themselves are covered in our guide to intercompany funding between regulated entities. This guide covers the matching that sits underneath them.
Can intercompany balances be netted against safeguarded funds?
No: UK, EU and US state rules each ring-fence customer funds for the customers of the licensed entity that holds them, so no group balance can be settled out of them or offset against them.
In the UK, regulation 20 of the Electronic Money Regulations 2011 requires an EMI to safeguard funds received in exchange for e-money it has issued. Regulation 21 requires those funds to be kept segregated from any other funds the EMI holds and, if still held at the end of the business day after receipt, placed in a separate designated account used only for those funds. No person other than the EMI may have any interest in or right over them, and the definition of an authorised credit institution excludes a bank in the same group as the EMI.
Regulation 23 of the Payment Services Regulations 2017 sets the same structure for payment institutions and adds the insolvency rule that matters most here: on an insolvency event, payment service users are paid from the asset pool first, and no right of set-off may be exercised against the pool until they are paid in full, except for fees and expenses of operating the safeguarding accounts. A sister company's receivable cannot be set off against it.
In the EU, Article 10 of Directive (EU) 2015/2366 requires that safeguarded funds are not commingled at any time with the funds of any person other than the payment service users on whose behalf they are held, and that they are insulated from the claims of the institution's other creditors. Insurance or a guarantee used instead must come from a firm outside the institution's group. Article 7 of Directive 2009/110/EC applies the same safeguarding methods to e-money institutions.
In the US, state law sets the rule. In Minnesota, section 53B.61 requires a licensee to hold permissible investments at all times worth no less than all of its outstanding money transmission obligations, held in trust for its customers on insolvency. Section 53B.62 lists what counts. It includes receivables from the licensee's authorized delegates under seven days old, within limits, but it does not list amounts owed by affiliates, so a receivable from a sister company does not count. Each state has its own list; see permissible investments by state.
The rule for reconciliation follows: intercompany balances are settled only from each entity's own money, and a balance representing another entity's customer funds is paid gross, in cash, into that entity's protected account.
What is the intercompany reconciliation process?
Match every intercompany cash flow daily on both sides, then revalue, reconcile balances, eliminate and sign off at month end.
| Step | Daily | Month end |
|---|---|---|
| 1. Tag | Every intercompany entry carries both entity codes, a shared reference and its flow type | Confirm no untagged entries sit in intercompany accounts |
| 2. Match | Pair each entry with its counterpart in the other entity, in the transaction currency | Agree the full balance for each pair of entities and each currency |
| 3. Classify | Mark whether the flow is own funds or another entity's customer funds | Confirm no customer-funds balance is outstanding beyond its legal deadline |
| 4. Explain | Raise unmatched items as breaks with an owner the same day | Every remaining difference has a documented cause: timing, FX, error |
| 5. Revalue | Not required | Retranslate foreign currency balances at the closing rate in each entity's books |
| 6. Eliminate | Not required | Post group eliminations; carry FX differences to group profit or loss |
| 7. Sign off | Breaks reviewed by a second person | Both entity finance leads and group finance approve the pairs |
Month-end matching alone is too late for a payment group: a customer-funds balance left open for a month can mean an entity was short of safeguarded money for a month. Our guide to reconciliation break management covers how unmatched items are owned and closed.
How should FX on intercompany balances be handled?
Agree balances in the currency of the transaction, revalue each side at the closing rate, and expect the FX gain or loss to remain in group results rather than eliminate.
A balance between a dollar company and a sterling company is denominated in one currency, and the company holding it in a foreign currency revalues it each month. Matching in each company's own reporting currency makes every rate movement look like a difference. Matching in the transaction currency removes that noise: GBP 1.2 million owed is GBP 1.2 million on both sides.
On consolidation, IAS 21 paragraph 45, quoted in the IFRS Interpretations Committee's April 2026 agenda decision, states that an intragroup monetary asset or liability, whether short-term or long-term, cannot be eliminated against the corresponding intragroup liability or asset without showing the results of currency fluctuations in the consolidated financial statements. The balance eliminates; the gain or loss one entity booked on it does not.
An intercompany FX loss reduces an entity's own funds; it never reduces what its customers are owed, which is tested in the currency owed to them (see safeguarding in more than one currency).
How are timing differences handled?
A timing difference is a payment one entity has recorded and the other has not yet received; it is valid only if the cash can be traced to a bank record and it clears within an agreed period.
A transfer sent from London late on Friday 31 October may reach Dublin on Monday 3 November. The sender has reduced its payable; the receiver still shows the full receivable. The difference is cash in transit.
Set one group cut-off time and one rate source for all entities. Clear a timing difference by rule only when the sending bank statement shows the payment and the receiving bank confirms it within the agreed window; anything older becomes a break. For balances that represent customer funds, the window is set by law, not by policy: under Article 10 of PSD2 and regulation 21 of the Electronic Money Regulations, funds still held at the end of the business day after receipt must already be in protected form.
What does a three-entity intercompany reconciliation look like?
This illustrative example follows Nexus Payments, a group with a US money transmitter (Nexus US, reporting in USD), a UK EMI (Nexus UK, GBP) and an EU EMI (Nexus EU, EUR), at 31 October. Group currency is USD.
Closing rates: 1.25 USD per GBP and 1.10 USD per EUR, which gives 0.88 GBP per EUR. Five balances are open between the three companies.
| Pair | Item | Receivable side | Payable side | Difference |
|---|---|---|---|---|
| UK and US | 1. Payout funding: Nexus UK paid UK recipients for US senders | Nexus UK: GBP 1,200,000 | Nexus US: GBP 1,200,000, booked at 1.26 (USD 1,512,000), revalued at 1.25 to USD 1,500,000 | None in GBP |
| US and EU | 2. Technology recharge invoiced in USD | Nexus US: USD 330,000 | Nexus EU: USD 330,000 (EUR 300,000 at closing rate) | None in USD |
| EU and UK | 3. Intragroup loan, EUR 500,000 repaid on 31 October | Nexus EU: EUR 2,000,000 | Nexus UK: EUR 1,500,000 | EUR 500,000 |
| EU and UK | 4. Card top-ups collected by Nexus UK for Nexus EU e-money customers | Nexus EU: EUR 400,000 | Nexus UK: EUR 400,000 | None in EUR |
| UK and EU | 5. Compliance services recharged by Nexus UK | Nexus UK: EUR 400,000 | Nexus EU: EUR 400,000 | None in EUR |
Item 1 matches in sterling. Nexus US booked its payable at 1.26 and revalued it at the closing rate of 1.25: GBP 1,200,000 multiplied by 1.25 is USD 1,500,000, against USD 1,512,000 originally, so Nexus US records an FX gain of USD 12,000. Item 2 matches in dollars. Item 3 differs by EUR 500,000: Nexus UK sent the repayment on Friday 31 October and Nexus EU receives it on Monday 3 November. The UK bank statement shows the payment, so it clears as a timing difference.
Items 4 and 5 are where the regulatory rule bites. Group treasury proposes to net them, since each side owes the other EUR 400,000 and no cash would need to move. That would leave Nexus EU's safeguarding account EUR 400,000 short of what its e-money customers are owed, because the top-ups are customer funds that must be in Nexus EU's protected account, not settled by cancelling a fee Nexus EU owes. The correct settlement is gross: Nexus UK pays EUR 400,000 into Nexus EU's safeguarding account, and Nexus EU pays the EUR 400,000 fee from its operating account. In the group accounts both pairs still eliminate. In each entity's safeguarding position they never offset.
| Pair | Receivable (USD) | Payable (USD) | Difference (USD) | Group treatment |
|---|---|---|---|---|
| 1. UK and US | 1,500,000 | 1,500,000 | 0 | Eliminate; keep the USD 12,000 FX gain in group profit or loss |
| 2. US and EU | 330,000 | 330,000 | 0 | Eliminate |
| 3. EU and UK | 2,200,000 | 1,650,000 | 550,000 | Record EUR 500,000 (USD 550,000) as cash in transit, then eliminate |
| 4. EU and UK, customer funds | 440,000 | 440,000 | 0 | Eliminate in group accounts; settle gross in cash to Nexus EU's safeguarding account |
| 5. UK and EU, fee | 440,000 | 440,000 | 0 | Eliminate; settle from Nexus EU's operating account |
| Total | 4,910,000 | 4,360,000 | 550,000 | Explained in full by cash in transit |
At 1.10, EUR 2,000,000 is USD 2,200,000, EUR 1,500,000 is USD 1,650,000 and EUR 400,000 is USD 440,000. The USD 550,000 gap between total receivables and payables is the loan repayment in transit, and nothing else.
How do eliminations work at group level?
Once every pair agrees, group finance removes the matched receivables and payables, and the related income and costs, so the consolidated accounts show only balances with parties outside the group.
In the example, the USD 330,000 technology recharge is revenue for Nexus US and a cost for Nexus EU; both are eliminated, so group revenue is not overstated. The loan and its interest are eliminated. The FX gain on item 1 stays, under IAS 21 paragraph 45. Customer liabilities, such as e-money owed to Nexus EU's customers, are never intercompany balances and are never eliminated: they are owed to people outside the group.
Never force an elimination with a balancing entry. In a payment group, an unexplained difference can be a customer-funds shortfall in one of the entities, so it goes back to the pair that caused it.
What should a payment group's intercompany control include?
These checks cover both the accounting and the regulatory side.
- A group intercompany policy naming every flow type, its booking, its currency and its settlement account.
- A shared reference on both sides of every intercompany entry, and one group cut-off time and rate source.
- Daily matching of intercompany cash flows in the transaction currency, with unmatched items raised as breaks the same day.
- Each balance classified as own funds or another entity's customer funds.
- Customer-funds balances settled gross, in cash, into the receiving entity's safeguarding or trust account within the legal deadline.
- No netting, set-off or cash pooling that touches safeguarded or trust funds.
- No receivable from a sister company counted towards a safeguarding requirement or permissible investment total.
- Monthly revaluation at the closing rate, with FX differences carried to group profit or loss, not eliminated.
- Sign-off of each entity pair by both finance leads and group finance, with residual differences documented.
How does Safeheld help?
Safeheld matches bank statements, partner reports and ledgers every day and keeps one position per legal entity, in its own currency, never offset against another company in the group, with every entity's position agreeing back to a group total.
Differences are raised as breaks the day they appear, timing items are cleared by rule, and others are worked to a cause with evidence recorded. Transfers between entities are proposed and approved by up to three people and paid by a standard payment file. See daily reconciliation in Safeheld.
Frequently asked questions
What is intercompany reconciliation?
It is the check that a receivable recorded by one company in a group equals the payable recorded by the other company, so that intragroup balances eliminate fully when consolidated accounts are prepared.
What is the intercompany reconciliation process?
Tag every intercompany entry with both entities and a shared reference, match each entry to its counterpart, explain differences as timing, FX or error, revalue foreign currency balances at month end, post eliminations and sign off each entity pair.
How often should a payment group reconcile intercompany balances?
Cash flows between entities should be matched daily, because some represent customer funds with legal deadlines. Revaluation, eliminations and sign-off can follow at month end.
Can a payment group net intercompany balances against safeguarded funds?
No. UK regulation 21 of the Electronic Money Regulations 2011, regulation 23 of the Payment Services Regulations 2017, Article 10 of PSD2 and US state permissible investment rules ring-fence customer funds for the licensed entity's own customers, so they cannot settle or offset a group balance.
Does a receivable from an affiliate count as a permissible investment?
Not in Minnesota, for example: section 53B.62 lists receivables from authorized delegates within limits but does not list amounts owed by affiliates. Each state sets its own list.
Are FX differences on intercompany balances eliminated?
No. IAS 21 paragraph 45 states that an intragroup monetary asset or liability cannot be eliminated without showing the results of currency fluctuations, so the FX gain or loss remains in consolidated profit or loss.
What is a timing difference in intercompany reconciliation?
A payment recorded by the sending entity but not yet by the receiving entity, usually because of cut-off times or weekends. It clears once the receiving bank confirms the cash within the agreed window.
Can two offsetting intercompany balances be settled by netting?
Only if both are the entities' own money. If one balance represents another entity's customer funds, it must be paid gross in cash into that entity's safeguarding or trust account.
References
- Electronic Money Regulations 2011, regulation 20 (safeguarding requirements), legislation.gov.uk
- Electronic Money Regulations 2011, regulation 21 (safeguarding option 1), legislation.gov.uk
- Payment Services Regulations 2017, regulation 23 (safeguarding requirements), legislation.gov.uk
- Directive (EU) 2015/2366 (PSD2), Article 10 (safeguarding requirements)
- Directive 2009/110/EC (EMD2), Article 7 (safeguarding requirements)
- Minnesota Statutes 2025, section 53B.61 (maintenance of permissible investments)
- Minnesota Statutes 2025, section 53B.62 (permissible investments)
- IFRS Interpretations Committee, agenda decision on foreign exchange differences from intragroup monetary items, quoting IAS 21 paragraph 45 (April 2026, PDF)
About Safeheld
Safeheld is reconciliation and regulatory reporting software for regulated firms that hold client money across countries, currencies and regulators. For payment groups with several licensed entities it reconciles each entity every day in its own currency, never offsets one entity against another, and agrees every position back to a group total. To discuss your safeguarding operations, contact us at safeheld.com/contact.
This article is general information on intercompany reconciliation and customer fund rules for payment groups and is not legal or regulatory advice.