Multi-Company Construction ERP Rollout

Rolling out ERP across a construction group with multiple legal entities or branches is markedly harder than a single company. The central question is not which software to pick, but deciding what is shared at group level and what each entity controls. Getting that balance wrong leads either to a group that loses control or to entities so constrained they cannot operate.

Why is multi-company ERP harder?

Four difficulties. First, the chart of accounts must be shared so reports consolidate, yet each entity has its own posting habits. Second, customer, vendor and project master data must be unified to avoid duplication. Third, approval processes differ between entities on limits and levels. Fourth, intercompany transactions must be handled correctly from the start, not deferred to period end.

Centralised or decentralised?

The model that fits construction groups best is centralised core with decentralised operations. The core covers company structure, chart of accounts, financial periods and accounting policy, shared across the group. Operations cover purchasing workflow, approval limits and project management approach, configurable by each entity within allowed boundaries.

How do you handle intercompany transactions?

This is the easiest part to get wrong. Define three things up front: how internal revenue and cost are recorded, how intercompany balances are reconciled between entities each period, and how they are eliminated on consolidation. Leaving it to the closing stage lets errors compound and makes root causes hard to find.

What rollout sequence works?

Start with one representative entity, ideally the one with the cleanest processes and strongest accounting team. Run it steadily through two accounting periods, distil a standard configuration, then replicate. This surfaces problems at small scale and creates an internal user group that can support later entities.

The group’s role in a multi-company model

The group should retain three powers: deciding the chart of accounts and accounting policy, setting management reporting standards, and approving changes affecting the whole system. Beyond that, entities should have autonomy, because centralising every small decision is a common cause of slow rollouts.

How does Acumatica Construction ERP support multi-company?

Acumatica Construction ERP does not charge per user, so a group can extend the system to every legal entity and branch without licence cost rising with user count, which matters especially for construction groups with many sites. The platform provides deep project financials to track committed cost and forecast cost at completion by project and by entity, a governance model based on established best practice to standardise processes across entities, and AI capability for repetitive data entry and reconciliation.

In Vietnam, S4 Consulting is a Gold Partner of Acumatica holding more than 31 global certifications. S4 localises Acumatica Construction through its Financial Localization suite, Vietnamese language packs, e-invoice integration, bank integration, and Excel integration with Velizo.

Frequently asked questions

Should all subsidiaries share one chart of accounts?

Yes, at the framework level. Subsidiaries can add detail accounts within allowed boundaries, but the main framework must be common so reports consolidate automatically.

How soon can you replicate to the next entity?

Once the first entity has run steadily through two accounting periods. Replicating earlier tends to repeat the same errors across several entities at once.

How should a newly acquired entity be onboarded?

Bring it in on its own schedule, starting with opening balance conversion and configuration from the established standard. Do not let a new entity run its own system and consolidate manually, because the maintenance cost grows over time.