Uruguay Electronic Invoicing Requirements: CFE Guide

Uruguay electronic invoicing runs through the Comprobantes Fiscales Electronicos (CFE) regime administered by the Direccion General Impositiva (DGI), not a generic PDF-by-email workflow. For anyone mapping Uruguay electronic invoicing requirements, the short answer is straightforward: from January 1, 2025, VAT taxpayers generally had to operate as electronic issuers, subject to limited exceptions, and those issuers document sales with CFE instead of manual tax documents except in justified contingency situations. The core CFE family starts with e-Factura, e-Ticket, and their related credit and debit notes, while additional variants apply when the workflow changes, especially in remittance and export scenarios.

That matters because an emailed invoice PDF, by itself, is not the regime. In Uruguay, the compliance question is whether the transaction is documented with the correct CFE by an authorized issuer, not whether a file was sent by email. If you need a broader baseline on how structured e-invoicing differs from emailed PDFs and basic digital invoices, Uruguay is a good example of why issuer status, validation, and document families matter more than the appearance of the invoice alone.

This guide answers six practical questions: who is covered, which document set forms the minimum baseline, when specialized variants apply, how issuance and recipient handling work in practice, what changes during contingency situations, and which 2025 to early 2026 updates finance teams should review carefully.

Who Had to Become an Electronic Issuer on January 1, 2025

If your question is is electronic invoicing mandatory in Uruguay, the practical answer is yes for most VAT taxpayers from January 1, 2025. Official DGI guidance published on January 30, 2025 was already treating that date as live, including guidance stating that IVA minimo taxpayers were required to document operations through electronic invoicing from January 1, 2025. Read together with DGI's general obligation guidance and the updated legal text published through IMPO, January 1, 2025 is the main regime-wide milestone for Uruguay factura electronica requirements.

In operational terms, an electronic issuer is not just a legal label. It is a taxpayer authorized by DGI to issue CFE, Comprobantes Fiscales Electronicos, for its sales documentation, to work inside the electronic invoicing flow, and to act as a mandatory electronic receiver as well. In practice, that means your taxable sales move into the CFE regime, paper stops being the ordinary tax document for those operations, and non-electronic customers receive a printed representation of the CFE rather than a traditional paper invoice.

The exception list is real, but it is narrower than many secondary summaries suggest. DGI and IMPO materials carve out:

• taxpayers engaged exclusively in agricultural activities with annual revenue below 4 million UI
• taxpayers engaged exclusively in acts of value added in construction over immovable property
• taxpayers subject to Non-Resident Income Tax
• taxpayers exempt from DGI-administered taxes on all operations, except direct and indirect free zone users
• Monotributo, Monotributo Social Mides, and Aporte Social Unico de PPL taxpayers

There is also a timing nuance that matters for implementation planning. Once a taxpayer obtains electronic issuer status, DGI generally allows a one-month transition period in which electronic and traditional paper documentation can coexist. That does not move the broad obligation date to 2026. It only softens the operational switchover after authorization, and the deeper process detail belongs later in this guide.

The January 1, 2025 versus January 1, 2026 confusion should be handled directly. Some vendor pages and compliance summaries use inconsistent framing, often because they were updated later, collapse later operational changes into a new headline date, or restate the regime as though it "starts" in 2026. Unless your facts place you inside one of the listed exceptions or a narrower sector-specific track, treat January 1, 2025 as the main answer for Uruguay factura electronica 2025 scoping, not January 1, 2026. For a reliable Uruguay DGI e-invoicing guide, use DGI's public guidance for the practical summary and IMPO's current legal text for the binding wording. Finance teams should still verify exception status, sector-specific rules, and the current consolidated text before implementation, because this is a practical reference, not legal advice.

The Minimum CFE Document Set Every Issuer Needs

In Uruguay, the minimum required CFE set is not a single invoice type. DGI treats it as a small operational family: one branch for transactions documented as e-Factura, one branch for transactions documented as e-Ticket, the matching credit and debit notes for each branch, and, for responsible parties, e-Resguardo. If you start there, the Uruguay CFE document types become a workable map instead of a long and confusing catalog.

A quick operational map looks like this:

• e-Factura: the core CFE for operations with taxpayers identified by RUC. In plain terms, this is the document your team should expect when the counterparty is being treated as a registered taxpayer rather than as a final consumer.
• e-Ticket: the core CFE for operations with final consumers. In practice, Uruguay e-Factura and e-Ticket rules turn first on recipient status: contributor identified by RUC points you toward e-Factura, while consumer final treatment points you toward e-Ticket.
• e-Resguardo: this belongs in the minimum set because electronic issuance in Uruguay is not only about billing sales. DGI includes e-Resguardo for responsible parties so they can support tax withholdings and perceptions in electronic form. Teams often miss this because they focus only on invoices and tickets, but withholding support is part of the compliance workflow too.
• Credit notes and debit notes tied to each document family: these are not optional extras. A note of credit reduces or cancels amounts from the original e-Factura or e-Ticket, while a note of debit increases or adjusts amounts upward. The correction has to stay in the same family as the original document, which is why teams need to classify the base document correctly from the start.

That distinction matters operationally. If your finance team knows when to issue e-Factura versus e-Ticket, and knows that every one of those originals needs its own correction tools, you already control the day-to-day core of the CFE regime. Then e-Resguardo covers the tax withholding side that many implementation teams overlook until testing or month-end review exposes the gap.

If you want the shortest routing logic, think of it this way: a sale to a RUC taxpayer calls for e-Factura, a sale to a final consumer calls for e-Ticket, and withholding or perception support calls for e-Resguardo. Goods movement and export belong to specialized families covered next.

This is the right place to begin because it keeps the analysis useful. Before you sort through export documents, movement documents, or other specialized variants, you need to recognize the small base set that governs most routine issuance, corrections, and withholding evidence.

When Specialized CFE Documents and Narrower Workflows Apply

Once you have mapped the core sales documents, the rest of the CFE universe is best treated as a set of conditional branches. DGI's functional CFE definitions list more document types than the minimum invoice, ticket, and adjustment set, but those extra variants are not mandatory for every issuer on day one. You add them only when a real business process, such as moving goods, exporting, issuing on behalf of another party, or operating in a public-sector route, actually requires them.

The clearest example is e-Remito. This is the CFE used to support the movement of goods, not a substitute for the sales document that records the commercial transaction itself. If your operation ships inventory between locations, dispatches goods before billing, sends stock on consignment, or needs proof of remittance during transport, e-Remito belongs in scope. If your business mainly provides services and does not run goods-movement scenarios, you may never need it.

Exports create a separate branch rather than a small variation on domestic billing. DGI defines e-Factura Exportacion, along with its related credit and debit notes, and also e-Remito de Exportacion for export goods movement. That is the practical scoping rule: first identify the domestic minimum set, then ask whether the company has export sales or export logistics. If the answer is no, you do not need to build export CFEs into the initial compliance design.

Uruguay also has narrower workflows that matter only in specific contexts. Some businesses encounter specialized branches for sale on behalf of another party or other less common operating models. SIRFE is another example. It is the public-sector reception environment described by the Ministry of Economy and Finance, and it becomes relevant when you invoice government entities or work inside those receipt and payment chains. It is not a universal extra layer for every private issuer, but a targeted workflow that can impose additional handling requirements for the affected documents.

That distinction is useful for scoping: if SIRFE becomes relevant, you are no longer just answering the broad country-level mandate question. You are entering a narrower public-sector sub-workflow that deserves its own implementation review.

A useful way to scope this is to build a simple document map:

• Start with the minimum sales documents the business cannot avoid.
• Add e-Remito only where goods movement must be documented.
• Add export variants only if the business actually exports.
• Check SIRFE and other narrow branches only when your counterparties or process make them relevant.

That keeps initial compliance focused while still reflecting how Uruguay's CFE system works in practice: minimum sales documents first, specialized variants only when the workflow calls for them.

How CFE Issuance, Validation, and Recipient Handling Work in Practice

Uruguay's CFE process is a controlled issuance workflow. DGI's CFE FAQ explains that once the taxpayer is authorized and notified as an electronic issuer for specific CFE types, it can issue those documents and also becomes an electronic recipient. Teams working across LATAM may recognize a similar control logic in Argentina's CAE-based factura electronica workflow, but Uruguay CFE requirements still turn on Uruguay's own issuer status, transmission rules, and recipient handling.

Authorization comes before issuance. A company does not enter normal operation just by installing invoicing software. It must complete DGI's entry process, certify the relevant CFE it plans to use, and receive the communication that states the authorized document types and the effective date from which it may act as an electronic issuer.

The one-month transition is the cutover window. DGI's FAQ explains that the transition window is now one month rather than the older four-month period. In practice, that month sits between authorization and steady-state operation: paper and electronic documents may coexist, staff finalize issuance procedures, and counterparties adjust to the new handling rules. The same FAQ also states that during the first 30 days after entry into the regime, the printed representation of a CFE keeps the same legal validity, which matters when the business is still stabilizing its electronic processes.

Issue and send the document through the required channels. The Formato del sobre says the electronic issuer sends the CFE or contingency document it issues to DGI and sends the CFE addressed to the electronic recipient. Resolution No. 798/2012 also requires sending CFE to electronic recipients through an agreed channel, with email as the minimum admitted protocol.

Watch the validation responses. DGI's FAQ says the issuer does not have to wait for an online authorization before sending the CFE to the recipient, moving goods, or handing a printed representation to a non-electronic recipient. The control still happens inside the operating cycle, though, because DGI returns a first acknowledgement or rejection for the envelope or report and a second acknowledgement or rejection for each CFE within it. Finance teams need a way to monitor those responses and resolve rejections quickly.

Handle recipients according to their status. For electronic recipients, Resolution No. 798/2012 requires receipt of electronic documents from authorized suppliers and the return of the corresponding acknowledgements. That issuer-to-issuer receipt layer becomes relevant only when both parties are inside the regime, so it is a narrower sub-workflow than the broad country-level mandate question. For non-electronic recipients, Resolution No. 798/2012 and the FAQ require a printed representation when the customer is non-electronic or goods are transported, unless a defined exception applies. Issuers must also retain the original CFE and related acknowledgements for the tax recordkeeping period, and DGI provides received CFE query tools for that downstream control.

What Issuers Can Do During Outages and Other Contingency Situations

Manual fallback in Uruguay's CFE regime is an exception for justified contingency, not a parallel alternative to ordinary electronic issuance. DGI's CFE FAQ and functional guidance frame contingency as a controlled fallback for cases where the issuer genuinely cannot keep issuing CFE normally.

The practical distinction that matters is this:

• If the problem is limited to communication or transmission, that does not automatically justify paper fallback. Teams should treat it as an interruption in sending and complete the normal CFE flow once the connection or service issue is resolved.
• If the issuer cannot issue CFE at all, contingency documentation becomes relevant. In that case, the issuer uses authorized preprinted Comprobantes Fiscales de Contingencia (CFC) while the justified interruption lasts.

That means contingency documentation is not an informal workaround. It replaces a specific CFE type, follows its own authorization logic, and uses numbering separate from normal CFE numbering. Teams should not assume that any manual invoice, spreadsheet printout, or improvised receipt is acceptable just because the system is down.

After the outage ends, the key control is post-event reconciliation. In high-level terms, finance teams should be ready to record which contingency documents were used, communicate the event through the applicable DGI process, fold those documents back into the later reporting flow, and reconcile numbering, amounts, taxes, counterparties, and later corrections once normal issuance resumes. That is how you avoid audit gaps or tax-support problems created by a short-lived systems incident.

What Changed in 2025 and Early 2026, and What Finance Teams Should Review Next

If you are reviewing Uruguay electronic invoicing requirements now, the key point is that Uruguay is operating a mature CFE environment, not a pilot-stage rollout. Uruguay's tax authority says 98.4% of issued fiscal documents are already CFE, according to DGI's CFE adoption data. That scale matters because most implementation questions are now about correct workflow design and ongoing maintenance, not whether the regime is established.

The broad compliance picture became clearer on January 30, 2025, when DGI guidance spelled out that authorized electronic issuers document sales through CFE and revert to manual tax documents only in justified contingency cases.

The fresher operational issue is what happened next at the technical layer. Version 25.1 changes took effect on March 3, 2026, alongside related format and validation updates. That matters because a business can be fully inside the mandate and still drift out of sync with current production schemas, validation rules, or provider configuration if it treats the rollout date as the end of the project. In other words, the mandate date tells you whether you belong in the regime; ongoing version and validation updates tell you whether your live setup still matches it.

Regional teams should also avoid assuming that neighboring systems work the same way. Chile's DTE document and validation model, for example, has its own terminology and control structure even though it is also a structured tax-document regime.

What finance teams should review next:

• Confirm the entity's current issuer status and the exact date from which it must operate as an electronic issuer.
• Map the minimum CFE set and any specialized CFE documents the business actually needs based on customer type, transaction mix, adjustments, exports, and industry workflow.
• Confirm who owns version maintenance, validation monitoring, and production-spec updates so the legal rollout does not drift away from the live technical setup.
• Verify contingency procedures, including when fallback is allowed, who authorizes it, and how the business returns to normal issuance.
• Check the latest DGI technical documentation, schema versions, and validation notes with local advisors or implementation partners so legal compliance does not drift out of sync with current production requirements.