E-invoicing in Malta: Government buyers on Peppol, and what 2030 brings

01Where Malta stands in November 2026

Malta started on the Government side. The Government chose the Peppol network, and the Ministry for Finance contracted a certified Peppol service provider so that departments, entities, regional authorities and local councils can receive e-invoices. Under its e-invoicing guidance (opens external site), contracting authorities must accept e-invoices that follow EN 16931 on contracts above the EU thresholds. The Department of Contracts names Peppol BIS Billing 3.0 as the format to use.

For suppliers there is, as of now, no legal requirement to send e-invoices to Maltese public bodies. Some calls for tenders published on ePPS do ask for them, so read the tender conditions of each contract. For invoices between businesses, plan against the EU timetable set out below.

Belgium, where our own teams work, went further: since 1 January 2026 businesses established there exchange structured e-invoices with each other, over Peppol by default. The federal e-invoicing site (opens external site) explains the rules, including fixed penalties after a tolerance period that ended on 31 March 2026. For a Maltese company with Belgian customers or a Belgian sister company, that obligation is already live.

02What an e-invoice actually is

An e-invoice in this sense is structured data: a file that software reads with no person interpreting it, following the EN 16931 data model. Scans of paper invoices, PDFs and word-processor files do not qualify, even if they come by email. The structured file may carry a PDF attachment for human readers, but the data is what has legal and technical weight.

For Maltese Government buyers the format is Peppol BIS Billing 3.0, the Peppol profile of EN 16931 expressed in UBL. Across Europe, Peppol is the network most trading partners will expect, although some countries use national platforms or a mix.

03How Peppol moves an invoice

Peppol combines a network that spans many countries with common specifications for business documents; OpenPeppol, a non-profit association based in Brussels, governs both. It uses a four-corner model. Your ERP (corner one) passes the invoice to your Peppol access point (corner two); that access point delivers it to the buyer’s access point (corner three), which hands it to the buyer’s system (corner four). Before sending, your access point looks the buyer up in the network’s address book, the Service Metadata Locator, which refers it to a Service Metadata Publisher showing whether the buyer is registered and what it can receive.

The result is what makes Peppol attractive: one contract with one access point provider gives you every participant on the network, whatever provider they chose. That includes Maltese Government buyers, which are connected through the provider the Ministry for Finance contracted. Many ERP and accounting packages come with an access point service, and specialist providers handle larger volumes and further document types such as orders and credit notes.

• Registration: your company appears on the network with its identifier and the document types it accepts. A missing or incorrect registration is one of the commonest reasons an invoice never arrives.
• Validation: access points test each invoice against the Peppol BIS Billing 3.0 rules, and one that fails is refused before the buyer sees it.
• Delivery status: the network confirms that the file was delivered. Business responses such as accepted, disputed or paid travel as separate messages, and only where both sides support them.

04Who has to do what, and what comes next

In Malta the duty today sits with the buyer: contracting authorities must be able to receive and process EN 16931 e-invoices on contracts above the EU thresholds. A supplier may keep sending other invoices unless the tender or contract says otherwise. Contracts and tender conditions under the Public Procurement Regulations (S.L. 601.03) are where that requirement appears, so a supplier that bids regularly on ePPS gains from being Peppol-ready before a tender demands it.

What comes next for business-to-business invoicing is set at EU level. A set-up that already sends every invoice it can over Peppol, with clean master data, is the strongest starting position for whatever Malta decides when it applies the EU rules.

05The EU framework behind the Maltese rules

Two EU texts shape every national set-up. Directive 2014/55/EU (opens external site) obliges contracting authorities to accept e-invoices that follow EN 16931, which explains why invoicing to government went electronic first in most Member States, Malta among them. The VAT in the Digital Age package (ViDA), with Council Directive (EU) 2025/516 (opens external site), was adopted on 11 March 2025 and has been in force since 14 April 2025. Member States may now introduce domestic e-invoicing without first seeking an EU derogation. On 1 July 2030 e-invoicing and digital reporting become compulsory for B2B supplies between Member States, and by 1 January 2035 national real-time reporting systems must match the EU model.

Until then, each country sets its own pace and architecture: Peppol in some, a national clearance platform in others, a mix elsewhere. A Maltese group that invoices customers in several countries needs one integration design with several outlets.

06Linking your ERP: where projects run smoothly or get stuck

Getting one invoice through Peppol can be an afternoon’s work. Sending all your invoices that way with no manual handling needs a design. The real effort lies in master data, validation, incoming invoices and archiving, not in the network itself.

• Start with master data. Each customer needs a correct identifier, VAT number and address, and each item a unit of measure and VAT category that translate into the codes the standard expects. Confirm a buyer’s registration on the network before the first invoice and keep confirming it, because organisations switch providers.
• Validate before sending. Apply the business rules the access point uses inside your own process, so a rejected invoice is caught and fixed in the ERP rather than discovered weeks later by a ministry or customer that never received it.
• Think through incoming invoices. Structured invoices can be matched automatically against the supplier, the purchase order and the goods receipt, and sent for approval only when something differs. That is where most of the saving lies. Invoices that still come on paper or as PDF, from smaller suppliers or from abroad, can enter the same flow through document capture.
• Keep the original file. The structured file sent or received is the invoice. Store it unchanged, with its delivery evidence, for the statutory retention period, and make sure it can be found and read during an audit.
• Watch the flow. Failed deliveries, rejections and invoices awaiting approval belong on a dashboard with a named owner, not in a shared mailbox.

In Odoo, Peppol sending and receiving is part of the Belgian localisation; for a Maltese family business invoicing Government, check the Peppol support in the version and localisation you run, after which the work is mostly configuration, master data and approval flows. In SAP, for instance at a manufacturer’s Maltese plant within a European group, the usual choice lies between SAP’s own compliance tooling for electronic documents and a link to an external access point; both need the same care over master data and error handling. Where several ERPs, a webshop and a group system all issue invoices, a shared integration layer keeps formats, validation and monitoring in one place rather than in each system.

07A plan you can work through

1. 01Map every invoicing flow. Which systems issue and receive invoices and credit notes, for which countries and through which channels, webshops, subscription billing and intercompany flows included.
2. 02Pick the access point model. The one in your ERP, a specialist provider, or a shared integration layer for several systems. Decide on volumes, document types other than invoices and the countries you need.
3. 03Clean the master data. Identifiers, VAT numbers, units and VAT categories for customers, suppliers and items.
4. 04Test with real trading partners. Exchange invoices with your largest customers and suppliers, and with a Government buyer where you hold a public contract, before switching over.
5. 05Automate incoming invoices. Matching, approval and posting, with exceptions sent to people.
6. 06Archive and monitor. Keep the structured originals and delivery evidence, and give every failed message an owner.
7. 07Prepare for reporting. Shape the data flows now so that invoice data can also go to a tax administration when digital reporting arrives under ViDA, in Malta and in the other countries where you trade.

08What to follow

• Guidance from the Ministry for Finance and the Department of Contracts on e-invoicing to Government, and the e-invoicing conditions in calls for tenders on ePPS.
• How Malta and other Member States implement ViDA, and which of them extend the 2030 obligation to domestic transactions.
• The roll-out in France and Spain, the end of the German transition periods in 2027 and 2028, and Belgian e-reporting planned for 2028.
• New releases of Peppol BIS Billing 3.0 and of the validation rules your access point applies.

E-invoicing rules are changing in nearly every country where our clients trade. Put a date on every internal note about them, and check the official sources before each design decision.