Running a multi-entity South African group on Sage Intacct: the consolidation playbook

For most South African mid-market organisations, the moment Sage Intacct earns its place is not the first single-entity close. It is the first consolidated month-end across a group of legal entities, possibly across borders, possibly in multiple currencies, where the parent entity's CFO needs to walk into a board meeting holding a number she trusts.

That number is the product of design decisions made months earlier — most of them during the Discover phase of the implementation. Get them right, and the consolidated close is a Sage Intacct routine. Get them wrong, and you end up with a cloud system feeding a spreadsheet, which is the exact failure mode you were paying to escape.

Design decision 1 — entity structure mirrors legal structure

The first rule, and the one most often broken: your Sage Intacct entity structure should match your legal structure. If you have a holding company in Johannesburg, a sub in Cape Town, a branch in Windhoek, and a 70%-owned JV in Lusaka, that is four entities in Sage Intacct. Not three, not five, and not bundled into one entity with classes.

Why this matters: statutory reporting, tax reporting, audit reporting, and SARS-aligned reporting all roll up by legal entity. If the books don't, every year-end becomes a manual derivation exercise. Sage Intacct's multi-entity architecture is designed for exactly this — set it up once, and consolidations follow ownership percentages automatically.

Design decision 2 — dimensions, not classes

Sage Intacct's dimensional reporting model is the feature that most differentiates it from QuickBooks, Xero, and Pastel. Dimensions tag every transaction with metadata — location, department, project, customer, vendor, item, class, employee, B-BBEE category — and let you slice reporting on any combination without rebuilding the books.

For a South African group, the dimensions we'd configure as default are:

• Entity (the legal entity; automatic).
• Location (physical site, branch, region).
• Department (cost centre).
• Project (for project-based businesses).
• B-BBEE category (custom dimension for procurement reporting).
• Funder or donor (for NPOs).
• Segment (IFRS 8 operating segments).

Every transaction carries the relevant tags. Consolidated reports then roll up by entity; operational reports drill across entities by location, project, or segment. The same data, different lenses.

Design decision 3 — multi-currency from day one

Even if your group is currently all-ZAR, configure multi-currency. The cost of enabling it later, once you have transactions on the books, is meaningful. Configure rate types (daily, monthly, custom), source feeds (Sage Intacct's built-in rate provider or a custom feed), and revaluation schedules (typically month-end). Currency translation adjustments (CTA) get posted to a dedicated equity account on consolidation — IFRS-compliant out of the box.

For SADC groups operating in ZAR, USD, BWP, NAD, ZMW, MWK, the currency stack is configured once and serves every entity. Where many finance teams trip up is on the FX revaluation policy: pick monthly average for income statement, period-end spot for balance sheet, and document it in your IFRS accounting policy memo before go-live. The auditor will ask.

Design decision 4 — intercompany transactions, both sides, automatic

Intercompany journals are where the spreadsheet sneaks back in. Sage Intacct's intercompany functionality posts both sides of an inter-entity transaction automatically — debit to one entity, matched credit to the other — with the receivable and payable cross-referenced for elimination on consolidation. Configure inter-entity AR and AP accounts, set up the elimination rules, and the spreadsheet goes away.

If your group has frequent management fees, cost recharges, or shared service centres, configure recurring intercompany allocations. The finance team should not be touching them manually after the third month.

Design decision 5 — local view and group view

Every entity in a Sage Intacct group can have its own functional currency, its own statutory chart of accounts mapping, and its own IFRS-aligned format. The group sees consolidated, IFRS, in reporting currency. Each entity sees local, in functional currency. Same underlying data, dual presentation. Auditors love this; CFOs use it.

What the close cycle looks like once it's running

For a typical mid-market SA group on Sage Intacct, the consolidated close runs like this:

1. Day 1–3: AP, AR, payroll, and bank rec close per entity.
2. Day 3: intercompany matching review (automated; manual review of exceptions).
3. Day 4: FX revaluation, accruals, prepayments per entity.
4. Day 5: consolidation runs; CTA posts; eliminations apply.
5. Day 5–6: management accounts produced; board pack drafted.
6. Day 7–8: review with operating leaders; sign-off.

Eight working days for a consolidated close, including review and sign-off, is the target. The companies we work with typically arrive at this from a starting baseline of fifteen to twenty days.

What this looks like in your engagement

Bo Gartner runs multi-entity SA group implementations as an eight-to-fourteen-week engagement under our Intacct Activation method. Two weeks of Discover (entity model, dimensions, currencies, intercompany rules, audit posture); four to six weeks of Configure and Migrate; two to three weeks of Validate; one weekend of cut-over; ninety days of Hypercare through the first consolidated close. Fixed price, predictable scope, no surprises.

If you're carrying a group close in spreadsheets and a creeping sense that one mistake away from a real problem with your auditor, book a consult. We'll show you what your version of this looks like.