NetSuite E-Invoicing Compliance: Which Mandates Affect You and What to Do Now

If you run NetSuite across European entities, e-invoicing is now a system configuration question with legal dates attached. Germany, Belgium, France and Poland each have a live or scheduled obligation that changes what counts as a valid invoice, and your ERP generates, sends, receives and stores that invoice.

Oracle supports parts of this through the European Union Electronic Invoicing SuiteApp. It is a set of installable SuiteApps, not built-in NetSuite functionality, and its coverage differs by country and by direction.

This guide sets out what each mandate requires, what Oracle documents for each country, and where the gaps and open questions sit. It is operational guidance for NetSuite owners, not tax advice, and it flags every point that official sources leave unclear.

What legally qualifies as an e-invoice

An e-invoice mandate is not a rule about sending invoices by email. It requires the invoice itself to exist as structured, machine-readable data that the recipient’s system can process automatically. The European reference is the EN 16931 standard, and the Peppol BIS Billing 3.0 specification is published as a usage specification of that standard.

In Germany, § 14(1) of the VAT Act (UStG) defines an electronic invoice as one issued, transmitted and received in a structured electronic format that enables electronic processing.

That has a practical consequence. A PDF, a scanned image or an emailed printout that looks identical to a person is not a structured invoice. Where a mandate applies to your transaction, the format your NetSuite instance produces, how the file is transmitted, how it is archived and how tax data is held on each line all become configuration decisions.

Formats and networks differ by country. Germany centres on XRechnung, Belgium on Peppol, Poland on a government-run clearance system called KSeF, and France on approved platforms. Treat the country sections below as separate projects that share a common data model.

Mandate status by country

The table shows the position reviewed in October 2026. Effective dates are for the obligations in scope for ordinary domestic B2B invoicing; exemptions and thresholds are covered in each country section.

Country requirements

Germany

According to the European Commission’s 2026 country sheet, German businesses must be able to receive structured e-invoices in the EN 16931 format from 1 January 2025. From 1 January 2027, businesses with turnover above EUR 800,000 may no longer issue paper invoices, and from 1 January 2028 the requirement extends to all businesses except those under the domestic small-business scheme.

XRechnung is the primary national format, with UBL 2.1 and CII syntaxes. The sheet also lists ZUGFeRD 2.2.0 (Profile XRechnung) as accepted and Peppol BIS Billing 3.0 as additionally supported, and it does not state Peppol as a B2B requirement.

The statute sets the detail. § 27(38) UStG allows paper, or another electronic format with the recipient’s consent, for supplies in 2025 and 2026. For supplies in 2027 that applies only where the issuer’s prior-year turnover did not exceed EUR 800,000. Non-compliant electronic formats sent by EDI are also allowed in 2027, with the recipient’s consent.

Belgium

Belgian B2B e-invoicing became mandatory on 1 January 2026 under the federal law of 6 February 2024, as the Commission’s country sheet records. It covers local B2B transactions between VAT-liable entities, including local reverse charge, and excludes intra-community supplies and certain VAT-exempt activities. The sheet says entities must screen themselves to see whether they are in scope.

Peppol is the primary format and transmission method. An alternative format or channel is allowed only by mutual agreement between the parties, must convert to EN 16931, and cannot be forced on a counterparty, so a Peppol route must always remain available. The sheet adds that the Federal Public Service Finance becomes the responsible authority from 1 January 2027.

On enforcement, a notice on the Belgian federal e-invoicing portal dated 18 December 2025 announces FPS Finance tolerance during the first three months of 2026 for companies that had acted in a timely and reasonable way. The official FAQ says suppliers and customers who do not comply risk penalties. The official pages reviewed do not state fine amounts, so confirm them with FPS Finance or your adviser.

France

France phases the reform by company size. The state e-invoicing agency AIFE states that receiving applies to all entities from 1 September 2026, issuing applies to large companies and mid-size companies (ETI) from 1 September 2026, and issuing applies to SMEs and very small businesses from 1 September 2027.

A ministry written answer published in the Journal Officiel on 4 August 2026 confirms receiving for all VAT-liable businesses from 1 September 2026 and issuing for small, medium and micro-enterprises from 1 September 2027.

Businesses exchange invoices through approved platforms (plateformes agréées). The written answer says companies must choose among platforms registered by the State, and that on 15 October 2024 the State decided not to build a public platform. AIFE also describes e-reporting, the transmission of additional data to the tax administration for B2C, non-domestic B2B and payment data.

Businesses should verify their company-size classification and their implementation obligations with the current French tax guidance or an adviser before relying on a date.

Poland

Poland’s KSeF is a central, government-run system rather than a distributed network. According to the KSeF portal, issuing became mandatory on 1 February 2026 for taxpayers whose sales including VAT exceeded PLN 200 million in 2024, and on 1 April 2026 for other taxpayers. Receiving invoices through KSeF has been mandatory since 1 February 2026.

Taxpayers whose monthly invoiced sales do not exceed PLN 10,000 including VAT may use paper or electronic invoices until the end of 2026. The Ministry of Finance says KSeF becomes mandatory for all entrepreneurs on 1 January 2027. The threshold test uses 2024 sales, as the KSeF portal and the official KSeF 2.0 handbook state (art. 145l of the VAT Act, in force from 1 February 2026).

Current KSeF guidance, last updated 27 April 2026, says penalties apply from 1 January 2027. Separately, the Ministry of Finance notice of 16 September 2026 says it plans to extend the deferral of penalties for incorrect use of KSeF to the end of 2027.

The notice says this needs a change in the law and that work on a bill is starting. It adds that deferring penalties does not remove the obligation to use KSeF. Treat the extension as proposed until it is enacted.

What Oracle’s EU Electronic Invoicing SuiteApp covers

NetSuite does not ship country e-invoicing as built-in functionality. Oracle’s Electronic Invoicing overview states that the base SuiteApp “does not include native support for any country-specific requirements or e-document standards”. Country coverage comes from the European Union Electronic Invoicing SuiteApp, installed alongside other SuiteApps. If you are new to the model, our guide to NetSuite SuiteApps explains how they are installed and licensed.

Prerequisites

Oracle’s installation prerequisites say you need a OneWorld account with the Custom Transactions feature enabled, and five SuiteApps: Advanced Localization Features, Electronic Invoicing, EMEA Localization, Localization Assistant and NetSuite Electronic Business. The Administrator, Accountant and CFO standard roles must be active for installation. A single-entity account without OneWorld cannot follow this route, which is one reason multi-entity structures matter here; our NetSuite OneWorld guide covers that structure.

Country and direction coverage

Licensing

Oracle states that the Electronic Invoicing SuiteApp is available free of charge when used for a single country, and that using e-documents across multiple countries requires a licence from your NetSuite account representative. Oracle’s licensing page adds that the NetSuite SuiteApps License Client must be installed first, and that OneWorld accounts select a free-use country for the parent company.

For a multi-country estate, treat licensing as a commercial step to settle early, not a footnote after the technical design.

Documented limitations and items to confirm

Oracle’s known limitations page gives limitation text for Belgium and Spain. The Denmark and Germany rows list a feature with no limitation text, and France and Poland are not listed. That absence is not a statement of full support. Before scoping, ask Oracle to confirm in writing:

• Which outbound formats are available for Germany, and what customization the reference Peppol template needs.
• How the France approved-platform connection and e-reporting work for your accredited platform.
• Whether inbound KSeF receiving is available for Poland.
• Whether inbound tax mapping is supported for Germany, since Oracle lists it as unsupported for Belgium.
• The current SuiteApp version and licensing terms for your countries.

When an integration or partner platform is still needed

This section is ERP Peers’ own architectural interpretation, not Oracle or government guidance.

Native SuiteApp configuration works best when your countries and directions are already covered and your volumes and formats are standard. A gap is the usual trigger for something more: Poland receiving, a German format Oracle does not document, or a France platform you must connect to. Each of these is a specific gap and not a reason to replace your whole invoicing stack.

Three routes exist. You can extend the SuiteApp with custom templates, connect an approved platform or Peppol access point for the country that needs it, or run the exchange through an integration layer that holds country logic in one place.

If EDI already carries your trading-partner documents, review how it relates to these mandates in our NetSuite EDI integration guide, because an EDI feed does not automatically satisfy a structured-invoice mandate.

The choice depends on how many countries you invoice from, whether you already run an integration platform, your invoice volume and who will maintain country-specific mapping as rules change. Our NetSuite integration architecture framework sets out how to weigh those layered options.

Implementation considerations and checklist

Master data is the most common source of delay and the one workstream you can start before choosing a solution. VAT numbers, registered addresses and network identifiers such as Peppol IDs should be validated against source records, not assumed correct. Oracle’s Peppol template expects the Peppol ID in the format country code, colon, GLN, so identifier formats need cleaning before any outbound test.

Inbound is as important as outbound. Receiving is already mandatory in several of these countries, and vendor bills arriving as structured files need a conversion and approval path. If supplier invoices are a pain point, our NetSuite accounts payable automation guide covers the downstream process that those files feed.

Archiving needs a decision before the first live invoice. If a rendered PDF replaces the original structured file in your document store, you may lose the compliant record, so confirm the retention rule and format with your adviser for each country.

Use this checklist to organise the work:

• List every NetSuite subsidiary, its country and the mandate and effective date that applies to it.
• Separate receiving, issuing and reporting obligations for each country.
• Confirm size and threshold categories, such as the German EUR 800,000 test and the French company-size category.
• Install and test the SuiteApp prerequisites in a sandbox, then confirm the open points with Oracle.
• Clean VAT numbers, addresses and Peppol IDs across customer and vendor records.
• Decide how original structured files are stored and retained.
• Test with real trading partners and an approved platform or access point, inbound as well as outbound.
• Agree who owns rule changes after go-live.

The ViDA horizon: 2030 and 2035

The European Union adopted its VAT in the Digital Age package on 11 March 2025. According to the European Commission, cross-border B2B digital reporting requirements start on 1 July 2030, and by 1 January 2035 member states with a domestic real-time reporting system must align it with the EU model and standards. The Commission says the reporting system will lead existing national systems to converge over time.

This is a planning horizon, not a replacement for the country dates above. Design your data model and archive so a structured EN 16931 invoice is the source record, and later reporting changes become a connector task instead of a rebuild.

Primary sources

Every country and Oracle claim in this guide links to the page that supports it beside the claim. The full source list is below, grouped by publisher.