What is Intercompany Break Resolution?

Table of Content
  1. No sections available

Definition

Intercompany Break Resolution is the process of investigating and clearing differences between related entities when intercompany balances, transactions, or accounting records do not match. A break may occur when one entity records a receivable but the counterparty records a different payable, posts in another period, uses a different currency rate, or misses the transaction entirely. Effective Break Resolution helps finance teams protect close accuracy, cash flow visibility, and consolidated financial reporting.

How Intercompany Break Resolution Works

The process starts when finance compares intercompany receivables, payables, revenue, expenses, loans, interest, inventory transfers, or settlements between counterparties. If the amounts do not agree, the difference becomes an intercompany break. The break is then assigned to an owner who reviews transaction references, invoices, journals, agreements, currencies, tax codes, and posting periods.

For example, Entity A may record $250,000 as an intercompany receivable, while Entity B records only $245,000 as a payable. The $5,000 break must be reviewed before consolidation. Intercompany Difference Analysis helps determine whether the issue came from a missing markup, partial posting, foreign exchange difference, tax treatment, timing gap, or incorrect account coding.

Common Causes of Breaks

Intercompany breaks usually happen because both sides of a transaction are recorded separately. If master data, timing, or documentation is not aligned, the two entities may not produce matching records during close.

  • Timing differences: One entity posts the transaction in the current period while the counterparty posts it later.

  • Currency differences: Entities use different exchange rates or remeasurement dates.

  • Missing documents: The counterparty has not received the invoice, journal support, or allocation file.

  • Coding errors: Incorrect entity, account, cost center, or Intercompany Counterparty Coding.

  • Disputed charges: The receiving entity disagrees with the amount, service basis, or allocation logic.

Resolution Metric and Example

A useful metric is: Intercompany Resolution Rate = Breaks Resolved ÷ Total Breaks Identified × 100. For example, if finance identified 120 intercompany breaks during month-end close and resolved 96 before reporting submission, the resolution rate is 96 ÷ 120 × 100 = 80%.

A high Intercompany Resolution Rate usually indicates strong ownership, clear documentation, and timely counterparty coordination. A low rate may indicate recurring data issues, unclear responsibility, delayed approvals, or unresolved disputes. The metric should be reviewed alongside break value, aging, entity pair, transaction type, and close deadline impact.

Workflow and Ownership

A structured Intercompany Resolution Workflow defines who reviews the break, what evidence is needed, how the correction is approved, and when the issue must be cleared. Ownership may sit with local accounting, shared services, tax, treasury, controllership, or consolidation teams depending on the transaction type.

For disputed items, Intercompany Dispute Resolution helps both entities agree whether the charge should be accepted, corrected, reversed, credited, or reissued. Exception-Based Intercompany Processing helps teams prioritize high-value, aged, material, or close-critical breaks so finance can focus on items with the greatest reporting impact.

Documentation and Controls

Break resolution depends on reliable supporting evidence. Finance teams often review invoices, journal entries, service agreements, loan schedules, transfer pricing support, allocation files, tax records, and settlement confirmations. A centralized Intercompany Agreement Repository helps teams verify whether the transaction follows approved terms.

Controls should confirm that each break has an owner, reason code, support file, expected action, due date, and final approval. If the break relates to inventory transfers, finance may also review Intercompany Profit in Inventory to ensure unrealized internal profit is identified before consolidation. These controls support cleaner intercompany reconciliation and more reliable financial reporting.

Best Practices

Strong break resolution is not only about clearing differences at month end. It also helps finance teams understand why the breaks occurred and how to prevent repeated issues. Break Root Cause Analysis can reveal recurring patterns such as weak master data, late invoices, inconsistent exchange rates, incomplete approvals, or unclear allocation logic.

  • Assign break owners by entity pair, account, and transaction type.

  • Use standard reason codes for timing, currency, tax, invoice, approval, and coding differences.

  • Set materiality thresholds and close deadlines for unresolved breaks.

  • Review aged breaks before consolidation and management reporting.

  • Track recurring issues through Intercompany Continuous Improvement routines.

Summary

Intercompany Break Resolution gives finance teams a structured way to identify, investigate, correct, and clear mismatches between related entities. It supports accurate balances, timely close, better cash flow visibility, stronger controls, and reliable consolidated reporting. When supported by clear ownership, strong documentation, resolution metrics, and root cause tracking, it becomes a critical part of intercompany finance management.

Build Custom Finance Workflows with 200+ Prebuilt AI APIs

Get Access to your Private F&A Chatbot

Ask questions in natural language & get instant insights

Ask questions in natural language & get instant insights