Void and modify e-CFs

How to void an issued e-CF, correct text or amount errors, and issue a replacement voucher - includes use cases for each DGII modification code.

Once an e-CF has been sent to the DGII, it cannot be edited directly. Corrections always happen by issuing a new voucher that references the original: a void, a credit or debit note, or a replacement e-CF. Each case has its own DGII modification code.

Reading time: ~10 min

When to use this

An e-CF has a text error (customer name, address) and you need to correct it.
An e-CF has incorrect amounts and you need to reverse or adjust them.
You need to void a voucher that should not have been issued.
Your customer returned merchandise or you want to grant them a later discount.
You came back from a contingency (DGII down or a technical failure) and you have to issue the replacement e-CFs for the paper vouchers you used during that period. See Contingency and backup plans.

Before you start

Your role includes fiscal:manage. Read-only does not allow issuing corrective vouchers.
To issue a replacement e-CF (Code 4) you also need the fiscal:replacement:create permission. If the replacement falls outside the 30-day window, you also need fiscal:replacement:override-window. The OWNER and ADMIN roles do not require additional permissions.
You have the active sequence for the corresponding corrective e-CF type (E33 for a debit note, E34 for a credit note, etc.).
You know the exact number of the original e-CF you are going to reference.

The five DGII modification codes

Per DGII Formato Comprobante Fiscal Electrónico v1.0 §F.4 (pages 56-57): the <CodigoModificacion> field identifies the reason why the corrective e-CF references an earlier one. The five canonical codes are:

Code	DGII name	When it is used
1	Voids	The referenced e-CF must be left without fiscal effect.
2	Corrects text	The original has incorrect text data (name, address, description) without any change to the amounts.
3	Corrects amounts	The amounts in the original are incorrect - a return, price adjustment, calculation error.
4	Replacement of NCF issued in contingency	Replaces a paper Series B voucher issued during a contingency episode, or replaces a queued e-CF that was cancelled locally after the regulated deadline expired.
5	Reference to Electronic Consumer Invoice	The e-CF (typically E34) references an electronic Consumer Invoice (E32) as a supporting voucher.

About the name of code 4. "Replacement of NCF issued in contingency" is DGII's literal wording in Formato e-CF v1.0 §F.4 - it includes the acronym NCF (which in the previous regime was the numbering of paper vouchers). Mosce ERP only issues e-CF and never generates a new NCF for you; what code 4 indicates is that the current e-CF replaces a paper Series B voucher previously issued off-platform during a contingency.

Mosce ERP writes the correct code automatically based on the flow you use.

Code 1 - Void

Use this code when the e-CF should not have existed: wrong recipient, duplicate, sale cancelled without an amount adjustment.

How to void from the documents inbox

Open Fiscal → e-CF Documents.
Find the e-CF you want to void. You can search for it by its number or filter by status.
In the row's action menu, choose Void.
In the dialog, type the Void reason (required field). This reason is recorded in the internal audit trail.
Confirm. The void is permanent.

Important: Voiding revokes the voucher in the Mosce ERP record. If the e-CF was already Accepted by the DGII, the accounting effect (income, ITBIS) is not reversed just by voiding it - you must also issue a Credit Note (E34) from the invoicing module to reverse the transaction.

Code 2 - Text correction

You issued the e-CF with the customer's name misspelled, the wrong address, or an incorrect description, but the amounts are correct. In that case:

From the documents inbox, open the detail of the original e-CF.
Issue a Credit Note (E34) or the equivalent type with <CodigoModificacion>2</CodigoModificacion>, referencing the number of the original.
The new voucher must have the same amounts as the original (the correction is text-only).

Note: In practice, many accountants prefer to void (Code 1) and reissue from scratch instead of using Code 2, because the flow is clearer for the recipient. Both approaches are valid before the DGII.

Code 3 - Amount correction

Use this code when you have to reverse or adjust the economic value of a transaction: merchandise returns, discounts granted after the invoice, price or calculation corrections.

The standard vehicle is the Credit Note (E34) issued from the invoicing module.

Example: Distribuidora La Esperanza, S.R.L. receives a return

The company issued E310000000083 (Fiscal Credit Invoice) for DOP 42,000 + ITBIS. The customer returns merchandise worth DOP 8,000.

In Operations → Invoices, open the original invoice.
Create a Credit Note from the menu action - Mosce ERP preloads the original e-CF as a reference.
Adjust the amount to the value of the return (DOP 8,000 + corresponding ITBIS).
Issue it. Mosce ERP generates an E34 with <CodigoModificacion>3</CodigoModificacion> and the number of the original e-CF in <NCFModificado>.

The customer ends up with the original voucher (E31) plus the credit note (E34) that reduces the amount payable.

Code 4 - Replacement of a voucher issued in contingency

Per DGII Formato Comprobante Fiscal Electrónico v1.0 §F.4: code 4 (Replacement of NCF issued in contingency) applies to any e-CF type whose type matches the equivalent of the Series B voucher being replaced.

This code covers two distinct scenarios:

Scenario A - Replacement of paper Series B (after Technical Incapacity)

When the system was technically incapacitated to issue e-CFs, the taxpayer operated with paper Series B vouchers. Once the service is restored, they have 30 calendar days to issue a replacement e-CF for each paper voucher used, from Fiscal → Replacements → New replacement.

Key characteristics:

One Series B = one replacement e-CF. There is no bulk replacement; each paper voucher requires its own electronic voucher. This is defined by the DGII specification.
The e-CF type must match the equivalent of the Series B (B01→E31, B02→E32, B03→E33, B04→E34, B11→E41, etc.). Mosce ERP detects it automatically when you enter the Series B number in the Voucher number field.
The replacement e-CF is sent only to the DGII, not to the recipient. Your customer already has their original paper voucher.

Scenario B - Replacement of a queued e-CF that crossed the regulated 72-hour deadline

When an e-CF in the contingency queue could not be delivered to the DGII within the regulated 72 hours, Mosce ERP surfaces it on the Fiscal → Contingency → Past-SLA Review screen. If you decide to cancel it instead of continuing to retry, you choose Void and issue replacement on that row. The flow is:

Mosce ERP starts the e-CF cancellation via the DGII.
Once the DGII accepts the cancellation, Mosce ERP takes you to the replacement form with the original document context preloaded.
The replacement is issued with <CodigoModificacion>4</CodigoModificacion> referencing the number of the cancelled original e-CF.

Note: This replacement flow is part of contingency handling. For the complete guide - what triggers the 72-hour deadline, how the Past-SLA screen works, and the 30-day clock for paper replacements - read Contingency and backup plans.

What Mosce ERP writes automatically

When you create the replacement in Mosce ERP (whether from the Past-SLA screen or directly from Fiscal → Replacements → New replacement), you complete the form fields: the number of the paper voucher or the original e-CF in the Voucher number field, the issue date, and the detail lines. Mosce ERP fills in automatically:

<CodigoModificacion>4</CodigoModificacion> in the reference block.
<NCFModificado> with the number of the referenced voucher (Series B or original e-CF).
The e-CF type according to the B→E mapping (auto-detected from the number prefix as you type it).

For types E33 (Debit Note) and E34 (Credit Note), the form shows an additional optional Modification reason field, which corresponds to the e-CF's <RazonModificacion>.

You do not have to remember any of the technical reference fields; you only provide the source voucher data and the detail lines.

Code 5 - Reference to an Electronic Consumer Invoice

Use this code when you issue a Credit Note (E34) that references a Consumer Invoice (E32). The DGII regulation requires distinguishing whether the reference voucher is a fiscal credit invoice (E31) or a consumer invoice (E32) because the recipient's fiscal treatment differs.

Mosce ERP applies Code 5 automatically when it detects that the referenced voucher is an E32.

Quick reference table

I want to...	Corrective e-CF type	Code
Void a voucher that should not have existed	E33 (Debit Note) or E34 (Credit Note), depending on the original type	1
Correct name / address / text without changing amounts	E34 or another type with corrected data	2
Return / reverse / adjust amounts	E34 (Credit Note)	3
Replace a paper Series B after a contingency	E31/E32/E33/E34/E41/etc. per equivalence	4
Replace a queued e-CF cancelled after 72 h	Same type as the cancelled original e-CF	4
Credit note referencing a consumer E32	E34	5

Common errors

Symptom	Likely cause	Solution
DGII rejects the replacement e-CF	The replacement type does not match the original Series B	Check the equivalence (B01→E31, B02→E32, etc.)
The replacement form does not appear or is locked	The 30-day window expired, there is no active episode, or you lack `fiscal:replacement:create`	Check the status in Fiscal → Contingency; if the window expired and you have authorization, use the out-of-window acceptance checkbox; if you lack the permission, ask your administrator
The recipient claims they did not receive the replacement	Expected behavior	Replacements (Code 4) go only to the DGII, not to the recipient
I cannot void an accepted e-CF	Voiding proceeds but you must also issue a Credit Note	Void the e-CF and issue the Credit Note from the original invoice

Contingency and backup plans - complete flow of Code 4 replacements after a contingency, the 30-day window and the Past SLA screen.
e-CF Documents - documents inbox with DGII statuses and the void action.
e-CF Sequences - management of active sequences for each e-CF type.
Fiscal configuration - issuer data required for any corrective voucher.

Last updated: 2026-05-22

Regulatory sources

DGII - Formato Comprobante Fiscal Electrónico v1.0, October 2025. §F.4 (pages 56-57) - the five canonical <CodigoModificacion> codes: 1=Voids, 2=Corrects Text, 3=Corrects amounts, 4=Replacement of NCF issued in contingency, 5=Reference to Electronic Consumer Invoice. §F.1 (page 56) - <NCFModificado> validation of type equivalence between the Series B and the replacement e-CF. Available on the DGII portal.

Void and modify e-CFs

On this page