El Salvador E-Invoicing Requirements: Complete DTE Guide

El Salvador's Documento Tributario Electrónico (DTE) system is the country's mandatory electronic invoicing framework, established under Legislative Decree No. 487 (approved August 30, 2022). Administered by the DGII (Dirección General de Impuestos Internos), a division of the Ministerio de Hacienda, the system requires every business to generate tax documents in structured JSON format, transmit them to the Ministry of Finance's reception system for validation, and receive a Sello de Recepción (a UUID stamp) before the document carries legal validity.

The DTE framework covers 11 distinct document types, ranging from the Comprobante de Crédito Fiscal used in B2B transactions to the Factura Electrónica for consumer sales, along with specialized documents for exports, credit and debit notes, and other tax events. Each follows the same core lifecycle: generation, transmission, validation, and stamping.

One technical detail that sets El Salvador apart from every other major Latin American e-invoicing country is its choice of JSON as the canonical document format. While regional peers like Mexico (CFDI), Colombia, Peru, and Ecuador's XML-based SRI electronic invoicing system all built their systems around XML schemas, El Salvador designed its DTE infrastructure around JSON from the ground up. For development teams integrating with the system, this means lighter payloads, native compatibility with modern web APIs, and no need for XML parsing libraries or XSLT transformations.

The system did not emerge in isolation. El Salvador's tax modernization drew on lessons from Colombia, Argentina, Peru, and Mexico, and was backed by a $30 million IDB (Inter-American Development Bank) program launched in 2018 to overhaul the country's tax administration infrastructure. That investment has produced measurable results: by January 2026, the Ministry of Finance had received over 1.5 billion DTEs from more than 122,000 registered electronic emitters, according to Infobae's analysis of Ministry of Finance data on El Salvador's DTE adoption.

The rollout is still underway. Businesses have been onboarded in waves based on taxpayer size and classification, with the final mandatory compliance deadline set for May 15, 2026, when micro and small businesses must begin issuing DTEs. If your company operates in El Salvador, trades with Salvadoran suppliers, or processes DTEs as part of your accounts payable workflow, understanding El Salvador e-invoicing requirements now is essential preparation.

All 11 DTE Document Types Explained

El Salvador's DTE system defines 11 distinct document types, each serving a specific transactional purpose. Every document type carries a two-digit code that determines its validation rules, required fields, and tax treatment within the Ministerio de Hacienda's platform.

The following reference table covers all 11 El Salvador DTE document types, their codes, and when each applies.

Code	Spanish Name	English Equivalent	Purpose / Use Case
01	Factura Electronica (FE)	Electronic Invoice	B2C sales to final consumers who will not claim IVA tax credits
03	Comprobante de Credito Fiscal (CCFE)	Tax Credit Certificate	B2B transactions between NRC-registered taxpayers; enables buyer to claim IVA credits
05	Nota de Credito (NCE)	Credit Note	Downward adjustments to previously issued documents (returns, discounts, corrections)
06	Nota de Debito (NDE)	Debit Note	Upward adjustments for additional charges, interest, or price increases on prior documents
07	Nota de Remision	Remittance Note	Documents the physical movement of goods without an underlying sale (e.g., warehouse transfers)
11	Comprobante de Retencion (CRE)	Withholding Certificate	Records income tax or IVA withholdings applied by the buyer, required for the withheld party's tax filings
14	Comprobante de Liquidacion (CLE)	Settlement Certificate	Issued by purchasers of agricultural or marine products to document payments to primary producers
15	Documento Contable de Liquidacion (DCLE)	Accounting Settlement Document	Used for inventory adjustments, consignment settlements, and similar accounting-driven liquidations
43	Factura de Exportacion (FEXE)	Export Invoice	Issued for export sales, which carry a 0% IVA rate; must include customs and destination data
44	Factura de Sujeto Excluido (FSEE)	Excluded Subject Invoice	Issued by the buyer when purchasing from a non-VAT-registered party (reversed issuing relationship)
46	Comprobante de Donacion (CDE)	Donation Certificate	Documents deductible donations to qualifying organizations for income tax purposes

The Critical CCFE vs. Factura Distinction

For AP departments, the distinction between the Comprobante de Credito Fiscal (CCFE) and the Factura Electronica (FE) is the single most consequential classification decision in El Salvador's e-invoicing system.

The CCFE (code 03) is issued when the buyer holds an active NRC (Numero de Registro de Contribuyente), El Salvador's VAT registration number. This document allows the purchasing company to claim the IVA charged on the transaction as a tax credit against its own IVA liability. To function correctly, the CCFE must contain complete fiscal data for both parties: the NIT (Numero de Identificacion Tributaria), a 14-digit tax identification number, the NRC, and the registered business name of both seller and buyer.

The Factura Electronica (code 01), by contrast, is issued to final consumers. It does not carry the buyer's NRC or full fiscal details, and the IVA included in the price cannot be claimed as a tax credit.

The practical consequence is direct: if a vendor issues a Factura instead of a CCFE for a B2B transaction, the buying company loses its right to deduct the IVA paid. This error cannot be corrected by simply requesting a new document; the original must first be invalidated through the Hacienda's formal process before a replacement CCFE can be issued. AP teams should verify that every B2B purchase from an NRC-registered vendor arrives as a CCFE, not a Factura, before accepting the document.

The Reversed Issuing Relationship of the FSEE

The Factura de Sujeto Excluido (FSEE, code 44) operates differently from every other DTE document type. In a standard transaction, the seller issues the invoice. With the FSEE, the buyer issues the document when purchasing goods or services from a party who is not registered for VAT. This occurs frequently with small vendors, informal suppliers, and individual service providers who fall below the registration threshold. The buyer assumes responsibility for generating the DTE, calculating any applicable withholdings, and transmitting it to the Hacienda, making the FSEE a document type that AP teams must be prepared to originate rather than simply receive. For a field-level breakdown of when this buyer-issued document applies, see our guide to excluded-subject invoice requirements in El Salvador.

DTE Transmission and Validation Workflow

Every DTE must pass through a defined five-step lifecycle before it carries legal weight. Understanding this workflow is essential for finance and IT teams configuring ERP or billing integrations with El Salvador's Ministerio de Hacienda.

The 5-Step DTE Lifecycle

Step 1: Generation in JSON format. The DTE is created according to DGII-defined JSON schemas. Since JSON structures map natively to objects in every modern programming language, ERP integrations can validate and construct DTEs without the XML parsing libraries, namespace handling, or XSLT transformations required by other LATAM e-invoicing systems.

Step 2: Digital signature. The generated document is signed using an electronic certificate issued by the DGII. This cryptographic signature authenticates the issuer and ensures the document has not been altered after creation.

Step 3: Transmission to the Ministerio de Hacienda. The signed DTE is sent to the government's validation platform. This is where El Salvador's model diverges sharply from post-audit jurisdictions, where invoices take effect immediately and are only reviewed later. El Salvador operates a pre-clearance (real-time clearance) model, meaning the tax authority validates every single document before it becomes legally effective. Costa Rica's electronic invoicing and clearance model follows an architecturally similar pre-clearance approach, though Costa Rica uses XML rather than JSON.

Step 4: The Sello de Recepcion. Upon successful validation, the DGII assigns a Sello de Recepcion — a UUID that serves as the government's official receipt stamp. This is the critical legal milestone in the entire workflow. A DTE without the El Salvador Sello de Recepcion has no legal standing whatsoever: it cannot support tax deductions, it cannot serve as proof of a transaction, and it cannot be presented in an audit. The Sello is what transforms a structured data file into a legally binding fiscal document.

Step 5: Delivery with representacion grafica. Once stamped, the DTE is delivered to the recipient. Alongside the electronic document, the issuer must provide a representacion grafica — a printable visual version of the DTE that includes a QR code for verification. This ensures recipients who lack electronic processing capabilities can still access and validate the document.

Two Transmission Systems

El Salvador provides two distinct paths for sending DTEs to the Ministerio de Hacienda, designed to serve businesses of different sizes.

Sistema de Transmision DTE is the API-based integration system. It is the standard path for any business with existing accounting or billing software. ERP platforms connect directly to the government's API endpoints, transmit signed JSON documents, and receive the Sello de Recepcion programmatically. This is the expected route for medium and large taxpayers processing significant document volumes.

Sistema de Facturacion DTE is a free government-provided invoicing tool available at admin.factura.gob.sv, intended for taxpayers issuing 100 or fewer documents per month. It is also available as a mobile app on Google Play. This system eliminates the need for commercial software or custom integrations, lowering the compliance barrier for micro and small businesses that would otherwise face disproportionate implementation costs. Taxpayers using this tool generate, sign, transmit, and receive their Sello de Recepcion entirely within the government platform.

Rollout Timeline and Compliance Deadlines

El Salvador's DTE system did not arrive overnight. The rollout has followed a phased approach spanning several years, gradually expanding from a small pilot to universal mandatory adoption.

Key milestones in the DTE rollout:

October 2020: The DGII launched a pilot program, onboarding a limited set of volunteer taxpayers to test the electronic invoicing infrastructure.
August 30, 2022: Legislative Decree 487 was approved, providing the formal legal framework for mandatory electronic invoicing across all taxpayer categories.
December 2022: The DTE system officially launched for broader adoption beyond pilot participants.
July 2023: Mandatory compliance began for Group 1, consisting of the largest taxpayers.
October 2023 through April 2024: Groups 2 through 4 were incorporated on a rolling basis, steadily expanding the mandatory base.
November 15, 2025: Large local and medium taxpayers must comply (extended from an original May 15, 2025 deadline).
May 15, 2026: Final deadline covering micro businesses, small businesses, and remaining state entities, bringing universal DTE adoption.

By the end of 2024, the system had onboarded 14,462 emitters, representing roughly 13% of registered taxpayers but capturing approximately 89% of all declared sales value. This concentration reflects a deliberate strategy: mandate the highest-volume taxpayers first to maximize fiscal coverage quickly, then extend to the long tail of smaller businesses by the May 2026 deadline. The fiscal impact has been measurable, with IVA collection reaching 8.7% of GDP compared to 3.5% in 2017.

Personalized Compliance Dates: A Distinctive Approach

Most Latin American countries implementing electronic invoicing publish phase schedules grouped by taxpayer size or economic sector. El Salvador takes a different approach. Rather than assigning a single deadline to an entire category, the DGII assigns each company an individual incorporation date. This personalized compliance date mechanism means that two businesses of similar size and industry may have different mandatory start dates.

The practical consequence is significant: a company cannot simply consult a phase chart to determine its obligation. Instead, each taxpayer must look up its specific deadline using its NIT on the Ministry of Finance portal. The NIT lookup returns the exact date by which that specific taxpayer must begin issuing DTEs.

For foreign companies trading with Salvadoran partners, this system adds a layer of due diligence. You cannot assume a supplier or customer is already on the DTE system based on their size alone. Confirming their individual compliance status through the portal or directly with the trading partner is the only reliable method.

This phased, individualized rollout mirrors a broader pattern across Central America, where countries are adopting mandatory electronic invoicing on varied timelines. Panama's SFEP electronic invoicing requirements, for example, represent another regional mandate that finance teams operating across borders must track in parallel with El Salvador's DTE deadlines.

How El Salvador's Two-Tier Invalidation System Works

Correcting or cancelling an electronic document after the Ministry of Finance has already validated it requires navigating El Salvador's invalidation event system. Unlike jurisdictions that offer a single, uniform correction window, El Salvador splits its DTE document types into two groups, each with a fundamentally different deadline. Getting this wrong is not a minor procedural issue: once the applicable window closes, the standard event mechanism for invalidation is no longer available.

Group 1: One-Business-Day Deadline

The following document types must be invalidated by 23:59:59 of the next business day after issuance:

Comprobante de Crédito Fiscal (CCF) — tax credit invoices
Credit notes
Debit notes
Withholding certificates (comprobantes de retención)
Settlement certificates (liquidaciones)
Donation certificates (donaciones)

This is an aggressive deadline. If a CCF is stamped at 2:00 PM on a Tuesday, the issuer has until 11:59:59 PM on Wednesday to submit the invalidation event. If that Wednesday is a holiday, the window extends to the next business day, but the margin for error remains razor-thin.

Group 2: 90-Calendar-Day Window

A more generous correction period applies to these three document types:

Facturas (standard consumer invoices)
Export invoices (facturas de exportación)
Sujeto excluido invoices (invoices to excluded taxpayers)

These documents can be invalidated within 90 calendar days of issuance. This extended window was updated in February 2026, replacing a previously shorter period.

Consumers who receive Group 2 documents can also request invalidation when they identify errors in name, NIT, item descriptions, or amounts. This consumer-initiated path follows the same 90-day limit.

The Sello de Recepción as the Baseline Clock

All invalidation deadlines are calculated from the Sello de Recepción timestamp, which is the government's reception stamp applied when the document passes validation. This is a critical distinction: the clock does not start when the document was created in an internal system or when it was transmitted. It starts when the Ministry of Finance stamps it. Any gap between document creation and successful transmission directly compresses the available invalidation window for Group 1 documents.

No Grace Period After Expiration

Once the applicable deadline passes, invalidation through the standard event mechanism is not possible. The public rules do not document any grace period, exception process, or administrative appeal for missed deadlines. For Group 1 documents especially, this means that operational delays in identifying errors can permanently foreclose the correction path.

February 2026 Regulatory Updates

The February 2026 changes extended beyond the Group 2 deadline adjustment. The same update introduced:

Two new mandatory fields for third-party transactions: identification number and name of the third party must now be included in the DTE when the transaction involves a third-party relationship.
Updated export invoice requirements, effective February 17, 2026, modifying the data elements required for facturas de exportación.

These changes apply to documents issued on or after their respective effective dates, making it essential to verify that document generation processes reflect the current field requirements alongside the updated El Salvador invoice invalidation rules.

Contingency Procedures and Recipient Data Requirements

Three operational requirements complete the DTE compliance picture: handling system outages, meeting recipient data thresholds, and maintaining records for audit purposes.

Contingency Procedures for System Outages

The DTE system does not require taxpayers to stop invoicing during an outage. When the Ministerio de Hacienda's transmission platform is unavailable or a taxpayer's own systems fail, the prescribed workflow is:

Continue generating DTEs normally, but flag each document as a contingency event.
Store all flagged DTEs locally for the duration of the outage.
Batch-transmit the stored DTEs once connectivity is restored, accompanied by a contingency event message that explains the reason for the delayed transmission.

One critical restriction applies during this window: documents generated under contingency cannot be cancelled while awaiting transmission. They remain in a pending state until the batch is processed. This means taxpayers must treat contingency-period DTEs as committed transactions and plan accordingly before issuing them.

Recipient Data Rules Under Legislative Decree 94

Legislative Decree 94, enacted in September 2024, established specific rules governing when recipient identification fields are required on invoices. The default position is permissive: recipient identification fields are optional on standard invoices.

These fields become mandatory in three situations:

The transaction equals or exceeds $25,000 USD. At this threshold, full recipient identification is required regardless of the customer's preference.
The customer requests an invoice for tax deduction purposes. When a buyer needs the document to support a deductible expense claim, the issuer must include the recipient's identification data.
The data is necessary to substantiate deductible expenses. This covers scenarios where the tax authority requires proof of the buyer's identity to validate a claimed deduction.

The decree also introduced a notable consumer protection provision. Unlawfully demanding identification from a customer when none of the three mandatory conditions apply carries a penalty of 30% of the transaction amount, with a floor of two monthly minimum wages. This provision prevents businesses from collecting personal data unnecessarily under the guise of invoicing requirements.

For finance teams, the practical implication is that invoice workflows need conditional logic: collect and include recipient data when the transaction value or customer request triggers the requirement, but do not default to collecting it in all cases.

Record Retention Requirements

Both issuers and recipients of electronic documents must retain them for 10 years from the date of issuance. This retention period aligns directly with the 10-year statute of limitations for tax enforcement, meaning the Ministerio de Hacienda can audit and assess penalties for the full duration that records must be preserved.

The symmetrical obligation is worth emphasizing: this is not solely an issuer responsibility. Recipients who claim tax deductions based on received DTEs must independently maintain their own copies for the same 10-year period. Organizations should ensure their document management systems and archival policies account for this extended retention window across both issued and received electronic documents.