DGII Reports

The DGII Reports automatically consolidate the month's movements and generate the files in the exact format the tax authority requires. Mosce ERP builds the 606, 607, 608 Formats and the IR-17 from your recorded purchases, sales, cancellations, and withholdings, and delivers them ready to upload to the Virtual Office.

Reading time: ~7 min

When to use this

• Month-end has arrived and you have to file the returns with DGII.
• You need to generate the 606 (Purchases), 607 (Sales), 608 (Cancellations), or the IR-17 (ISR withholding on third parties) for a specific month.
• You applied ITBIS or ISR withholding on your purchases and need the detail to file it.
• Your accountant asks for the files in the official DGII format for review and filing.
• You want to review the history of previously generated reports.

Before you start

• The Fiscal module is active and your role includes fiscal:read - enough to view the history, view a report's content, and download it. To generate a new report or delete an existing one you need fiscal:manage.
• The Fiscal Configuration is complete (RNC, legal name, regime) and saved.
• There is data to report in the period:
  • 606 - expenses / purchases recorded with a supplier voucher.
  • 607 - invoices and notes emitted with an e-CF (status Accepted or Conditional).
  • 608 - vouchers in Cancelled status in the month.
  • IR-17 - ISR withholding applied to third parties in the month.

What each report includes

Mosce ERP builds each file respecting DGII's current Technical Description for the format the Virtual Office requires.

The 606 Format and withholdings on purchases

When your business acts as a withholding agent and withholds ITBIS or ISR when purchasing (see ITBIS and ISR withholding on purchases), those amounts travel automatically to the 606 Format of each reportable purchase. The file is generated with the complete column structure DGII defines, including the withheld ITBIS, the type and amount of ISR withholding, and the payment date to the supplier. You do not have to fill in anything by hand: if the withholding was calculated when the purchase was received, it is reflected in the period's 606. (The official structure is in the Instructivo de llenado y envío del Formato 606 published by DGII at https://dgii.gov.do.)

The 607 Format and withholdings your clients apply

When a customer withholds ITBIS and/or ISR when paying you (see Collecting with third-party withholding), the 607 Format carries the date they withheld, how much ITBIS they withheld, and how much ISR they withheld, alongside the rest of that invoice's detail. These are filled in only when a withholding was actually recorded on that invoice's payment during the period being generated.

A credit invoice with a later withholding can appear in two periods, and that is correct. If you issue the invoice on credit in one month and the customer pays withholding in a later month, the 607 for the month of issuance declares it without that data - it was not yet known whether they would withhold - and the 607 for the month it was collected declares it again, with the same original issue date but now with the withholding filled in. For example: a June invoice, withheld on in August, appears in June's 607 with no withholding and in August's withheld. It is not a duplicate voucher: each appearance reports what belongs to its own period.

When you invoice and collect with a withholding the same day, the invoice appears only once, already with the withholding. If you have several partial withholdings on the same invoice in the same month, the 607 sums them and declares the most recent date.

If you refund an invoice whose withholding was already declared in a report that has already been generated, Mosce ERP detects it and flags it for manual review - it does not correct the file already filed nor void anything on its own, because the withholding certificate was issued by the customer and only the customer can correct or void it. Resolve it by talking to the customer.

Debit notes are included in the 607 too. A debit note (E33) you issue to increase the amount of an already-invoiced invoice is declared with its amount positive, referencing the number of the original voucher it adjusts - it is never declared separately or subtracted from anything.

The general consumer-invoice summary, apart from the file. When you upload the 607, the Virtual Office asks in a separate module for the period's total count of consumer invoices and their amount. Those two figures do not come from the file: the 607 detail only carries consumer invoices worth RD$250,000 or more (Norma General 10-18); smaller ones never travel in the .TXT, but they still count toward that separate summary. Mosce ERP computes both figures automatically over every accepted or conditional consumer e-CF in the period, regardless of amount, and shows them to you alongside the report - see Viewing a report before uploading it below.

How the 607 counts what you collected, and what happens with refunds

The 607's payment-method boxes (Cash, Cheque/Transfer/Deposit, Card, Credit Sale and the rest) declare the proportion of the sale's payment you received. That is why all of them together must add up to exactly the invoice total, which is what the format's official instructions require.

A refund is not subtracted from those boxes. If you returned money to the client, that amount does not reduce what the invoice declares as collected: the sale still states what was received for it, and the refund is declared separately, on its own credit note row. It is the same logic that applies to withholding - each fact is declared where it belongs, not netted off the previous one.

This can be surprising when you compare the 607 against the month's cash, so it is worth knowing before you treat a difference as an error. If you generated a file before this change and have not filed it yet, generate it again.

The ITBIS you keep on a late credit note

When you issue a credit note more than 30 days after the tax obligation arose, you return the price to the client but not the ITBIS: that tax stays with you. It is neither income nor does it disappear - it is declared as a positive adjustment in your monthly return, in the "Otras Operaciones (Positivas)" box of Annex A of the IT-1.

Mosce ERP does not file the IT-1, so it gives you the figure and its backing in the Late credit-note ITBIS report, under Reports. There you see, grouped by declarable month, how much ITBIS the business kept and which credit notes back it, one by one, with the affected voucher and the client. That is the number your accountant copies into the Virtual Office.

The report groups by the month the refund was processed, not the month of the original invoice, because that is the return that carries the adjustment.

The 608 Format and cancellations

The 608 Format declares the vouchers you cancelled during the period, with three pieces of data per line: the number of the cancelled voucher, the date that invoice was originally issued, and the cancellation reason.

The period is anchored to when you cancelled, not to when the original invoice was issued. An e-CF issued in March and cancelled in June is declared in June's 608, not March's - the report declares the act of cancelling, not the original sale. The original issue date still travels inside that same line, exactly as DGII requires; what changes is which period the whole line belongs to.

The cancellation reason comes from a closed DGII catalog, not free text. DGII defines ten possible reasons; six apply to an electronic voucher and are the ones you see when cancelling one: information correction, product change, product return, missing products, wrong voucher number, and business closure. The other four describe defects of pre-printed paper vouchers (deterioration, printing errors or defective printing on the paper, lost or stolen booklets) and make no sense for an e-CF, so they are not offered. You pick the reason when confirming the cancellation - see Void and modify e-CFs for that screen's detail.

Cap of 4,999 vouchers per file. That is the limit DGII itself sets for this format.

Minor Expenses in the 606 Format

The Voucher for Minor Expenses (E43) that you emit once a month to group the staff's minor expenses is automatically included in the 606 Format (Purchases of Goods and Services) of the period. You do not have to add it by hand: when you emit the monthly voucher, its amounts enter the 606 along with the rest of your reportable purchases. See Minor Expenses.

The IR-17 report

The IR-17 declares the ISR withholding on third parties you applied during the month, summarized by beneficiary. If you withheld ISR on service purchases (professional fees, technical services), that detail feeds the period's IR-17. It is generated per month like the rest of the formats.

Filing deadline: the 606 Format is filed no later than the 15th day of the month following the reported period. Always confirm DGII's current calendar with your tax advisor, since the deadlines may be adjusted.

Step by step

1. Open Fiscal → DGII Reports from the side menu.
2. In the top form:
   • Report type - Choose 606, 607, 608, or IR-17.
   • Year - Year of the period (e.g. 2026). Defaults to the current year.
   • Month - Month of the period (January to December). Defaults to the current month.
3. Press Generate report.
   • If that period (type, year, month) already has a generated report, Mosce ERP rejects the request immediately with a message that stays fixed on screen - not a notification that fades away - telling you to delete it first. Nothing gets queued.
   • If the period is free, Mosce ERP queues the job in the background and confirms right away that it was queued. Once the job runs, it queries the period's e-CFs, vouchers, and cancellations, applies the current DGII format, computes the file's SHA-256 hash for integrity, and persists the result.
4. While the job runs in the background you see an indicator next to the form. You can close the page and come back later: the report keeps generating regardless, and shows up on its own in the Report history as soon as it finishes.
5. When it finishes, the Download button appears next to the form and the row is added to the history.
6. If generation fails, a message fixed on screen tells you why, instead of leaving the indicator spinning forever. If a while passes with no success or failure signal at all, Mosce ERP also warns you to check the history or try again, instead of leaving you waiting indefinitely.

Report history

Below the form, the Report history table lists each generated report with:

• Type - 606 / 607 / 608 / IR-17.
• Period - year and month.
• Generated - date and time it finished generating.
• Actions - view, download, or delete.

A row only appears here once the report has finished generating. While the job runs in the background, or if it fails, what you see is the message next to the Generate report button - described in the step-by-step above - not a row with an intermediate status in this table.

There is only one report per (type, year, month), and it is not replaced on its own. To redo a period you already generated, use the Delete button on that row - it asks for confirmation, and the deletion is permanent: you will need to generate the report again if you need it.

The reason for this lock: the 606/607/608 is the file you file with DGII. If it could be swapped out quietly, there would be no way to know afterward which version was actually filed. Deleting and regenerating stay as two deliberate acts, and both are logged.

You can filter the history by format type, year, and month. The filters you choose travel in the page's URL, so you can share the link with that filtered view already applied or refresh the page without losing it.

Viewing a report before uploading it

Each row in the history has a View button that opens the file's content exactly as it is, before downloading it.

For the 606 and 607 formats, besides the full content, the viewer shows the header (issuer RNC, period, and declared record count), how many detail lines the file actually has, and tells you if those two numbers don't match. DGII rejects a file where the header's declared count doesn't match the detail lines, so it's better to find out from Mosce ERP than when uploading it to the Virtual Office.

For 607 specifically, the viewer also adds the general consumer-invoice summary described above.

Upload to DGII

The downloaded file is in the exact format the Virtual Office requires:

1. Log in to DGII → Virtual Office with your certificate.
2. Look for the Envío de Datos → 606 / 607 / 608 section as applicable.
3. Upload the file downloaded from Mosce ERP.
4. DGII issues you an acknowledgment of receipt. Save it as proof of filing.

A period with no operations is not skipped. If a month's 606, 607, or 608 comes out empty because you genuinely had no purchases, sales, or cancellations to declare, you still have to file it - informationally, at zero - from the Virtual Office itself, under Declaraciones Juradas → Declaraciones en Cero, choosing the format and the matching period. This is not a file you generate in Mosce ERP: it's a separate step you do directly on DGII's portal.

Expected result

• File in the official DGII format downloaded to your computer.
• SHA-256 hash computed and persisted to verify integrity.
• Visible history with each report generated per (type, year, month).
• Reports ready to upload to DGII's Virtual Office within the legal deadline.

Common errors

Related

• e-CF Documents
• Void and modify e-CFs - how a voucher gets cancelled and how the reason declared on the 608 is chosen.
• Fiscal configuration
• e-CF sequences
• e-CF certificate
• ITBIS and other taxes - ITBIS and ISR withholding on purchases.
• Payments and payment methods - recording the withholding a customer applies when paying.
• Minor Expenses - the E43 voucher that feeds the period's 606.
• Purchases - withholding preview on receipt.