Uruguay Public-Sector E-Invoicing: SIRFE Supplier Guide

In Uruguay public sector e-invoicing, the main change for suppliers is that billing a public body operating as a SIRFE receptor follows a public-sector receiving workflow, not a send-the-PDF-and-wait workflow. You still issue a CFE, meaning a Comprobante Fiscal Electronico, within Uruguay's wider electronic invoicing system, but the operational handoff changes: before issuing, you should confirm the correct Unidad Ejecutora and recipient RUT, include the purchase-order identifier when the procurement flow requires it, and treat SIRFE, not email delivery of a PDF or printed copy, as the real submission path. The same logic matters for related resguardos, because they also move through that government receiving chain.

For a supplier, SIRFE is best understood as the layer that public entities use to receive and process electronic invoices inside the state workflow. That is why a sale to a ministry, agency, or other public body can feel different from billing a private customer even when the tax document itself is still a CFE. The question is not only whether the invoice is valid in tax terms, but whether it reaches the buyer's public-sector intake correctly so the organization can match it to its internal purchasing and payment controls.

This Uruguay SIRFE supplier guide stays focused on that supplier-side job. It does not attempt to restate every rule of Uruguay e-invoicing or summarize decree history. Instead, it concentrates on the practical sequence: confirm whether your customer falls into the SIRFE receiving workflow, prepare the invoice with the right recipient and order data, route it correctly, and understand what acknowledgment, acceptance, or resguardo-related response you should expect afterward.

If you only remember one point at the outset, remember this: a valid CFE is only the start. The invoice still needs the correct public-body data and the right SIRFE receiving path so the buyer can process it inside the state workflow described in supplier guidance from the Ministerio de Economia y Finanzas.

Which Public Bodies Fall Into the SIRFE Receiving Workflow

For suppliers, the key public-sector rule is Decreto 31/023. In practical terms, the workflow discussed here is aimed at invoices issued to Central Administration entities and to Article 220 bodies that receive supplier invoices through SIRFE, the government receiving environment tied to Contaduria General de la Nacion. That is the part of the Uruguay public sector where the receiving process changes most for the vendor.

What matters is that SIRFE is not Uruguay's entire e-invoicing system. Uruguay's national CFE framework still governs the core electronic tax document, validation, and issuer obligations. SIRFE adds a public-sector receiving layer on top of that broader regime, which is why Uruguay public sector e-invoicing is not the same thing as general private-sector billing or even every government billing scenario.

That distinction is where many suppliers get tripped up. A ministry, agency, or other public body may be public, but you still need to confirm whether the specific entity and receiving unit you are dealing with is actually configured as a SIRFE receptor. Do not assume that every public customer follows the same path, or that implementation timing, internal routing, and supplier instructions are identical across the state. In practice, Uruguay SIRFE invoice requirements often depend on the exact body, business unit, and purchasing flow behind the invoice.

The fragmentation is real. The rules are spread across decree text, MEF and CGN notices, and body-specific supplier instructions, so vendors often end up piecing together the process from several sources just to answer a basic question about a Uruguay public procurement e-invoice. Other Latin American markets layer their own distinct requirements on top of a national e-invoicing regime in the same way -- Panama's B2G e-invoicing rules for suppliers are a useful comparison because the prior-authorization and classification steps differ completely from SIRFE, even though both countries separate government receiving from general tax compliance. That is why a practical, operational synthesis matters more than a decree summary alone.

If you are unsure whether a specific body is already receiving through SIRFE, start with that entity's supplier instructions or public notice, then confirm the receiving Unidad Ejecutora with the procurement contact handling the transaction. If the status is still unclear, use the guidance channel linked from the MEF or CGN SIRFE material before issuing the CFE.

If you need a refresher on Uruguay's broader CFE rules and document types, start there first. This guide is intentionally narrower: it focuses only on what changes when your customer is a public body already operating within the SIRFE receiving workflow, not on the full national CFE framework and not on imported EU assumptions such as a Peppol-style public invoicing model.

---

What To Verify Before You Issue the CFE

Before you issue a CFE to a Uruguayan public body, treat setup as a control point, not a last-minute admin check. In Uruguay MEF guidance for state suppliers using SIRFE, the Ministry of Economy and Finance says suppliers should verify the RUT of the correct Unidad Ejecutora, include the unique purchase-order identifier when applicable, and avoid treating PDF or printed delivery as the real invoice submission step. That is the practical pre-issue standard.

1. Identify the receiving Unidad Ejecutora first. Do not invoice only to the ministry or agency name if the actual receiver is a specific executing unit. In the SIRFE workflow, the correct Unidad Ejecutora is the operational recipient, so getting that wrong can misroute the document before anyone checks the commercial details.

2. Validate the recipient RUT before creating the invoice. The Uruguay SIRFE recipient RUT is not a minor field. It is a routing and control datum. If the RUT does not match the right Unidad Ejecutora, the invoice can be delayed, rejected, or sent into the wrong review path even when the amounts and tax treatment are correct.

3. Confirm whether a procurement reference is mandatory. If the public buyer issued a purchase order or obligation that carries the ARCE purchase-order identifier, that unique reference should already be on the invoice when you issue it. For a Uruguay purchase-order identifier invoice, the safe rule is to copy the identifier exactly as provided, rather than adding a partial reference or sending it later in a separate email.

4. Check your issuer master data before sending anything. The same MEF guidance tells suppliers to make sure their issuer details are complete in the electronic invoicing setup they use for submission. Missing or inconsistent issuer data can complicate routing and processing even when the recipient data is right.

5. Issue the CFE only after those fields align. The sequence is simple: identify the receiving unit, validate its RUT, confirm whether the procurement identifier must appear, and then issue the CFE with those details already in place.

Why A PDF Is Not the Submission Step

Use a PDF, printed copy, or emailed image only as a courtesy copy for human review. When your customer receives through SIRFE, the real submission step is the structured route that carries the CFE into the correct public-sector receiving flow with the data the entity needs to match it to its internal process.

That is why suppliers run into delays when they treat a public-sector invoice like an ordinary commercial invoice. You can send a PDF to a contact for visibility, but if the structured invoice is routed with the wrong recipient details, missing references, or incomplete public-sector identifiers, the buyer may not be able to receive, validate, or process it correctly. For a Uruguay supplier invoice to government, routing data usually matters more than sending a human-readable copy.

Think of the PDF as a representation, not the workflow itself. The operational workflow depends on the invoice landing in the right destination and carrying the identifiers the public body expects. If those data points are wrong, the invoice can stall even when the PDF looks perfect to the human eye. That is the extra layer many suppliers miss when moving from standard CFE issuance into a Uruguay government supplier invoice workflow.

The failures this section is trying to help you avoid are usually practical, not technical:

• Relying on PDF delivery alone. Emailing the invoice to an official or procurement contact does not replace the structured receiving path.
• Using the wrong recipient details. If the invoice is addressed or routed to the wrong public-sector receiver, it may not enter the correct process.
• Omitting a required procurement identifier. A readable invoice is not enough if the entity cannot link it to the purchase, order, or contracting record it expects.
• Confusing CFE issuance with public-sector receipt. Issuing a valid electronic invoice is only part of the job when the buyer also operates under a SIRFE receiving workflow.

In practice, you should treat the PDF as support material and the structured submission as the real handoff. If a ministry, agency, or other public entity tells you it receives through SIRFE, your goal is not just to generate the invoice correctly. Your goal is to make sure it reaches the right public-sector intake path with the exact routing and reference data needed to prevent rejection or manual rework.

---

How Invoices and Resguardos Move After Submission

After you issue the CFE to a public body operating as a SIRFE receptor, use a three-step follow-up sequence. First confirm that the invoice entered the receiving workflow correctly. Then check whether any related resguardo appears through a separate consultation channel. Treat payment follow-up as a later step, not as proof that the invoice or resguardo was handled correctly.

An e-resguardo is not the same as proof that the invoice was delivered, and it is not the same as a payment-status check. In Uruguay, the e-resguardo is the electronic withholding receipt tied to the transaction. In the SIRFE context, that means suppliers may need to monitor one channel for invoice reception and another for the withholding document or consultation step. For Uruguay suppliers handling e-resguardos, that distinction matters because the invoice and the withholding document do not always surface through the same follow-up path.

What you should monitor after submission is usually this:

• Did the CFE enter SIRFE correctly? That tells you the document reached the receiving workflow.
• Was an e-resguardo generated? This matters if retentions apply, but it can appear through a different consultation or delivery channel.
• Has the body completed its own review steps? Internal validation, confirmation, and payment handling happen after routing and are not guaranteed just because the CFE was accepted into the workflow.

The exact retrieval path can vary by entity instructions and the designated consultation channel. If you are told to check a portal or follow-up screen, confirm whether it shows received CFEs, e-resguardos, or later payment-related information. Those are related but not interchangeable. If the entity gives you a portal for resguardos, do not assume that same screen confirms invoice receipt. If an expected e-resguardo or response does not appear, check the channel named in the supplier instructions for that public body before assuming the invoice itself failed.

---

Supplier Checklist Before You Send the Invoice

If you are asking how to invoice a public body in Uruguay, use this final pass before you submit. For a broader view of how structured invoice processing workflows depend on clean routing and identifiers, and for a separate government invoice field and routing checklist, review those alongside the steps below.

• Confirm the customer is actually receiving through SIRFE. Do not assume every public entity follows the same receiving path just because it is part of the state.
• Match the exact receiving unit and RUT. Check the specific ministry, agency, office, or executing unit that will receive the CFE, not just the umbrella body name.
• Verify whether a purchase order, obligation, or other procurement reference is mandatory. If the buyer gave you a reference number, confirm the exact value and where it must appear before issuing.
• Review your issuer data for completeness. Make sure your own tax and invoice details are correct, because a valid CFE can still fail the public-sector receiving flow if the core data does not match the buyer's setup.
• Send the invoice through the proper SIRFE route. A PDF may be useful as a copy for internal contacts, but it is not the submission step that places the invoice into the public body's receiving workflow.
• Know where you will check the result afterward. Before sending, confirm who monitors acceptance, rejection, or the resguardo so follow-up does not stall after submission.

The most common supplier mistakes are avoidable: never confirming that the body is already receiving through SIRFE, sending to the wrong unit, using the wrong RUT, omitting a required procurement reference, or assuming that general CFE compliance automatically satisfies the narrower public-sector receiving process. A two-minute check on those points usually prevents the longest delays.