Skip to main content

What is an e-CF and how it differs from an NCF

Moving from NCF to e-CF is not about turning receipts into PDFs. The format changes, who validates it changes, and the moment the document becomes fiscally valid changes.

5 min read

If your company issues tax receipts in the Dominican Republic, the DGII calendar will eventually require you to stop issuing paper NCFs and start issuing e-CFs. The practical difference goes well beyond no longer printing.

What an e-CF is

An e-CF (electronic tax receipt) is an XML document carrying the transaction data, signed with a digital certificate and transmitted to the DGII for validation. It is not a PDF, a scan, or an invoice emailed to the client: the signed XML file is the fiscal document.

The digital signature does two things: it identifies the issuer and guarantees the content was not altered after issuance. That is why the digital certificate is a prerequisite rather than an administrative afterthought.

What an NCF is, and why it is being replaced

The NCF is the receipt-numbering sequence authorised by the DGII for paper documents. Control happens up front: the DGII authorises a range and the company consumes it as it invoices. Verification that the receipt exists and is correct happens later, through the 606, 607 and 608 reports.

With the e-CF that order is reversed: the receipt is transmitted and validated at the moment of issuance. This reduces downstream errors, but it also means invoicing depends on a technical process that has to work every day.

The differences that affect operations

  • Format: a printed document with an authorised number, versus a structured XML whose data arrives already in fields
  • Validation: monthly reports, versus a response from the DGII during issuance
  • Signature: none required for the NCF, versus a digital certificate for tax procedures for the e-CF
  • Archiving: printing, delivery and physical filing, versus electronic retention and delivery at the time of the transaction

What this means for your company

Becoming an authorised electronic issuer is not a software installation. It requires obtaining the digital certificate, formally applying for electronic issuer status, configuring the authorised sequences, passing the DGII test set in the certification environment, and signing a sworn statement before issuing in production.

  • Your current invoicing system must be able to generate and sign the XML, or integrate with something that does
  • Someone has to handle rejections: a rejected receipt is not an issued invoice
  • Credit and debit notes, consumer invoices and contingency scenarios each have their own treatment
  • The 606, 607 and 608 reports come out cleaner, because the data is already structured at issuance

The calendar

The DGII calendar advances by taxpayer category. For micro, small and medium-sized companies, unclassified taxpayers and independent professionals, the current deadline is November 15, 2026. Because certification takes weeks, the date that matters for planning is the start date, not the deadline.

Frequently asked questions

For taxpayers covered by the calendar, yes: once a company is authorised as an electronic issuer, electronic receipts are the fiscally valid ones. Regulation provides contingency mechanisms for cases where electronic issuance is not possible at that moment.

It depends on whether that system can generate, sign and transmit the XML, or integrate with something that does. This is the first thing to check, because it determines whether the project is a configuration or a system change.

No. The fiscal document is the signed and validated XML. A printed or PDF representation is a way to show the receipt to the client, but it does not replace the electronic file.

Need to become an authorised electronic issuer?

We guide companies through the technical process of implementation, integration and certification as electronic issuers with the DGII, from the digital certificate to issuing in production.

See our e-CF electronic invoicing service

Keep reading