Aeion Finance for Multi-Entity
Multi-entity finance (parent + subsidiaries spanning multiple jurisdictions and currencies) traditionally meant NetSuite OneWorld at $50-150K/yr. Aeion tracks your corporate structure — parent, subsidiaries, ownership percentages, jurisdictions — as a real entity registry, and gives you segment-level reporting (cost centers, accounting classes, multi-currency accounts) on one ledger at flat-tier pricing. Intercompany journal pairing, consolidation eliminations, and transfer-pricing automation are modeled through custom Blueprint workflows on top of that foundation today, not a separate per-entity-ledger engine. Pro tier supports up to 3 entities; Enterprise unlimited.
When Multi-Entity Becomes Necessary
Common triggers:
Multi-Entity Setup
Aeion's legal-entity registry (used by the executive/board tooling) models the corporate structure itself:
Intercompany Journal Entries
When one entity transacts with another, here's how you'd model it on Aeion's ledger today:
Consolidation Approach
Aeion doesn't ship an automated consolidation engine today — this is the model teams implement via cost-center/accounting-class segmentation on one ledger, plus a custom Blueprint workflow for the eliminations:
Transfer Pricing Models
Multi-entity teams must price intercompany transactions at arm's length (US Sec 482, OECD BEPS).
Per-Entity Compliance
`
FAQ
Multi-tenant = separate Aeion tenants (separate billing accounts, separate user pools, separate databases via row-level security). Multi-entity = same Aeion tenant, multiple legal entities within. Multi-entity for ONE company with multiple subsidiaries; multi-tenant for separate businesses.
ASC 830 / IAS 21 (monetary at current rate, non-monetary at historical, P&L at average rate, CTA captures the difference) is the standard methodology to apply — Aeion's accounts support per-account currency, but the translation + CTA posting is a journal entry you (or a Blueprint workflow) create, not an automatic default.
Standard treatment: the acquired entity's results consolidate from the acquisition date forward, with purchase accounting (goodwill, intangibles) recognized separately. This is accounting guidance to apply through manual journal entries — Aeion doesn't have an acquisition-date consolidation cutover built in.
The entity registry doesn't have a native ownership-percentage field today — you'd track that in a custom field/collection or your cap-table tool, then compute the minority-interest carve-out manually or via a custom report. No automatic equity-line generation yet.
Every journal entry on Aeion's ledger is immutable and cross-referenced with an audit trail, which auditors generally like. Whether that translates to faster Big 4 audits than a NetSuite OneWorld setup will depend on your specific engagement.
For >$750M revenue multinationals, CbCR is a compliance requirement — Aeion doesn't generate CbCR filings today; this needs specialized tax software or your advisor.
You can configure which legal entity's info appears on an invoice per customer (e.g., UK customers billed by the UK entity in GBP). Routing the underlying revenue + intercompany service charges to the right entity is a ledger-configuration exercise today, not an automatic per-customer entity assignment.
NetSuite OneWorld ($50-150K/yr), SAP Business One ($30-100K/yr), Microsoft Dynamics F&O ($50-200K/yr), Oracle Fusion (enterprise) all ship built-in multi-entity consolidation. Aeion's Enterprise tier is priced well below that range, but today ships the entity registry + ledger primitives rather than a turnkey consolidation engine — expect to invest in Blueprint configuration to match OneWorld's out-of-the-box depth.
Data export via Singularity's reverse-connector or CSV is the path to fold Aeion data into an acquirer's NetSuite or other ERP.