NetSuite localisation · e-invoicing mandates
NetSuite e-invoicing by country: mandates, dates and native coverage.
Many countries now require structured e-invoices or real-time invoice reporting. Oracle's NetSuite SuiteApps cover some natively; others need an accredited provider, an access point or a custom build inside NetSuite. The table shows, country by country, what is required, when, and which route NetSuite takes.
It reflects the rules as published or proposed at the time of writing (November 2026). Rules move often, so treat it as a planning aid and check your obligations with a tax adviser.
Country by country
E-invoicing and e-reporting mandates, and what NetSuite covers
| Country | What's required | Key dates | NetSuite coverage |
|---|---|---|---|
| Belgium Source: FPS Finance | Structured e-invoices over Peppol (EN 16931) between Belgian VAT-registered businesses. | Mandatory since 1 Jan 2026. A bill proposes near-real-time e-reporting via Peppol from 1 Jan 2028. | Native: EU Electronic Invoicing SuiteApp sends and receives Peppol invoices, credit memos, vendor bills and vendor credits. Gap: the proposed e-reporting leg. |
| Poland (KSeF) Source: Ministry of Finance | Structured invoices issued and received through the national KSeF system. | Receiving since 1 Feb 2026. Issuing since 1 Feb 2026 (2024 sales above PLN 200m) or 1 Apr 2026 (others). Businesses invoicing up to PLN 10,000 a month join on 1 Jan 2027. | Native: outbound invoices and credit memos to KSeF. Gap: pulling purchase invoices back from KSeF into AP needs a custom build or provider. |
| France Source: Service-Public | E-invoices through approved platforms (plateformes agréées), plus e-reporting of B2C and international sales. | All businesses receive from 1 Sep 2026; large and mid-sized businesses issue from 1 Sep 2026; SMEs and micro-businesses from 1 Sep 2027. | Native: France Electronic Invoicing and E-Reporting in the EU SuiteApp, through Oracle Business Network and Avalara. FEC from the France Localization SuiteApp. |
| Germany Source: BMF | Structured B2B e-invoices (EN 16931), typically XRechnung or ZUGFeRD. No central platform. | Receiving since 1 Jan 2025. Issuing from 1 Jan 2027 (prior-year turnover above €800,000), all others from 1 Jan 2028. | Native: Peppol and ZUGFeRD in and out through the EU SuiteApp; inbound XML to vendor bills. DATEV through a partner or custom export. Read the Germany article. |
| Spain Source: AEAT | Two regimes: Veri*Factu certified invoicing software, and B2B e-invoicing with status reporting (Crea y Crece). | Veri*Factu: companies by 1 Jan 2027, others by 1 Jul 2027 under current law (a postponement to Oct 2028 was announced, not yet enacted). B2B: 6 Oct 2027 above €8m turnover, 6 Oct 2028 for everyone else. | Native: Veri*Factu outbound invoices and credit memos; SII from the Spain Localization SuiteApp. Gap: B2B sending, receiving and status reporting. |
| Croatia Source: Tax Administration | Fiskalizacija 2.0: EN 16931 e-invoices over the national access-point network, with real-time e-reporting. | Live for VAT-registered businesses since 1 Jan 2026. Non-VAT taxpayers must also issue from 1 Jan 2027. | Gap: no Oracle Fiskalizacija SuiteApp. Delivered through a certified intermediary or custom build. |
| Greece Source: AADE | B2B e-invoices through a certified provider or AADE's free timologio app, transmitted to myDATA. | Mandatory from 2 Feb 2026 for businesses with 2023 gross revenue above €1m; from 1 Oct 2026 for all others. | Gap: no native Greek flow. Delivered through a certified provider, with the MARK reference written back. |
| Romania Source: ANAF | RO e-Factura: domestic invoices submitted to ANAF's national system. | B2B since 1 Jan 2024 (with a reporting transition to 30 Jun 2024); B2C since 1 Jan 2025. | Gap: no native RO e-Factura flow. UBL upload to and download from ANAF's SPV through a custom build or provider. |
| Hungary Source: European Commission | Real-time invoice data reporting to NAV (Online Számla). Issuing e-invoices is generally voluntary. | All B2B and B2C invoices reported in real time since 4 Jan 2021. | Gap: not covered by Oracle's EU SuiteApp. Reporting through a partner localisation or a custom build. |
| Italy Source: Agenzia delle Entrate | All B2B, B2G and B2C invoices cleared through the SDI in FatturaPA XML; cross-border invoices reported through SDI. | In force; no new 2027 date. | Partner: FatturaPA and SDI typically through an Italian partner localisation SuiteApp. |
| Portugal Source: Tax and Customs Authority (AT) | Certified billing software with ATCUD and QR code; B2G e-invoices through FEAP. | From 1 Jan 2027 PDFs need a qualified electronic signature and SMEs must send structured B2G e-invoices (the draft 2027 Budget may move the PDF rule to 2028). | Native: Portugal Localization SuiteApp for certification, ATCUD, QR and PT SAF-T. Gap: B2G through FEAP. |
| Sweden and Nordics Source: Upphandlingsmyndigheten, Skatteetaten | Sweden: Peppol BIS Billing 3 e-invoices for public-sector procurement. Norway: B2B e-invoices in EHF or Peppol BIS. Finland: EN 16931 for the public sector. | Sweden: procurements started after 1 Apr 2019. Norway: B2B issuing from 1 Jan 2027. Sweden's B2B inquiry reports by 30 Nov 2027. | Native: Denmark Peppol in and out in the EU SuiteApp. Access point: Sweden, Norway and Finland Peppol. |
| United Kingdom Source: HMRC roadmap | VAT invoices between VAT-registered persons must be issued and received as e-invoices. | From 1 Apr 2029. The government aims to set out compliance requirements between Oct 2027 and Apr 2028. | To be decided: standards not yet published, so the NetSuite route is chosen once they are. |
| United Arab Emirates Source: Ministry of Finance | Five-corner e-invoicing through Accredited Service Providers in PINT AE, B2B and B2G. | 1 Jan 2027 for revenue of AED 50m or more; 1 Jul 2027 below AED 50m; 1 Oct 2027 for government entities. | Native: UAE Electronic Invoicing SuiteApp (PINT AE out, vendor bills in, certified through Avalara). |
| Saudi Arabia Source: ZATCA | FATOORA: standard B2B invoices cleared by ZATCA before they are valid; simplified invoices reported within 24 hours. | Phase 2 in waves since 1 Jan 2023. Wave 25 (revenue above SAR 187,500) integrates by 1 Feb 2027. | Native: Saudi Arabia E-Invoicing SuiteApp, including CSID onboarding. |
| Malaysia Source: LHDN | Invoices validated by LHDN's MyInvois in UBL 2.1. | All phases live. The no-penalty relaxation runs to 31 Dec 2027; full enforcement from 1 Jan 2028. | Native: Malaysia Electronic Invoicing SuiteApp, certified through Avalara. |
| Singapore Source: IRAS | GST InvoiceNow: invoice data sent to IRAS over the InvoiceNow (Peppol) network. | New voluntary GST registrants since 1 Nov 2025 / 1 Apr 2026. All others in phases from 1 Apr 2028 to 1 Apr 2031, by annual supplies. | Access point: through an IMDA-accredited access point provider; not in our list of Oracle country SuiteApps. |
Native means an Oracle SuiteApp covers the flow, as described in Oracle's EU Electronic Invoicing overview and Oracle's country SuiteApp documentation. Gap means a provider, partner or custom build is needed for that part. Dates marked as proposed, announced or draft may still change.
Three ways NetSuite meets an e-invoicing mandate
- An Oracle SuiteApp. Built on Oracle's Electronic Invoicing SuiteApp, which Oracle documents as free for one country and licensed for more.
- An accredited provider or access point. Some regimes require one, such as approved platforms in France and Accredited Service Providers in the UAE.
- A custom build inside NetSuite. Where Oracle has no SuiteApp, or the SuiteApp stops short, I build the format, signing, sending and status tracking in SuiteScript 2.1, with the e-document stored against the transaction. I compare the options in NetSuite e-invoicing: prebuilt add-ons or a custom native localisation.
Most groups end up with a mix, which is fine if finance sees every country's statuses in one place.
Where the native SuiteApps stop
The gaps I see most often are missing halves of a process:
- Inbound. Poland's SuiteApp sends to KSeF, but purchase invoices still have to be pulled back and turned into vendor bills.
- Reporting. Belgium's proposed e-reporting and Spain's B2B status reporting sit outside today's native flows.
- Whole regimes. Croatia, Greece, Romania and Hungary have no Oracle country flow on the list above.
The E-Invoicing Control Centre demo shows how these gaps can be filled and monitored from one screen, with sample data.
How I can help
SuiteHeroes and its collaborating NetSuite consultants have delivered localisation and e-invoicing across many of the countries above. Through my NetSuite e-invoicing and tax reporting service I map your entities to their obligations, choose the route per country, then build, test and monitor it. If your Nordic or German entities come first, see NetSuite for Swedish and Nordic subsidiaries and NetSuite for German entities.
FAQ
NetSuite e-invoicing by country: common questions.
Does NetSuite handle e-invoicing in every country?
No. Oracle provides the Electronic Invoicing SuiteApp framework and country SuiteApps for places such as Belgium, Denmark, France, Germany, Poland and Spain (in its EU SuiteApp), plus the UAE, Saudi Arabia, Malaysia and Portugal, among others. Countries such as Croatia, Greece, Romania and Hungary need a certified provider, a partner localisation or a custom build.
Is the Electronic Invoicing SuiteApp free?
Oracle's documentation states it is free for one country and licensed for more. Confirm your own licence position with Oracle.
What does "native" mean in your table?
It means an Oracle SuiteApp covers that flow today, as Oracle documents it. Native does not always mean complete: Poland's SuiteApp sends to KSeF but does not pull purchase invoices back, and Spain's covers Veri*Factu but not B2B exchange under Crea y Crece.
Can you tell us which rules apply to our subsidiaries?
Yes. I map each subsidiary to the rules that apply and the gaps in your set-up, for your tax advisers to confirm. The obligation finder gives a quick first view.
Keep reading
Related service, insight and demo.
NetSuite e-invoicing and tax reporting
Readiness, build and testing, country by country, before your deadline.
See the service →Add-ons or a custom localisation?
When a prebuilt add-on is enough, and when a native build gives you control.
Read the insight →Live demo: E-Invoicing Control Centre
Native gaps, rejections with the fix, inbound AP and VAT reconciliation.
Try the demo →Which e-invoicing deadline hits your group first?
Book a free 30-minute call. Tell me where your subsidiaries are and I'll tell you honestly what applies, by when, and what it will take in NetSuite.