Intercompany Reconciliation Template & Method

Intercompany reconciliation template for EU groupsA workable intercompany reconciliation template holds one row per counterparty pair per account category per period, with both sides' amounts in transaction and group currency, the difference, a difference category, an owner and an ageing date. The template matters less than the rules attached to it: a documented matching key, a tolerance policy, a difference taxonomy and a hard cut-off before consolidation.Intercompany differences are rarely fraud and rarely large individually. They accumulate: a timing difference here, an FX rate difference there, a rebilling booked to the wrong account. By year-end the elimination column carries an unexplained residual, and the auditor tests it at transaction level.The fix is procedural, not technological. Groups running this well use a plain template with strict rules and a fixed monthly rhythm — long before they invest in a matching engine.Fields the template needsAnything less than this and you will not be able to explain a difference two months later. Anything more and it stops being filled in.

Period, entity A, entity B (both with the group entity code, not the local name)

Account category: trade, loan, interest, service recharge, dividend, cost allocation

Amount per side in transaction currency, plus the currency code

Amount per side in group currency, with the rate and rate type used

Difference in group currency, calculated, not typed

Difference category from a fixed list (see below)

Owner: one named person, on the side responsible for resolving it

Origin date of the oldest unresolved item, for ageing

Status: matched, in dispute, resolved-pending-posting, written off

Resolution note and reference to the correcting journal

Matching rules that avoid false differences

Match on the counterparty entity code, never on the account description

Reconcile balances per account category, not one lump-sum receivable versus payable

Use one group rate table with a defined rate type per transaction class, published before period end

Set a cut-off date for intercompany invoicing that is earlier than the ledger close — typically three working days

Apply a tolerance per pair (for example EUR 1,000 or 0.5% of the balance, whichever is lower) and record write-offs above it as decisions, not as noise

A difference taxonomy worth usingCategorising differences is what turns the reconciliation from a chore into a diagnostic. Five categories cover almost everything.

Timing — invoiced by one side, not yet received or booked by the other. Should clear next period; if it does not, it is not timing.

FX — same transaction, different rate or rate date. Points to a rate-governance gap.

Classification — booked to a different account category on each side. Points to a chart-of-accounts mapping gap.

Dispute — the counterparty rejects the charge. Needs an owner and an escalation date, not a monthly re-explanation.

Error — wrong amount, wrong counterparty, duplicate. Needs a correcting journal, referenced in the template.

The monthly routine

Day -3: intercompany invoicing cut-off; no new intercompany postings without approval

Day +1: both sides upload balances per counterparty pair and account category

Day +2: automated or template comparison; differences categorised and assigned

Day +3: dispute call for anything above tolerance, with both owners present

Day +4: correcting journals posted in the same period wherever possible

Day +5: residual reported to group with ageing; anything older than two periods escalated

Transfer pricing and Pillar Two implicationsIntercompany balances are also transfer pricing data. Service recharges, loans and cost allocations that sit unreconciled become documentation gaps in the local file, and interest and financing flows feed Pillar Two computations. A clean pair-level reconciliation with a category and a rate reference gives all three processes the same underlying numbers — which is the whole point of reconciling at category rather than aggregate level.Intercompany reconciliation checklist

Entity register with group codes, kept current for acquisitions and liquidations

Counterparty pair matrix showing which pairs are expected to have balances

Account categories defined and mapped in every local chart of accounts

Group rate table published before period end, with rate type per transaction class

Intercompany invoicing cut-off documented and enforced

Tolerance policy per pair, with approval rules for write-offs

Difference taxonomy applied to every open item

Named owner per open difference, on the resolving side

Ageing report by pair, with escalation over two periods

Correcting journals referenced from the reconciliation row

Reviewer sign-off captured in the system, with date

Residual reported to group and reconciled to the consolidation elimination

How we would approach this

We fix the matching key and the account categories first — most 'system' problems are mapping problems.

We put the calendar and the tolerance policy in writing so the same difference cannot be re-litigated every month.

We wire the reconciliation output into the consolidation elimination, so the residual is visible instead of absorbed.

What should an intercompany reconciliation template contain?Counterparty pair, entity-side balances in transaction and group currency, matched amount, difference, difference category, owner, age and resolution status — one row per pair, per period.Should the template live in a spreadsheet?A spreadsheet is acceptable as a starting structure, but the reconciliation must be reproducible from the ledgers. Where the spreadsheet holds the only version of the truth, the evidence trail breaks at audit.Primary sources

IFRS 10 — Consolidated Financial Statements — https://www.ifrs.org/issued-standards/list-of-standards/ifrs-10-consolidated-financial-statements/

OECD Transfer Pricing Guidelines — https://www.oecd.org/tax/transfer-pricing/oecd-transfer-pricing-guidelines-for-multinational-enterprises-and-tax-administrations-20769717.htm