Features

• D100 and D710 in one wizard — l10n.ro.anaf.d100.v2 emits both forms (<declaratie100> namespace mfp:anaf:dgti:d100:declaratie:v2 and <declaratie710> namespace mfp:anaf:dgti:d710:declaratie:v1). The declaration type selects the root element only.
• Complete obligation nomenclator — about 107 records in l10n.ro.anaf.d100.config covering income tax, micro-enterprise tax, dividend tax, excises, withholding taxes, gambling, construction, special funds, royalties, disability fund (810), Pillar 2 (131, 132), electricity producer levies and recent 2026 additions (logistics tax 707, energy transition fund 708).
• Computed payment deadline (scadenta) — derived from period_type (L monthly / T quarterly / S semi-annual / A annual): the 25th of the next month, rolling forward at quarter end and across year boundaries.
• Unique 23-digit nr_evid — generated per obligation line with checksum, in the ANAF format 10<cod:3>01<MM><YY><scadenta:6>0000<checksum:2>.
• Auto-computation from accounting — for obligations with a standard PCG RO account range (corporate income tax 441100–441199, micro tax 441800–441899, dividend tax 446200–446299, disability fund 446500–446599) the wizard fills the obligation lines from posted move lines over the wizard period.
• Manual lines for industry-specific obligations (excise, gambling, mining royalties, offshore wind, electricity producers, medicine clawback) that depend on each company's analytical accounts.
• PDF preview report — the d100_v2_report and d100_v2_report_excise QWeb templates render the populated wizard for internal review and archiving.
• Special situations supported — successor filing (d_succ, cifS), cancellation of reserve (d_anulare), dissolution without liquidation (d_dizolv) and legal basis (temei) for article 105 alin.(6) cases.
• XSD validation before download — output is checked against the ANAF schema d100_24022022.xsd (D100) or d710_20012025.xsd (D710); a new XSD is added as a sibling submodule under models/v<N>/ when ANAF publishes one.

Configuration

1. Prerequisites

Complete the setup described in the l10n_ro_declaration base module shipped with this one:

• Romanian VAT/CUI on the company.
• At least one ANAF signature record (declarant name, function, CNP/CUI) under Accounting → Configuration → Romania → ANAF Signatures.
• The company bank account used for budget payments.
• The CAEN code, address, phone and e-mail on the company record.

2. Review the obligation nomenclator

About 107 D100 obligation codes are loaded as configuration records in l10n.ro.anaf.d100.config. Open Accounting → Configuration → Romania → D100 — Obligation Configuration and check the records relevant to your company:

3. Map your analytical accounts

Out of the box only the obligations using standardized PCG RO sub-accounts are pre-mapped (about 12 of the 107):

The remaining sector-specific obligations (excise duties, gambling fees, mining and oil royalties, offshore wind, electricity producer levies, medicine clawback, etc.) are intentionally left without an account range because PCG RO does not standardize sub-accounts below 4 digits. For each obligation your company is liable for, open the config record and fill Account Code From / To with the analytical range you book the liability on (typically a sub-account of 446 or 447). If you leave the range empty the obligation still works — the amount has to be entered manually on the wizard line.

4. D710 menu entry

D710 is the rectifying form of a previously submitted D100. The module adds a dedicated menu Accounting → Reports → Romania → D710 Declaration that opens the same wizard pre-set to emit the <declaratie710> root element and namespace. No separate nomenclator is needed — compute_from_config searches across both declarations.

5. Run the declaration

After configuration, generate the declaration as described in USAGE.md.

How it works

Open Accounting → Reports → Romania → D100 Declaration for the regular form, or Accounting → Reports → Romania → D710 Declaration for the rectifying form. The wizard layout is identical — only the namespace and root element of the generated XML differ.

Steps

1. Header fields

   • Declaration / Version — defaults to D100 / Versiunea 2 (or D710 v1).
   • Date From / Date To — defaults to the previous calendar month; change to a quarter / semester / year if you file for a longer period.
   • Signature — pick the ANAF signature configured for the declarant.
   • Bank Account — the company account from which obligations are paid.

2. Special situations — toggle only if applicable:

   • Temei — set to art. 105 alin.(6) Codul de Procedură Fiscală when filing under that legal basis.
   • Succesor — filing on behalf of a successor entity (art.90 alin.4) populates d_succ and cifS in the XML.
   • D_anulare — for the specific case in art.42 alin.4^1 Cod Fiscal (cancellation of reserve).
   • D_dizolv — set to Yes when filing at the point of dissolution.

3. Compute from accounting — click Compute from Accounting. The wizard reads account_code_from–account_code_to for each nomenclator line and fills the obligation lines table. The wizard re-opens with the populated lines so you can review.

4. Adjust the obligations table

   • Add lines for sector-specific obligations (excise, gambling, mining, etc.) that aren't pre-mapped.
   • Override suma_dat, suma_ded, suma_plata or suma_rest as needed.
   • Remove lines that don't apply.

5. Get Report — generates the XML, validates it against d100_24022022.xsd (D100) or d710_20012025.xsd (D710) and attaches the file to the wizard for download.

   

6. PDF preview — the bundled d100_v2_report and d100_v2_report_excise QWeb templates can be printed from the wizard for internal review and archiving.

7. Validate with DUKIntegrator, sign with the digital signature (Sectigo / certSIGN / other token), then upload to ANAF at the Depunere declarații portal under D100 or D710.

Generated XML — key fields

• Root <declaratie100> (or <declaratie710>) with attributes luna, an, cui, den, adresa, nume_declar, prenume_declar, functie_declar and totalPlata_A.
• One <obligatie> child per obligation line with cod_oblig, cod_bugetar, scadenta (DD.MM.YYYY), the 23-digit nr_evid and the suma_* amounts (zero amounts are omitted).

Deadlines (scadenta)

Versions

19.0.1.1.0 (2026-05-24)

• Changelog tracking starts at this release.