e-CF sequences

The Fiscal module has two connected tabs that control emission:

• Authorizations - registers each range DGII assigns you per voucher type and per environment. Each authorization carries an initial-final range, an authorization date, an expiration date (except for E32 and E34, which do not expire), and an optional DGII reference.
• Sequences - shows the emission counter per voucher type and per environment: how many numbers were consumed, which is the next to emit, and how many remain available under the active authorization.

Each voucher number has 13 characters: the letter E + 2 digits for the type + 10 sequential digits (e.g. E3100000000042). Without a valid active authorization for the type and the current environment, the corresponding e-CF cannot be emitted.

Reading time: ~9 min

When to use this

• You just configured the Fiscal module and are going to load your first sequence.
• DGII issued you a new authorization with an expanded range.
• Your current sequence is close to 90% used or about to expire and you need the next one.
• You want to deactivate a sequence and replace it with another (range change).

Before you start

• The Fiscal Configuration is saved (RNC + legal name) and the Certificate is active.
• Your role includes fiscal:manage.
• You have the DGII authorization on hand with: voucher type, authorization number, initial number, final number, and expiration date.

e-CF number format

Each electronic tax voucher has a sequence of 13 alphanumeric positions:

E  3 1  0 0 0 0 0 0 0 0 4 2
↑  ↑↑   ↑──────────────────↑
│  └┘   └── 10 sequential digits
│  e-CF type (2 digits)
└── letter "E" (electronic series)

DGII authorizes ranges by type and by period. The validity of each sequence runs from the authorization date until December 31 of the following year - it cannot be used outside that period.

Supported voucher types

Mosce ERP handles the following e-CF types:

Each type has a single active authorization per environment. Inactive (withdrawn) authorizations are kept as history for audit, but only one active per type and per environment.

Authorizations per environment - manual registration in the three environments

Each DGII environment (Testing, Certification, Production) operates with independent authorizations. The authorizations of one environment do not carry over to another: if you are going to operate in Certification first and then in Production, you must register the authorizations of each environment separately as DGII delivers them to you.

In the Authorizations and Sequences tabs you will see a badge with the active environment at the moment (for example, Environment: CERTECF). What you see listed are only the rows of the environment that corresponds to your current configuration. To see those of the other environment, first change the DGII Environment from Fiscal Configuration.

Mosce ERP does not preload authorizations automatically in any environment. Every time DGII delivers you a new range - whether testing, certification, or production - you must register it manually from the Authorizations tab of the corresponding environment. This prevents your system from silently diverging from what DGII has on record.

Step by step - register an authorization

1. Open Fiscal → Authorizations.
2. Check that the badge shows the correct environment (Environment: ECF, Environment: CERTECF, or Environment: TESTECF).
3. Press Add authorization for {environment}.
4. Fill in the fields:
   • e-CF type - Select the code (E31, E32, etc.). If there is already an active authorization for that type in this environment, you must first withdraw the current one.
   • Initial number - First number of the range DGII authorized (e.g. 1).
   • Final number - Last number of the range (e.g. 9000).
   • DGII authorization date - Day on which DGII issued the authorization.
   • Expiration date - Date until which DGII authorizes emission against that range. The E32 and E34 types do not carry an expiration date by DGII rule; the field is hidden automatically for those types.
   • DGII reference (optional) - Virtual Office (OFV) ticket number or internal note for audit.
5. Press Save.
6. The row appears in the Authorizations table with a usage indicator (progress bar with a percentage) that updates as the sequence consumes numbers.

Correct a mistyped field in an authorization

If, when registering the authorization, you captured the wrong expiration date or you need to note the DGII reference afterwards, the Authorizations tab has a per-row edit button.

It is important to do it: if the expiration date you send in each e-CF does not match exactly the one DGII has in its records for that sequence, DGII rejects the voucher with code 145 - "Fecha de vencimiento de secuencia inválida".

1. On the row of the active authorization, open the pencil-icon button.
2. In the dialog only the editable fields are shown: Expiration date and DGII reference. The range and the authorization date stay locked to keep traceability with DGII.
3. For the E32 and E34 types the expiration field does not appear; these vouchers never expire per DGII rule.
4. For the rest of the types the date is mandatory - leave it exactly the same as the one on the OFV document DGII delivered to you.
5. Press Save changes. The correction applies immediately and the next vouchers emitted against that authorization will carry the corrected date.

The range (initial and final numbers), the original authorization date, the voucher type, and the environment cannot be modified once the authorization is created. If you need to change any of those fields, withdraw the authorization with the Withdraw button and register a new one with the correct data.

Validity period and what happens on expiration

DGII authorizes each sequence range with a validity period: from the authorization date until December 31 of the following year. Past that date, the numbers cannot be used, even if the range has not been exhausted.

When a sequence expires before being exhausted:

• Emission of that e-CF type is blocked until you load a new sequence.
• You must request a new authorization range from DGII.
• The expired sequence remains in the table as a historical reference.

When a sequence is exhausted (reaches the last number):

• Emission of that e-CF type is blocked until you load a new active sequence.
• You must request a new authorization range from DGII for that type.

Plan the renewal ahead of time - ideally when the sequence reaches 80% usage or 30 days before expiration.

Monitor consumption

The Sequences tab shows the emission counter per voucher type in the active environment. Each row includes a progress bar with a percentage:

• Green - more than 30% of the authorized range available.
• Amber - between 10% and 30% available. It is a good time to request the next range from DGII.
• Red - less than 10% available. Request a new authorization before running out of numbers.

Above the table the alert "Some sequences have few numbers available. Request a new authorization from DGII before they run out." may appear. It is an invitation to plan the next range.

The expiration date column lives in the Authorizations tab (not in Sequences) - expiration is a property of the range DGII authorized to you, not of the internal counter. If you need to know when the range you are using expires, check the corresponding row in Authorizations.

View the next number

On the row of each active sequence there is a View next action that shows the next e-CF number Mosce ERP will assign. Useful for auditing continuity before a close.

A content rejection consumes the number

The sequence counter does not only advance with accepted emissions. When DGII rejects an e-CF for a content or business reason (an amount that does not add up, a wrong client RNC, a missing mandatory field, etc.), that voucher number is consumed and cannot be reused: the sequence advances all the same. When you correct the value and retry, the corrected voucher goes out with the next number.

By contrast, if the rejection is due to a structural or signature cause (invalid XML structure, invalid certificate or signature, unauthorized signer, unauthorized or expired eNCF), the number can be reused and the same voucher is retried with the same eNCF. DGII indicates which of the two cases applies in its response. The detail is in e-CF Documents.

That is why, when reconciling the continuity of a sequence, you may see "jumps" that correspond to numbers consumed by content rejections. They are not an error: the DGII rule considers the number rejected by content to be consumed.

Withdraw an authorization

When a range is exhausted, expires, or you want to replace it ahead of time:

1. In the Authorizations tab, open the row and press Withdraw.
2. Confirm in the dialog. The authorization becomes inactive but its history is kept for audit.
3. Register a new active authorization for the same type and environment. The emission counter continues from where it left off - the numbers already emitted are not lost or reused.

It is not possible to physically delete a registered authorization. The rule is designed to preserve traceability before DGII: every range that ever appeared in the system must remain available for historical query.

Cancel a sequence range (ANECF)

In exceptional cases you may need to permanently cancel a range of e-CF sequence numbers. The two most common cases are:

• DGII authorized a range larger than the one you are going to use and you want to release the unused numbers.
• You signed e-CFs locally (for example during a contingency) but could not send them to DGII and you are no longer going to resend them.

Warning: this operation is irreversible. Once DGII accepts the cancellation of the range (Anulación de e-NCF - ANECF), those voucher numbers cannot be reused for emission. Act only when you are sure the numbers are not going to be used.

Permission required

Cancelling a range requires the fiscal:sequences:anular permission, separate from the general fiscal:manage permission. Because of the irreversible nature of the action, it is recommended to assign this permission only to the smallest circle of administrators with advanced fiscal access.

How to cancel a range

1. In the Sequences table, open the row's action menu and choose Cancel range.
2. In the dialog, fill in:
   • e-CF from - initial sequence number of the range to cancel (format E + type + 10 digits, e.g. E3100000000050).
   • e-CF to - final sequence number of the range (same format).
   • Cancellation reason - briefly describe why the range is being cancelled. It is recorded for audit purposes.
3. On the confirmation screen, review the range and the voucher type. If everything is correct, confirm the cancellation.

The request is queued asynchronously. Mosce ERP sends it to DGII using the e-NCF Cancellation (ANECF) format. The action may take a few minutes until DGII confirms. The sequences table updates the status when DGII responds.

For large ranges, DGII may take longer than usual. If the status does not change in several minutes, refresh the page or check e-CF Documents for any related DGII response.

Expected result

• One active sequence for each e-CF type you are going to use.
• Green indicators for sequences with enough headroom.
• Next e-CF number visible at the start of each invoicing operation.
• Clear alerts when a range is running low or about to expire.

Common errors

Related

• Fiscal configuration
• e-CF certificate
• e-CF Documents
• DGII reports
• Certification process - sequences are part of the process of becoming an authorized electronic issuer.
• Contingency and backup plans - what happens with e-CFs signed in contingency that did not reach DGII.

Regulatory sources

1. DGII - Informe Técnico e-CF v1.0 §7 (pages 13-14): the 13-alphanumeric-position structure of the e-NCF: E + 2 type digits + 10 sequential digits; validity from the authorization date until December 31 of the following year. Available at the DGII portal.
2. DGII - Formato Comprobante Fiscal Electrónico v1.0 (pages 1-2): table of the 10 e-CF types with their codes (31-47) and full names. Available at the DGII portal.
3. DGII - Descripción Técnica de los Servicios (e-CF validation response): the secuenciaUtilizada parameter - True = the number cannot be reused (it is consumed), False = the number can be reused (rejections by certificate/signature, XML structure, unauthorized signer, or unauthorized/expired eNCF). Available at the DGII portal.