NetSuite e-invoicing in the UK

NetSuite handles e-invoicing through two SuiteApps: the Electronic Invoicing SuiteApp, which can receive XML e-documents from vendors and convert them into vendor bills, and the NetSuite Electronic Business SuiteApp, which links NetSuite accounts to the Peppol network through a partner service so you do not sign up for access points country by country. Oracle says the Electronic Invoicing SuiteApp has no built-in support for any country’s requirements, and we found no NetSuite page on the UK mandate, which gov.uk confirms starts in April 2029.

Below is what gov.uk has confirmed, what Oracle’s NetSuite documentation says, and what receiving e-invoices alongside PDFs looks like for an AP team on NetSuite. Every source was checked on 16 October 2026.

What has gov.uk confirmed about UK e-invoicing?

• The Budget 2025 document (26 November 2025) says the government will require all VAT invoices to be issued in a specified electronic format from April 2029, with an implementation roadmap to be published at Budget 2026.

• The Tax update 2026 summary (23 June 2026) announced that Peppol will be the core interoperability network for e-invoicing in the UK.

• The government’s consultation response (26 November 2025) says real-time reporting of invoice data to HMRC will not be introduced alongside the mandate in 2029.

• The Budget is on 28 October 2026, as the Chancellor’s letter to the Treasury Committee of 31 July 2026 confirms.

The formats and the rules for connecting are still to come. Our guide to the UK e-invoicing mandate covers what is settled and what is open.

What does Oracle say about e-invoicing in NetSuite?

Oracle’s Electronic Invoicing Overview describes the Electronic Invoicing SuiteApp:

• It supports outbound and inbound e-documents, in XML or JSON for outbound and XML for inbound.

• Inbound processing receives XML e-documents from vendors and converts them into NetSuite records. Oracle’s examples include a vendor invoice converted into a vendor bill, and a vendor credit memo converted into a vendor credit.

• Both directions use templates you create, and sample templates are included.

• It provides a framework only. Oracle says it does not include native support for any country-specific requirements or e-document standards, though you can build country templates with it.

• It is free for use in a single country. Use across several countries needs a licence from your NetSuite account representative.

Oracle’s NetSuite Electronic Business Overview describes the second piece. The NetSuite Electronic Business SuiteApp links participating NetSuite users to the Peppol network through a partner e-invoicing service, without signing up for access points in each country. The SuiteApp installs free from the marketplace, and the partner features need licences, which Oracle names as NetSuite Electronic Business Network Extension and NetSuite Electronic Document Processing Cloud Service.

Do you need a Peppol access point for NetSuite?

NetSuite reaches Peppol through the partner service behind the Electronic Business SuiteApp, which acts as the access point. So you do not arrange one separately on that route, though you do need the licences above. Our explainer on whether you need a Peppol access point covers what an access point does and who needs Peppol before 2029.

Where is the Peppol ID in NetSuite?

Oracle’s page on the PEPPOL template says the Peppol ID field sits under the E-Document subtab on customer and vendor records, and on the Electronic Invoicing Preferences page for each subsidiary. Entities registered on the Peppol network add their Peppol ID there manually.

The same page notes that the Peppol templates and plug-ins supplied are for reference, and may not produce a valid Peppol e-document for your case until they are customised. Plan for that work, or ask your NetSuite partner who will do it.

What changes for an AP team receiving e-invoices alongside PDFs?

E-invoicing stays voluntary for most UK suppliers until April 2029, so a NetSuite team that starts receiving e-invoices will still receive PDFs from most suppliers. The practical points:

• Two routes into vendor bills. Inbound e-documents convert through templates, while PDFs still have to be read and keyed or captured. Both need the same checks before approval.

• Subsidiaries. NetSuite holds Peppol IDs per subsidiary, so each invoice has to reach the right one, as a PDF must today.

• Matching. Each bill still needs matching to its purchase order and item receipt under your tolerances, whatever format it arrived in.

• Duplicates. A supplier moving to Peppol may also send the same invoice by email during the changeover.

For the manual routes into NetSuite, see our guide to importing vendor bills into NetSuite.

Where Stratas fits

Stratas receives Peppol, UBL and XML invoices alongside the PDFs and scans your suppliers send today, and every format is validated, approved and posted to your ERP the same way. Your team works one queue, whichever way each supplier sends. Supplier details, VAT, totals, order references and duplicates are checked on arrival, and anything that fails is held with the reason attached.

Invoice number, supplier, order reference, VAT and totals map to the fields NetSuite expects, then post with the original file and a complete audit trail. See our NetSuite AP automation page, our UK e-invoicing mandate guide and e-invoicing with Stratas.