Finance areas · Multi-entity finance

One control model.
Every entity's local rules.

Entities share one governed ledger, one chart-of-accounts model and one approval discipline — while each keeps its currency, tax jurisdiction and country procedures. Standardized control without pretending every country works the same.

Read the multi-org reference
End to endMulti-entity finance
A new entity in one setupOnboard
Master data defined onceShare
Every posting knows its entityTransact
Entity and group views, same data
Report

The whole group surface

  • Entity management
  • Shared master data
  • Multi-currency
  • Country compliance
  • Intercompany activity
  • Group reporting

01 / The lifecycle

From new entity to group view,
without a second system.

  1. ONBOARD01

    A new entity in one setup

    Country setup provisions the chart of accounts, tax codes, fiscal periods and number series for the jurisdiction — configured, not rebuilt.

  2. SHARE02

    Master data defined once

    Accounts, items, customers and vendors live as organization-wide masters with per-entity overrides only where an entity genuinely differs.

  3. LOCALIZE03

    Country procedures as plugins

    Payroll, VAT and statutory filings are country plugins — adaptable logic per jurisdiction, not hardcoded vendor assumptions.

  4. TRANSACT04

    Every posting knows its entity

    Each transaction carries its legal entity and currency — cross-entity queries work naturally, without partition gymnastics.

  5. CONVERT05

    Currencies handled at the source

    Multi-currency postings with exchange rates applied and preserved — the functional and transaction amounts both on the ledger.

  6. REPORT06

    Entity and group views, same data

    Per-entity statements and consolidated group views come from one dimensional model — no export-merge-reconcile cycle.

Every table carries the legal entity as a dimension — one ledger, simple cross-entity queries, one audit trail.

02 / Coverage

Group finance without
a system per country.

01

Entity management

Legal entities with their own currency, fiscal calendar and jurisdiction — on one ledger.

02

Shared master data

Defined once at group level, overridden per entity only where needed — no drift between six copies.

03

Multi-currency

Transaction and functional amounts with preserved rates — conversion is recorded, not implied.

04

Country compliance

Payroll, VAT and statutory reporting per jurisdiction, delivered and updated as plugins.

05

Intercompany activity

Cross-entity transactions carry both sides' context — visible in one place, not two inboxes.

06

Group reporting

Consolidated views built from the same per-entity postings your auditors will trace.

03 / Who does the work

Local rules ship as
plugins.

Country logic is the clearest case for plugins: each jurisdiction’s procedures are owned, versioned and adaptable — Estonia today, your next country as a plugin, not a migration.

PLUGIN

Estonian Payroll Calculator

Gross-to-net payroll with TSD declaration

PLUGIN

Estonian VAT Declaration

KMD + KMD INF + EC Sales List for EMTA

PLUGIN

Estonian Annual Report

Complete majandusaasta aruanne for ariregister.rik.ee

Not limited to three

Add your own agents.
They follow your rules.

Accountants describe the work to Claude in plain language — what starts it, what to check, when to ask a person. Claude turns it into an agent with its own triggers, steps and limits, running under the same controls and audit trail as the three above.

Flag intercompany balances that don’t netPost FX revaluation at period endRoute local filings to the entity’s reviewer
See all plugins

04 / Go deeper

The reference,
and the walkthroughs.

Start with this workflow

Start with one entity.
Keep the model.

Bring one entity onto the governed ledger in shadow mode — the group structure, masters and controls are already built for the second one.

hello@ar-ti-fi.com