NextERP Documentation
ROEN

ANAF returns · Article 15

D390: ANAF versions

Applies to Odoo 19 · 20

ANAF periodically changes the structure of D390 (Declarația recapitulativă, the EC sales and purchases list). This page lists the versions applied by the NextERP declarations server, the period from which each one applies, what changes in the file and what to check in Odoo. The right version is selected automatically from the period of the return; do not choose it manually.

Versions

Version Applies from Details
v41 12 February 2021 what changes
v3 18 March 2020 what changes
2017-02-01 1 February 2017 what changes
2013-07-29 29 July 2013 what changes

Version v41, from February 2021

Applies to returns for periods starting with February 2021 (12 February 2021)
Replaces v3

What changes

Compared with the previous version, the D390 file has: 5 fields with changed rules.

  • 3 fields become mandatory.
  • New allowed values (3 fields): XI.
Detail: structural differences in the XML file

Version identifier in the file: mfp:anaf:dgti:d390:declaratie:v3.

Fields with changed rules

Section Field What changes
cos cod_m1 becomes mandatory
cos tara_m1 becomes mandatory; new values: XI; removed values: GB
cos tara_m2 new values: XI; removed values: GB
cos tip becomes mandatory
operatie tara new values: XI; removed values: GB

What to configure in Odoo

The configuration rules of the previous version still apply. From February 2021, the United Kingdom is no longer a member state: operations with Northern Ireland are declared with the country code XI (instead of GB). On partners from Northern Ireland, the VAT number must have the XI prefix and be valid in VIES. Partners from the rest of the United Kingdom no longer appear in D390. In the call-off stock section, the customer code and country and the operation type become mandatory.

Version v3, from March 2020

Applies to returns for periods starting with March 2020 (18 March 2020)
Replaces 2017-02-01

What changes

Compared with the previous version, the D390 file has: 6 new fields, 1 fields with changed rules, 1 new sections.

  • 6 new fields, in the same section; 3 are required, without them the file fails the ANAF validation.
  • New allowed values (1 fields): XI.
  • Sections: 1 new, 0 removed.
Detail: the structural differences of the XML file

Version identifier in the file: mfp:anaf:dgti:d390:declaratie:v3.

New sections: cos.

New fields

Section Field Required Format
cos cod_m1 yes string; max. 12 characters
cos cod_m2 no string; max. 12 characters
cos motiv no integer; 1–3
cos tara_m1 yes string; max. 2 characters; values: AT, BE, BG, CZ, CY, DK, EE, DE (+19)
cos tara_m2 no string; max. 2 characters; values: AT, BE, BG, CZ, CY, DK, EE, DE (+19)
cos tip yes string; max. 1 characters; values: A, B

Fields with changed rules

Section Field What changes
operatie tara new values: XI; removed values: GB

Version 2017-02-01, from February 2017

Applies to returns for periods starting with February 2017 (1 February 2017)
Replaces 2013-07-29

What changes

Compared with the previous version, the D390 file has: 1 new fields, 2 fields with changed rules.

  • 1 new fields, in the same section; 1 are required, without them the file fails the ANAF validation.
  • New allowed values (1 fields): R.
  • 1 fields have other length, format or value limits.
Detail: the structural differences of the XML file

Version identifier in the file: mfp:anaf:dgti:d390:declaratie:v2.

New fields

Section Field Required Format
rezumat bazaR yes integer; -999999999999999999–999999999999999999

Fields with changed rules

Section Field What changes
declaratie390 an minimum: 2011 → 2017
operatie tip new values: R

Version 2013-07-29, from July 2013

Applies to returns for periods starting with July 2013 (29 July 2013)

What changes

The first version of the return in the NextERP catalogue; there is no earlier version to compare it with.

What to configure in Odoo

For this version, the oldest in the catalogue, below are all the configuration rules D390 needs. The next version describes only what changes.

The obligation

The obligation. D390 is proposed from the fiscal profile for VAT-registered companies, monthly, with the deadline the 25th of the following month, marked optional: it is filed only in months with intra-community supplies or acquisitions. Confirm the obligation; in months without operations, archive the filing from Schedule. The steps are in Obligations and filing schedule.

Taxes and tags

The return includes the lines of posted invoices that have an intra-community VAT report tag, to type 3 partners (see below). Plain journal entries without VAT are not included, even if the partner is from the EU. The operation type:

Type When
L supply of goods customer invoice, goods product
P supply of services customer invoice, service product
A acquisition of goods vendor bill, goods product
S acquisition of services vendor bill, service product
T triangular operation sales line with the Triangular Operation checkbox

An intra-community tax without tags appears neither in D390 nor in D300. The total by type must equal the corresponding D300 (Decont de TVA, the VAT return) rows for the same month.

Accounts

No accounts are mapped: the operations come from the tax tags, whatever the account.

Analytics

The return does not use the Odoo analytic plans (analytic accounts by project, department or activity): a separate activity is not declared separately through them.

Partners

The partner must be a company (Is a Company), from an EU state, with a VAT number valid in VIES, with the country prefix, and with the country filled in. An EU partner without a valid VIES number does not appear in D390. Greece is declared with the EL prefix.

Company configuration requirements

Documentation by the NextERP team.