Disclaimer. The Most HK does not provide transfer pricing policy, tax rulings, or tax compliance advice. Those remain with the group's appointed tax advisers. Our role is limited to the reporting layer: helping ensure intercompany balances, supporting schedules, and elimination workpapers are organised so the group finance team can reconcile reporting outputs with the documentation prepared by its tax advisers.
Two things that look similar and are not
Transfer pricing (TP) documentation and intercompany eliminations both sit on top of the same underlying transactions: a cross-border sale, a service charge, a loan, a royalty. Because they share a substrate, finance teams sometimes treat them as the same problem under two names.
They aren't. They serve different stakeholders, follow different rules, and break in different ways:
- Transfer pricing documentation supports tax defensibility. The audience is the Australian Taxation Office (ATO), the State Taxation Administration (STA) in the PRC, the Inland Revenue Department (IRD) in Hong Kong, and any other tax authority with jurisdiction. The framework is OECD-aligned (the OECD Transfer Pricing Guidelines, BEPS Action 13 master file / local file / country-by-country reporting), implemented locally — for Australia, principally under Subdivision 815-B of the Income Tax Assessment Act 1997 and ATO PCG / TR guidance.
- Intercompany eliminations support consolidated financial statement integrity. The audience is the group's external auditor, the audit committee, and the readers of the financial statements. The framework is AASB / IFRS (or the local statutory equivalent) with the entity-level books prepared under PRC ASBE, HKFRS, etc.
Mixing them up costs both money and trust.
Where the two regimes overlap (and where they don't)
The overlap is real but limited. Both regimes care about:
- The identity of the counterparties in the transaction
- The nature of the transaction (goods, services, financing, royalties)
- The amount and currency
- The period in which it occurred
The divergence starts immediately after that.
Transfer pricing documentation cares about:
- Whether the price reflects what unrelated parties would charge (the arm's-length principle)
- Functional analysis: who does what, who owns what risks, who owns what assets
- Comparable transactions and benchmarking
- Substance — where decisions are actually made, where people actually work
- Local file, master file, and CbCR thresholds and formats per jurisdiction
Intercompany eliminations care about:
- Whether both sides have recorded the same transaction at the same amount
- Whether timing differences are explained and resolved
- Whether FX is treated consistently across counterparties
- Whether elimination journals carry through to the consolidated trial balance
- Whether the group view tells a coherent story to an external auditor
A transaction can be perfectly documented for transfer pricing and still produce a broken elimination. A transaction can eliminate cleanly and still fail a transfer pricing review. The two regimes do not validate each other.
If you are unsure how this transfer pricing vs elimination boundary friction is currently impacting your group close, you can run a 2-minute diagnostic via our Close Clash Calculator to see where the evidence path is breaking down.
What goes wrong when they are conflated
We see four recurring failure patterns:
1. Year-end TP adjustments posted as elimination entries
Groups that run a year-end TP true-up — adjusting the price of intercompany transactions to land within an arm's-length range — sometimes route those adjustments through the elimination journal. The arithmetic works at the consolidated level (the adjustment cancels), but the documentation trail breaks: the tax authority sees a price adjustment, the auditor sees an elimination entry, and the policy reference connecting them is missing.
The cleaner pattern is to post the TP adjustment at the entity level, with a documented policy reference and TP working paper, and then eliminate the intercompany balance separately.
2. TP documentation written from elimination data
The temptation, particularly when documentation deadlines are tight, is to extract intercompany totals from the elimination working file and use them as the TP local file inputs. Those numbers are aggregates. They have lost the transaction-level detail (counterparty pairs, transaction types, currency, function) that a tax authority will ask for.
TP documentation should be sourced from the entity-level subledger, not from the consolidated elimination file.
3. Substance evidence borrowed from accounting records
Transfer pricing review increasingly focuses on substance: where decisions are made, where people sit, what authority they hold. Accounting records — invoices, journals, bank statements — show where money flowed, not where decisions were made. Using accounting evidence as a substance argument is brittle and tends to fail under questioning.
Substance evidence belongs in a separate folder: board minutes, decision logs, employment records, organisation charts, contracts.
4. Inconsistent treatment of management charges and intra-group services
Management charges between the parent and PRC subsidiaries are common in Australian-headed groups. They have to satisfy both regimes simultaneously: priced at arm's length (with benefit test, mark-up, and documentation), and recorded consistently on both sides for clean elimination. Charges that are arbitrarily set at year-end fail TP review; charges that are not mirrored on both sides fail elimination review.
How to design the boundary cleanly
The structure that works:
- One source of truth at the entity level. Each PRC and HK entity maintains its intercompany subledger with full transaction detail. This subledger feeds both the elimination process and the TP documentation, but each downstream process pulls what it needs separately.
- TP policy documented, dated, and owned. Pricing methodology per transaction class is set at the start of the year, not at the end. Adjustments are made within the year, not as a single year-end true-up.
- TP adjustments booked as entity-level journals, with a policy reference and working paper. They are then eliminated like any other intercompany balance.
- Elimination journals reference the underlying transaction, not the TP working paper. The two artefacts cite each other but stay separate.
- Substance evidence kept outside the accounting system, in a maintained governance log.
Two parallel trails, sharing a substrate, never substituting for each other.