We don’t sell ERP. We put multi-entity chaos back in order.

Most NAV migrations fail because consultants treat them like data dumps.

We treat them like surgery.

We audit your NAV setup - technical and functional. We challenge every process like we’re building from scratch. We map what actually moves the business forward, and we kill what doesn’t hold up.

We don’t migrate 15 years of accumulated customizations just because they exist. We isolate what’s worth keeping. We rebuild it clean in Business Central.

The result: a faster, leaner system that does more with less code.

We can keep 100% of your historical data if you need it - but that doesn’t mean we recommend migrating 100% of your logic. The past stays accessible. The future stays clean.

A close that takes fifteen days. A consolidation the CFO reconciles by hand. Five subsidiaries solving the same problem five different ways. None of these are technical problems.

They are what an unmade decision looks like once software has encoded it, at group scale.

In a single company, a bad process is annoying. In a group, it gets replicated per entity, and every year it stays it gets more expensive to unwind. That is why the same symptom costs ten times more here than the vendor’s case study suggests.

So we do not start with your system. We start with the question behind the request — the one that has usually never been asked out loud, which is exactly why the answer keeps costing you money.

We challenge the assumption, compare it against how groups in your industry actually operate, and follow the chain down until it stops moving. It normally stops three layers below where the ticket was written, and it is normally governance, not software.

Then we tell you what we found. Including when the honest answer is that you do not need us.

Business Central’s native e-invoicing service handles the purchase draft. It does not talk to a certified platform on its own — someone has to build that connection, per platform, per protocol.

We built the layer that does. Not to sell it as a module — because a multi-entity group betting everything on one platform’s connector is a bottleneck we kept walking into.

Business Central’s E-Documents service creates and manages the purchase draft once an invoice arrives — matching, VAT, posting. What it does not do on its own is talk to a certified platform (a Plateforme Agréée), the certified operator the French reform requires between every buyer and seller. That connection — authentication, polling, the AFNOR status lifecycle — has to be built, and it has to be built per platform.

We built FacturaLink after watching multi-entity groups get boxed into a single platform’s connector, one that only spoke that platform’s dialect of the reform — a bottleneck the moment you have more than one entity with different volumes and a different fit.

FacturaLink sits on top of the native E-Documents service. It retrieves incoming e-documents from the connected platform, tracks the four AFNOR statuses a document goes through in Business Central — Déposée (filed with the platform), Rejetée (rejected by the platform), Refusée (rejected by you), Encaissée (paid) — and sends the outgoing status back: Approuvée (approved) when you post the invoice, Refusée (rejected) with the AFNOR reason code when you reject it.

The connector layer is built to an interface, not to a specific platform: SuperPDP and Tréso2 today, more can be added without touching the business logic. That is deliberate — a group should be free to change or split platforms per entity without rebuilding the Business Central side.