A renminbi ledger and a U.S. dollar ledger are not the root cause of a difference. The parties usually recorded different entities, dates, amounts, transaction character or currency layers, without one end-to-end transaction ID.

1. Define transactions in an intercompany master

For every entity pair, maintain seller, buyer, legal name, tax status, functional currency, bank, due-to and due-from accounts, agreement, pricing policy and contacts. Assign one transaction ID to every invoice, payment on behalf, loan, capital item, allocation, royalty or service charge; both ledgers use the same ID and original-currency amount.

Payment narration alone does not determine substance. A headquarters payment of U.S. costs may be an intercompany receivable, contribution, loan or service charge based on agreement, approval, invoice, beneficiary and repayment plan. Give master-data additions and changes an effective date so a Chinese abbreviation cannot map silently to the wrong U.S. entity.

  • Legal entities and tax status of both parties
  • Agreement, pricing policy and nature of service or funding
  • Transaction, functional, settlement and reporting currencies
  • Mirror accounts and shared transaction ID
  • Effective date, preparer, reviewer and contacts

2. Mirror transactions, not merely total balances

Exchange a transaction-level statement showing invoice date, service period, currency, gross amount, tax, payment, credit, open amount and aging. China due-from should mirror U.S. due-to, but cutoff, in-transit cash, credit memos and payment-on-behalf timing create temporary differences. Assign every difference a reason code.

Match original currency first and book currency second. An original-currency difference generally means omission, duplication, wrong entity or different characterization; it is not FX. Only after original amounts match should rates and booking dates explain functional-currency differences. Escalate stale balances for settlement ability, contract terms and possible reclassification.

  • Matched, timing, missing, duplicate and classification
  • Payments in transit and credit memos
  • Wrong entity, period and currency
  • Original-currency and FX differences separated
  • Owner, cause and resolution date for aged items

3. Separate transaction remeasurement from translation

An entity first records foreign-currency transactions in its functional currency. Monetary items denominated in another currency generally require period-end remeasurement under applicable ASC 830 principles, with the difference treated under the reporting basis. If the group reporting currency differs, functional-currency financial statements are then translated. Accounts, rates and equity treatment for these layers should not share one journal.

Create a rate hierarchy for spot, actual transaction, approved average, closing and historical rates, with source, retrieval time and rounding. Two parties using the same provider may still show different book amounts because functional currencies differ. The consolidation system should preserve local amount, transaction amount, rate type and translated amount.

  • Approved functional currency for each entity
  • Purpose of transaction, average, closing and historical rates
  • Layered remeasurement and translation journals
  • Rate source, version, timestamp and rounding
  • Local, transaction and reporting-currency fields

4. Connect reconciled books to U.S. tax

When a U.S. entity is a Form 5472 reporting corporation, specified reportable transactions with foreign related parties are reported in U.S. dollars under the form instructions, with rate method and detail retained. Accounting elimination does not cancel information reporting; a zero net balance can contain gross or categorized transactions that remain reportable.

Services, royalties, loan interest, goods and allocations must align with transfer-pricing policy, agreements, invoices, withholding and deduction timing. IRS transfer-pricing materials emphasize complete documentation consistent with actual transactions. Feed monthly transaction IDs into the year-end related-party matrix rather than reconstructing the story during return preparation.

  • Form 5472 filer and related-party scope
  • Reportable categories and U.S. dollar conversion
  • Agreements, invoices and transfer-pricing method
  • Withholding, deduction timing and payment evidence
  • Ledger index to information and income-tax workpapers

5. Prove close through confirmation, aging and elimination

By Day 6, both parties sign an electronic confirmation of original and functional-currency balances, unmatched items, rate version and resolution plan. On Days 7–8, consolidation reviews eliminations for receivables, payables, revenue, expense, interest and FX at the correct layer, keeping differences visible.

Quarterly, analyze aging, unbilled services, cash pools and recurring reason codes. Retest mappings for a new entity, agreement, currency or system. Archive statements, confirmations, rates, journals, agreements and the tax matrix. Success is not a zero balance; it is one shared fact set and an executable settlement plan.

  • Signed month-end balances and unmatched-item list
  • Elimination journals traceable to transactions
  • Aging, overdue cause and settlement plan
  • Review trigger for entity, currency, agreement and system changes
  • Unified accounting, FX, consolidation and tax archive