Home

EU e-invoicing, generated the way EN 16931 expects

Alongside the PDF you already send, ComOps generates every invoice, credit note and debit note as a standards-compliant Peppol e-invoice. This page covers what goes into that file and where the feature stops today.

What ComOps generates

Every issued invoice, credit note and debit note can be exported as UBL 2.1 XML built to the Peppol BIS Billing 3.0 profile, itself a compliant implementation of EN 16931, the European semantic data model for electronic invoices. The three document types map onto the standard's own type codes: an invoice is coded 380, a credit note 381, and a debit note 383. A credit note carries a reference back to the invoice it corrects, so the relationship between the documents survives the conversion to XML instead of living only in the ComOps database.

Tax categories, mapped automatically

UBL does not store a VAT rate as a bare percentage. It needs a tax category code alongside it (standard-rated, reverse charge, export, exempt, and so on), each with its own legal wording when the rate is zero. ComOps derives that category from the tax class already assigned to the line, the same classification the invoice used to calculate VAT, so the exported document and the invoice it came from cannot disagree about which rule applied.

Traceable corrections

A credit or debit note is exported with a reference back to the original invoice number. Because UBL expresses a credit note's amounts as positive figures while ComOps stores them internally with a negative sign, the conversion carries that sign change through line by line, not only on the document total.

Where this sits in the platform

The export reads from the same effective-dated VAT engine and tax classes that built the invoice, so the exported document and the invoice behind it come out of one decision rather than two. See how that tax engine works in the fiscal engine section.

What this does not do yet

ComOps generates the compliant file. It does not transmit it over the Peppol network on its own, and there is no live network connection from ComOps to Peppol today. Marking a document as submitted is a manual step your team completes once the file has left the system through your own Peppol Access Point or your accountant's channel. The claim here is the narrow one: the files ComOps produces are structured the way the standard requires.

Implements EN 16931:2017 · Peppol BIS Billing 3.0 (UBL 2.1)

Questions we get asked

See also

• VAT: the rate follows the date of the document
• Invoicing: documents that trace back to their source