How Intercompany Transfer Pricing Works
Finance and tax teams first determine which intercompany transaction requires a transfer price and establish the appropriate pricing method. The originating subsidiary records the sale, service charge, royalty, or other transaction, while the receiving subsidiary records the corresponding cost or liability. NetSuite subsidiary, currency, account, and intercompany information provides the accounting context for each side.
- Identify the transaction: Determine the goods, services, financing, or other value exchanged between subsidiaries.
- Apply the pricing policy: Use the approved transfer pricing method and supporting assumptions.
- Record both sides: Recognize the intercompany revenue, expense, receivable, and payable in the appropriate entities.
- Settle balances: Process intercompany obligations according to approved treasury and settlement policies.
- Eliminate internally: Remove reciprocal group activity during consolidation while retaining legal-entity results.
Transfer Pricing Methods and Example
A commonly used method for service transactions is cost plus. The basic calculation is Transfer price = Eligible cost × (1 + Markup rate). The eligible cost base and markup should follow the organization's documented transfer pricing policy and applicable tax requirements.
Assume Subsidiary A provides shared IT services to Subsidiary B and incurs $400,000 of eligible costs. If the approved markup is 8%, the transfer price is $400,000 × (1 + 8%) = $432,000. Subsidiary A records $432,000 of intercompany service revenue, while Subsidiary B records the corresponding $432,000 service cost or other appropriate accounting treatment. At group consolidation, the internal revenue and expense are eliminated, while the subsidiary-level profitability remains available for legal-entity reporting.
Settlement, Approval, and Treasury Impact
After an intercompany charge is established, settlement should follow controlled treasury procedures. Payment Approval provides the governance concept for authorizing settlement obligations, while Payment Approvals can support context-aware approval, partial-payment, and processing decisions that help treasury manage liquidity.
Automated payments can coordinate authorization, payment timing, and fraud controls so approved intercompany liabilities are settled consistently. Where bank transfer methods include ACH, Payment Processing By ACH can support file generation, bank-format compliance, access control, and audit trails.
Transfer pricing settlements can also affect short-term cash flow because intercompany receivables and payables move liquidity between legal entities. Treasury teams should therefore consider settlement schedules alongside working capital, liquidity forecasts, and entity-level funding requirements.
Controls, Fraud Checks, and Reconciliation
Intercompany pricing requires strong documentation and accounting controls because the transaction affects both legal entities. Where purchase orders or procurement-related charges support the transaction, Fraud Prevention in Purchase Orders | Secure Automation provides relevant context for requisitions, approvals, procurement controls, and secure procure-to-pay activity.
Supplier-style settlements should also be reviewed for contract terms and timing. A vendor payment review can help identify deviations between agreed terms and actual invoices or settlement activity, while Fraud Prevention can validate bank details, detect duplicate transactions, and generate alerts before funds are released.
If the intercompany charge is supported by an invoice, invoice approval should verify capture, matching, GL coding, approval, and posting before settlement. An Accounts Payable Payment then represents the accounting and operational step used to discharge an approved payable according to authorized terms.
Bank and ERP Reconciliation
After settlement, finance teams should confirm that cash movement agrees with the accounting records. Bank Reconciliation compares ERP cash entries with bank activity so differences can be identified and resolved. Reconciliation Of Bank Statements can further match invoices with bank transactions, flag discrepancies, and update ERP records to improve the accuracy of cash balances.
These reconciliation activities are important when several subsidiaries exchange funds during the same close cycle. Clear references, entity identifiers, currencies, and settlement documentation make it easier to connect bank activity with the underlying intercompany transactions.
Best Practices for Intercompany Transfer Pricing
- Document the pricing method, cost base, markup, and business rationale for each material transaction type.
- Apply consistent pricing policies to comparable transactions across subsidiaries.
- Align intercompany agreements, invoices, accounting entries, and settlement terms.
- Maintain clear subsidiary, currency, account, and counterparty identifiers in NetSuite.
- Reconcile intercompany receivables and payables before consolidation.
- Review pricing assumptions periodically when functions, risks, markets, or operating models change.
These practices help finance teams preserve legal-entity profitability, support tax documentation, maintain transparent settlement records, and produce reliable consolidated financial reporting.
Summary
NetSuite OneWorld Intercompany Transfer Pricing establishes the value assigned to transactions between subsidiaries and records the resulting revenue, cost, receivable, and payable effects within the appropriate legal entities. By combining documented pricing methods, controlled approvals, reliable settlement procedures, and disciplined reconciliation, organizations can support tax requirements, entity-level profitability analysis, treasury decisions, and accurate consolidated financial reporting.