PEPPOL in Portugal: What It Is and Why Accountants Should Care

The first time a client forwards you a PEPPOL delivery confirmation, you'll probably read it twice. It looks like an invoice. Then again, it also looks like a system receipt. There's a .xml attached, an IBLND identifier somewhere, and a subject line that mentions Peppol BIS Billing 3.0. Your client asks: "Is this a fatura? Do I still need the PDF?"

That question is going to come up more often. PEPPOL isn't new — Portugal plugged into it years ago through ESPAP — but the set of businesses that touch it is slowly widening. If you run the books for a company that sells to public-sector entities, or one that has EU suppliers, you're already on the edge of this.

This guide walks through what PEPPOL actually is, where it already applies in Portugal today, and the specific things that change in your processing flow when a client moves onto it — all of which feeds into the SAF-T obligations covered in our SAF-T Portugal guide.

What PEPPOL Actually Is

PEPPOL (Pan-European Public Procurement On-Line) is a delivery network for business documents. Think of it less as an invoicing format and more as the postal system for structured invoices and related documents across the EU.

Three pieces matter:

• The network. A set of certified Access Points that exchange documents between senders and receivers. A business connects once, to one Access Point, and can then send or receive from anyone else on the network.
• The format. PEPPOL specifies a standardized XML structure — currently Peppol BIS Billing 3.0 — based on the EU norm EN 16931. Every invoice that travels the network uses this structure.
• The identifiers. Each participant has a Peppol ID. In Portugal, this is typically the NIF with a scheme identifier (9946: for Portugal).

What PEPPOL is not: it isn't a replacement for AT. It isn't a replacement for SAF-T. It isn't a competitor to the Portal das Finanças. A PEPPOL invoice still needs to end up in your client's accounting, still needs to be reported to AT through the normal channels, and still shows up in the monthly SAF-T.

It's a pipe, not a regulator.

Where PEPPOL Already Applies in Portugal

This is the part most articles get wrong. The honest status today:

Public procurement (B2G): Since the transposition of EU Directive 2014/55/EU and the ESPAP rules, Portuguese public entities must be able to receive structured electronic invoices in line with EN 16931. In practice, suppliers to the public sector increasingly issue via PEPPOL or via the platforms operated under ESPAP's framework (FE-AP and related channels). If your client invoices ministries, municipalities, hospitals, or other public bodies, this is already live for them — the deadlines have been phased in over the last several years and apply across company sizes today.

Cross-border EU B2B: Large multinationals increasingly send and receive PEPPOL invoices across borders because their group policies mandate it. A Portuguese subsidiary of a Belgian or Dutch group may already be on the network.

Domestic B2B: There is no general mandate today requiring private Portuguese companies to use PEPPOL between each other. Some do, voluntarily, because they already connected for public-procurement reasons. The EU's "VAT in the Digital Age" (ViDA) package points toward broader structured e-invoicing in the coming years, but as of today domestic B2B PEPPOL use in Portugal is optional, not required. For a full breakdown of what mandatory B2B e-invoicing in Portugal will actually require and when, see the dedicated 2026 preparation guide.

So when a client asks "do I have to do PEPPOL?", the answer depends entirely on who they sell to and where.

What Changes in Your Monthly Processing

When a client starts receiving PEPPOL invoices, a few things shift in the workflow. None are dramatic individually. Together they change how you handle that client's close.

1. The invoice arrives as structured data, not a PDF

A PEPPOL invoice is an XML document that carries every field you normally re-key: supplier NIF, invoice number, line items, VAT rates, totals, payment terms. The supplier also typically sends a human-readable PDF rendering, but the XML is the legal document, not the PDF.

This is the part that matters for you: the data entry step largely disappears. If your tooling can read Peppol BIS 3.0, you're not OCR-ing a PDF and double-checking fields — you're ingesting the already-structured XML.

2. Duplicates behave differently

In a paper or PDF workflow, duplicates happen when the same invoice arrives through two channels (email + supplier portal, say). In PEPPOL, each document has a unique network-level ID. If you also keep receiving PDFs by email from the same supplier, you need a deduplication rule: the PEPPOL XML is canonical; the PDF is a copy.

Without that rule, you'll book things twice. It's a common early mistake.

3. The archive question changes

Portuguese archiving rules require invoices to be stored for 10 years in a format that preserves integrity and readability. For PEPPOL invoices, that means archiving the XML plus the visual representation — not just the PDF. The XML is the source of truth if AT ever asks.

If your current archive flow drops the XML and keeps only the PDF, you're discarding the legal document and keeping a copy.

4. e-Fatura and SAF-T still apply

A PEPPOL invoice doesn't exempt your client from the normal reporting obligations. The issuing supplier still has to communicate the invoice to AT (either via their certified billing software or through e-Fatura), and the receiving client's accounting still has to book it, reconcile it against e-Fatura data, and include it in the monthly SAF-T.

The content doesn't change. The delivery channel does.

What AT Actually Checks

In a PEPPOL context, the scrutiny points are largely the same as for any other invoice — but with a few wrinkles.

• NIFs must still validate. The XML carries the supplier and customer NIFs in structured fields. Get them wrong and you'll hit the same cross-reference flags as with any other invoice.
• ATCUD and QR code fields. If the PEPPOL invoice comes from a Portuguese supplier, the XML should still carry ATCUD and the data that would normally populate the QR code, because the supplier's certified software is still obliged to generate them. Missing ATCUD on a Portuguese-issued invoice is a red flag regardless of the delivery channel.
• Foreign suppliers. A PEPPOL invoice from, say, a German supplier won't carry ATCUD — ATCUD is a Portuguese construct. That's expected and fine. But those are typically reverse-charge transactions, and the usual reverse-charge rules still apply.

None of this is new compliance territory. It's the same checks, adapted to a new format.

A Practical Checklist When a Client Goes Live on PEPPOL

If a client tells you they're about to start sending or receiving invoices via PEPPOL, work through this list with them before the first cycle closes:

1. Find out who their Access Point is. It's usually their billing software vendor or a specialized provider. Get the Peppol ID (the NIF with the 9946: scheme prefix for Portugal).
2. Confirm how invoices will reach you. Will you get the raw XML? A rendered PDF? Both? In what channel — email, shared drive, direct integration? Decide before volume starts.
3. Set the deduplication rule. Write it down: "The XML is the primary record. Any PDF received for the same invoice is a copy." Make sure your software or process follows it.
4. Update the archive. Store the XML alongside (or instead of) the PDF. For 10 years. In a place AT can reach if asked.
5. Check e-Fatura reconciliation. Verify that invoices received via PEPPOL still show up on e-Fatura as expected (because the supplier still reports them). If they don't, you have a communication problem, not a PEPPOL problem.
6. Talk about volume. If this client starts receiving dozens or hundreds of PEPPOL invoices monthly, your manual-processing habits from the PDF era will break. Plan the automation step before the volume does.

Where to Go From Here

PEPPOL isn't a revolution for Portuguese accountants. It's a quieter shift — part of the slow move from PDFs-as-invoices toward structured data as the default. The businesses that connect to it for public-procurement reasons today are the leading edge; ViDA and future EU rules will bring more along over time.

The practical thing to do is get familiar with it on the two or three clients who already touch it, so when the fourth and fifth arrive, the workflow is already decided. That's easier than rebuilding the process under time pressure.

If you handle multiple clients and some are already on PEPPOL while others still run PDF-and-email, see how Faturiza's multi-client dashboard helps accountants keep different workflows straight. The same approach that already handles mixed SAF-T realities across a client portfolio extends naturally to mixed PEPPOL-and-PDF realities — because, at the end of the month, the SAF-T and the books still have to balance either way.

Related reading:

• SAF-T in Portugal: The Accountant's Survival Guide
• ATCUD and QR Codes on Invoices: What Changes for Accountants' Processing
• Reverse-Charge VAT on EU Supplier Invoices

Part of our SAF-T & Compliance guide series.