NextERP Documentation
ROEN

Returns setup · Article 03

Declarations and Registers: what the company files and when

Applies to Odoo 19 · 20

Odoo knows which returns the company files, how often and by when, from the list of tax obligations. The list is proposed automatically from the company's fiscal profile, according to the rules of the NextERP declarations server, and the accountant checks and confirms it. From each confirmed obligation, Odoo creates the filings for ended periods by itself and puts them in the ANAF Declarations › Schedule calendar, with the legal deadline. The legal registers, reports and monthly archives are scheduled from the same list.

When to use

  • You are setting up the company for the first time and want returns to appear in the schedule by themselves.
  • The tax regime changed (for example moving from micro-enterprise tax to profit tax) or the VAT frequency changed.
  • A return is missing from the schedule, one appears that the company does not file, or the deadline is wrong.
  • You must file a return that has no frequency, only at the request of ANAF (for example D406 Stocks).

Before you start

  • The company's NextERP subscription is active: the obligation rules come from the declarations server.
  • The fiscal profile valid today is filled in under ANAF Declarations › Configuration › General › Fiscal Profile (see Fiscal profile and frequency). Without it, the proposal stops with a message that the fiscal profile must be recorded first.
  • You work with accounting administrator rights: only an administrator can propose and confirm obligations.

Steps in Odoo

1. Propose the obligations from the fiscal profile

Open ANAF Declarations › Configuration › General › Declarations and Registers and click Propose from Fiscal Profile. Odoo reads the server rules and applies them to the fiscal profile valid today:

Return Proposed when Proposed frequency Proposed deadline
D300 the VAT return the company is a VAT payer the VAT frequency in the profile 25th of the following month
D394 the company is a VAT payer the VAT frequency in the profile 30th of the following month
D390 the company is a VAT payer monthly, marked optional: only in months with intra-community operations 25th of the following month
D100 profit tax or micro-enterprise regime monthly 25th of the following month
D101 profit tax regime yearly 25th, 6 months after year end
D112 the company has employees (payroll frequency in the profile) monthly 25th of the following month
Bilanț (S1002, S1003, S1005) profit tax or micro-enterprise regime yearly, optional: choose the form by company size 30th, 5 months after year end
S1004 annual reports profit tax or micro-enterprise regime yearly, optional: only for a financial year different from the calendar year 1st, 3 months after year end
D318 the company is a VAT payer yearly, optional 30 September of the following year
D120 and D9 there are journal entries with excise tags (D120 ...) in the last 12 months monthly, optional D120: 25th; D9: 15th of the following month
Intrastat arrivals / dispatches the intra-community value of goods in the previous year, or cumulated in the current year, exceeds the INS threshold (1,000,000 lei per flow, in 2025 and 2026) monthly, optional 15th of the following month
D406 SAF-T monthly always monthly last day of the following month
D406 Assets always yearly last day, 3 months after year end
D406 Stocks always On Request no fixed deadline

Short glossary: D100 (Declarația privind obligațiile de plată la bugetul de stat, the return of payment obligations to the state budget), D101 (the annual profit tax return), D112 (the payroll contributions return), D318 (the VAT refund return for non-established persons), D120 (Decontul privind accizele, the excise return), INS (Institutul Național de Statistică, the National Institute of Statistics).

The Intrastat threshold is measured on the taxable base of the VAT report tags: lines 5, 5.1 and 6 for arrivals, lines 1 and 2 for dispatches. D398 (OSS) is not proposed from the profile; add it manually if the company makes distance sales under OSS.

New obligations appear with the status Proposed. Clicking Propose from Fiscal Profile again updates the proposals and deletes those whose rule no longer applies; obligations already confirmed are not touched. At the same time Odoo fetches the nomenclature of return codes (the D100, D120, D394, D318, D406 codes) and the ANAF calendar with the exact deadlines.

2. Add the registers and reports

Click Add Registers and Reports. Odoo adds the legal registers (Registrul-jurnal the general journal, Cartea mare the general ledger, Registrul-inventar the inventory register, the tax records register, the cash register, the sales and purchase journals) and the reports, with the frequency and deadline published by the server or, where there is no legal deadline, monthly, by the last day of the following month. Aged balances and the bank register stay On Request. Details are in The legal registers.

3. Check each obligation

The list is grouped by category: Declaration, Register, Report and Archive. On each line check:

  • Periodicity: monthly, quarterly, half-yearly, yearly or On Request. For D300 and D394 it must be the same as the VAT frequency in the fiscal profile.
  • Applies From: the first day of the first period filed with this frequency. By default it is the start of the current year, but not earlier than the date of the fiscal profile, so that the months of the year already ended are filed too. Change the date if the company started its activity later or if Odoo takes over only from a given month.
  • Deadline Months and Deadline Day: the deadline is computed from the end of the period; for example 1 and 25 mean the 25th of the following month, and day 31 means the last day of the month. The Deadline column shows the deadline in words. If ANAF moves the deadline (public holiday, non-working day), Odoo uses the exact date from the ANAF calendar, at most one week later.
  • Description and the server note: they explain why the obligation was proposed or when it applies (for example D390 only in months with intra-community operations).

Delete the proposals that do not concern the company (for example the balance sheet forms that do not match its size) or deactivate them.

4. Confirm the obligations

Select the checked obligations and click Confirm. Only confirmed obligations create filings. The Generated Automatically column shows that the obligation is confirmed, active and has a frequency; On Request obligations are not scheduled automatically.

When you confirm a new obligation for the same return, the old one closes by itself: Applies Until gets the day before the new start date. A confirmed obligation can no longer be changed (frequency, dates, deadline); for a change, create a new obligation from the date it applies. Reset to Proposed returns an obligation to the proposal stage.

5. Filings appear in the schedule

Once a day, Odoo creates the missing filings for all ended periods of confirmed obligations, each with its deadline, and refreshes the ANAF calendar. To avoid waiting, select the obligations in the list and use the Create Filings for Ended Periods action. A period that already has a filing is not duplicated.

6. Work from the Schedule

ANAF Declarations › Schedule shows the filings by month, in four segments: Declarations, Registers, Reports and Archives. The To Do, Late, Done, All and Archived filters show what is left to do, what is late and what has been filed. The screen is described in The filing schedule; for each filing follow How to file a return.

7. Add an on-request filing

The + card in the Schedule (Add a filing manually) opens a new filing in the current segment. The full steps are in On-request returns. Use it for On Request obligations (D406 Stocks, at the request of ANAF), for an optional return in a given month (D390, Intrastat) or for a missing period. Choose the return and the period, then work as with any filing.

Variants

The tax regime or the frequency changed

First add a new line in the fiscal profile, from the date of the change, then click Propose from Fiscal Profile again. New obligations are proposed for the affected returns; change Applies From to the date of the change and confirm them. The old obligations close automatically one day before, and filings already created stay unchanged.

D100 and D112

The payment obligation codes are in a single nomenclature, synchronised from the server: the D100 codes (profit tax, micro-enterprise tax, dividends, excise duties, non-residents, etc.) and the codes of section A of D112 (CAS, CASS, income tax on salaries, CAM — the Romanian pension, health and work insurance contributions). The D112 codes come with the synchronisation of the D112 version and are not configured on taxes. The contribution to the fund for persons with disabilities is not computed on payslips: it is declared through D100. The D100 obligation stays monthly; the quarterly codes (103, 121) appear only in March, June, September and December, with the quarter's amount, and codes with a zero amount are not declared.

Optional return with no operations in the month

D390, D120, D9 and Intrastat are marked optional. If the month has no operations, do not file D390; for Intrastat, months without operations are filed as a nil return. Archive the filing that must not be sent.

Common mistakes

  • Obligations left in Proposed. Proposals do not create filings. Confirm them.
  • D300 frequency different from the profile. The return is computed on a different period from the one declared to ANAF. Correct the profile and propose again.
  • Start date too late. The months between the start of the year and the chosen date do not appear in the schedule. Create the obligation with the correct date.
  • Changing a confirmed obligation. Odoo refuses it: create a new obligation from the date of the change.
  • Looking for D406 Stocks in the schedule. Being on request, it does not appear by itself: add it with the + card.
For the accountant: where the rules come from
  • The rules (when they apply, frequency, deadline, note) are published by the NextERP declarations server and applied to the fiscal profile valid on the day of the proposal. For D120 and D9, Odoo looks for journal entries with the excise tags in the last 12 months; for Intrastat, it compares the base of the intra-community tags with the INS threshold for the year.
  • Each filing keeps the deadline computed at creation; an update of the ANAF calendar moves the deadline of filings not yet filed.
  • With Odoo Enterprise, the same obligations set the frequency and deadlines in Accounting › Accounting › Closing › Tax Returns.
Documentation by the NextERP team.