How to implement intercompany charges and group eliminations
Approve the commercial and tax treatment before automating an intercompany charge. A balanced receivable and payable prove that two ledgers agree on an amount. They do not establish that the price is appropriate, the service occurred or the invoice meets each entity's tax obligations.
Use this process for a defined service-charge population, then extend it to goods, royalties or financing only after reviewing their different requirements. The synthetic example excludes VAT, withholding tax, currency differences and payment fees so the pricing and consolidation calculations remain visible.
Record the implementation in the intercompany charge worksheet. Its approvals and reconciliations are recommended controls rather than a universal transfer-pricing policy.
Separate five decisions
Identify the service and contracting entities, decide the price, post both entities' accounting, settle the balances and eliminate applicable amounts in consolidation. Give each decision an owner. A transfer-pricing adviser may approve the pricing method while local tax owners decide invoicing and withholding treatment.
The OECD's 2022 Transfer Pricing Guidelines address the arm's-length principle for associated-enterprise transactions. Applying those guidelines and subsequent relevant guidance requires the actual facts and domestic rules; an ERP's allocation engine does not supply that analysis. OECD, Transfer Pricing Guidelines 2022.
Put the approved agreement, service description, cost eligibility, allocation key and pricing period into one specification. Explain excluded costs explicitly. A group headquarters expense is not automatically chargeable merely because it appears in the shared-services cost centre.
Keep the policy approval separate from an approval to run a monthly invoice batch. Operations should reproduce an approved calculation, not decide a new markup whenever the budget changes.
Worksheet: Intercompany charge and elimination worksheet
Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.
Show the worksheet
Use with the intercompany guide. Complete one copy for each charge policy and close period. Blank fields are operator inputs, not predetermined tax conclusions.
Policy and evidence
- Seller, buyer entities, period and agreement reference:
- Service received, beneficiary evidence and excluded activities:
- Eligible cost definition, approved markup and support:
- Allocation driver, recipient percentages and approval:
- VAT, withholding, currency and documentation decisions, with owner:
Calculation and reciprocal posting
Record actual total costs, exclusions, eligible costs, markup amount and final charge. Allocate the final charge and any true-up to each recipient. Record seller document IDs and each buyer's matching expense/payable IDs. Explain every unmatched amount; approval on only one side is incomplete.
Rehearsal: eligible costs90,000 plus5% produce94,500; A60% is56,700 and B40% is37,800. Original84,000 leaves true-up10,500, split6,300/4,200.
Consolidation completion
- Elimination batch, matched income/expense amount and balance-sheet pairs:
- Remaining external cost and explanation of residual entity profit or loss:
- FX, timing or classification differences, owner and resolution:
- Controller sign-off and evidence location:
Rehearse a missing buyer true-up and prove that the unmatched4,200 is identified before elimination approval.
Define the source population and pairing keys
Choose the cost accounts, dimensions and period included in the charge. Retain an extract with its filters and source-ledger revision. Record adjustments made outside the ERP so another operator can reproduce the calculation.
Use stable identifiers for the charging entity, receiving entity, service agreement, period and calculation version. Carry those identifiers into the seller's invoice and the buyer's bill or journal. Record original local document numbers rather than forcing both systems to use the same number.
If the entities close on different dates, define who accrues a charge before the invoice arrives and who clears that accrual later. Otherwise an automated payable can duplicate the buyer's existing month-end estimate.
NetSuite OneWorld's Automated Intercompany Management documents transaction management and elimination journals. This is a specific product feature, not evidence that its use validates the underlying transfer price. Oracle, Automated Intercompany Management.
Work the initial service charge
Assume a service company incurs 100,000 currency units of costs. The approved calculation excludes 20,000 and allocates the remaining 80,000. The fictional agreement applies a 5% markup to eligible cost and uses an approved 60:40 allocation between operating companies A and B.
The markup is 4,000 and the total charge is 84,000. A receives 50,400 and B receives 33,600. The 5% is an illustrative contractual assumption, not a general safe harbour or an assertion that every shared service qualifies for a particular simplified method.
The service company records receivables of 84,000 and service revenue of 84,000. A records service expense and a payable of 50,400; B records the same categories for 33,600. Total counterparty payables equal the seller's receivables.
Before settlement, compare both sides by agreement and period. The seller's 84,000 minus A's 50,400 minus B's 33,600 must equal zero. Check document counts too: one charge to each buyer should not appear as two invoices in one ledger and one combined payable without an explained linkage in another.
The service company's standalone result from this population is revenue of 84,000 less cost of 100,000, or a loss of 16,000. That result is consistent with the assumptions: excluded cost of 20,000 is partly offset by markup of 4,000.
Calculate a true-up without losing the original charge
At final close, assume eligible actual cost is 90,000 while excluded cost remains 20,000. Total actual cost is now 110,000. The approved markup remains 5%, giving a final charge of 94,500.
Subtract the 84,000 already charged. The additional amount is 10,500, allocated 6,300 to A and 4,200 to B. Final charges become 56,700 and 37,800 respectively, which total 94,500.
Keep the original calculation and issue a controlled true-up reference. Do not replace an already issued invoice silently. The local tax owner must decide whether the adjustment requires a credit or debit document, changes taxable consideration or has other local consequences.
After posting, the seller and both buyers reconcile 94,500. If their balances are settled in one payment or through netting, preserve how that settlement clears each legal obligation. Settlement is not the group elimination journal.
Eliminate the accounting effect at group level
Before elimination, the combined service population shows seller revenue of 94,500, seller costs of 110,000 and buyer expenses of 94,500. Consolidation removes the intra-group revenue and matching buyer expense by debiting revenue and crediting service expense for 94,500.
The consolidated cost remaining is 110,000. It is not 15,500, the service company's standalone loss, and it is not 204,500, the combined expenses before elimination. The underlying external costs remain in the group's result.
Where outstanding balances remain, eliminate the applicable intra-group receivable and payable separately. Do not remove real local obligations from individual entity accounts simply because the group eliminates them in consolidation.
Oracle's elimination documentation describes designated transaction lines and the period-close elimination process, including specific reversing balance entries. Confirm the exact feature and period behaviour in the proposed NetSuite OneWorld release before building an operating instruction. Oracle, intercompany elimination workflow.
Recover when one buyer misses the true-up
Suppose B has posted only 33,600 while the seller includes the final 37,800. The counterparty difference is 4,200. An operator might be tempted to post an unexplained consolidation plug so the group report can close.
Instead, identify the missing true-up using the agreement, period and version. Check whether B already has an accrual for the same service. Its controller then approves the missing bill, correction or accrual clearing. Rerun the counterparty reconciliation before releasing elimination.
If the charge is disputed, keep the dispute and accounting decision visible. Do not mark a transaction reconciled merely because someone forced both sides to the same amount. Pricing disagreements and posting errors require different resolution owners.
For goods transfers, add an inventory-profit analysis rather than assuming revenue/expense elimination removes every unrealised margin. For cross-currency balances, retain original amounts and translation differences so the matching rule does not confuse exchange movements with missing documents.
Complete the recurring operating process
The service owner confirms delivery and beneficiary evidence. Tax approves pricing and local treatment. Local controllers approve their own entries and settlement. The group controller approves elimination; the application owner maintains the interfaces and exception reports.
Before closing the population, confirm:
- Agreements, eligible costs and allocation keys are approved and reproducible.
- Markups and exclusions have a recorded rationale.
- Seller and buyer documents share stable matching references.
- Estimates, final charges and true-ups cannot be counted twice.
- Counterparty balances and document populations reconcile before elimination.
- Consolidated revenue, expense and remaining external cost match the approved bridge.
- Disputes, tax questions and missing documents have named owners.
Retain calculation versions, source extracts, local documents, settlement allocations and elimination evidence. Use parallel books where accounting bases differ, and local statutory accounts to preserve each entity's own reporting result.
Source verification date: 17 October 2026. This guide describes a source-based design and synthetic calculation, not a live NetSuite implementation or a country-specific transfer-pricing opinion.
Related on this site
- Country pages: key facts with sources
- E-invoicing matrix: country × ERP support
- All guides
Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.
Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).
Page last updated: · Markdown version