Preparing a supplier for Portuguese public e-invoicing

A supplier preparing to invoice a Portuguese public customer needs to decide how its accounting documents will reach that customer's receiving system. FE-AP is a practical route where the receiving entity participates in the service. The preparation involves the supplier's identity, its chosen transmission channel and the references the customer needs to match each invoice to the contract. Those decisions should be settled while the contract is being mobilised, before the first payment depends on them.

The timing deserves attention in September 2026. Current eSPap guidance gives 1 January 2027 as the electronic-invoicing start date for SMEs and microenterprises under the relevant public-contract regime. Article 260(2) of the enacted 2026 budget law extends the associated transitional provision through 31 December 2026. Use the national service guidance and Law 73-A/2025 when planning the transition; an older country summary can carry a superseded date.

Establish the receiving entity and the supplier role

An award from a public organisation establishes the commercial relationship. It does not give the supplier all the information needed to configure document exchange. Ask the customer which receiving entity will handle the invoices, whether it uses FE-AP for that purpose and what contract, order or commitment references it expects. The answer should be associated with the actual contract, particularly where a supplier serves several organisations with similar names.

The public FE-AP adherence form separates an entity wishing to receive invoices from a supplier wishing to issue them to a public entity. It asks for identification and representation evidence and incorporates an EDI agreement for document exchange. These are onboarding steps for the invoicing relationship, rather than an application to qualify for future public contracts.

This distinction matters when commercial research began with a contract record. A team may have used Portugal's BASE data to identify a buying account, then successfully competed for related work. The invoice setup needs its own handover from that account history. The legal supplier name, the awarded contract and the receiving organisation should agree across the sales, delivery and finance records.

Choose a channel that fits the document workload

eSPap describes the Microportal as a simplified option for small public-sector suppliers issuing fewer than 250 documents a year, when their customers receive through FE-AP. Its guidance also allows suppliers to use a technology partner where their accounting system cannot produce the required electronic format. The B2AP portal supports monitoring delivery and document status. These choices make the supplier's existing workload and systems relevant to the onboarding decision. See the supplier and Microportal sections of the official FAQ.

A company with a few recurring invoices can evaluate a manual process differently from a business issuing many documents with complex line references. The decision should include preparation time, checking time and the cost of correcting a document. The number of customers is less informative than the volume and variety of invoices, credit notes and other documents the workflow must handle.

The channel should also preserve the connection to the company's accounting record. A manual entry that produces the right total but loses the contract reference can create a customer-side matching problem. An integrated process that repeatedly transmits an incorrect reference simply produces that problem faster. Agree the required fields before deciding how much of the process to automate.

Map commercial references before the first invoice

The eSPap supplier portal documented a Microportal improvement in November 2022 that added a commitment-line identifier, among other changes. That dated release is useful evidence that a buyer's reference can operate at line level, rather than only at the top of an invoice. The official improvement notice supports the distinction; the current customer instruction determines which reference belongs on an actual document.

For implementation, take an example of the work that will be billed and map it to the buyer's expected information. A recurring service and a separately authorised assignment may need different references. Write down where each value originates and who is responsible for providing it. Accounts staff should not have to invent a reference from a contract title when the customer expects an identifier issued through its own purchasing process.

Keep the invoice lines understandable to the person checking performance. A description such as monthly support should identify the period and the relevant service sufficiently for the customer to connect the charge to the agreed work. A separate expense or additional task should remain distinguishable where the contract requires separate approval. This is commercial clarity that supports electronic matching, without turning the invoice description into a copy of the entire agreement.

A worked transition for a small supplier

Consider a hypothetical environmental-monitoring consultancy with twelve monthly service invoices and twelve occasional project invoices each year. It is comparing a manual submission process with an integration into its accounting system. At twenty-four documents, even a careful manual workflow may require relatively little annual time. The company should nevertheless include checking and follow-up, rather than measuring only the time needed to press a submission button.

Suppose preparing, checking and recording each document takes fifteen minutes. Twenty-four documents represent six hours annually. At an internal cost of €45 an hour, that is €270 of staff time before exceptional corrections. If the company expects two hundred documents, the same assumptions produce fifty hours and €2,250. These are planning calculations, not service prices; they show why the appropriate channel can change as the public-sector business grows.

The consultancy should then consider complexity. A twenty-line project invoice tied to several customer references may justify more preparation than a single recurring charge. If the integration needs custom work, compare that setup cost with the actual document workload and the benefits of reusing the data. A staged approach can be sensible: establish correct references on the first contract, then automate a process whose requirements are understood.

Keep the document, its transmission and payment connected

The adherence agreement distinguishes electronic receipt acknowledgements from status messages. In commercial administration, that supports a useful separation between the document being transmitted and the customer's subsequent handling of it. Preserve the invoice identifier, submission evidence and relevant response together, so the team can follow a payment enquiry without reconstructing the process from individual inboxes. The public adherence terms describe that message relationship.

If an invoice needs correction, agree how the customer expects the correction to be represented and preserve its relationship to the earlier document. A second transmission should not leave either party uncertain about which amount remains due. Reconciliation should connect the accounting entry, the document sent and the customer's response.

Portugal's budget law also treats PDF invoices as electronic invoices for fiscal purposes through the end of 2026. That transitional treatment does not identify a particular customer's receiving address or replace its contract references. Plan the operational route separately from the fiscal date. Suppliers already working across borders can compare the same organisational issue in our guide to Spanish DIR3 invoice destinations.

The useful readiness decision is whether the supplier can produce one correct invoice for the actual contract and trace it through the receiving process. Once that works, the company can repeat or automate the workflow with confidence grounded in its own transaction, rather than in a generic claim that its accounting software supports electronic invoicing.

Assign that first-cycle review to a named finance colleague and retain the confirmed customer instructions with the contract record for subsequent billing periods.