A contract and year-end invoice show how much was charged. Defensible documentation also proves who did what, what the U.S. entity received, which costs entered the pool, and why the allocation and price are reasonable.

1. Make the functional analysis specific to services and people

“Group management support” is too broad. Separate finance, HR, IT, legal, procurement, R&D coordination, marketing, and executive activity. Identify the provider, team, role, location, deliverable, and beneficiary for each service. Reconcile interviews to organization charts, time records, project systems, and sample communications rather than inferring activity from job titles.

Ask three questions for every service: did the U.S. entity receive commercial or economic value; would an independent company pay for it or perform it internally; and does it duplicate a U.S. team or another vendor? Parent activity undertaken for shareholder oversight, capital raising, or ownership of the group should not be swept into subsidiary charges without distinction. Document the result by service.

2. Cost-pool boundaries determine credibility

Build cost pools from reconcilable ledger accounts and employee lists, with a policy for direct payroll, benefits, third-party fees, travel, systems, and indirect costs. Allocating every parent management expense by revenue can import shareholder activity, acquisition, financing, local-benefit, or duplicate projects. Each inclusion and exclusion needs an articulated basis and evidence.

Multi-tier service centers require protection against duplicate markup. If the Chinese headquarters receives a marked-up charge from a Hong Kong center and passes it to the United States, identify underlying cost and the already-marked component. Maintain a three-part bridge from statutory books to service pool, pool to beneficiaries, and allocations to invoices, separately displaying exchange and true-up effects.

  • Map every cost pool to ledger accounts, people, and third-party invoices
  • Document exclusions for shareholder, acquisition, financing, local, and duplicate activity
  • Identify prior markups in multi-tier services to avoid stacking profit

3. Allocation keys should approximate benefit, not convenience

Different services call for different keys. IT may use users or devices, HR may use headcount, procurement may use purchasing volume, and finance may use transaction volume or entity complexity. Revenue can be reasonable in some settings but should not be a universal answer because it is easy to obtain. Explain how each key approximates expected benefit and preserve the source data.

Charge direct services directly and allocate only shared activity. When operations change rapidly, budgeted ratios may diverge from actual benefit, so establish quarterly refresh and year-end true-up. Apply a reasonableness test: a holding entity without employees should not absorb a large HR charge, and a new U.S. company should not bear mature-market costs without explanation.

4. Match the method and markup to the service

The Section 482 services regulations provide multiple methods, potentially including the services cost method when its conditions are satisfied, and methods based on comparable prices, gross margins, or profit indicators. Whether to mark up and by how much cannot be copied from a global policy without analysis. Consider whether the activity is routine support or contributes core capabilities or intangibles, then apply the best-method principle with supportable comparables.

Contemporaneous documentation should contain substantive analysis when the return is filed, not first appear after an examination request. Describe controlled transactions, parties, functions, risks, assets, method selection, comparable screening, financial data, and results, including changes from prior years. Scale the workpaper to risk, but have management and local tax owners approve material judgments.

  • Record why each feasible transfer-pricing method was selected or rejected
  • Connect any markup to the service character and comparable support
  • Complete documentation before filing and preserve the exact data version

5. Turn policy into an executable monthly invoice process

The agreement should cover service scope, pricing method, allocation, invoice cycle, currency, taxes, records, and adjustment mechanics. Accumulate costs against the approved catalog monthly or quarterly, produce the allocation and invoice, and obtain U.S. confirmation that service was received. Separate pass-through reimbursement from marked-up services and analyze withholding, sales tax, or other taxes independently.

At year-end, true up actual cost against advances and reconcile the ledger, bank, Form 5472, income-tax deduction, and withholding filings. Preserve deliverables, time records, meeting minutes, and ticket samples so business evidence sits behind the numbers. Refresh the policy for organizational, systems, and business changes instead of copying the prior report unchanged.