Andorra Public-Sector E-Invoicing: 2027 Supplier Guide

Andorra public sector e-invoicing is already a live supplier workflow, but the exact rule depends on which public body you invoice. The Portal de factures electroniques del sector public and the Registre de factures electroniques del sector public opened on October 1, 2024. Invoices to the general administration became mandatory through that framework on January 1, 2025, while communes and other public entities were later extended to January 1, 2027. Suppliers access the process through the government's electronic channels with an electronic certificate, and some entities still rely on electronically signed PDF invoices until structured e-invoicing is fully in place for them.

That phased answer matters because many English summaries flatten the whole regime into one national deadline. In practice, the useful question is narrower: which Andorran public entity are you billing, and what submission path has that entity activated today under the Govern d'Andorra rollout? Once you know that, the workflow becomes much clearer.

For most suppliers, the operating sequence is:

• confirm whether the customer is part of the general administration or another public body still on the extended timeline
• make sure you can access the public-administration workflow with a valid certificate
• follow the active submission path for that entity, which may still involve an electronically signed PDF during the transition
• monitor the invoice inside the official process instead of treating an email attachment as proof of receipt

The rest of this guide turns those steps into a practical English reference for scope, dates, portal access, submission format, and invoice-status tracking.

Which Public Bodies Are Already in Scope

The main compliance mistake is assuming that every Andorran public body moved at the same time. They did not. The rollout has been phased by entity type, which is why suppliers need to identify the customer correctly before deciding how to send an invoice.

The July 24, 2024 government announcement paired the October 1, 2024 portal launch with a hard change for the general administration from January 1, 2025. If you invoice a ministry or another body already operating inside that central public-administration framework, you should assume the electronic route is the live path, not a future option.

The same official rollout set a later path for dependent entities, communes, and the rest of the public sector. Those bodies were originally pointed toward January 1, 2026, with a possible one-year extension. The December 15, 2025 update then confirmed that the extension had been used, moving those entities to January 1, 2027.

For suppliers, the practical distinction is straightforward:

• General administration: the obligation is already active from January 1, 2025.
• Communes and other public entities on the extended path: prepare for the January 1, 2027 deadline, while checking whether the specific entity has already implemented parts of the workflow earlier.

This is why Andorra electronic invoicing for the public administration is not just a date question. It is also a routing question. A public authority may already be required to receive invoices through the official workflow, which means the supplier must use that route to bill successfully. Sending a normal PDF by email may create the appearance of delivery while still leaving the invoice outside the valid public procurement e-invoicing process.

---

How Suppliers Get Access to the Andorran Invoice Portal

Before the first submission, focus on access. Andorra's public invoice portal is reached through the government's electronic channels, not through informal exchange with the contracting body. In practice, suppliers should expect to work through the Seu electronica and e-tramits.ad environment, then move into the relevant invoicing and procurement tools from there.

The key prerequisite is a qualified electronic certificate that the Andorran public workflow accepts for identification, signing, and follow-up. The brief's official-source notes tie this to OSCEPA-qualified access, so certificate readiness is not a side issue. Without the right credential, a supplier may be blocked from submission, status checks, or both.

If your organization does not already have digital-signature access, a sensible onboarding sequence is:

1. Obtain the certificate first. Do this before invoice day rather than after a contract is awarded.
2. Test access to the electronic channels. Confirm that the certificate works in the government's portal environment and not just on internal systems.
3. Check the procurement setup. If the contract sits inside the public procurement platform, make sure the supplier record and any related permissions are already in place.
4. Confirm whether registration is needed upstream. Some suppliers will also need their contracting status and supplier details aligned with the Registre de licitadors i d'empreses classificades or related procurement records.

That sequence matters because an Andorra electronic certificate invoice submission problem often starts well before the invoice itself. A team may have the right billing data but still fail on access, identity, or registration. Treat the Andorra electronic invoicing portal as part of a larger administrative workflow: certificate, electronic entry point, procurement record, then invoice submission.

When a Structured E-Invoice Is Required and When a Signed PDF Still Applies

After access is in place, the next risk is using the wrong format. Andorra's public-sector rollout uses a transition model, so suppliers need to separate two different ideas: a structured electronic invoice and an electronically signed PDF. They are not interchangeable.

A structured electronic invoice is the end-state workflow. It is built for system handling, validation, and public-sector processing inside the official environment. That is the direction of travel for the Andorra public-administration invoicing framework.

The transitional PDF path exists for entities that have not yet completed full structured e-invoicing implementation. When that path applies, the requirement is not "send any PDF you have." The PDF still needs to be electronically signed and submitted through the official route the entity accepts. In other words, the transitional option still sits inside a controlled public workflow.

For suppliers, the safest way to think about format choice is:

• if the public body has activated structured submission for your invoice path, use the structured route
• if the entity is still operating under the transitional model described in the official materials, follow the electronically signed PDF path exactly as instructed
• do not assume that one entity's process applies to all other Andorran public bodies

Format rules also sit on top of the normal invoice-content rules rather than replacing them. Even if the routing method is correct, the invoice still needs the right commercial and tax information. That is why it helps to review the underlying Andorra IGI invoice field rules alongside the public-sector submission workflow.

---

Submission and Status Tracking Inside the Public Workflow

Once access and format are settled, the working discipline is not just "upload and wait." Suppliers should treat Andorra supplier invoice tracking as part of the compliance process, because submission, receipt, validation, and follow-up are distinct steps.

A useful operating routine looks like this:

1. Choose the correct entity path. Confirm the customer body and its current implementation stage before starting the submission.
2. Match the format to the entity. Use the structured route or the signed-PDF route that applies to that body.
3. Keep identity and contract details aligned. Certificate credentials, supplier details, and procurement references should all match the contracting record.
4. Check the status after submission. Use the official workflow to confirm the invoice was received and is progressing, rather than assuming that a successful upload means final acceptance.

Most avoidable delays come from control failures rather than from the invoice amount itself. Common examples include routing the invoice to the wrong entity, using a certificate that does not match the authorized submitting party, omitting procurement references the contracting body expects, or sending the wrong format for the customer's current stage. The same control logic behind government invoice acceptance rules and common rejection points applies here, even though the Andorran process uses its own public systems and terminology.

Status visibility is one reason governments keep pushing formal e-invoicing workflows. According to the European Commission's estimate of e-invoicing savings, EU businesses saved EUR 920 million between 2015 and 2017 from eInvoicing use alone. In Andorra, that broader efficiency goal only helps suppliers if their own process is disciplined enough to catch routing, signing, and status issues before they turn into payment delays.

---

A Practical Checklist Before You Bill an Andorran Public Entity

Use this checklist before the first invoice and whenever a new public-sector customer is added:

Before submission

• identify whether the customer is part of the general administration or another public entity still working toward January 1, 2027
• confirm the active submission format for that entity, structured e-invoice or electronically signed PDF
• make sure the submitting user has the required certificate and portal access
• verify any procurement-platform or supplier-registration prerequisites tied to the contract

On the invoice day

• send the invoice through the official public workflow, not as a standalone email attachment
• use the format and signature method that match the entity's current implementation stage
• check that invoice details, contract references, and supplier identity line up with the public record

After submission

• confirm that the invoice appears in the workflow and is not stuck at receipt stage
• monitor status changes and respond quickly if the entity requests correction or resubmission
• document the exact route used so the next invoice follows the same path

If you work across borders, it can help to compare Andorra with another public-sector e-invoicing model built around a supplier portal. The screens and terminology differ, but the recurring operational controls are familiar: identify the right public body, complete certificate-backed access, use the correct format, and track status until acceptance.

For broader cross-border reference material, our invoice processing workflow guides can help you map portal, certificate, and document-control requirements country by country.