> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Intercompany Imbalances (consolidation blocker), SAP > Intercompany Imbalances (consolidation blocker) counts sub-company journals that do not balance across the CompanyCode group in S/4HANA Cloud. How to read it, why it matters, and how to ... **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Period Close](/nerve-centre/connectors#connectors-by-type) > Sub-company journals that do not balance across the CompanyCode group. The single number that decides whether SAP Group Reporting consolidation can run tonight or stalls until someone fixes a mismatched intercompany pair. ## At a glance > The count of intercompany postings that do not balance across the Company Code group. When one Company Code books an intercompany transaction (a sale, a loan, a recharge, a dividend) the matching Company Code must book the mirror side at the same value. When the two sides disagree, the pair fails to net to zero on elimination, and SAP Group Reporting cannot consolidate the group until it is fixed. This is a hero card because a non-zero value here is not a "watch this", it is a "consolidation is blocked right now". The CFO's group close stops here. | | | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The number of intercompany journal pairs where the two sides do not match, across the selected Company Codes. An intercompany posting in one Company Code (flagged with the trading-partner / partner Company Code field on the Universal Journal line) should have an equal and opposite posting in the partner Company Code. The card counts the pairs that fail to reconcile to zero on elimination. | | **Why it blocks consolidation** | SAP Group Reporting consolidates by adding up every Company Code's ledger and then eliminating intercompany balances so the group is not double-counting internal trade. Elimination only nets to zero if both sides of each intercompany pair agree. A mismatched pair leaves a residual that breaks the elimination task and stops the consolidation run. | | **Common causes** | Timing (one side posted this period, the mirror side next period), FX (the two Company Codes translated the same transaction at different rates), value mismatch (a recharge entered at a rounded figure on one side), missing trading-partner code (a posting that should be flagged intercompany but was not), or a one-sided manual journal that was never mirrored. | | **Why a count, not a value** | The alert is binary in spirit: any unbalanced pair blocks consolidation. The count tells you how many fires there are to put out before the group close can proceed. The monetary residual of each pair sits on the related intercompany-balance card. | | **Company Code scope** | Respects the selected Company Code filter, but the metric is inherently group-level: an imbalance is a property of a pair of Company Codes, not one. Filtering to a single Company Code shows the pairs that entity is involved in. | | **Time window** | `RT` (real time, the current state of unbalanced intercompany pairs) | | **Alert trigger** | `>0` (any unbalanced pair flags, because any imbalance blocks consolidation) | | **Roles** | owner, finance | ## Calculation Calculated automatically from your SAP data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A group running SAP S/4HANA Cloud Public Edition with three Company Codes: 1000 UK Holdings Ltd (GBP), 2000 US Trading Inc (USD), and 3000 EU Trading BV (EUR). Group currency is GBP. The group close for the period ending 31 May 26 is being prepared on 04 Jun 26. The card reads the live intercompany position. | Intercompany pair | CC 1 side | CC 2 side | Residual on elimination | Counted? | | --------------------------------------- | ---------------- | --------------------------------------- | ------------------------ | -------- | | 1000 to 2000 management recharge | £120,000 booked | \$120,000 booked, translated to £93,840 | £26,160 FX residual | Yes | | 1000 to 3000 intercompany loan interest | £40,000 booked | €47,000 booked, translated to £40,138 | £138 rounding residual | Yes | | 2000 to 3000 inventory transfer | \$310,000 booked | mirror not yet posted | full \$310,000 unmatched | Yes | | 1000 to 2000 royalty | £85,000 booked | £85,000 booked | £0 balanced | No | | **Intercompany Imbalances (this card)** | | | | **3** | Five things to notice: 1. **The count is 3, and the `>0` alert fires immediately.** As a hero card with a zero-tolerance threshold, any non-zero value stops the group close. Consolidation cannot run clean until all three are resolved. 2. **The biggest residual is an FX mismatch, not a value error.** The £120,000 management recharge was booked as a fixed sterling figure in the UK but the US side recorded the dollar equivalent and translated it back at a different rate, leaving a £26,160 residual. This is the classic intercompany FX trap: both sides agree on the economics, but the two ledgers translated independently. The fix is a Group Reporting reclassification or a harmonised intercompany FX rate, not a re-posting. 3. **One pair is purely a timing problem.** The \$310,000 inventory transfer was booked in US Trading Inc but the EU side has not posted its mirror yet. This is the most common blocker at close: one entity is faster than the other. The fix is simply to get the lagging side posted before the elimination task runs. 4. **A £138 rounding residual still counts.** Even a tiny mismatch blocks a clean elimination. SAP Group Reporting can be configured with a rounding tolerance, but absent that, the card faithfully reports that the pair does not net to zero. Small residuals are usually rounding or sub-unit currency differences. 5. **The balanced royalty pair is correctly excluded.** The £85,000 royalty matched exactly on both sides, eliminated cleanly, and does not appear in the count. The card only surfaces the pairs that will actually break consolidation. ## Sibling cards merchants should reference together An intercompany imbalance is a group-close blocker. Read it with the wider intercompany and period-close family to find and fix the cause fast. | Card | Why pair it with Intercompany Imbalances (consolidation blocker) | | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | [Intercompany Balance](/nerve-centre/kpi-cards/sap/sap-intercompany-balance) | The monetary view. This card counts the unbalanced pairs; that card shows the value sitting in intercompany accounts and where the residuals are. | | [Period Close Status by CompanyCode](/nerve-centre/kpi-cards/sap/period-close-status-by-companycode) | A timing imbalance often means one Company Code has not finished posting. Check which entities are still open. | | [Period Close Past Deadline (any CompanyCode)](/nerve-centre/kpi-cards/sap/period-close-past-deadline-any-companycode) | A late Company Code is frequently the source of the missing mirror side. Pair to spot the lagging entity. | | [Period Close On-Time Rate (12mo)](/nerve-centre/kpi-cards/sap/period-close-on-time-rate-12mo) | Persistent intercompany imbalances drag closes late, which shows up in the on-time rate over time. | | [Journal Imbalances (Debit/Credit)](/nerve-centre/kpi-cards/sap/journal-imbalances-debit-credit) | A one-sided manual intercompany journal can be both a journal imbalance and an intercompany imbalance. Pair to catch both. | | [Top Findings Across Company Codes](/nerve-centre/kpi-cards/sap/top-findings-across-company-codes) | The group-wide rollup of what is wrong across all entities, with intercompany blockers prominent at close. | ## Reconciling against SAP **Where to look in S/4HANA Cloud:** The closest native equivalents inside the SAP Fiori launchpad are: > **Intercompany Reconciliation** Fiori apps (Manage / Monitor Intercompany Reconciliation) to match trading-partner balances pair by pair > **Group Reporting** apps (Consolidation Monitor, Data Monitor) where the elimination tasks run and fail on residuals > **Display Journal Entries** filtered to the trading-partner / partner Company Code field to inspect each side of a pair > **Embedded Analytics**: intercompany CDS views that expose trading-partner balances by Company Code To match this card, run the Intercompany Reconciliation app for the period and list the pairs whose trading-partner balances do not net to zero (within any configured tolerance). Each unmatched pair the app shows should correspond to one count on this card. The Consolidation Monitor will independently fail its elimination task on the same pairs. Common mistakes when comparing against SAP's own reports: * **Comparing per-Company-Code balances without translation.** Each side is in its own Company Code currency. An apparent imbalance can vanish once both sides are translated to group currency at the consolidation rate, and vice versa. Always reconcile at the group-currency layer that elimination uses. * **Missing the trading-partner code.** A posting that should be flagged intercompany but lacks the partner Company Code field will not be picked up by the reconciliation app as intercompany at all. The card relies on the same flag, so an unflagged one-sided posting shows up as a different finding, not as an imbalance. * **Ignoring tolerance settings.** Group Reporting can be configured with a rounding tolerance. If your tolerance nets a tiny residual to zero in the Consolidation Monitor but the card reports it, the difference is the tolerance, not an error. **Why our number may legitimately differ from SAP's reports:** | Reason | Direction | Why | | ----------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **FX translation layer** | Either | An imbalance in Company Code currency may net out in group currency, or appear only after translation. The card reconciles at the elimination (group-currency) layer; a per-Company-Code report will differ. | | **Rounding tolerance** | Card higher | If Group Reporting is set to ignore residuals under a tolerance, the Consolidation Monitor passes them while the card may still flag the pair as not exactly zero. | | **Timing of the mirror side** | Either | A pair where one side posts this period and the mirror posts next period reads as imbalanced now and balanced later. The card is real time, so it reflects the current state. | | **Trading-partner flag** | Either | Postings missing the partner Company Code field are not recognised as intercompany. They surface as other findings rather than as imbalances. | | **Consolidation reclassifications** | Card higher | A residual that Group Reporting will clear via a reclassification or elimination-adjustment task still reads as imbalanced before that task runs. | ## Known limitations / merchant FAQs **Why is the alert threshold zero?** Because any unbalanced intercompany pair blocks a clean elimination, and a blocked elimination stops group consolidation. There is no "acceptable" non-zero level: one mismatched pair is enough to halt the group close. That is why this is a hero card with a `>0` trigger. **Most of my imbalances are tiny FX or rounding residuals. Are they really a problem?** They are a real blocker unless Group Reporting is configured with a rounding tolerance that nets them out. If you have a tolerance, those sub-threshold residuals will pass the Consolidation Monitor even though the card flags that the pair is not exactly zero. If you do not have a tolerance, even a small residual breaks the elimination task and must be cleared. **The most common cause for me is timing, one side posts before the other. How should I read that?** As a genuine real-time blocker that will self-resolve once the lagging Company Code posts its mirror. The card is real time, so the count drops the moment the missing side is booked. Pair with the period-close status cards to find which entity is behind. **Does an intercompany imbalance always mean someone made an error?** No. The most frequent causes are timing (one side not yet posted) and independent FX translation, neither of which is a data-entry mistake. Value mismatches and missing trading-partner codes are the ones that usually need a correction posting. **How does the card handle multi-currency intercompany pairs?** It reconciles at the group-currency layer that elimination uses, because that is where consolidation actually nets the pair. An imbalance that exists only in Company Code currency, or only after translation, is reported as the elimination layer sees it. **Can a balanced pair still block consolidation?** A pair that nets to zero on elimination will not block on this metric. Other things can still block a group close (a Company Code not yet closed, an unposted journal, an IDoc error), which is why this card is best read alongside the period-close family rather than alone. **How fresh is the number?** It is real time. S/4HANA Cloud exposes trading-partner balances through live APIs, and Vortex IQ's connector refreshes frequently, so the count reflects the current intercompany position. The moment a mismatched side is corrected or a missing mirror is posted, the count updates. For pair-by-pair detail, pivot into the Intercompany Reconciliation Fiori app. *** ### Tracked live in Vortex IQ Nerve Centre *Intercompany Imbalances (consolidation blocker)* is one of hundreds of KPI pulses Vortex IQ tracks across SAP and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.