eInvoicing in Europe: How CFOs should architect NetSuite for compliance

European eInvoicing has outgrown the tax department. For CFOs managing entities across Belgium, France, Poland, Germany, Italy, Spain and beyond, it is turning into a finance architecture decision.
At Novutech, we see this first-hand in multi-entity NetSuite rollouts. The finance teams that handle eInvoicing best are not simply asking how to comply in each country. They are asking which processes should live in NetSuite, which should connect to it, and how to avoid creating a fragmented compliance stack.

Europe's eInvoicing clock is already running

The regulatory timeline is moving quickly, and it is not moving at the same speed everywhere.

Belgium made structured B2B eInvoicing mandatory for most VAT-liable domestic business transactions from 1 January 2026. France requires all companies to be able to receive e-invoices from 1 September 2026, with issuing obligations phased from September 2026 for large and mid-sized companies and September 2027 for SMEs and micro-businesses.

Poland's KSeF mandate is also active in phases: large taxpayers started from 1 February 2026, most other VAT-registered businesses from 1 April 2026, and micro-entrepreneurs follow in 2027. Germany has already introduced B2B eInvoice reception obligations from 2025, with issuing requirements phased through 2027 and 2028. Italy has been operating mandatory B2B and B2C eInvoicing through Sistema di Interscambio since 1 January 2019.

Spain is also moving forward. Royal Decree 238/2026, published in March 2026, established the framework for mandatory B2B eInvoicing, with phased application linked to the technical Ministerial Order. At EU level, ViDA was adopted in March 2025 and will roll out progressively, with digital reporting and eInvoicing for intra-EU transactions becoming a core part of the 2030–2035 compliance horizon.

For a CFO, none of this is hypothetical. Several mandates are already live, and others are months away.

The expensive mistake: a country-by-country stack

When each country deadline is treated as a separate implementation, finance teams tend to make practical short-term decisions: a connector for France, a separate setup for Belgium, a KSeF integration for Poland, another workflow for Spain, and a manual bridge for the one acquired entity still running a different ERP.

Each decision looks reasonable on its own. Together they add up to an expensive compliance patchwork, and that patchwork usually creates five problems:

• Invoice fields, tax logic, vendor records and approval statuses drift apart by country.
• Finance has to prove compliance across several systems and workflows.
• Local invoice data reaches group finance late, or in formats that don't line up.
• Every country-specific integration needs its own maintenance, testing and monitoring.
• NetSuite slips into being one system among many, rather than the central source of truth.

As Frédéric Szikora, Co-founder & COO at Novutech, explains:

In 80% of the eInvoicing migrations we support across the EU, the friction point isn't the technology - it's having treated each country mandate as a separate project. The architecture decision they regret 18 months later is not having consolidated on a central system earlier.

That is the pattern worth avoiding. Treated as an architecture decision, each mandate can reinforce your ERP strategy instead of splintering it.

What should live in NetSuite?

NetSuite is built to be the finance backbone, especially for multi-entity and international businesses.

NetSuite OneWorld supports accounting and financial consolidation across subsidiaries, including subsidiary financial statements, multiple currencies, intercompany activity, and a shared chart of accounts where appropriate. It also provides financial consolidation capabilities for businesses operating across subsidiaries, regions, and business units.

That means NetSuite should remain the system of record for the finance processes that need group-level control.

Keep core finance data in NetSuite

NetSuite should own the data and workflows that define your financial truth:

• Chart of accounts
• Subsidiary structure
• Vendor and customer master data
• Tax codes and accounting dimensions
• Intercompany transactions
• Revenue recognition
• Financial reporting
• Consolidation and close processes

NetSuite revenue recognition capabilities also support automation of revenue scheduling, allocation, forecasting, and reporting. SuiteTax is designed to support global tax complexity and country-specific tax requirements.

These are foundational ERP responsibilities, not things to rebuild inside a local e-invoicing tool.

Use NetSuite as the control point

A good eInvoicing architecture strengthens NetSuite's role instead of bypassing it. Invoice data should flow back into NetSuite in a way that supports:

• Accurate posting
• Consistent approval status
• Clean audit trails
• VAT reporting
• Real-time or near-real-time visibility
• Month-end close
• Multi-entity consolidation

This is where architecture discipline matters. If the eInvoicing tool sends structured data to a local portal but leaves finance reconciling manually in NetSuite, compliance has been solved at the edge and left broken at the core.

What should connect to NetSuite?

The eInvoicing transmission layer plugs into NetSuite rather than standing in for it. It handles the country-specific requirements that change frequently and differ by jurisdiction:

• Invoice format validation
• Peppol connectivity
• Clearance platform submission
• Government or tax authority acknowledgements
• Country-specific schemas
• PDP requirements in France
• KSeF submission and response flows in Poland
• Local routing rules and status updates

This is where Novutech and Payhawk work together in a NetSuite-led architecture. Novutech helps define what should remain in NetSuite as the system of record, while Payhawk handles the major European eInvoice formats in one place (Peppol BIS 3.0, XRechnung, ZUGFeRD, Factur-X, KSeF and the rest), captures and validates each invoice, and exports it into NetSuite through a native integration rather than a bolt-on connector.

The transmission itself runs through a certified layer. In France, Payhawk connects to a registered PDP through its partnership with Invopop, so B2B e-invoices can be received, processed and reported in line with the September 2026 rollout. Invopop's role goes wider than France: as a certified transmission layer, it generates compliant invoice formats, validates them against each jurisdiction's schema, and submits them across Peppol and the country-specific clearance networks. That means the same connection model extends to each new mandate as it activates, rather than requiring a fresh integration for every country - which is exactly the fragmentation this architecture is designed to avoid.

And the great part is that none of this moves ERP logic out of NetSuite. It connects NetSuite to the right compliant exchange networks, without a new integration for every country.

The scalable model: one ERP backbone, one connected transmission layer

A scalable European eInvoicing architecture usually has three layers.

1. NetSuite as the finance backbone
NetSuite remains the system of record for accounting, tax logic, subsidiary structure, reporting, and close. That lets the CFO compare entities consistently, manage intercompany processes, and report at group level without reassembling data from local systems.

2. Payhawk as the unified spend and AP workflow layer
This is the layer that captures how money actually leaves the business, company cards, employee expenses, supplier invoices and payments, and turns it into structured, coded, approved data before anything reaches the ledger. Payhawk runs this layer: cards, reimbursements, accounts payable and purchase orders go through one workflow, approvals and validation happen up front, and NetSuite receives posting-ready entries with the right accounts, tax codes and dimensions already attached. eInvoicing runs on the same layer, not a separate tool. For the AP and accounting team, this is where the manual re-keying, the exports and the month-end reconciliation scramble disappear.

3. A compliant transmission layer
This layer connects to Peppol, PDPs, clearance models, and local government platforms. It absorbs regulatory change without forcing the ERP team to rebuild each country workflow from scratch.

This is the plug-in model: NetSuite does what it is built to do, specialist tools handle local exchange and validation, and finance keeps control of the whole process.

What this looks like in practice

This is the pattern Novutech designs for multi-entity finance teams. NetSuite sits at the centre as the finance backbone, while Payhawk feeds it with coded, validated data from card payments, expenses, purchase orders, supplier invoices, and eInvoicing workflows. The finance team stops re-keying and reconciling by hand, and the ledger stays clean enough to close on time.

That is what Flowdesk saw after moving onto Payhawk alongside NetSuite while scaling across four international entities:

Payhawk is already connected to NetSuite, and the accounting is practically done automatically... the time taken to process expenses has been reduced to a few minutes, whereas it used to take a whole day to manage them each month.

— Eric Olombel, CFO, Flowdesk

The same setup is what turns the next eInvoicing mandate into a configuration step rather than a fresh project. The workflow layer already holds structured, validated invoice data, and the transmission layer handles the local exchange and clearance.

Why eInvoicing is forcing ERP decisions

For many companies, eInvoicing is the moment the limits of the current finance stack become impossible to ignore.

Scale-ups whose accounting setup was built for one entity

Many of the companies we work with started on a single-entity accounting setup that did its job well for years. The pressure rarely comes from the software. It comes from the business changing shape: new entities, new currencies, cross-border VAT, and a group that now needs to consolidate. Those are questions a single-entity setup was never designed to answer.

The warning signs are usually clear:

• Multiple entities are managed differently.
• VAT treatment depends on local workarounds.
• Finance teams export reports to spreadsheets for consolidation.
• Structured invoice flows require manual mapping.
• Close timelines vary by country.

In this situation, eInvoicing becomes the forcing function. The company can keep adding local patches, or move to an ERP architecture that supports the next stage of scale.

Mid-market companies solving mandates one at a time

Plenty of mid-market finance teams already run a capable ERP with solid controls. Fragmentation still creeps in when every new mandate gets its own connector and its own workflow. The weak point there is the method rather than the core system, and that holds whichever ERP you run.

A connector-per-country approach may meet the immediate legal requirement. It can also leave you with a stack that is difficult to audit, hard to consolidate, and costly to maintain.

PE-backed groups after an acquisition

Post-acquisition finance is where this shows up first. One entity runs NetSuite, another runs a local accounting tool, and the business acquired last quarter is still on spreadsheets and outsourced bookkeeping. A new mandate hits all three at once and exposes the inconsistent master data, the missing approval controls and the gaps in group visibility that were tolerable while nobody was looking.

For a PE-backed finance leader, that is the decision point: keep feeding several local systems, or use the mandate as the trigger to consolidate onto one backbone. In our experience it is also where the integration work pays for itself fastest, because the consolidation was already on the roadmap and the deadline simply sets the date.

Where the constraints get sharper by vertical

Company shape is one lens; the sector is another. Some verticals hit structural constraints earlier and harder than a general “multi-entity” description captures:

• SaaS scale-ups running subscription billing across multiple entities face a specific challenge: ARR allocation must now be structurally distinguishable at invoice level, per jurisdiction. Manual mapping between billing, revenue recognition and the local eInvoice format breaks down fast once several mandates are live at once.
• Fintech operators with VAT-exempt and taxable revenue lines cannot rely on manual mapping once mandates activate. The mix of exempt and taxable flows has to be distinguishable in the structured invoice itself, per country, or reporting and audit exposure grows with every entity added.
• Investor-backed groups carrying several entities from acquisition inherit mismatched invoice, tax and master-data structures. A mandate lands on all of them at once and turns a known integration backlog into a hard deadline.

In each case, the eInvoicing mandate is not just a compliance task — it is the point where a vertical-specific data structure has to be built correctly at the architecture level, not patched at the edge.

How to assess your readiness

Before signing off on another country-specific connector, five questions tell you whether you are looking at a compliance task or an architecture decision. They are the same questions we work through with finance teams before a rollout, so they double as a discovery checklist if you are the one advising.
1. Can every entity close on the same timeline?
This is one of the clearest indicators of finance maturity.
Maxime Lothe, Co-founder & CEO at Novutech, puts it simply:

We measure the success of a multi-entity rollout with a single indicator: can the CFO close all entities in the same week? Three years ago, the answer was rarely. Today, with NetSuite as the backbone and eInvoicing handled at the architecture level, we see scale-ups with 5 to 7 entities closing in under 5 business days

If eInvoicing data is compliant locally but unavailable centrally, close speed suffers.

2. Is NetSuite your system of record, or just one system in the stack?
If invoice approvals, tax data, and payment statuses sit across multiple tools, NetSuite does not have the complete view finance needs. A scalable model gets structured invoice data into NetSuite cleanly and consistently.

3. Are you solving mandates country by country?
If the answer is yes, the team is building future maintenance cost into today's compliance project. Define a reusable architecture first, then configure it country by country.

4. Can your AP process handle structured invoice data?
E-invoicing changes how invoices are received, validated, approved and reconciled, not only how they are sent. Check whether your AP process can handle structured intake, automated validation and exception handling before the deadlines arrive.

5. Can you audit the full invoice journey?
A complete audit trail shows when an invoice was received, validated, approved, transmitted, accepted, posted, paid and reconciled. If that journey crosses too many disconnected systems, audit readiness gets harder.

Practical next steps for CFOs and finance systems leaders

Treat eInvoicing readiness as a finance architecture project rather than a local compliance scramble. A workable sequence:

• Map your entity footprint: each country, ERP, accounting tool, AP workflow, invoice volume and mandate deadline.
• Find the fragmentation: where you already rely on local portals, manual uploads or country-specific connectors.
• Define what NetSuite owns: the data and workflows that have to stay in the system of record.
• Choose a transmission strategy: a layer that can reach Peppol, PDPs, KSeF-style clearance models and whatever comes next.
• Test end to end: receipt, approval, posting, transmission, rejection handling and reporting, before the deadline.
• Measure the close: whether e-invoicing actually improves entity close speed, data consistency and group visibility.

Pros and cons of the connected architecture model

A central NetSuite-led architecture is usually more scalable, but it still requires planning.

Pros

• Reduces the number of local compliance tools
• Keeps NetSuite as the source of financial truth
• Improves auditability across entities
• Supports faster group consolidation
• Makes future mandates easier to onboard
• Helps finance teams standardise AP and reporting workflows

Cons

• Requires upfront architecture design
• Needs clean master data before rollout
• May require change management across local finance teams
• Depends on strong integration quality between NetSuite and connected tools
• Requires country-by-country testing even with a unified model

A centralised model does not remove complexity. It puts complexity in the place where it is cheapest to manage.

Turn the mandate into an architecture decision

For a single-entity company with no international expansion planned in the next 12–24 months, a local compliance tool may be all you need. For multi-entity groups (scale-ups, PE-backed businesses, international mid-market), the mandate lands on a stack that is already under strain, and the country-by-country reflex quietly makes it worse.

The teams that come out ahead treat the next deadline as the prompt to set their architecture: NetSuite as the backbone, one workflow layer feeding it, one transmission layer absorbing regulatory change. Do it once, and every future mandate becomes configuration rather than a new project.

If you are preparing for eInvoicing across multiple European entities, Novutech can help assess your NetSuite architecture and identify where country-by-country fragmentation is building up. Novutech helps European scale-ups architect their NetSuite implementation to absorb e-invoicing mandates across multiple entities, and integrates the transmission and spend layer of your choice (Payhawk, Invopop, and other certified partners) - so you can set the architecture before deadlines force rushed decisions.