Due To and Due From: Consolidation, Elimination, and Disclosure

Due to and due from accounts are the paired intercompany asset and liability entries that track money owed between related entities in the same corporate group. One side records a “due from” as an asset (a claim for repayment); the other side records a “due to” as a liability (the matching obligation). They exist as mirror images: for every dollar Entity A shows as due from an affiliate, that affiliate shows a dollar due to Entity A. On each entity’s own books, both sides are recorded and kept gross. On the consolidated financial statements, they are eliminated so the group reports only what it owes to and is owed by outside parties.

How the Mirror Works in Practice

Take a parent that pays a $50,000 vendor invoice on behalf of its subsidiary. The parent books a $50,000 due from subsidiary (asset) with a credit to cash. The subsidiary books the $50,000 expense and credits due to parent (liability). No cash has left the group, but each entity’s standalone books now reflect the real obligation between them. That standalone accuracy matters for regulatory filings, subsidiary-level covenants, and any minority-shareholder reporting tied to the individual entity.

Where Intercompany Balances Come From

Three activities create the bulk of these balances.

Centralized cash management is the most common source. When a treasury function pays external bills for subsidiaries, the paying entity records due from and the receiving entity records due to. A $10,000 third-party expense paid by the parent produces a debit to due from subsidiary and a credit to cash on the parent’s books, while the subsidiary debits the expense and credits due to parent.

Intercompany loans work the same way at the entry level but carry more weight. The lender debits due from borrower and credits cash; the borrower debits cash and credits due to lender. These loans need formal agreements covering the interest rate, maturity, and repayment schedule. Under Section 482 of the Internal Revenue Code, the IRS can reallocate income between commonly controlled entities whenever the arrangement doesn’t clearly reflect each entity’s income.1Office of the Law Revision Counsel. 26 USC 482 Treasury Regulation Section 1.482-2 lets the IRS impute an arm’s length interest rate when the stated rate is off-market.2eCFR. 26 CFR 1.482-2 – Determination of Taxable Income in Specific Situations A common safe-harbor practice is to price intercompany loans at the IRS Applicable Federal Rate for the appropriate loan term, with rates between 100% and 130% of AFR generally treated as satisfying the arm’s length standard.3Internal Revenue Service. Revenue Ruling 2026-2

Shared service allocations round out the list. When a centralized IT or HR function bills its costs to operating units, the servicing entity records due from and the operating unit records due to. If the parent’s IT group allocates $5,000 in server costs to a subsidiary, the parent debits due from subsidiary and credits a cost recovery account; the subsidiary debits the expense and credits due to parent.

Classifying the Balances on Each Entity’s Books

Before anything gets eliminated, each entity has to classify its side correctly on its own balance sheet. If settlement is expected within twelve months of the balance sheet date, the balance is current. If it’s beyond twelve months, it’s non-current. This matters most for intercompany loans: a five-year loan sits as a non-current asset on the lender and a non-current liability on the borrower, supported by a written agreement with a specified term, rate, and repayment schedule. Misclassifying a long-term intercompany loan as current distorts liquidity ratios and working capital on both sides, which can create false readings against external credit covenants.

Do Not Net Offsetting Balances

If Entity A owes Subsidiary B $3,000 and Subsidiary B owes Entity A $10,000, instinct says show a net $7,000 receivable. Both U.S. GAAP and IFRS prohibit this unless specific conditions are all met.4IFRS Foundation. IASB/FASB Staff Paper – Offsetting of Financial Assets and Liabilities Under ASC 210-20-45-1, netting requires all four: each party owes the other a determinable amount, the reporting entity has the right of setoff, the entity intends to exercise that right, and the right is enforceable at law. In practice, this means a master netting agreement covering the mutual obligations. Without one, the full gross asset and full gross liability both sit on the balance sheet, even though they involve the same counterparty. Notes receivable from affiliates also cannot be buried inside general “accounts receivable” line items; they show separately.

The Consolidation Elimination Entry

The elimination happens only on the consolidation worksheet, which combines the individual trial balances into group financials. No individual entity’s general ledger is touched. The entry debits the total due to liability across the group and credits the total due from asset for the same amount, driving both to zero in the consolidated column.

If the aggregate due to parent across all subsidiaries is $1,000,000 and the aggregate due from subsidiaries on the parent’s books is $1,000,000, the elimination is a $1,000,000 debit to the liability and a $1,000,000 credit to the asset. After the entry, neither figure appears on the consolidated balance sheet. ASC 810-10-45-1 requires this: all intra-entity balances and transactions must be eliminated in preparing consolidated statements. The reasoning is that a $1 million intercompany receivable and $1 million intercompany payable represent the same transaction seen from both sides. Leaving both in the consolidated statements would overstate total assets and total liabilities by $1 million each.

Resolving Mismatches Before You Eliminate

In theory the two sides always match. In practice they rarely match without effort, and this is where most of the month-end pain lives. You cannot force-eliminate balances that don’t agree; the difference has to be found and corrected first.

Timing differences are the usual culprit. Entity A records a cash transfer on June 30, but Entity B doesn’t post the receipt until July 2. At month-end the parent’s books show a receivable the subsidiary hasn’t yet acknowledged. The fix is usually an accrual on the receiving side, but locating the mismatch inside thousands of transactions is the hard part. Other causes include transposed digits, wrong entity codes, disputed allocation amounts, and rounding or categorization differences between systems. High-volume groups increasingly use reconciliation software that pulls transactions from each entity’s ERP, matches them algorithmically, and flags exceptions for review.

The PCAOB has flagged poor intercompany reconciliation as a potential material weakness. Its guidance describes a company that processes frequent, material intercompany transactions but fails to reconcile consistently, leaving significant unresolved differences that could produce material misstatements in the consolidated financials.5Securities and Exchange Commission. PCAOB Appendix D – Examples of Significant Deficiencies and Material Weaknesses

Foreign Currency Wrinkle

When affiliates use different functional currencies, balances that started as exact matches drift apart with exchange rate movement. A parent lending $100,000 to a foreign subsidiary records the receivable in dollars; the subsidiary records the payable in its local currency. Under ASC 830, each entity remeasures its intercompany balance to the current rate at every balance sheet date, and the gain or loss flows through earnings. The point that catches people out: even though the intercompany receivable and payable are eliminated in consolidation, the foreign currency gain or loss on each entity’s books survives that elimination, because it reflects a real change in expected cash flows to the group.

Tax and Disclosure Obligations

Corporations with reportable transactions with related parties, including intercompany loans and service charges, must file Form 5472 to disclose those transactions.6Internal Revenue Service. About Form 5472 The penalty for failing to file, or for filing a substantially incomplete form, is $25,000 per taxable year, with an additional $25,000 for each 30-day period the failure continues more than 90 days after IRS notice. The penalties are assessed per related party, not per return.7Office of the Law Revision Counsel. 26 USC 6038A

For intercompany loans and service charges, the IRS expects contemporaneous transfer pricing documentation showing the pricing reflects arm’s length terms. The documentation must exist when the return is filed and be produced within 30 days of an IRS request during exam.8Internal Revenue Service. Transfer Pricing Documentation Best Practices Frequently Asked Questions (FAQs) When the IRS adjusts intercompany pricing under Section 482, accuracy-related penalties of 20% or 40% can apply to the resulting underpayment, depending on how far the claimed price is from the arm’s length result and the size of the net adjustment. Maintaining contemporaneous documentation is the primary defense.9Internal Revenue Service. The Section 6662(e) Substantial and Gross Valuation Misstatement Penalty

On the financial-reporting side, ASC 850 requires disclosure of material related party transactions, including amounts due to or from related parties and their settlement terms. Transactions fully eliminated in consolidation don’t need separate disclosure in the consolidated statements. But standalone subsidiary financials, whether issued for regulatory reasons, minority shareholders, or debt covenants, still have to disclose the intercompany balances and terms.

What Poor Controls Cost

A material weakness finding triggers public disclosure in the annual report, possible restatements, and the kind of investor scrutiny no finance team wants. For privately held groups, unreconciled intercompany accounts slow audits, raise audit fees, and can delay financial statement issuance, which can breach timing covenants in credit agreements. Companies that handle this well reconcile monthly rather than quarterly, set a policy for investigating and resolving differences within a fixed number of business days, and automate transaction matching where volume justifies it. When the upstream work is done, the period-end elimination entry is mechanical.