El Salvador's electronic invoicing model has one detail that surprises teams coming from Mexico, Colombia, or Peru. The documents aren't XML. Instead, they're JSON. For companies rolling out Business Central El Salvador, that choice ripples into how teams build, validate, and deliver documents. It also affects the schema tooling they use and how they parse errors.
Beyond the format, however, the underlying logic follows a familiar LATAM pattern: generate, sign, transmit, validate.
How DTE Validation Works in El Salvador
Every invoice, credit note, or other tax document becomes a Documento Tributario Electrónico (DTE), built in JSON and digitally signed with a certificate issued by the Dirección General de Impuestos Internos (DGII), part of the Ministerio de Hacienda. The signed DTE is transmitted for validation, and once approved, the DTE receives a Sello de Recepción — a UUID-based stamp that confirms the document was received and is legally valid. Without that stamp, the document carries no fiscal weight, no matter how correctly it was built.
What Happens When Transmission Fails
El Salvador's regulation includes formal contingency rules for when normal transmission isn't possible. Documents can be issued to the buyer without a Sello de Recepción during the outage, but the issuer must transmit the full contingency batch within 72 hours once service is restored. Skipping that step means the documents never gain full tax validity — and the buyer can't use them to support a tax credit until they do.
Where This Shows Up in Business Central El Salvador Projects
For implementation teams, a handful of configuration points recur:
- Generating DTEs in the correct JSON schema for each document type
- Maintaining a valid, renewed DGII signing certificate
- Registering the correct establishment and point-of-sale codes assigned by Hacienda
- Handling contingency transmission within the required window
- Supporting the different DTE types — invoices, fiscal credit documents, export invoices, and excluded-subject invoices
- Meeting the differentiated invalidation deadlines that now apply depending on document type
Common Challenges in El Salvador Implementations
In practice, most issues come down to a few recurring gaps:
- Using unregistered establishment or point-of-sale codes, which triggers automatic rejection
- Missing the field-naming conventions Hacienda's updated normativa now requires exactly
- Letting the signing certificate lapse without a renewal process in place
- Delivering a rejected DTE to a customer, which the regulation treats as a direct infraction
- Reusing invalidation windows meant for one document type on another, since deadlines now differ by type
Each of these is avoidable with the right configuration — but expensive to fix retroactively once documents are already in the field, since a rejected or invalidated DTE can mean re-issuing the transaction entirely.
Why a Dedicated Localization Matters for Business Central El Salvador
A proper El Salvador localization automates DTE generation in the correct JSON structure, manages the signing and transmission cycle, and handles contingency scenarios automatically. Built as an extension, it does this without touching Business Central's core, keeping future upgrades simple. It also tracks Hacienda's periodic normativa updates, so a schema change doesn't surface as a wave of rejected documents.
How LLB Solutions Supports Business Central El Salvador
LLB Solutions' for Microsoft Dynamics 365 Business Central covers DTE generation, ISR and VAT withholdings, and fiscal reporting — built as an AppSource-certified extension integrated with a DGII-recognized provider. The localization also keeps pace with Hacienda's periodic catalog and normativa updates, so a schema revision doesn't turn into a wave of rejected documents.
El Salvador's DTE model is stable, but its JSON-based format and formal contingency rules are different enough from neighboring countries that assumptions carried over from another LATAM project rarely hold. Companies that plan for the format and the certificate lifecycle from day one avoid the compliance gaps that come from treating it as "just another XML invoice."
For Microsoft partners moving between Mexico, Guatemala, and El Salvador projects, that format switch is worth flagging early — it's an easy assumption to carry over by mistake.
See how LLB Solutions' El Salvador Localization fits your Business Central project —