|
WORKFLOW |
How to automate multi-entity consolidation in Sage Intacct
The payoff is continuous consolidation instead of a frantic period-end batch - but dimension design determines whether you get there.
Multi-entity consolidation is one of those tasks that looks straightforward on an org chart and turns into a three-day spreadsheet exercise in practice. Sage Intacct is built around the idea that intercompany eliminations and currency translations should happen as transactions post, not after the fact. That is a real architectural difference from ERP systems that run consolidation as a period-end batch job, and it is why controllers managing four or more legal entities are the core audience for this workflow.
BY THE NUMBERS
|
83/100 AF SCORE, SAGE INTACCT |
2 to 3 months TIME TO LIVE, AS REVIEWED |
STEP BY STEP
Multi-entity consolidation in Sage Intacct, step by step
This workflow takes a controller from a new Sage Intacct environment through the configuration steps needed to produce an automated, continuously updated consolidated trial balance across multiple legal entities. Complete entity setup before configuring eliminations.
1 |
Create each legal entity as a separate entity record in Sage Intacct, assigning the correct functional currency to each one so that currency translation rules apply at the entity level, not globally. |
2 |
Define the shared dimension structure - location, department, project, and any custom dimensions - before posting any transactions; use the consolidated report requirements from the business as the design input, not the existing chart of accounts. |
3 |
Configure intercompany transaction rules by tagging the accounts and transaction types that represent entity-to-entity charges; Intacct will use these tags to generate elimination entries automatically when transactions post. |
4 |
Set up exchange rate tables for each currency pair in scope, specifying whether each account class uses the period-end rate, the average rate, or a historical rate for translation. |
5 |
Run a test consolidation using a small set of seeded intercompany transactions across at least two entities; compare the system-generated elimination entries against a manual calculation to confirm the tagging rules are firing correctly. |
6 |
Use the following prompt to have an AI assistant review the elimination logic before go-live: 'I have the following intercompany transaction types and their assigned elimination accounts in Sage Intacct: [paste your tagging configuration]. Identify any transaction type that could create an out-of-balance elimination entry, and flag any account that appears on both sides of an elimination rule |
7 |
After the first live period close, pull the consolidated trial balance report and compare the intercompany receivable and payable balances across all entities; any nonzero net balance in those accounts indicates an untagged transaction or a missing elimination rule. |
8 |
Document the dimension structure and elimination rules in a configuration register outside the system so that any partner or internal change to setup has a baseline to revert to. |
The mechanism behind it is a combination of tagged intercompany transactions and a dimensional general ledger. When an entity-to-entity charge is recorded and tagged, Intacct generates the matching elimination entries automatically. Currency translation runs against the exchange rates stored in the system rather than a manual rate table someone maintains in Excel. The dimensional layer - location, department, project, customer, vendor, and any custom dimensions you configure - means you can slice the consolidated view without adding accounts to the chart of accounts. That matters because a bloated chart is usually what makes manual consolidation slow: every new reporting cut becomes a new account range to reconcile.
Where this breaks is dimension design. If the dimensions modeled at go-live do not map to the reports leadership will actually request, the consolidation output is correct but not useful, and someone rebuilds the mapping outside the system anyway. The other pressure point is module scope: the base financials license covers the core consolidation engine, but multi-entity work that touches project accounting, revenue recognition, or fixed assets requires additional licensed modules. Price the full target state before implementation, not the minimal footprint.
The practical measure of success is how long the consolidated trial balance takes to produce after the last subsidiary closes. If that number is still measured in days after go-live, the intercompany tagging rules or the dimension structure probably need a rework, not a workaround.
WORKED EXAMPLE
In practice
A controller manages five legal entities across the US, Canada, and the UK in Sage Intacct. After configuring intercompany tags this month, she runs the first automated consolidation for the period just ended and needs to verify that all intercompany charges eliminated correctly before locking the period.
What came back. The assistant identified that the most likely cause was a currency translation mismatch: the Canadian entity's CAD 5,600 charges had translated at the average rate into USD for the receivable side, but the elimination rule was referencing the period-end rate for the payable side, producing a nonzero net. It listed three checks - confirming that both sides of the elimination rule reference the same translation rate type, verifying that the exchange rate table for CAD-USD was updated before the elimination ran, and checking whether the elimination journal entry posted in the parent entity's
How it was checked. The controller pulled the elimination journal entry detail from the consolidated close report and confirmed the rate used on each side; the payable entry showed the period-end rate while the receivable showed the average rate, matching the assistant's primary finding.
A constructed example. The prompt is usable as written; the figures show the shape of a result, not a measured one.
WHEN TO USE IT
| WHEN NOT TO
|
WHAT TO TAKE FROM THIS
| Map every consolidated report you need before configuring dimensions - restructuring them post-go-live is painful. | |
| Confirm which modules your entity count and reporting needs require; consolidation, project accounting, and revenue recognition are each licensed separately. | |
| Vet your implementation partner on references at comparable entity counts, not just industry. |
SPONSORED
QUESTIONS THIS ANSWERS
Does Sage Intacct handle multi-currency consolidation automatically?
Yes - currency translation runs against exchange rates stored in the system and applies automatically as transactions post, rather than requiring a manual period-end step.
Is the consolidation module included in the base Sage Intacct price?
Core financials are priced attractively, but consolidation, project accounting, revenue recognition, and fixed assets are each licensed on top of the base. Price the full target scope before signing.
How long does a Sage Intacct implementation typically take for a multi-entity finance build?
Partner and comparison sources commonly cite 2 to 3 months for a finance-focused build. What drives the timeline is dimension and entity design, opening balance migration, and the number of integrations required.
SOURCES
Where this comes from
Agent readiness, pricing and go-live watchouts.
GO DEEPER
Go deeper
An original workflow written for practitioners. Replicate it in a sandbox first; nothing here replaces your review.
The modern accounting tech stack: tools, automations and workflows shaping the next generation of finance operations.
Modern Accounting · Audit Friendly Data · Remote A&F Jobs
Audit Friendly · accountingstack.ai