Compliance for Portugal

Portugal mandates e-invoicing for B2G transactions, and e-reporting for all transaction types. Invoice data must be produced by billing software certified by Autoridade TributƔria e Aduaneira (AT) and reported using the Portuguese version of Standard Audit File for Tax Purposes (SAF-T (PT)) billing process.

šŸ“˜

Note
This page covers B2G e-invoicing exchange only. SAF‑T (PT) data is generated by your AT‑certified billing software and included in the invoice data sent to ecosio. For more information about SAF-T (PT), see Decreto-Lei n.Āŗ 28/2019 and Portaria n.Āŗ 302/2016.

E-invoicing requirements

In Portugal, all invoices must be generated and signed using AT-certified billing software, and the resulting invoice data must be reported to the Tax Authority via the SAF-T (PT) billing process. This applies regardless of whether invoices are exchanged as structured e-invoices or in other formats.

For B2G transactions, invoices must also be exchanged as structured e-invoices in a CIUS-PT compliant format through designated government channels. Exchange with public administrations is typically handled via the Fatura Eletrónica na Administração PĆŗblica (FE-AP) platform, managed by Entidade de ServiƧos Partilhados da Administração PĆŗblica (eSPap), Portugal’s Public Administration Shared Services Entity. Some public entities may exchange invoices through alternative service providers in specific cases.

Portugal compliance summary

Learn more about compliance transactions terms and concepts.

AspectDescriptionRequirement
B2BInvoices exchanged between businesses.Mandatory reporting via SAF-T Billing process
B2CInvoices issued by businesses to consumers.Mandatory reporting via SAF-T Billing process
B2GInvoices issued by businesses to public administrations for public procurement.Mandatory exchange and reporting via SAF-T Billing process
Electronic signatureSignature or seal rules for authenticity and integrity of e‑invoices.

Qualified electronic signature (QES) mandatory on PDF e-invoices from 1 January 2027.

A hash value must be generated by certified billing software for every invoice, regardless of format.

Legal archivingMinimum retention period for e‑invoices.10 years
ModelThe e-invoicing flow model used by the country.Clearance via the SAF-T billing process, previous to e-invoice exchange
PlatformThe government-managed platform for e-invoicing.FE-AP (eSPap) central platform, though not all public administrations are obligated to use this.
Supported formatThe e-invoicing format legally required by the country.UBL 2.1 or CII per the CIUS-PT
Automatic updatesWhether invoice status updates synchronise automatically in Monitor.Yes

Invoice format

B2G invoices must align with the EN 16931 standard and follow the country-specific CIUS known as CIUS-PT. For technical specifications, see the CIUS-PT Technical Standard.

Invoice types

The following invoice type codes are used in CIUS-PT for B2G invoices.

DocumentCodeDescription
Accepted reinsuranceRADocument used for reinsurance operations.
Allocation to co-insurersCSDocument type specific to insurance co-insurers.
Allocation to lead co-insurerLDUsed when the lead insurer issues to co-insurers.
Credit note381Used to correct amounts or settle a balance between a supplier and a buyer.
Credit noteNCEquivalent to code 381.
Debit note383A document issued by a supplier to apply additional charges or increase the total value of a previously issued e-invoice.
Debit noteNDEquivalent to code 383.
Invoice380Standard sales invoice.
Invoice issued under Article 36 of the VAT CodeFTRegular VAT invoice.
Invoice receiptFRInvoice that simultaneously serves as a receipt.
Premium or premium receiptRPUsed in insurance for premium payments.
Prepayment or advance invoice386Issued when payment is received before the supply of goods or services.
Reversal or refund receiptREUsed in insurance for returned premiums.
Self-billed invoice389A document that a buyer must create and report to the tax authorities to account for an invoice received from a foreign supplier, which is an import. This is a statutory tax reporting requirement and is separate from the self-billing process used in other industries..
Simplified invoiceFSUsed for low-value transactions.

Automated e‑invoicing flow

ecosio enables you to automate the transmission of compliant invoices for B2G invoices in Portugal.

B2G invoice flow

The following steps illustrate the process for B2G invoices in Portugal.

Flow of an electronic document from a supplier to a public administration in Portugal.
  1. You send the invoice data from your ERP or business software to ecosio in a structured format, such as VRBL. The data includes SAF-T information previously generated via your certified billing software.
  2. Once received, ecosio converts the structured format into the UBL 2.1 format and validates that all mandatory fields are present in accordance with technical requirements. ecosio sends the invoice in one of two ways.
    1. If the public administration is connected to eSPap, the invoice is sent to the FE-AP portal (FE-AP).
    2. If the public administration is identified as not connected to eSPap, the invoice is sent to their service provider.
  3. The invoice reaches the public administration in one of two ways, depending on how it was sent.
    1. If the invoice was sent to the FE-AP portal, eSPap routes the invoice to the public administration identified in the invoice.
    2. If the invoice was sent to a service provider, they send the invoice to the public administration identified in the invoice as the final recipient.
  4. Life cycle statuses can be sent back to ecosio via eSPap and service providers, and made available in the Monitor and through integrations.

Legal and technical resources

The following official documents define the legal and technical framework for e-invoicing and reporting in Portugal.


Did this page help you?