Peppol e-invoicing for Maltese businesses — what's coming in 2026

If you run a B2B business in Malta — a wholesale food supplier, a venue that hosts corporate events, a restaurant that invoices catering clients — the way you issue invoices is about to change. Not next decade. This year and next.

This post is the plain-English brief on Peppol and ViDA, what they ask of your POS, and where VIND’s Peppol surface sits right now. The headline up front: we support UBL output today; CTC transmission is in beta. We say so on the marketing page because we’d rather you know the truth than be surprised at signing time.

What Peppol is

Peppol (Pan-European Public Procurement Online) is a network of access points that route electronic documents — most importantly, invoices — between businesses across the EU using a shared format. Instead of you emailing a PDF invoice to your customer, and your customer’s accountant manually re-keying it into their accounting system, the invoice travels machine-to-machine in a structured format called UBL (Universal Business Language).

Peppol has existed since 2012. What changed is that more and more EU governments are mandating it for B2G (business-to-government) invoicing, and ViDA (the EU’s “VAT in the Digital Age” initiative) is moving B2B in the same direction.

What ViDA mandates, and when

ViDA was adopted in March 2025 and rolls out in phases. The most relevant dates for Maltese businesses:

• By July 2030. All intra-EU B2B invoices must be issued in a structured electronic format (UBL or equivalent) and reported to the tax authority in near-real-time. This is called Continuous Transaction Controls (CTC).
• Domestic mandate. Each member state can mandate domestic B2B e-invoicing earlier, without needing further EU approval. Italy already mandates it (since 2019). France mandates it from September 2026. Belgium from January 2026. Malta has not yet announced a domestic date, but the precedent is clear.

The practical translation: if your customer is in France from late 2026, or in Italy today, you must send them an electronic UBL invoice through a recognised access point — not an emailed PDF.

What your POS has to do

A POS that issues invoices (not just receipts — invoices are different documents, with VAT broken out by line, customer VAT number, and a payment due date) has to:

1. Generate the invoice as a UBL document, not a PDF. PDF is for humans; UBL is for the network.
2. Sign it cryptographically, so the receiver can verify the issuer.
3. Submit it through a Peppol access point — that’s a certified intermediary that routes the document to the recipient’s access point.
4. Receive the recipient’s response (accepted, rejected, paid) and update the invoice status.
5. Report the invoice to the tax authority in near-real-time, per CTC rules.

Step 5 is the new one. The CTC report has a different format and a different recipient (your country’s tax authority, not the customer’s access point). It’s machine-to-machine, and the deadline for submission is typically 24 hours after issuance.

Where VIND sits today — the honest version

We are not going to give you the marketing-language version. Here’s the inventory.

UBL output: live

VIND can generate UBL invoices today. Open an invoice in the backoffice, click “Download UBL”, and you get a compliant XML file. You can manually upload that to a Peppol access point (your accountant will know one) or import it into your customer’s accounting system.

This covers your needs if you have a small handful of B2B invoices a month and your customer can ingest UBL via their existing tooling.

Peppol access-point submission: beta

We are piloting direct Peppol transmission with selected customers. That means VIND submits the UBL through our certified access-point partner on your behalf, and tracks the delivery receipt. The customer journey is “issue invoice → done”, with no manual upload.

The reason this is in beta and not GA is twofold:

1. The access-point certification is an annual audit. Our partner has it; we’re in the middle of our own technical-certification process to handle the routing directly. Until that closes, we depend on the partner’s API and we’ve only stress-tested it at moderate volume.
2. The CTC reporting deadline (24 hours) requires us to handle the failure case rigorously — if the access point is slow, we have to retry, fall back to a secondary access point, and alert the customer if the deadline is at risk. The retry + fallback logic is implemented but we want more hours on it before we put a customer’s tax-authority deadline behind it.

You can opt into the beta today. We’ll tell you exactly what’s monitored, what’s manual, and where we’d reach out to you if something needed your attention.

CTC reporting to MTCA: not yet

Malta has not yet announced a CTC reporting mandate. When it does, we will have a defined endpoint to submit to, and we’ll wire it up the same way. We’ve kept the UBL signing key infrastructure deliberately generic so that the CTC pipeline reuses 80 % of the Peppol code.

We will tell you the timeline as soon as MTCA publishes the spec.

What this asks of you, the operator

Three actions for 2026:

1. Get your customer’s Peppol IDs. If you invoice French or Belgian businesses today, ask them for their Peppol participant ID. The shape is 0184:GB123456789 or similar. Add it to their contact record in VIND.
2. Plan for July 2030 even if Malta’s domestic mandate is later. If you sell across the EU, the cross-border requirement applies on the EU date regardless of Malta’s domestic timing. Five years sounds like a lot; it’s two upgrade cycles and one accountant change.
3. Try the UBL export today. Issue one invoice as UBL, send it to your accountant, and see if they ingest it. If yes, the Peppol switch will be invisible to your day-to-day. If no, that’s a conversation worth having with the accountant now.

Why honesty pays

We considered marketing Peppol as a finished feature. The Maltese hospitality and B2B market is unlikely to push us on the difference for another 18 months, and “Peppol-ready” reads cleanly on a pricing page.

We didn’t, because the day a customer signs and then learns Peppol direct-submit is still in beta is the day we lose the relationship. So the compliance page says “beta” in the same font as everything else, and this blog post says it too.

That is our pitch for VIND. The features we ship, we ship. The features we’re building, we say so. Either way you know where you stand.