DGII Environment

The DGII Environment is the configuration piece that tells Mosce ERP which of the three official DGII environments to send your electronic vouchers to (e-CF, ARECF, ANECF, RFCE). Your active environment determines whether your vouchers are internal tests, official tests of the certification process, or vouchers with real fiscal validity. Switching environments is a high-impact decision: this article explains what each environment is, when to switch it, and the warnings you will see on screen when you try.

Reading time: ~6 min

When to use this

• You just set up your account and want to start testing e-CF issuance before starting the official application.
• The DGII approved your application and you need to switch from Testing to Certification to start the Step 2 test set of the certification process.
• You completed the Sworn Declaration (Step 13) and the DGII authorized you as an electronic issuer - you are going to flip to Production.
• An administrator asked you to check which environment is active because something is not behaving as expected (for example, vouchers that are not reaching the DGII).

Before you start

• Your role includes the fiscal:manage permission to modify the fiscal configuration.
• To use Certification or Production you first have to have uploaded your P12 digital certificate in the Certificate tab of the Fiscal module. The Testing environment works without your own certificate (it uses a temporary platform one).
• Understand that you will perform this action only when you are fiscally authorized - flipping from Production to Testing by mistake can create discrepancies between your internal accounting and the official DGII records.

The three environments

The DGII operates three independent environments for electronic invoicing. Each one has its own database, its own sequence counters, and its own URLs:

Testing (TESTECF)

What it is used for. Initial exploration and technical integration before formally applying before the DGII. It does not require your own digital certificate or being enrolled in the electronic invoicing program.

Fiscal validity. None. The vouchers issued here are not valid as tax support and do not affect your official books at the DGII.

When to use it. When you have just installed Mosce ERP and want to practice the issuance flow, see how the printed representations look, test the contingency scenario, or train your team without risk. Also when a software provider asks you for it to do an initial integration.

Data retention. 60 days per cycle. What you issue here may be deleted by the DGII within that period - do not expect your test history to be kept forever.

Certification (CERTECF)

What it is used for. It is where the official 15-step flow of the DGII certification process runs once your application has been approved. Each e-CF you issue in this environment is part of your certification file and the DGII evaluates it.

Fiscal validity. None yet - the vouchers are received and validated by the DGII, but only as part of the tests that prove your system complies with the regulations. They are not binding for your tax filings.

When to use it. Once you uploaded the signed application XML to the DGII certification portal and the DGII approved it. From there you are in Step 2 (Data Tests) and everything you issue must go to the Certification environment until you complete the 15 steps.

Requirement. Your P12 digital certificate has to be uploaded in Mosce ERP, because the DGII expects each voucher to come signed with the certificate of the representative registered in your RNC.

Production (ECF)

What it is used for. Normal operation. Each e-CF issued here is fiscally binding: it is part of your monthly ITBIS filing, stays in your official sales ledger, and serves as legal support in audits.

Fiscal validity. Full. Voiding a voucher issued in production requires a formal electronic void process (ANECF) within deadlines regulated by the DGII.

When to use it. Only after the DGII has officially issued your Authorization to be an Electronic Issuer upon successfully completing the 15 steps of the certification flow.

Requirement. The same P12 digital certificate uploaded and current. If your certificate expires while you are in Production, voucher issuance is interrupted until you renew.

How to change the environment

1. Go to Fiscal → Configuration.
2. Find the DGII Environment selector.
3. Choose the option you want to activate.
4. When you click Save, Mosce ERP shows you a confirmation dialog with four sections:
   • Operation: what changes technically (which DGII URLs will start being used).
   • Operational implication: what the new environment means for your business (testing / certification / production).
   • Administrator responsibility: a mandatory warning that you have to read and accept by checking the box.
   • Downgrade warning (only appears if you are going to a lower environment than the current one): reminds you of the accounting risks of stepping back.
5. Check the box "I have read the implications and understand that I perform this action under my responsibility as an authorized administrator".
6. Click Confirm change.

If you want to cancel, press Cancel, the ESC key, or close the dialog by clicking outside. No change is saved until you confirm.

The header indicator

While your account is in an environment other than Production, Mosce ERP shows a persistent banner in the header of every screen, visible to all users connected to the account:

The banner cannot be closed - it is a status indicator, not a notification. When an administrator changes the environment, all connected users see the banner update in real time and receive a notice-type notification.

Blocks and validations

Mosce ERP enforces three restrictions to prevent costly errors:

1. For Certification or Production you need an active certificate

If you select Certification or Production but you have not yet uploaded your P12 certificate (or the one you uploaded is expired), the options appear disabled in the selector. You will see a note: "To use Certification or Production you must first upload your P12 certificate in the Certificate tab."

If for some reason the system let the selection through, the server responds with a clear error on save:

2. You cannot downgrade from Production if you already issued accepted vouchers

Once your account is in Production and has issued at least one e-CF that the DGII has accepted (with status Aceptado or Aceptado Condicional), the Testing and Certification options become disabled in the selector. You will see: "It is not possible to downgrade from Production to Testing or Certification because you already issued accepted fiscal vouchers."

If for some reason the system let the selection through, the server responds:

This restriction is intentional. Downgrading to a sandbox environment after having vouchers in production creates two serious problems:

1. The next vouchers you issue will go to the wrong environment and you will create a discrepancy between what Mosce ERP records and what the DGII records - irreconcilable without support intervention.
2. Your monthly accounting before the DGII may end up incomplete or with crossed figures.

If for some exceptional case you need to downgrade from Production after having issued vouchers (for example, because the Production environment was activated by mistake and you do not want to keep operating there), contact support - the operation requires manual intervention.

3. If your certificate expires soon, we warn you

When you select Certification or Production and your P12 certificate expires in fewer than 30 days, Mosce ERP shows an inline warning above the Save button: "Your certificate expires in N days (DD-MM-YYYY). Consider renewing it before switching to Certification to avoid interruptions."

The warning does not block the operation - it is a reminder. If you end up using the environment with an expired certificate, the calls to the DGII will fail and the vouchers will remain in a pending status until you renew the certificate and retry.

Change the issuer's RNC

The RNC that appears in the fiscal configuration is the one Mosce ERP prints on each electronic voucher and the one the DGII uses to associate the issuance with your taxpayer. Changing it is not something you do routinely, but there are two valid cases:

• Before issuing - you correct an initial data-entry error (typically during account setup or integration setup).
• Special operations - mergers, spin-offs, formal changes to the legal name that the DGII has approved.

How to change the RNC

1. In Fiscal → Configuration, edit the RNC field.
2. Type the 9 digits of the company RNC or the 11 digits of the cédula (for individuals). Numbers only, no hyphens or spaces.
3. Press Save.

Mosce ERP validates the format on the client and on the server. If the length or content is not valid, you see the message "RNC must have exactly 9 or 11 numeric digits".

RNC change block after accepted issuances

Once your account has issued at least one e-CF that the DGII has accepted (status Aceptado or Aceptado Condicional), the RNC field is locked for editing from the interface. This is deliberate and for the same reasons that apply to the environment change:

• Vouchers already issued with an RNC are recorded before the DGII with that RNC and are fiscally binding.
• Changing the account's RNC would create an irreconcilable discrepancy between the internal Mosce ERP records and the official DGII records.

If you try to change the RNC with accepted vouchers in production, the server responds with:

If your case genuinely requires an RNC change in this scenario (for example, a formal legal merger), contact support - the operation requires a manual migration coordinated with the Mosce ERP team.

Fiscal address - maximum length

The Fiscal address field that Mosce ERP prints on each voucher and that the DGII expects inside the XML as <DireccionEmisor> has a maximum limit of 100 characters. The DGII rejects any e-CF whose address exceeds that length, so Mosce ERP validates and blocks saving if you go over the limit.

If your original address is longer than 100 characters, abbreviate common terms (Calle, Avenida, Provincia) and prioritize the essential data to identify the location. The abbreviated address must still be recognizable as your company's official address before the DGII.

Change audit

Every change to the DGII Environment and to the RNC is recorded in the account's audit log with:

• The user who made the change.
• The previous and the new value.
• The exact date and time.

You can review the log in Configuration → Audit log filtering by the entity Fiscal Configuration.

Frequently asked questions

Can I have accounts with different environments in the same business group?

Yes. The environment is configured per account (tenant). If you manage several companies in Mosce ERP, each one has its own independent DGII Environment selector.

What happens if I leave the environment "Unconfigured"?

Mosce ERP does not send vouchers to the DGII. Issuance requests are paused until you select an environment.

How do I know which voucher types I can issue in each environment?

All the e-CF types you list in your application (E31, E32, E33, E34, E41, E43, E44, E45, E46, E47) are available in all three environments. The difference is not what you can issue, but what fiscal effect the vouchers have.

Does changing the environment affect vouchers already issued?

No. Changing the environment only affects the next vouchers you issue. The previous ones remain recorded in the environment where they were originally issued.

Why is the Production option disabled even though I uploaded my certificate?

If your account never passed through Certification successfully (you did not reach Step 15 of the certification process), the DGII has not yet authorized you as an Electronic Issuer. In practice, even if the selector lets you choose Production, your vouchers will be rejected by the DGII until you complete the official certification. That is why the safest thing is not to switch to Production until you have the official DGII authorization in your email / Virtual Office Mailbox.

What do I do if I see "Invalid Signature" after switching to Certification?

Generally it means the uploaded certificate does not correspond to the representative registered in your RNC before the DGII. Check on the DGII portal that the representative's name and cédula match exactly those of the certificate. If they are out of sync, update the representative in the DGII Virtual Office (not in Mosce ERP) before continuing.

Related

• e-CF certification process - the 15 official steps you will go through in CERTECF.
• e-CF Certificate - how to upload your P12 before switching to Certification or Production.
• e-CF Documents - which voucher types you can issue and under which rules.
• e-CF configuration - the rest of the fiscal configuration (RNC, legal name, legal representative).

---

Last updated: 2026-06-10