Every invoice, in the right entity
Each entity has its own accounts, approvers and rules. Cortena reads every incoming invoice, identifies the entity it belongs to, and routes it into that tenant, where its own coding and approvals take over.
Many entities make payables messy
When one company becomes a group, the payables work multiplies. Invoices for every entity pile into one place, land on the wrong company, and each entity lives in its own tenant of the accounting tool.
One mailbox, manual routing
Invoices for every entity land in one inbox, and someone sorts them by hand into the right company. Slow, and easy to get wrong.
Booked to the wrong entity
Suppliers put the wrong group company on the invoice, so it posts against the wrong entity and has to be unpicked later.
A tenant for every entity
Each entity is a separate tenant in DATEV, Exact Online or Twinfield, so your team logs in and out all day to post each one.
One group inbox. Every invoice finds its entity.
Connect one central mailbox, or give each entity its own. Cortena reads the entity named on each invoice and routes it to the matching tenant. When a supplier gets it wrong, pin their invoices to the right entity so the rule always holds.
- Automatic routing from mailbox to the right entity
- Supplier pinning for deterministic matches
- Unmatched invoices held for one-click assignment
Set the rules once at the root. Unlock per entity.
Approval workflows are locked to the group by default, so a new subsidiary starts consistent on day one. When an entity needs its own chain, unlock that workflow for that entity alone. Everything else keeps inheriting from the root.
- New entities inherit the group workflow automatically
- Unlock a single workflow without touching the others
- Root changes flow to every entity still inheriting
Every entity, booked like it had its own accountant.
Cortena books each entity the way a dedicated accountant would, then posts straight into that entity's own accounting tenant. The ledger connection is shared at the group, but the administration, transaction type and document series stay the entity's own, so a booking never lands in the wrong company.
Every entity keeps its own books.
Shared where it saves you time, separate where it has to be. An entity's data, decisions and archive never bleed into another.
Its own accounts
Each entity has its own chart of accounts, cost centres and precedents. AI coding learns per entity, not across the group.
Its own approvals
Approvers and thresholds are scoped to the entity. A reviewer sees only the entities they are assigned to.
Its own exports
Booking batches go to the right administration in DATEV, Exact Online or Twinfield, tagged to the correct company.
Its own audit trail
The per-invoice activity log stays with the entity. Reporting rolls up to the group only when you ask for it.
Built for multi-entity companies.
Holdings and groups
Run payables for every subsidiary from one account. Consistent workflows, one place to see what is waiting, and clean separation for the audit.
VCs and family offices
Run payables across every fund, holding and portfolio company from one account. Each entity keeps its own books, approvals and exports, with clean separation for reporting and audit.
See the VC and family office setupMulti-entity, answered
Yes. Cortena is built for multiple entities under one account. Each entity keeps its own inbox, ledger, approvers and exports, while workflows and connections can be shared from the root.
Root-mailbox routing rules read the recipient line, the sender domain and the VAT ID and assign each invoice before coding. Anything that does not match a rule waits in a group tray for one-click assignment, so nothing is lost.
No. Workflows are inherited from the root by default so new entities start consistent. You can unlock a single workflow for one entity and leave the rest inheriting. Root changes still flow to every entity that inherits.
Yes. The ledger connection can be shared at the group, while each entity points at its own administration, transaction type and document series. A booking batch always lands in the correct company.
Yes. Approvers and reviewers are scoped per entity. Someone assigned to two subsidiaries sees only those two, and the per-invoice activity log stays with the entity it belongs to.
No. Accounts, cost centres, precedents, approvals and archives are kept per entity. AI coding learns within an entity, not across the group. Data stays on Hetzner servers in Germany with AES-256 encryption.
- Still have a question?
See it with your own entities.
Bring a group inbox and two or three entities. We will show routing, inheritance and per-entity exports on your own data.
Book a demo