Cross-entity consolidation — statutory and management views from the same ledgers.
Consolidation traverses the entity hierarchy honouring participation percentages, eliminates intercompany positions by configuration, computes minority interests, generates the consolidated balance sheet and P&L on demand. Multi-tier group structures handled natively.
On-demand consolidation
Group P&L and balance sheet derivable at any moment from the entity ledgers — period close consolidates formally, but real-time visibility is always available.
Multi-tier structures
Parent → subsidiary → joint-venture → minority participation — participation percentages traverse the hierarchy correctly.
Automatic eliminations
Intercompany positions eliminate at the right consolidation level by configuration. The configuration is auditor-reviewable.
Statutory and management
Two consolidation views from the same entity ledgers: the statutory one for the regulator, the management one for the CFO.
What the consolidation engine covers
Hierarchy traversal
Consolidation runs through the entity hierarchy honouring per-relationship participation percentages, voting versus economic interest where they differ, time-bounded participation changes.
Intercompany elimination
Configured per account pair. Revenue eliminates against cost; intercompany AR against intercompany AP; intercompany inventory profit deferred until external sale.
Minority interests
Computed at each consolidation level where participation is less than 100%. Equity, P&L and OCI portions surfaced separately per the regime.
Multi-currency consolidation
Translation to the group currency per the regime's method. Translation differences posted to the appropriate equity component.
Consolidation adjustments
Manual top-side adjustments for items not captured at the entity level (e.g. fair-value step-ups on acquisitions). Audit-trailed.
Reporting outputs
Consolidated P&L, balance sheet, cash-flow and equity statement — generated in the formats each regime expects (Spanish PGC, IFRS, US GAAP).
Why consolidation is engine-derived, not separately-maintained
Some groups run consolidation in a separate system fed by entity ledgers. The system has its own master data, its own period-close cycle, its own reconciliation cycle to the source ledgers. Three problems compound: master-data drift between source and consolidation; period-close timing that delays the consolidated view; reconciliation effort that consumes finance team hours.
Axional derives consolidation from the entity ledgers directly. There is no separate master data, no separate ledger to reconcile, no separate close. The CFO sees the group view today; the auditor reviews the same derivation; the entity controllers know that what they post is what the group sees.