What the DGII actually checks in an NCF
An NCF gets rejected for what you can't see: the sequence used up, a type that doesn't match the customer, a date outside the authorisation. How to avoid it.
The receipt looks right and still gets rejected
The NCF (Número de Comprobante Fiscal) is what turns an invoice into a document with tax value in the Dominican Republic. And the part that surprises almost everyone starting out is that an invoice can be issued perfectly — right amounts, right customer, ITBIS calculated — and still be useless.
The reason is that an NCF isn't a number you pick: it's a sequence authorised by the DGII, with a type, a range and an expiry date. When any of those three doesn't fit, the receipt stops being valid for the customer to use, and that's found out late: when the customer reports it in their 606 and it doesn't match.
The symptom of a badly issued NCF isn't an error on screen. It's a call from the customer three months later saying their accountant can't use your invoice. By then you have to void and reissue, with the tax period already closed.
The three things that have to line up
A valid receipt needs the type, the sequence and the validity period to line up at the same time:
- The type has to match the customer. A tax-credit receipt (type 01) is for a customer with an RNC who will use it to deduct. A final-consumer one (02) is for someone who won't. Issuing an 02 to a company throws no error, but it takes away the customer's right to deduct the ITBIS.
- The sequence has to be inside the authorised range. Each range has a start and an end number. When it runs out, you can't keep numbering: you have to request a new one.
- The date has to be inside the validity period. Ranges expire. An NCF issued after its authorisation's expiry date is worthless, even if the number is inside the range.
And there's a fourth that isn't the DGII's but breaks things just the same: the sequence can't repeat or skip. A number used twice is a serious problem, and a gap has to be explainable.
The types most often confused
Most of the rejections we've seen come from choosing the wrong type, not from a numbering fault:
- 01 · Tax credit. A customer with an RNC who will deduct the ITBIS. It requires the customer's RNC, and that it be correct.
- 02 · Final consumer. An individual who doesn't deduct. If you issue it to a company, that company can't use it.
- 03 · Debit note and 04 · Credit note. They amend an earlier receipt and have to reference it. A credit note without the NCF it corrects is orphaned.
- 11 · Purchases. The buyer issues it when buying from someone who can't issue a receipt. It's the most forgotten one.
- 14 · Special regime and 15 · Government. For customers under a particular regime; using an 01 with them usually ends in rejection.
The practical rule: the type is decided by who the customer is, not by what you sell them. That's the most repeated mistake.
What fails in practice
After rolling out invoicing in quite a few Dominican companies, the problems repeat with striking regularity:
- The sequence runs out on a Friday afternoon. Nobody watches how many are left until none are, and then you can't invoice. A warning at 80% solves 90% of these scares.
- Two points of sale share a range. If two tills take numbers from the same range without coordinating, sooner or later they issue the same one. The number has to come from a single place that knows which was the last.
- The customer's RNC is mistyped. One digit wrong and the receipt is useless for deducting. Validating the RNC against the official register when you create the customer avoids the whole problem.
- Voiding is done wrong. An issued receipt isn't deleted: it's voided and reported as voided. Deleting it from the database leaves a gap in the sequence that you then have to explain.
How to prevent it before issuing
All of this is checkable before the invoice exists, and that's where a system really earns its keep. What should happen when you press «Invoice»:
- The type proposes itself, based on whether the customer has an RNC and on their regime.
- The number comes from the authorised sequence, from a single source, with no way to repeat even if three tills invoice at once.
- The range's validity is checked against the document's date, not today's.
- You're warned when few receipts are left, with time to request the new authorisation.
- Voiding leaves the receipt voided and reportable; it never deletes it.
None of these checks is hard. What's hard is remembering to do them by hand every time, with the customer waiting at the counter. And if you're already on e-invoicing with e-CF, there's even less room to improvise.
Tax rules change. This article explains how things work in general as of September 2026; for a specific case, always confirm with the DGII or your accountant.