What is eInvoicing?
The eInvoicing app gives Frappe and ERPNext native support for the PEPPOL BIS Billing 3.0 standard. With it, you can generate, validate, send and receive structured electronic invoices through the PEPPOL network — instead of (or alongside) PDF or paper.
Key features
- PEPPOL BIS Billing 3.0: Full implementation of the specification
- UBL 2.1 XML: Compliant generation for invoices and credit notes
- Multiple document types: Invoice and CreditNote (CreditNote auto-detected when
is_return = 1) - Validation: XSD schema + Schematron business rules (BR-CO-15, BR-CO-17, BR-IC-10/11/12, …)
- HTML preview: Visual preview of generated XML via XSLT transformations
- Entity matching: Incoming XML entities (supplier, items, PO) auto-match to ERPNext master data, with manual fallback
- Code list management: Automatic code list handling for PEPPOL standards
- Profile-based architecture: Extensible — add country-specific CIUS or other e-document standards via new profiles
- Service provider integration: Send and receive via B2B Router or Recommand (see Service Provider Integration)
Who this is for
- Administrators configuring the PEPPOL participant, code lists, and choosing which customers/suppliers exchange documents over PEPPOL
- Accounting users sending and receiving invoices day-to-day
Architecture in one paragraph
The app uses a profile-based system so different e-document standards can coexist. Each profile (PEPPOL is the one shipped) defines six function paths: generator, parser, validator, preview, detector, matcher. Outgoing flow: Sales Invoice → generator → UBL XML → validator → attached to EDocument. Incoming flow: XML → detector (profile + company + target type) → validator → matcher (supplier, items, PO) → parser → Purchase Invoice.
Where to start
- New here? Continue with Getting Started.
- Setting up to send invoices? Sending an Invoice.
- Receiving PEPPOL invoices? Receiving Invoices.
- Connecting a service provider? Setting Up a Provider.
Last updated 3 days ago
Was this helpful?