What this article covers: How to configure BrizoConsol based on your group structure — understanding the hierarchy, how entities connect, the role of the CCOA, and how consolidation nodes work.
Before connecting entities and running consolidations, it is important to understand how BrizoConsol handles your group structure. The key concepts are: how entities connect to data sources, what the Common Chart of Accounts (CCOA) is, and how consolidation nodes work in the hierarchy.
Key Concepts
Entity Types in the Hierarchy
Entity Type
Description
Connected entity
An entity with its own accounting book connected to BrizoConsol via Xero, QuickBooks, MYOB, or Zoho Books. Trial balance data is pulled automatically each period.
Manual entity
An entity whose trial balance is uploaded as Excel / CSV each period. Used for entities not on a supported accounting system.
Consolidation node (Con)
A group-level entity in the hierarchy that has no accounting book of its own. It consolidates the results of its child entities. BrizoConsol shows it as Connected via consol in the hierarchy. A consolidation node does not need account mapping — it has no accounts of its own to map.
🛈 Important — consolidation nodes: BrizoConsol does not connect consolidation nodes (group-level entities) to third-party accounting systems. The Group node consolidates its children — it does not pull its own trial balance from Xero or any other system. If the group has a holding company with its own book, connect that book as an entity of its own under the Group node, like any subsidiary.
The Common Chart of Accounts (CCOA)
The CCOA is the standardised account structure that all entities map their accounts to. Every entity's accounts must be mapped to a CCOA account before its balances appear in consolidated reports.
If Group has a holding book
Use the holding company’s chart of accounts as the anchor for the CCOA, and connect the holding company as an entity under the Group so its balances, including its investments in subsidiaries, are loaded.
If no Group book
Create the CCOA in BrizoConsol directly, or use AI Suggest to derive a structure from the connected subsidiaries' accounts.
Consolidation nodes
Do not need account mapping. They have no accounts of their own — their consolidated figures are derived from their child entities' mapped accounts.
Setup Questionnaire
Answer each question in order to identify your scenario.
#
Question
Routing
Q1
Does your group have a holding company book (in Xero, QuickBooks, MYOB, or Zoho Books)?
Yes → Q2
No → Scenario B
Q2
Does the holding book contain only holding entries (investments, intercompany loans, dividends) — or does it already contain consolidated results?
Holding only → Scenario A
Already consolidated → Scenario C
Q3
Does any subsidiary own another subsidiary (not directly owned by the top group)?
Yes → Scenario D
No → continue
Q4
Are some entities on accounting systems BrizoConsol cannot connect to directly?
Yes → Scenario E
No → Scenario A or B
Q5
Are you migrating from another consolidation tool with historical data?
Yes → Scenario F
No → use above
Scenario A — Group has a holding-only book
When this applies
The Group entity has its own accounting book containing holding entries only — investments in subsidiaries, intercompany loans, dividend income, cash. It does not contain consolidated results. Subsidiaries each have their own books.
Example Structure
Group (consolidation node — no book)
├── HoldCo (Xero — connected, holding book)
├── Sub1 (Xero — connected)
├── Sub2 (QuickBooks — connected)
└── Con1 (consolidation node — no book, no account mapping needed)
Recommended Setup
Item
Detail
Hierarchy
The Group is the consolidation node at the top, created when you name your group — it shows Connected via consol. On the setup page (Global Settings → Setup Progress, under System), click + Add company for HoldCo, Sub1, Sub2 (and any other subsidiary entities) and connect each to its accounting system. If needed, add Con1 as a group beneath the Group in Global Settings → Group Structure → Organisation Hierarchy.
CCOA
Use the Group's chart of accounts as the anchor. When setting up the CCOA in Global Settings → Chart of Accounts → Common COA, base it on HoldCo’s chart of accounts. HoldCo contributes its trial balance like any other entity.
Account mapping
Map HoldCo, Sub1 and Sub2 accounts to the CCOA. Con1 and the Group node do not require account mapping — they are consolidation nodes with no accounts of their own.
Investment in subs
In HoldCo’s book. Record each acquisition in Ownership & Equity → Ownership, and choose HoldCo’s investment account as the company’s Investment in subsidiary account. BrizoConsol eliminates it against the subsidiary’s equity.
Goodwill
Measured from the acquisition recorded in Ownership & Equity → Ownership (price and net assets at fair value), and posted by BrizoConsol with the NCI.
CTA
Calculated and posted by BrizoConsol each month for foreign subsidiaries. Configured in Adjustments → Settings (under Currency translation).
🌟 Most common setup: HoldCo’s book provides a clean anchor for the CCOA and carries the investments. HoldCo, Sub1, Sub2 and any other subsidiaries connect directly. Consolidation nodes like Con1 require no mapping and no data connection — BrizoConsol aggregates their children automatically.
Scenario B — No group book
When this applies
There is no Group entity with its own accounting book. The Group exists only as a consolidation construct — not a legal entity that files its own accounts. All operating entities have their own books.
Example Structure
Group (consolidation node — no book)
├── Sub1 (Xero — connected)
└── Sub2 (QuickBooks — connected)
Recommended Setup
Item
Detail
Hierarchy
The Group is the consolidation node at the top, created when you name your group. It appears as Connected via consol. On the setup page (Global Settings → Setup Progress, under System), add Sub1 and Sub2 with + Add company and connect each to its accounting system.
CCOA
Create the CCOA in BrizoConsol directly, or use AI Suggest in Global Settings → Chart of Accounts → Common COA to derive a structure from Sub1 and Sub2's imported accounts.
Account mapping
Map Sub1 and Sub2 accounts to the CCOA via Global Settings → Chart of Accounts → Account Mapping. The Group node does not require mapping.
Investment in subs
Record each acquisition in Ownership & Equity → Ownership. BrizoConsol eliminates the cost held in the company’s Investment in subsidiary account against its equity; with no book holding the cost, post it to that account in Adjustments → Consolidation Journals.
Goodwill
Measured from the acquisition recorded in Ownership & Equity → Ownership, and posted by BrizoConsol with the NCI.
CTA
Calculated and posted by BrizoConsol each month for foreign subsidiaries.
🌟 Common for SME groups: Use AI Suggest to minimise the effort of building the CCOA from scratch. Once Sub1 and Sub2 are connected, the AI generates a suggested CCOA from their imported accounts — review and save.
Scenario C — Group book contains consolidated results
⚠️ Risk of double-counting
The Group's book already contains rolled-up results from the subsidiaries. If you were to use this book as a CCOA source alongside Sub1 and Sub2's data, every figure would be counted twice. The Group book cannot be used in BrizoConsol in this scenario.
Example Structure
Group (book contains consolidated results — do NOT use)
├── Sub1 (own book)
└── Sub2 (own book)
Recommended Setup
Item
Detail
Hierarchy
The Group is the consolidation node at the top. On the setup page, add Sub1 and Sub2 and connect them to their accounting systems. Do not use the Group's consolidated book as a CCOA source or data source.
CCOA
Create the CCOA from Sub1 and Sub2's accounts using AI Suggest, or build manually. The Group's consolidated book cannot be used as the CCOA anchor.
Account mapping
Map Sub1 and Sub2 accounts to the CCOA only. The Group node requires no mapping.
Everything else
Same as Scenario B — the investment and goodwill through Ownership & Equity → Ownership, and the CTA posted by BrizoConsol.
Treat the Group book as reference only. It can be useful for manually verifying your consolidated outputs match your existing reports, but it cannot be connected to BrizoConsol as a data source in this scenario.
Scenario D — Multi-level hierarchy (sub-subsidiary)
When this applies
One subsidiary owns another. Ownership passes through an intermediate entity rather than directly from the top Group. The effective group interest is the product of the ownership percentages cascaded up the chain.
Example Structure
Group (consolidation node)
├── Con1 (consolidation node — Sub1 and the company it owns)
│ ├── Sub1 (Xero — connected, owns Sub2)
│ └── Sub2 (QuickBooks — connected)
└── Sub3 (Zoho Books — connected)
Ownership (Ownership & Equity → Ownership): Sub1 — parent Group; Sub2 — parent Sub1
Group effective interest in Sub2 = Group % in Sub1 × Sub1 % in Sub2
Example: 80% × 75% = 60% effective interest
Recommended Setup
Item
Detail
Hierarchy tree
In Global Settings → Group Structure → Organisation Hierarchy, add Con1 as a group (+ Add Group) under the Group, then add Sub1 and Sub2 inside Con1. Con1 gives the Sub1–Sub2 sub-total and has no data source of its own.
Account mapping
Map Sub1, Sub2 and Sub3 accounts to the CCOA. Con1 does not require account mapping — it is a consolidation node.
Investment in Sub2
In Sub1’s book (Sub1 paid for Sub2). Record Sub2’s acquisition in Ownership & Equity → Ownership with Sub1 as the Parent entity and Sub1’s investment account as Sub2’s Investment in subsidiary account. BrizoConsol eliminates it against Sub2’s equity.
Goodwill on Sub2
Measured from Sub2’s ownership record, and posted by BrizoConsol with the NCI.
🛈 Two separate configurations: The Organisation Hierarchy decides how figures roll up — Sub1 and Sub2 together in Con1. Ownership decides who owns whom — in Ownership & Equity → Ownership, record Sub2 with Sub1 as its Parent entity. These are separate — setting one does not set the other.
💡 Or under Sub1: Instead of the Con1 group, you can drag Sub2 under Sub1 in the Organisation Hierarchy. Sub1’s reports then show its own books together with Sub2, Sub2’s acquisition entry is posted on Sub1, and Sub1’s reports carry the part of Sub2’s NCI that is outside Sub1. See
Multi-level groups.
Scenario E — Mixed: some entities on manual upload
When this applies
Some subsidiaries are on Xero, QuickBooks, MYOB, or Zoho Books and connect directly. Others are not — their trial balances must be uploaded as Excel / CSV each period.
Example Structure
Group (consolidation node)
├── Sub1 (Xero — connected)
└── Sub2 (spreadsheet — manual Excel / CSV upload each period)
Recommended Setup
Item
Detail
Hierarchy
On the setup page (Global Settings → Setup Progress, under System), click + Add company and connect Sub1 to its accounting system. Add Sub2 the same way, choosing Excel / CSV, and enter its name.
Manual TB upload
Each reporting period, export Sub2's trial balance and upload it to BrizoConsol via Organisation Settings → Data Loading. BrizoConsol does not pull data automatically for manual entities.
Account mapping
Map Sub2's manually uploaded accounts to the CCOA the same way as connected entities.
Goodwill, CTA
Same approach as Scenario A or B depending on whether the Group has its own holding book.
💡 Set a reminder: Manual entities must have an updated trial balance uploaded before each consolidation run. BrizoConsol will not flag stale data automatically for manual entities — upload Sub2's TB first, then run consolidation.
Scenario F — Migrating from another consolidation tool
When this applies
Your group has been using a different consolidation tool and is switching to BrizoConsol. Historical consolidated data exists in the old tool and opening balances must be seeded into BrizoConsol before it can produce correct reports from day one.
Recommended Setup
Item
Detail
Connect entities
Set up the hierarchy and connect all entities as in Scenario A or B. Do not import historical consolidated figures from the old tool — treat BrizoConsol as live from the migration date.
Opening balances
The first trial balance loaded for each entity is treated as its opening position. Load each entity from the migration month onward; its balances that month carry the history the old tool held.
CTA seeding
In Adjustments → Settings (under Currency translation), give each foreign company’s equity the rate on the day it came in, and its retained earnings a rate for each year, so its opening equity translates at the historical rates.
Goodwill seeding
Record each acquisition in Ownership & Equity → Ownership, with its price and net assets at fair value. BrizoConsol measures the goodwill from them.
Parallel run
Run BrizoConsol in parallel with the old tool for one to two reporting periods to validate consolidated outputs match before fully switching over.
💡 Migration tip: The most critical seeding items are CTA and goodwill opening balances. Without these the consolidated balance sheet will not foot correctly from day one. Contact BrizoConsol support to assist with the seeding process.
Scenario Summary
Scenario
Group book?
Group as data source?
CCOA source
Con node mapping?
A
Yes — holding only
Yes — as HoldCo, an entity
HoldCo’s COA
Not required
B
No
N/A
AI Suggest or manual
Not required
C
Yes — consolidated
No — do not use
AI Suggest or manual from subsidiaries
Not required
D
Optional
No
As per A or B
Not required
E
Optional
No
As per A or B
Not required
F
As per A or B
No
Existing CCOA
Not required