consolidation close failed: "subsidiary ledger not balanced" error for entity DE-02
Fixes a consolidation close failing with subsidiary ledger not balanced for entity DE-02: balance DE-02 in its own books and currency first, find the one-sided or unposted local item, and only then rerun consolidation. Use when one subsidiary blocks the group close. Not for translation-only differences.
TL;DR
Consolidation cannot balance what is not balanced locally. Open DE-02's own trial balance in EUR, find where it fails to balance or where a subledger disagrees with its GL, and fix it at source: typically an unposted batch, a one-sided manual journal, or a subledger posting that never reached the GL during a local system issue. A consolidation plug would export the local error into group accounts where it becomes far harder to find.
consolidation close failed: "subsidiary ledger not balanced" error for entity DE-02Use this when
- Consolidation stops or errors naming DE-02 and subsidiary ledger not balanced.
- Other subsidiaries consolidate without this error.
- DE-02 had a local close issue, system outage, or late batch in the period.
Not for this skill when
- DE-02 balances locally and the failure is translation or elimination. Then the problem lives in the consolidation layer, not the subsidiary ledger.
- DE-02 reports in a newly changed chart or structure. Mapping, not balancing, may be the block; check the consolidation mapping for unmapped accounts.
Steps
- Pull DE-02's trial balance in its local currency and check it balances, then tie its AR, AP, and bank subledgers to their GL control accounts. Verify: the local imbalance is located to a ledger or subledger, not just suspected
- Review DE-02's recent batches and journals for failed, partial, or unposted status, especially around any local outage. Verify: suspect batches are listed with their posting state
- Trace the located difference to the specific journal or batch and prove its one-sided nature. Verify: the difference amount equals the identified item exactly
- Correct the item in DE-02's books through the local process, with local approval, rather than from the consolidation side. Verify: DE-02's trial balance and subledgers now agree locally
- Rerun consolidation for DE-02 and confirm the error clears and its balances flow into the group. Verify: group consolidation completes with DE-02 included and no plug
Variant phrasings
subsidiary ledger not balanced consolidation DE entity
The blocking-subsidiary phrasing.
one subsidiary trial balance out of balance close
When balancing the local books first.
Compatibility: Subsidiary close and consolidation in NetSuite OneWorld, SAP, Oracle FCCS, and Dynamics group reporting.
Why it happens
Group close inherits every local close's quality. A subsidiary ledger imbalance usually originates in a mundane local event: a batch interrupted, a manual journal saved unbalanced in a system that allows draft imbalance to post through an interface, or a subledger that posted during a GL outage. Consolidation error messages point at the group layer, but the evidence and the fix are always local, in the subsidiary's own currency and controls.
Edge cases / pitfalls
- Timezone and calendar differences mean DE-02's close may still be in progress when the group runs. Confirm local close completion before diagnosing imbalance.
- If DE-02 recently migrated systems, opening balance loads are a prime suspect for a first-close imbalance.
- Give the group checklist a local-balance gate per subsidiary so consolidation never again discovers a local imbalance at group runtime.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_MP6jWPebGgNR-MpsbcZNsw