maesn
By function

Financial teams consolidate from every entity system, in one shape

A group's subsidiaries run whichever ERP their country and their history left them with. Maesn connects each one and returns the same objects in the same shape, so the work of producing a group format stops being repeated inside every entity.

Book a demoRead the docs
Four entities, four systems
  • DATEVGermany
  • Exact OnlineNetherlands
  • FortnoxSweden
  • XeroUnited Kingdom
arrives at the centre as
accounts[] · journalEntries[]
The same field names from all four, with nothing mapped in between.
Trusted by winning software teams
HubSpotTipaltiPaywiseRallyQredNordhealthFindityFintoClockinHEROHolviLanes & PlanesAgicapHubSpotTipaltiPaywiseRallyQredNordhealthFindityFintoClockinHEROHolviLanes & PlanesAgicap
4.8on G24.8 out of 5 stars on G2
The problem

The group format exists, and every entity rebuilds it by hand

The centre cannot consolidate what it cannot compare, so the comparison gets manufactured at the edges.

How the group format is produced today
  • Entity, GermanyDATEVIts own field names, its own export
  • Entity, NetherlandsExact OnlineIts own field names, its own export
  • Entity, SwedenFortnoxIts own field names, its own export
  • Entity, United KingdomXeroIts own field names, its own export
Every row ends in the same manual step: someone at that entity maps its export into the group standard before the centre can add anything up. Four entities means the mapping is maintained four times, by four teams, none of whom own the group format.

A group settles on a standard format, and then each subsidiary becomes responsible for getting its own system into it. That work is real accounting judgement done in a spreadsheet by whoever knows that system, it is repeated every period, and it is invisible until somebody leaves. The centre sees a clean file arriving and not the four different ways it was produced.

The reason it is per entity is not laziness, it is that the systems genuinely differ: different data models, different formats, different technologies and different countries, because statutory requirements are national. That is also why the answer cannot be to standardise the subsidiaries.

How Maesn solves it

One connection per entity, and identical objects coming back

Each entity's system is connected through Maesn rather than exported from. The common data model means what comes back carries the same field names and the same types whichever system answered, so there is nothing left to map into a group format. The mapping does not move to the centre, it stops existing.

Getting to those systems at all is the other half, and usually the half that stalls a consolidation project. Unified authentication makes it one flow per entity instead of one integration per vendor, including the systems that hold several companies behind a single login, where the entity is a selection rather than another connection.

What you get

The postings generalise, the balance report does not

Which consolidation route holds across a mixed group is a measurement rather than a preference.

Readable across the 30+ connected systems
  • The chart of accountsAccounts19

    The spine every consolidation maps onto, readable on the widest set of systems.

  • The postingsJournal entries11

    The smallest honest unit. Summed per account and per period they reproduce a balance anyway.

  • The trial balanceTrial balance2

    The report a group asks for first, and the route that does not generalise.

Counted per object from the per-system documentation. The ranking is the point rather than any single row: a consolidation built on the postings works across the group, one built on trial balances works on two.

This is worth knowing before a project is scoped, because the instinct is to ask each entity for its balance. Built on the postings and the chart of accounts, the same consolidation runs on every entity in the group. Built on the balance report, it runs on two of them and needs a manual workaround for the rest, which is the situation it was meant to remove.

What the team owns

Consolidation is one job of the CFO office, and the rest run on the same connection

Once every entity's system is reachable and answers in one shape, the workflows on top of it are a choice rather than a project each.

Nine of the workflows on this site sit with the Office of the CFO in one company or across a group. What Maesn supplies in each case is the same thing: reachable systems and identical objects coming back out of them.

Where this ends

We deliver comparable data, the consolidated result stays yours

Nothing here produces a consolidated balance sheet, and a layer that claimed to would be easy to disprove.

Maesn delivers
  • One connection per entity, including several entities behind one login
  • The same objects in the same shape from every subsidiary system
  • What changed since a timestamp, so a close and a forecast are one integration
  • The access problem per system, absorbed rather than passed on
Your finance function owns
  • The group chart of accounts and the mapping onto it
  • Intercompany eliminations and currency translation
  • The statutory result and who signs it
  • Which entities are in scope for which period

Read from the company's side rather than the team's, the same ground is covered for multi-entity enterprises, where the subject is the mixed system landscape itself. A group that already runs this way is Immocloud, and which systems an entity can be connected to at all is the integration directory. What is kept on the way through, which is the first question a group's own audit will ask, is on the security page.

Financial Teams FAQ

Common questions

Our entities run different systems in different countries. Does that change the integration?

No, and that is the point of the layer. Each entity's system is connected once and returns the same objects in the same shape as every other, so the group format stops being produced 30+ different ways. The differences between the systems are real, they just stop being yours to absorb.

Can we get each entity's trial balance instead of its postings?

On two of the connected systems, which is why the postings are the route that generalises. Summing postings per account and per period reproduces a balance anyway, and the chart of accounts is readable on 19. A consolidation built on the postings works across the group; one built on the balance report works on two entities.

Does Maesn produce the consolidated statement?

No, and the category name invites the opposite reading, so it is the one thing to be unambiguous about. What arrives is each entity's own data in one shape, on a schedule you choose. The group chart, the intercompany eliminations, the currency translation and the statutory result are produced in your own tooling or in the consolidation system the group already owns.

How many connections does a group with ten entities need?

One per entity and system pair, and onboarding one is an authentication flow rather than an integration project. Several systems hold more than one company behind a single login, and there the entity is a selection made during the connect step rather than another connection.

How current is the data at the point we consolidate?

You decide, because you decide when to read. Asking each system what changed since a timestamp is the same request everywhere, so a monthly close and a weekly forecast are the same integration run on different schedules rather than two projects.

Which workflows can a financial team own with this?

Most of the ones on this site. Payables, receivables, invoicing, reconciliation, expenses, tax, collections and analysis all sit with the Office of the CFO in one company or across a group, and each has its own page with the objects and the coverage behind it.

Is this the same thing as the Enterprises industry page?

They answer different halves. The industry page is about the company: historically grown, international, a mixed landscape of vendors and country variants. This page is about the team inside it that has to turn all of that into one set of numbers.
Maesn for other teams
Product & EngineeringShip one integration instead of one per system.Learn moreGo-to-MarketAnswer which systems you support, without asking.Learn moreCustomer SuccessSee every request, response and webhook per customer.Learn more

Build once on the Unified API.

See how one shape from every entity works for your integration, or dive into the technical reference.

Book a demoRead the docs