El Salvador DTE 2.0: SAP Business One checklist before 1 December 2026

By Zain Abbas, Kodenova · Updated

Short answerVersion 2.0 of El Salvador's DTE compliance rules must be applied by 1 December 2026 by taxpayers who issue electronic tax documents through an integrated transmission system. It brings updated JSON schemas and catalogs, new Return and Special Operations events, a revised contingency and invalidation process and lower submission size limits. SAP Business One integrations must be updated and retested before that date.

What is changing

El Salvador’s Ministerio de Hacienda (DGII) published version 2.0 of the DTE compliance rules, replacing version 1.2. According to published guidance, taxpayers that use an integrated DTE transmission system must adapt by 1 December 2026.

ChangeImpact on SAP Business One
Updated JSON schemas and catalogsThe JSON your integration builds from SAP B1 documents must be regenerated and validated
New Return eventReturns need their own event flow, not only a credit note
New Special Operations eventSome transactions need a new event type
Refined contingency modelOffline batches follow new rules; limits of 100 documents per batch and 400 batches per transmission are reported
Lower submission size limitsLarge documents or batches may need splitting
Revised invalidation processInvalidations must follow the new flow, and the recipient receives the JSON plus a printable version

Checklist for SAP Business One users

  1. Find out who generates your DTEs. Your own connector, an add-on, or an external provider.
  2. Get the version 2.0 schemas from the Ministerio de Hacienda and compare them with what your integration sends today.
  3. Map every SAP B1 document type to its DTE type: Factura, Comprobante de Crédito Fiscal, Factura de Exportación, notas de crédito and débito, nota de remisión.
  4. Add the new events (Return, Special Operations) where your business needs them.
  5. Update contingency and invalidation logic, including batch sizes.
  6. Test in the DGII test environment with real documents from your SAP B1 company.
  7. Update the printed version sent to customers.
  8. Plan go-live before 1 December 2026, with a rollback plan.

Why start now

Version changes look small on paper, but schema changes break integrations quietly: documents are rejected, and nobody notices until customers complain. A few weeks of testing before the deadline costs far less than a month of rejected invoices after it.

Kodenova has delivered DTE integrations for SAP Business One in El Salvador. See our DTE guide or contact us for a version 2.0 review.

Sources

Related services

FAQ

Frequently asked questions

When does DTE version 2.0 become mandatory?

Published guidance gives 1 December 2026 as the date by which taxpayers using the DTE transmission system must comply with version 2.0.

What changes in DTE 2.0?

Updated JSON schemas and official catalogs, two new events (Return and Special Operations), a refined contingency model, lower submission size limits, a longer window for future-dated documents and a revised invalidation process.

Do I need to change my SAP Business One integration?

If your SAP B1 sends DTEs directly or through your own connector, yes: the JSON it generates, its contingency logic and invalidations must follow version 2.0. If a provider handles it, confirm their update date in writing.

Ready to get started?

Tell us what you need. You get a clear technical answer, a fixed scope and a price, usually within 24 hours.