A parent company pays a supplier invoice on behalf of a subsidiary. One entity provides management services to another. A hotel group transfers cash between properties. Each transaction may be commercially routine, but it can create material reporting errors when the receiving and sending entities record it differently. This intercompany accounting procedures guide explains how to establish a disciplined process that keeps entity-level books accurate and consolidated financial statements reliable.
Intercompany accounting is not just a month-end elimination exercise. It begins when a transaction is initiated, continues through approval and recording, and ends only after reciprocal balances are reconciled and eliminated. Organizations that treat these steps as separate activities often face delayed closes, unexplained differences, and audit pressure.
Intercompany transactions occur between entities under common control. They may involve loans, shared payroll, centralized purchasing, management fees, inventory transfers, royalty charges, rent, or cost allocations. At the legal-entity level, each side must record the transaction. At the consolidated level, the group must remove the transaction's impact so revenue, expenses, assets, liabilities, and profit are not overstated.
The difficulty is rarely the debit and credit alone. It is maintaining agreement across entities that may use different teams, locations, currencies, accounting systems, close calendars, and approval practices. Hospitality and aviation organizations can face added complexity because shared operating costs, intercompany billing, deferred revenue, and multi-location activity create high transaction volume.
A formal procedure creates a common operating standard. It clarifies which entity owns the cost, when a charge should be raised, what support is required, which accounts to use, and who resolves a discrepancy. The result is a faster close and financial reports that management can use with greater confidence.
Before processing transactions, establish an intercompany policy approved by finance leadership. The policy should define the group entities covered, permitted transaction types, required documentation, pricing or allocation methods, settlement terms, materiality thresholds, currency treatment, and monthly close deadlines.
The policy should also state whether charges are recorded through invoices, journal entries, automated system postings, or a combination. Invoicing gives the receiving entity a clear payable and a supporting document, which is useful for recurring services and regulated environments. Journal entries can be practical for timely month-end allocations, but they require stronger review controls because they can be posted without the normal accounts payable workflow.
Create a consistent entity and account structure in the general ledger. Each entity should have dedicated due-to and due-from accounts, rather than recording intercompany activity in generic receivables, payables, or clearing accounts. Separate accounts by counterparty when transaction volume or risk warrants it. For example, Parent Due From Subsidiary A is easier to reconcile than one pooled intercompany receivable account.
A standard chart of accounts should also distinguish the nature of activity: intercompany service revenue, management fee expense, interest income, interest expense, inventory transfers, and equity contributions. Clear account design makes eliminations more accurate and gives management visibility into how entities support one another.
The most reliable intercompany entries begin with a shared transaction record. That record should identify the legal entities involved, transaction date, amount, currency, description, allocation basis, contract or approval reference, and the accounts each entity will use.
If Entity A provides $20,000 of administrative support to Entity B, Entity A records a debit to intercompany receivable and a credit to intercompany service revenue. Entity B records a debit to administrative expense and a credit to intercompany payable. The amounts, dates, currencies, and counterparty codes must match.
Timing is a frequent source of variance. One entity may book an invoice in March while the other records it in April, especially if teams work on different close schedules. A practical approach is to use a group-wide cutoff calendar and require both entities to record material intercompany activity in the same accounting period. When timing differences are unavoidable, document them in a reconciling-items schedule and reverse or clear them promptly.
For cost allocations, the methodology matters as much as the entry. Shared corporate expenses may be allocated based on headcount, revenue, room nights, labor hours, flight activity, or another supportable driver. The method should be reasonable, consistently applied, reviewed periodically, and supported by underlying data. Avoid using broad estimates merely to force balances to agree.
Monthly reconciliation is the operating control that prevents small mismatches from becoming year-end problems. Each entity should prepare an intercompany aging and balance confirmation by counterparty. Finance compares the due-to balance on one entity's books with the corresponding due-from balance on the other entity's books, then investigates differences.
Common reconciling items include invoices recorded in different periods, payment-in-transit items, foreign currency remeasurement, tax treatment, duplicate postings, incorrect entity codes, and one-sided journals. A difference should never be cleared by posting an unexplained plug entry. The preparer should identify the cause, propose the correction, retain support, and obtain review where required.
A disciplined reconciliation package usually includes the general ledger detail, counterparty confirmation, invoice or journal support, an aging report, and a log of open exceptions. The reviewer should focus on aged balances, recurring differences, unusual manual journals, and transactions that lack a documented business purpose.
Settlement also deserves attention. Some groups settle balances monthly through bank transfers; others allow balances to accumulate under formal intercompany loan arrangements. Either approach can work, depending on cash management needs and the volume of activity. Long-outstanding balances, however, can create liquidity, tax, legal, and audit concerns. Define settlement expectations and escalate exceptions early.
Once entity-level balances are reconciled, the consolidation process removes intercompany effects from group financial statements. At a basic level, intercompany receivables eliminate against intercompany payables, and intercompany revenue eliminates against intercompany expense.
More complex activity requires additional analysis. Intercompany inventory sales may include unrealized profit that remains in ending inventory and must be deferred until the goods are sold externally. Fixed-asset transfers may require adjustment for the gain or loss recorded between entities and for depreciation based on the group’s original carrying amount. Intercompany loans can require elimination of both principal and interest, while foreign-currency balances may generate translation or remeasurement considerations.
Maintain separate elimination entries and supporting schedules rather than altering each entity's statutory ledger solely for consolidation purposes. This preserves local reporting while creating a clear trail from entity books to consolidated results. Every elimination should identify the entities involved, relevant accounts, calculation, preparer, reviewer, and period.
Even a well-written policy fails when no one owns the process. Finance leadership should assign responsibility across transaction initiation, entry preparation, reconciliation, approval, consolidation, and exception resolution. The same person should not be able to create a manual intercompany journal, approve it, and clear the resulting difference without independent review.
A workable monthly workflow has four essential control points:
Automation can reduce manual work, particularly where entities use an integrated enterprise resource planning system. Automated matching, intercompany invoicing, and standardized reporting can improve consistency. However, automation does not replace policy decisions, review of allocation drivers, or accountability for exceptions. A poorly configured system can spread an error quickly across several ledgers.
For growing businesses, outsourced accounting support can provide the additional capacity needed to prepare reconciliations, maintain close schedules, and document controls without immediately expanding an internal finance team. The most effective arrangement is one where the outsourced team follows documented ownership, approval, and reporting protocols established with company leadership.
A reliable intercompany process gives leadership more than a clean consolidation. It provides a clearer view of entity performance, working capital, shared-service costs, and the decisions that drive them. Start with one controlled monthly close cycle, resolve the recurring exceptions, and make the procedure part of the regular finance calendar rather than a year-end repair project.
