El Salvador Electronic Invoicing in SAP: DTE Integration Guide

Status: Active, with taxpayer incorporation managed in stages. Verified on: 10 July 2026. El Salvador’s Ministry of Finance can notify each taxpayer’s required DTE start date, while eligible taxpayers may also join earlier through the authorisation process.

A Documento Tributario Electrónico, or DTE, is generated and retained electronically, carries an electronic signature and receives the tax administration’s validation seal. It documents supplies of goods and services and is not the same as an unsigned PDF or a generic XML invoice. The implementation has to control the structured document, its signature, the Ministry response, customer delivery and any later event.

Scope and onboarding

The 2022 Tax Code reform introduced DTE provisions for VAT taxpayers that issue the documents and for their recipients. The tax administration was authorised to define and communicate a gradual incorporation plan. A company should therefore rely on its official notification or approved voluntary onboarding—not a generic web date—to determine the production start.

• B2B examples: electronic tax credit receipt, credit note, debit note, remittance note, VAT withholding receipt, liquidation documents and export invoice.
• B2C examples: electronic final-consumer invoice and the applicable ticket document.
• Other documents: excluded-subject invoice and electronic donation receipt, subject to the current catalogues and rules.

Only enable the document types and events that apply to the taxpayer’s operations. The Ministry’s onboarding process requires test-environment access, electronic-signature credentials, minimum tests for the relevant DTE and events, authorisation as an issuer, and then production credentials.

JSON, signing and integration channel

The transmission model uses DTE structures defined through JSON schemas and current tax catalogues. The DTE is electronically signed; the official technical materials describe JWS-based signing. The taxpayer’s transmission system connects to Ministry services through REST interfaces, with JWT used for service authentication. These are distinct controls: the access token protects the service call, while the document signature protects the DTE.

The Ministry currently offers two operating options. The web-based Sistema de Facturación is a free service intended for eligible taxpayers averaging no more than 500 DTE per month. The Sistema de Transmisión is the taxpayer’s own or acquired solution, built to the Ministry’s functional and technical specifications and capable of integrating with internal systems. A higher-volume SAP environment will normally assess the transmission route, but eligibility and the approved route must be confirmed during onboarding.

Document lifecycle and exceptions

1. SAP produces complete commercial, tax and customer data for the applicable DTE type.
2. The integration maps the source to the current JSON schema, applies catalogues and creates the generation code and other required references.
3. The signing component applies the issuer’s electronic signature to the DTE.
4. The signed DTE is transmitted to the Ministry. The response and validation seal are recorded against the SAP business document.
5. The issuer delivers both the DTE file and graphical representation to the customer through the agreed electronic channel.
6. Corrections and exceptions use the appropriate DTE or event, including credit or debit notes, invalidation, contingency, special-operation or return events where applicable.

For the Sistema de Transmisión, the official onboarding tests include the contingency event as well as invalidation. The production design should retain the reason, start and end of an incident; queue affected documents in sequence; apply the official retry policy; submit the required contingency event; and reconcile every document and response after service restoration. Do not invent a local fallback workflow or resend blindly after a timeout.

What this means for SAP

• Govern NIT, NRC, establishment, activity, address, recipient and catalogue data before mapping starts.
• Version JSON schemas and tax catalogues independently from SAP transport cycles.
• Keep private keys and API credentials outside ordinary business configuration, with controlled renewal and access.
• Model generated, signed, submitted, accepted, rejected, delivered, invalidated and contingency states separately.
• Test every used document type and event, including rounding, discounts, exports, retentions, invalidation and failed responses.

S4FN delivery classification: S4FN-developed custom integration and implementation service where an SAP-to-DTE connection is required. SAP ECC or SAP S/4HANA landscapes are assessed individually; this page does not imply SAP-delivered El Salvador DTE localisation or a single deployment model.

Primary sources

• Ministry of Finance — DTE Tax Code reform and gradual incorporation
• Ministry of Finance — Electronic invoicing portal
• Ministry of Finance — Current technical and functional documents
• Ministry of Finance — DTE issuer onboarding and operating options

Review note: Taxpayer waves, catalogues, schemas, test cases and service specifications can change. Confirm the taxpayer’s notified start date and the current production package with the Ministry of Finance and Salvadoran tax counsel before go-live. This page is implementation guidance, not legal or tax advice.