)
|
|---|
Since the introduction of the general e-invoicing obligation in January 2026, technical terms have been flying around. Your software asks for an "Access Point," your supplier talks about "BIS 3.0," and your accountant asks if your "UBL" is in order.
Previously, an invoice was just an invoice. Now it looks like IT science. Don't worry: you don't need to be an IT expert to comply with the legislation. In this blog, we translate the most important concepts into understandable language, so you know exactly what is happening behind the scenes of Banqup.
The highway: Peppol & Access Points
Everything starts with the network. You are not allowed to just send an e-invoice via email; it must go through a secure line.
Peppol Network: Think of this as a secure, international digital highway built specifically for exchanging business documents. It is managed by the non-profit organization OpenPeppol, which oversees standards and security.
Peppol Access Point: This is your on-ramp to that highway. You cannot just "hop on" Peppol; you need a certified service provider (a gateway) that connects your systems to the network. Banqup is such an Access Point. We take care of the security, validation, and actual transmission of your invoices. Without an Access Point, you cannot send or receive official e-invoices.
The address book: Peppol Directory & ID
On a highway, you naturally need to know where you are driving.
Peppol Directory: This is essentially the "Yellow Pages" of the e-invoicing world. It is a public search function that allows you to look up which companies are on Peppol and which documents they can receive. This is crucial to know if your invoice will actually arrive.
Peppol ID: To be found in that directory, you need a unique number. Just as a telephone number is unique to your device, a Peppol ID is unique to your company on the network.
The language: XML, UBL, and BIS 3.0
Once you are on the highway and have the right address, the recipient must still be able to read your message. This is often where the most confusion arises.
XML & UBL: An e-invoice is not an image (PDF), but a series of computer codes. This format is called XML. The specific "language" we use within that XML to structure invoice data is called UBL (Universal Business Language).
Peppol BIS 3.0: Because "UBL" is still quite broad (you can interpret it in many ways), strict agreements have been made. BIS 3.0 is the official standard within the Peppol network. It is a set of rules that determines which fields are mandatory. Does your file not meet these rules (for example: VAT number missing)? Then you get the message "Document not compliant with BIS standard," and the invoice is rejected.
BIS Credit Note: Do you need to correct an invoice? Then you use the BIS Credit Note standard. This is the same technical format, but specifically set up with fields that refer to the original invoice.
The details: OGM and e-fff
Finally, two more terms you might come across:
Structured Communication (OGM): You probably already know this from your bank transfers (those groups of digits with +++/+++/+++). In an e-invoice, this reference can be included in a specific XML field, so that your customer's accounting software can later match the payment to the invoice completely automatically.
e-fff: This was the old Belgian standard for electronic invoicing. Do you still encounter this term? Know that it is outdated. Peppol only accepts the modern BIS 3.0 standard; e-fff files must be converted first.
Banqup is your interpreter
Is your head spinning after reading all these terms? The good news is: as a Banqup user, you don't really need to know this.
You simply create your invoice in our interface. In the background:
Banqup translates your input into perfect UBL/BIS 3.0 code.
We look up your customer in the Directory.
We send it safely via our Access Point onto the Peppol highway.
This way, you are 100% compliant with the 2026 rules, without having to write XML code yourself.