Skip to content
part of the groupApertiaDraivix

01Finance and accounting · module

Peppol e-invoicing (UBL)

Prepares and validates UBL e-invoices for the Peppol network and tracks delivery

Core available, part in progressBook a consultation
  • Peppol delivery
  • Issued invoice
  • Company (e-invoice recipient)
10
capabilities
3
record types
0
automations
2
integrations and AI tools

02What the module does

Less routine. More value.

The PeppolIntegration module generates a UBL e-invoice for the Peppol network from an issued invoice, validates it and tracks its delivery. For every e-invoice, your business retains the exact file, recipient, content hash and confirmation from the access point.

  • Mandatory fields checked upfrontThe system verifies that the invoice, its line items and seller details contain all mandatory Peppol BIS fields—catching missing data before the e-invoice is even generated.
  • From invoice to UBL e-invoiceAn issued invoice is converted directly into a UBL e-invoice, so you never have to recreate it in another tool or re-enter the data.
  • Two-stage file validationEvery e-invoice is validated against the XSD schema and Schematron rules—checking both structure and content—so you catch issues before handing the file over.
  • Second opinion from an external validatorOptionally, an external validator can also verify the e-invoice and generate a validation log, giving you documented proof of the check.
  • Validation bundle readiness checkYou can verify upfront that the set of validation files is in place, ensuring checks never fail simply because files are missing.
  • Record of every deliveryEach delivery record lists the recipient, access point and provider, so you always know who an e-invoice is for and how it is routed.
  • Hash binds record to XMLA SHA-256 hash links the delivery record to the exact XML file, letting you prove later which file a delivery pertained to.
  • Status from draft to acknowledgmentThe delivery record tracks every stage from draft to acknowledgment alongside the provider's own status, so you always know where an e-invoice stands.
  • Delivered only with proofA delivery can only be completed with documented confirmation from the access point—nobody can mark an e-invoice as delivered without proof.
  • Retry after rejectionIf an e-invoice is rejected, you can schedule a retry. A rejection isn't a dead end and the entire case stays on record.

What is currently in progress

  • Draivix does not call a Peppol access point directly. Queued e-invoices are dispatched by an operator or an external provider.
  • Delivery confirmation is recorded via command. There is no confirmation API in this version.
  • Export is implemented for invoices only. Credit notes and purchase orders over Peppol are not yet supported.

03How it works

How it works step by step.

  1. E-invoice preparation and validation

    First, the system checks that the invoice, its line items and the seller's details contain all mandatory Peppol BIS fields. Next, it generates a UBL XML file and validates it against the XSD schema and Schematron rules. Optionally, an external validator can also check the file and produce a validation log.

    Read in detail

    Before running these checks, you can verify that the validation artifact bundle is available. Checks are triggered by the system administrator via command.

  2. Delivery record

    A prepared e-invoice receives a delivery record with the status queued. It stores the recipient identifier, access point, provider, file path and a SHA-256 hash binding it to the exact XML file. Without a successful readiness check, no delivery record is created.

    Read in detail

    The record moves through the statuses draft, queued, sent, delivered, acknowledged, error, rejected, cancelled and archived. Alongside these, the original status reported by the provider is also stored.

  3. Access point confirmation

    Dispatch is handled by an operator or an external access point provider, whose confirmation is then recorded in the system. Acceptance or delivery requires a message ID or acknowledgment code together with a response file. A delivery is only marked complete with such confirmation. If an e-invoice is rejected, a retry can be scheduled.

04What runs automatically

Connected to the outside world.

External integrations

  • Connection via access pointAccess to the Peppol network runs through an external provider's access point. Files and confirmations are handed over and logged by Draivix; Draivix does not call the access point directly.
  • External UBL validationOptionally, you can pass the e-invoice to an external UBL validator for an additional check and a logged result report.

05Frequently asked questions

Does Draivix send invoices to the Peppol network automatically?

No. It prepares and validates the UBL file and creates a queued delivery record. Actual transmission is handled by an operator or an external access point provider.

How is an e-invoice validated?

By checking mandatory Peppol BIS fields, the XSD schema and Schematron rules. Optionally, an external validator can check it as well.

When is an e-invoice considered delivered?

Only after confirmation from the access point is recorded along with a message ID or acknowledgment code and a response file.

Can credit notes be sent via Peppol?

Not in this version. Export is only available for invoices.

Do I need my own Peppol access point provider?

Yes. Dispatch is handled by an operator or an external provider, and you can use any access point. Its confirmation is then recorded in Draivix.

06Related modules

Modules that work great together.

All modules in Finance and accounting

Let’s start together

Tell us how your business works.

We will show you what a system that takes over part of that work could look like.

Book a consultation