Fiscal configuration
Electronic issuer data (RNC, legal name, trade name, branch), environment selector, and certificate decision. Mandatory base to issue electronic fiscal vouchers.
The Fiscal configuration is the first step to activate the issuance of electronic fiscal vouchers (e-CF). Here you register the taxpayer's RNC, the legal name, the optional trade name and branch data, the operating environment (testing, certification or production), and whether you are going to sign with the platform certificate or your own. Without this configuration, the rest of the Fiscal module is locked.
Reading time: ~7 min
Paper Series B is not configured here.
Mosce ERP does not generate or store sequences of non-electronic fiscal vouchers (Series B). If the system enters Technical Incapacity, the taxpayer must use its pre-printed Series B booklet off-platform. Mosce ERP retrieves those numbers when the service is restored to issue the replacement e-CFs within the regulated 30-day window. Details in Contingency and backup plans.
When to use this
- You activated the Fiscal module for the first time and need to configure the issuer data.
- The fiscal address registered with the DGII changed and you must update it in Mosce ERP.
- You want to change the default e-CF type that appears when creating invoices.
- You are going to switch between the testing and production environments.
- You are going to start issuing e-CF with your own certificate and need to review the base data.
Before you start
- Your role includes the
fiscal:managepermission. Read access is not enough to save changes. - You have the taxpayer's RNC at hand (in the format the DGII uses, e.g.
101-23456-7or without hyphens). - You know the legal name exactly as it is registered before the DGII - it must match letter by letter the information in the Mercantile Registry.
- You know the business's tax regime: Ordinary, Simplified, or Special.
- You have decided whether you sign with the platform certificate (default option, recommended to start) or with your own certificate uploaded by you. See e-CF Certificate.
Step by step
- Open Fiscal → Configuration from the side menu.
- Fill in the form fields:
- RNC - Taxpayer's RNC or cédula number. Important: once saved for the first time, this field is locked. If you make a mistake, contact support to correct it.
- Legal name - Fiscal name exactly as it is registered with the DGII.
- Trade name (optional) - The name the business operates under commercially, if it differs from the legal name. When you fill it in, it appears in the header of the e-CF Printed Representation (RI) above the legal name.
- Branch (optional, maximum 20 characters per DGII) - Name of the branch that issues the vouchers. Useful when the taxpayer operates with several locations and wants to identify them in the e-CF header.
- Fiscal address - Address registered before the DGII for the taxpayer.
- Tax regime - Choose between Ordinary, Simplified, or Special.
- Default e-CF type - The voucher type that is preselected when invoicing. The most common is E31 - Fiscal Credit Invoice or E32 - Consumer Invoice.
- Press Save. If the RNC already existed, the button saves only the other fields.
- Review the Operating environment section and the Certificate mode card (details in the following sections).
Environment selector
The environment selector determines which DGII environment the e-CF are sent to:
| Environment | When to use it |
|---|---|
| Testing | During development and initial integration. The e-CF are sent to the DGII testing environment and have no fiscal value. |
| Certification | During the formal certification process before the DGII to become an authorized electronic issuer. |
| Production | Once the certification process is complete. The sent e-CF have full fiscal validity. |
Never use the Production environment until you have completed the certification process with the DGII. The e-CF sent in production have real fiscal effects. See Certification process for the step by step.
Available e-CF types
| Code | Name |
|---|---|
| E31 | Fiscal Credit Invoice |
| E32 | Consumer Invoice |
| E33 | Debit Note |
| E34 | Credit Note |
| E41 | Purchases |
| E43 | Minor Expenses |
| E44 | Special Accounting Regime |
| E45 | Governmental |
| E46 | Export |
| E47 | Payment Abroad |
The default type is used to preselect in the invoice form, but you can change it manually when issuing each document.
Certificate mode
Mosce ERP offers two modes to sign the e-CF:
Platform certificate (recommended to start)
Mosce ERP signs the e-CF with a central certificate maintained by the platform team. You do not have to upload anything - only confirm the delegation with the DGII.
When you use the Mosce ERP central certificate, the DGII requires you to register an electronic signature delegation in the Virtual Office authorizing the platform's RNC to sign vouchers on your behalf.
Steps:
- Enter DGII → Virtual Office with your taxpayer certificate.
- Find the Electronic signature delegation option and register the platform's RNC as the authorized agent.
- Go back to Mosce ERP, to Fiscal → Configuration, and press I already registered the delegation. The confirmation date is saved and the card changes to Confirmed status.
Without this step confirmed, the e-CF will be rejected by the DGII.
Own certificate
If your organization already has a digital certificate issued by the DGII and prefers to use it directly, you can upload it from the Certificate tab. See e-CF Certificate for the complete upload and validation process.
Expected result
- Taxpayer data saved and visible in the Configuration tab.
- RNC locked after the first save (with a clarifying message).
- Operating environment clearly indicated: Testing, Certification, or Production.
- Certificate mode clearly indicated: Platform or Own.
- If you use the platform certificate, the delegation is confirmed with a visible date.
Common errors
| Error | Cause | Solution |
|---|---|---|
| I cannot edit the RNC | It was already saved once (field locked for fiscal security) | Contact support for corrections |
| The RNC is valid but the DGII rejects the e-CF | You have not yet confirmed the platform signature delegation | Register the delegation in the DGII Virtual Office and press I already registered the delegation |
| The Fiscal tab does not appear in the menu | The Fiscal module is not active or the fiscal:read permission is missing | Ask the administrator to activate the module and assign the permission |
| The Save button is disabled | Your role does not have fiscal:manage | Ask the administrator to update your permissions |
| Legal name rejected by the DGII | It does not match exactly the Mercantile Registry | Copy the exact text from your RNC certificate and save again |
| I issued in Production when it should have been Testing | Wrong environment on save | Change the selector to Testing and save; e-CF issued in the wrong environment have different effects |