ToolForge
Browse All 111 Tools

Categories

Home/Tools/Calculators/Peppol E-Invoice Generator
Zero-Data-Retention ยท 100% Client-Side

Peppol BIS Billing 3.0 E-Invoice Generator

Generate compliant UBL 2.1 XML electronic invoices for official Peppol B2G & B2B networks. Dynamic line items, automated VAT calculations, instant XML download.

Advertisement

๐Ÿ”’ 100% Client-Side Processing

Your invoice data never leaves your browser. No server uploads. GDPR & ePrivacy compliant.

1Document Details

2Supplier (Seller)

3Customer (Buyer)

4Invoice Line Items

Item #1
850.00 EUR
Line Extension Total850.00 EUR
VAT Amount161.50 EUR
Payable Amount1011.50 EUR

5Compliant UBL 2.1 Peppol Output

Click "Generate Peppol UBL XML" to preview your compliant invoice output.

Advertisement

Peppol BIS 3.0 XML Generator: 2026-2027 B2B E-Invoicing Mandate Guide

Electronic invoicing (e-invoicing) through the Peppol network is no longer optional for businesses trading within Europe and international jurisdictions. The rollout of B2B electronic invoicing in Europe is accelerating rapidly. 2026 and 2027 mark a tipping point, with mandates going live in countries like Belgium (Belgium B2B e-invoicing mandate January 2026), France (France B2B e-invoicing September 2026), Croatia (Croatia Fiskalizacija 2.0), and Poland (Poland KSeF platform). Germany (Germany e-invoicing transition 2027) is also introducing a phased obligation leading up to 2027 and 2028.

Our free Peppol BIS Billing 3.0 e-invoice generator creates syntactically valid UBL 2.1 XML documents directly in your browser. Every field maps to the mandatory and conditional business terms defined by OpenPeppol's Business Interoperability Specification (BIS) for cross-border and domestic invoice exchange.

EN16931 Compliance and Format Interoperability

Whether you are preparing for the Belgian mandate using Peppol BIS 3.0 or ensuring your ERP can generate XRechnung or ZUGFeRD output for Germany, our tool ensures your structured e-invoices align perfectly with the EN16931 European standard. By utilizing client-side UBL XML generation to validate data syntax against official OASIS and OpenPeppol schemas, finance and software development teams can establish seamless cross-border interoperability before connecting to a certified Peppol Access Point.

Bridging the Gap: ERP Systems and Peppol Access Points

A major friction point for enterprise compliance teams is ERP system integration. Legacy systems (such as SAP, Oracle, or Microsoft Dynamics) often struggle to natively output valid EN16931 XML or manage complex 4-Corner network delivery. Missing VAT numbers, malformed endpoint identifiers, or incomplete legal entity master data will trigger instant rejection by certified Peppol Access Points. Positioning this generator as a quick client-side tool allows AP (Accounts Payable) teams and software developers to execute master data validation and test payload creation prior to live transmission.

Understanding the Peppol E-Invoicing Ecosystem

The Pan-European Public Procurement Online (Peppol) network is a set of technical specifications and infrastructure enabling standardized document exchange between businesses and government entities. At its core, the network operates on a four-corner model:

  • Corner 1 (Sender): The supplier who originates the invoice.
  • Corner 2 (Sender Access Point): A certified Peppol service provider that transmits the invoice.
  • Corner 3 (Receiver Access Point): The certified service provider receiving on behalf of the buyer.
  • Corner 4 (Receiver): The buyer/government entity that receives the invoice.

The Service Metadata Publisher (SMP) and the Service Metadata Locator (SML) work together to route documents to the correct Access Point. Our tool generates the XML payload for Corner 1, which you then submit through your Corner 2 Access Point provider.

Mandatory UBL 2.1 XML Elements for Peppol BIS 3.0

Every Peppol-compliant invoice must include specific elements defined in the OASIS UBL 2.1 schema. Our generator populates all mandatory fields:

XML ElementBusiness TermDescription
cbc:CustomizationIDBT-24Peppol BIS 3.0 specification identifier
cbc:ProfileIDBT-23Billing process profile identifier
cbc:IDBT-1Unique invoice number
cbc:IssueDateBT-2Invoice issue date (YYYY-MM-DD)
cbc:InvoiceTypeCodeBT-3380 = Commercial Invoice
cbc:DocumentCurrencyCodeBT-5ISO 4217 currency code
cbc:EndpointIDBT-34/BT-49Peppol participant identifier (EAS scheme)
cac:TaxTotalBG-22Total tax amount with subtotals per category
cac:LegalMonetaryTotalBG-22Document-level monetary totals
cac:InvoiceLineBG-25Individual invoice line items

EAS (Electronic Address Scheme) Codes Reference

The Endpoint Identifier Scheme (EAS) determines the routing of your e-invoice through the Peppol network. Each participating country and organization type uses a specific code:

EAS CodeScheme NameUsage
0007Swedish Organization NumberSwedish entities
0009SIRET (France)French companies
0088GLN (Global Location Number)International / GS1 members
0106Dutch KVK NumberNetherlands
0184Danish CVR NumberDanish entities
0190Dutch OINDutch government
0201Italian IPA CodeItalian public administration
9925Italian VAT NumberItalian VAT-registered entities

EU B2B E-Invoicing Mandate Timeline: 2026-2027 Deadlines

The rollout of B2B electronic invoicing in Europe is accelerating rapidly. 2026 and 2027 mark a tipping point, with mandates going live across the continent. Accounts Payable teams and developers must prepare structured e-invoices compliant with the EN16931 European standard well before these deadlines:

  • Belgium B2B e-invoicing mandate January 2026: All VAT-registered entities must issue and receive structured e-invoices via Peppol BIS 3.0 from January 1, 2026.
  • France B2B e-invoicing September 2026: Mandatory receipt of structured electronic invoices begins September 2026. Mandatory issuance phases in for large enterprises and mid-caps through 2027.
  • Germany e-invoicing transition 2027: Phased B2B obligation requires all companies to accept e-invoices from January 2025, with mandatory issuance using XRechnung and ZUGFeRD formats rolling out through 2027-2028.
  • Croatia Fiskalizacija 2.0: Comprehensive B2B e-invoicing framework integrating real-time fiscal reporting with Peppol network connectivity and EN16931 compliance.
  • Poland KSeF platform: The Krajowy System e-Faktur (National e-Invoicing System) mandates all B2B transactions through a centralized government platform for VAT-registered businesses.
  • Italy: Mandatory B2G and B2B since 2019 via SDI (Sistema di Interscambio). FatturaPA format required domestically, Peppol for cross-border.
  • Spain (Crea y Crece law): B2B mandatory structured e-invoicing for companies with annual turnover above โ‚ฌ8M enforced from 2026.
  • Romania: Mandatory B2B via RO e-Factura since January 2024 for all domestic transactions.

VAT Tax Category Codes in Peppol

The ClassifiedTaxCategory element in each invoice line uses standardized codes from the UNCL5305 code list:

CodeCategoryWhen to Use
SStandard RateNormal VAT rate applies (19%, 20%, 21%, 25% etc.)
ZZero RatedVAT at 0% (exports, certain food, children's clothing)
EExemptTransaction exempt from VAT (medical, education, financial services)
AEReverse ChargeVAT accounted by buyer (cross-border B2B within EU)
GExportExport outside the EU/EEA
ONot SubjectServices not subject to VAT

How This Tool Works: Client-Side XML Generation

Unlike server-based invoice generators that transmit your business data to remote servers, our Peppol e-invoice generator operates entirely within your web browser. The technical architecture ensures:

  • Zero Data Transmission: All form inputs, calculations, and XML construction happen locally in JavaScript. No API calls are made.
  • GDPR Compliance: Since no personal or business data is collected, stored, or processed server-side, there are no GDPR obligations triggered by using this tool.
  • Offline Capability: Once the page loads, you can disconnect from the internet and continue generating invoices.
  • Instant Download: The generated XML file is created as a Blob object in memory and downloaded directly - no server round-trip required.

Validation: What Happens After Generation

While this tool generates syntactically valid Peppol BIS 3.0 XML, production invoices should undergo multi-layer validation before submission:

  • Schema Validation: Verify the XML conforms to the UBL 2.1 XSD schema definitions from OASIS.
  • Schematron Validation: OpenPeppol publishes Schematron rules that enforce business rules beyond schema compliance (e.g., if InvoiceTypeCode is 380, DueDate must be present).
  • CIUS Validation: Country-specific Core Invoice Usage Specifications may impose additional requirements (e.g., XRechnung for Germany requires Leitweg-ID in BT-10).
  • Access Point Validation: Your Peppol Access Point provider performs final validation before transmitting to the receiver.

Free validation services include the OpenPeppol Testbed and the European Commission's CEF Digital validator.

Frequently Asked Questions (FAQ)

What is a Peppol BIS Billing 3.0 e-invoice?

Peppol BIS Billing 3.0 is the standardized e-invoicing specification used across EU and global B2G (Business-to-Government) and B2B networks. It mandates a UBL 2.1 XML structure compliant with EN 16931, ensuring interoperability between all Peppol Access Points. The specification defines which XML elements are mandatory, conditional, and optional for a valid electronic invoice.

Is this Peppol invoice generator free to use?

Yes. This tool is 100% free with no signup, no usage limits, and no watermarks. All XML generation happens in your browser using client-side JavaScript - your invoice data is never transmitted to any server, making it inherently GDPR compliant.

Can I use this for official EU government e-invoicing?

This tool generates the correct UBL 2.1 XML structure with Peppol BIS 3.0 CustomizationID and ProfileID. However, to submit to a government Access Point, you must transmit the XML through a registered Peppol Access Point provider (Corner 2). The tool produces the payload; transmission requires a certified service provider.

What EAS codes should I use for Peppol endpoints?

Common EAS codes include: 0088 (GLN - Global Location Number), 0007 (Swedish organization number), 0009 (French SIRET), 0184 (Danish CVR), 0201 (Italian IPA), and 9925 (Italian VAT). Your Peppol Access Point provider will specify which Electronic Address Scheme applies to your registration.

Does this tool support credit notes?

The current version generates standard commercial invoices (InvoiceTypeCode 380). Credit notes (InvoiceTypeCode 381) follow a nearly identical XML structure but use the CreditNote root element instead of Invoice. Support for credit notes is planned for a future update.

TF

About FreeToolForge

This Peppol e-invoice generator was built for finance teams, accountants, and developers who need to create or test UBL 2.1 XML invoices without exposing sensitive business data to third-party servers. FreeToolForge specializes in building production-grade, client-side utilities that prioritize data privacy and compliance.