Returns setup · Article 08
Configuration checklist
Applies to Odoo 19 · 20
Each version of a return comes from the declarations server with a short list of configuration requirements: what must be set in Odoo so that the company can calculate the return correctly (fiscal profile, taxes, invoice series, payroll accounts and so on). Odoo creates the requirements for the company when it synchronises the version, and the accountant checks and confirms them once. As long as a requirement of the version is unconfirmed, Odoo does not calculate or generate the return. This article shows how the check works and, further down, describes each requirement.
When to use
- You are configuring the company for the first return of a given type.
- When calculating, Odoo shows a message that the return has configuration requirements to confirm.
- The server has published a new version of the return or changed the guide of a requirement, and the requirement is back up for review.
Before you start
- The company's NextERP subscription is active and the return versions are synchronised.
- The list of returns the company files is confirmed in ANAF Declarations › Configuration › General › Declarations and Registers: requirements appear only for the returns the company files. How to propose and confirm the list: Obligations and filing schedule.
- Confirming requirements needs accounting administrator rights.
Steps in Odoo
1. Open the list of requirements to confirm
ANAF Declarations › Configuration Checklist. The menu is shown only while there is something to confirm. The list shows, grouped by return, the requirements of the current versions of the returns the company files. The full list, with all versions and the requirements already confirmed, is in ANAF Declarations › Configuration › General › Checklist.
You see the same information on the return version: the Company Checks column shows how many requirements are still to confirm, and the Company Configuration / Guides tab lists them.
2. Open the requirement and its guide
Each requirement has a name, a summary and an Open guide link. The link first goes to the requirement's section in this article; if the requirement has no section of its own, it goes to the page of the return version and, as a last resort, to the article about the return.
| Status | Meaning |
|---|---|
| Needs Configuration | The requirement has not yet been confirmed for the company |
| Needs Review | It was confirmed, but the guide has changed or you edited the notes: check it again |
| Ready | Confirmed for the guide currently in force |
| Removed / Historical | The requirement no longer exists in the approved configuration of the version |
3. Do the configuration in Odoo
The configuration itself is done where the guide points (fiscal profile, taxes, journals, partners, salary rules). When the guide asks for rows calculated from journal entries, the Configure Journal Item Rows button opens the rows of the version directly; the Rows to Configure field shows which rows are concerned.
4. Note what you checked
In Company Configuration / Evidence write the company's decision briefly, for example "quarterly profit tax from 4411; code 604 does not apply". If a requirement does not concern the company, clear Applicable and explain why in the notes.
5. Confirm the requirement
Click Confirm Configuration on the requirement, or select several in the list and click Confirm Selected. The requirement moves to Ready. For requirements with an automatic check, Odoo runs the check first; if it is Failed, confirmation stops until you fix the data or fill in the Manual Confirmation Reason (see below). When nothing is left to confirm, the Configuration Checklist menu disappears.
Automatic checks
Many requirements have an Auto Check: Odoo checks by itself, from the company data, whether the requirement is met (for example that taxes have tags or that partners have a tax ID). The result is shown on the requirement in Check Result, with the Checked Period (by default the last ended month) and Checked On; the check state is Passed, Failed or Not Applicable.
- Check Now runs the check again after you fixed the data.
- If the check fails but the situation is correct for the company (for example VAT adjusted manually), write the reason in Manual Confirmation Reason and confirm the requirement. The reason stays on the requirement, for control.
- Requirements without an automatic check are confirmed after the manual check described in their guide (Open guide).
What Odoo checks before calculating
On Calculate on Server and Generate XML, Odoo looks up the return version valid for the period and checks its requirements for the company:
- if the version does not have its requirements synchronised yet, a message says they must be synchronised first;
- if a requirement is in Needs Configuration or Needs Review, or is missing for the company, the calculation stops with the message "… has N company configuration requirements to confirm", and the Open the requirements button opens exactly the requirements of that version.
Confirming calculates nothing and does not change the formulas of the return: it only records that the company has checked the configuration. Formulas and validations come approved from the server.
Common mistakes
- Confirming without configuring. Confirmation does not fix a tax without a tag or a wrong account. Do the configuration indicated by the guide first.
- Notes edited after confirmation. Any change to the notes or to Applicable sends the requirement back for review.
- The requirement does not appear. The return is not in the company's Declarations and Registers list, or its version is not the current one.
Configuration requirements
The sections below are the target of the Open guide link on each requirement. Some requirements appear under slightly different names in different versions of the same return; they point to the same section.
Company data, signatory and period
The header of every return is taken from the company data and the signature. Check:
- the company's name, tax ID (with the RO prefix for VAT payers), registered address, phone and email;
- the company's main bank account, when the return asks for it;
- the default signatory, in ANAF Declarations › Configuration › General › Signatures: name, position and, where relevant, who prepares the return;
- the company's fiscal year, for annual returns.
The form version is chosen automatically from the period of the return; do not choose it manually. Returns already filed do not change when you change the company data.
Fiscal profile and periodicity
ANAF Declarations › Configuration › General › Fiscal Profile. Add a line with the date from which it applies and fill in:
- the tax regime: profit tax, micro-enterprise income tax or specific tax;
- the profit tax periodicity: quarterly or annual, with advance payments;
- the VAT periodicity (monthly, quarterly, half-yearly or annual) and that of the payroll returns.
From the profile, Odoo knows which obligations are due each month. For example, quarterly profit tax appears only in March, June, September and December. The D300 (Decont de TVA, the VAT return) in Declarations and Registers must have the same periodicity as the profile; after a profile change, propose the obligations again, as in Obligations and filing schedule. VAT on collection (cash accounting for VAT) is not configured here: it is taken from fiscal positions and invoice taxes.
When the regime changes (for example from micro-enterprise to profit tax), close the old line and add a new one from the date of the change.
Taxes and VAT report tags
D300 is calculated from the VAT report tags set on taxes. The mapping between tags and return rows, for each ANAF version, comes from the server and is not configured manually.
In Accounting › Configuration › Accounting › Taxes open each tax in use and check, in its definition, that both the base and the VAT have a tag. The most common problems:
- taxes with no tag at all (for example an exempt intra-community purchase tax): their invoices are missing from the return;
- import of services under reverse charge configured with the base only, without collected and deducted VAT: the amount does not reach the return;
- intra-community purchases declared as exempt instead of reverse charge.
The Odoo VAT report uses the same tags: if an amount is missing there, it is missing from the return too. Changing a tax does not correct invoices already posted; check them separately.
Invoice series
For D394 (Declarația informativă privind livrările/prestările și achizițiile efectuate pe teritoriul național, the domestic supplies and purchases statement), invoice series are taken from the sales journals. On the journal, the sequence type (own invoices, self-billing, invoices issued by third parties) decides the section in which the series appears, and the number range is taken from the journal numbering. Cancelled invoices and reversals are reported automatically.
Partners and operation type
D394 is filled in from the invoices of the period, grouped by partner, operation type and rate.
- Partner type (VAT payer, non-payer, foreign) comes from the partner's tax ID and country: fill in the tax ID on every company.
- Operation type (supply, purchase, reverse-charge purchase and so on) comes from the invoice taxes and fiscal position; you see it on the invoice line.
- ANAF product code, for reverse-charge operations, is set on the product.
If a partner appears wrongly, correct the partner or the invoice and recalculate in a new document.
Intra-community operations
D390 (Declarația recapitulativă, the EC sales and purchases list) is filled in from invoices with EU partners that carry the intra-community supply or purchase tags of the VAT report.
- The partner has a VAT number valid in VIES, with the country prefix, and the country filled in.
- The intra-community tax has tags: a tax without tags appears neither in D390 nor in D300.
- Triangular operations are marked on the invoice line.
D100 obligations
D100 (Declarația privind obligațiile de plată la bugetul de stat, the return of payment obligations to the state budget) contains several obligations, each with its own code and amounts due, deductible, payable and refundable. Check which codes the company owes (profit tax, micro-enterprise tax, dividend tax, tax withheld from non-residents and so on) and that each is calculated from its own account; a single rate is not applied to all obligations. The codes due in a month follow from the fiscal profile and the confirmed D100 obligation; the codes of the D112 (payroll contributions return) obligations are in the same code list (see D100 and D112). The accountant confirms the codes and the tax treatment that apply to the company.
The profit tax account (D100, code 103)
In D100, the profit tax (obligation code 103) is taken from the credit turnover of the account in which the company records the tax due. By default it is 4411 Profit tax: the amount on row 103 is the tax recorded in the period through the entry 691 = 4411.
The accountant confirms that the company records the profit tax in 4411. If it uses a sub-account (for example 4411.01) or another account, choose it on row 103 with Configure Journal Item Rows on the requirement (the full mapping is in ANAF Declarations › Configuration › Accounting › Calculation). A few situations to check:
- Tax payments (4411 = 5121) are debit turnover and are not counted; if row 103 equals the payment, the chosen account is not the account of the tax due.
- The D101 adjustments (the year-end difference) also go through 4411 and appear in the period in which they are recorded.
- A company that pays the micro-enterprise income tax has no row 103: its tax is on row 121, from 4418.
After the calculation, compare the amount on row 103 with the ledger of the chosen account for the same period (see Account sheet).
Rows calculated from journal entries
Rows that come from the accounting are already filled in with the standard setting, based on the Romanian chart of accounts; configure only the deviations. The Configure Journal Item Rows button on the requirement opens the rows, and the full mappings are in ANAF Declarations › Configuration › Accounting › Calculation.
| Return | Row | Standard setting |
|---|---|---|
| D100 | 103 profit tax | credit turnover of account 4411 |
| D100 | 121 micro-enterprise income tax | credit turnover of account 4418 |
| D100 | 604 | credit turnover of account 446, only the lines with the obligation's tag |
| D101 | P1 / P2 operating income / expenses | 70–75, 781, 79 / 60–65, 681, 69 |
| D101 | P4 / P5 financial income / expenses | 76, 786 / 66, 686 |
| D101 | P13 legal reserve | 1061 |
| D101 | P23 profit tax | 691 |
| D101 | P28 accounting depreciation | 6811 |
Account 446 is used for several taxes: put the obligation's tag on the sub-account (for example 446100) or on the tax used, and the row takes only those lines. Entries closing income and expense accounts into 121 are not counted, even if the company closes monthly. The formulas and validations from the ANAF annex (amount payable, control total) cannot be changed. On the calculated return (D101 is the Declarația privind impozitul pe profit, the annual profit tax return), each row shows exactly the journal entries it took.
Amounts entered by the accountant
Some rows do not follow from journal entries and are filled in on the document, in the Manual Rows tab, before calculating. For D101, for example:
- interest, late-payment penalties and fines; entertainment expenses above the limit; sponsorships;
- non-deductible provisions and adjustments; other non-deductible expenses;
- tax losses from previous years; tax reductions;
- the tax declared during the year through D100.
Enter 0 in the rows you do not use. Totals and tax are calculated with the formulas in the annex. Tax adjustments, losses and reductions are checked against the company's documents and the legislation of the period.
Reconciliation with the accounting
Before confirming and after each calculation, compare the return with the accounting of the same period:
- D300: the VAT report, the sales and purchase journals and the balances of the VAT accounts; check adjustments, the balance carried forward, the pro-rata and the refund option, only if they apply to the company;
- D394: the total bases and VAT against the sales and purchase journals and against D300;
- D100: each obligation against its account ledger;
- D101: income and expenses against the trial balance and the Registrul de evidență fiscală (the tax records register); watch the signs and double counting.
Correct the selection (tax, account, invoice), not the amount in the return.
Tax review on the return
For returns with their own rules, the guide asks for a tax review before the first filing:
- D318: the refund state, the period, the invoices, the suppliers, the codes of goods and services, the currency and the right of deduction; the applicant's data must not be confused with that of the representative or the supplier. See D318.
- D390: the operation type, the partner's country and VAT number, the amounts; corrections stay separate from current transactions. See D390.
- D398: the scheme and the period, the member state of consumption, the rate, the base and the VAT, corrections of previous periods. See D398.
- D120: obligations and tax treatment by product category and year; reconciliation with the excise records. See D120.
- Bilanț (the annual financial statements): the form by entity category and accounting regulation, the fiscal year, the comparative balances and the reconciliation with the trial balance; the signatory, the auditor and the tax options. See Bilanț.
Intrastat
The Intrastat return is filed separately for arrivals and dispatches, in three variants: nil (period with no operations), new or corrective. On the lines, check the CN code, the countries, the nature of transaction, the net mass, the supplementary unit and the values required by the return type. File validation does not replace checking the INS (National Institute of Statistics) code lists. See Intrastat.
Payroll accounts (D112)
With Enterprise Payroll, D112 (Declarația privind obligațiile de plată a contribuțiilor sociale, the payroll contributions return) is not calculated or generated until the payroll accounts requirement is confirmed. When the D112 version is synchronised, Romanian salary rules without accounts receive the accounts from the server schema, according to OMFP 1802/2014 (the Romanian accounting regulations order): Odoo looks for the account with the code in the schema, then its first sub-account (for example 4315, then 431510). Rules you have already configured are not changed. Gross and net have no accounts: gross is recorded through its components, and net remains as a balance on 421.
Check the rule accounts in Payroll › Configuration › Rules, then confirm the requirement. If the chart of accounts is loaded later, the Complete Payroll Accounts button on the requirement runs the completion again. A new schema sent by the server sets the requirement back to Needs Review. The full steps are in Payroll - configuration.
Check before filing
After Calculate on Server, compare the main amounts before Generate XML:
- D300: collected and deducted VAT against the sales and purchase journals and the balances of 4423/4424. Differences almost always come from a tax without a tag: correct the tax, not the amount in the return.
- D394: the total bases and VAT against the journals and against D300 for the same month. On the document you can edit the declarant's data (name, position, who prepares it).
- D390: total intra-community supplies and purchases against the corresponding D300 rows.
- D100: the account ledger of each tax. D101: total income and expenses against the accounting result, then the tax payable or recoverable.
If an amount differs, open the row, look at the journal entries it took and correct the selection. Automatic file validation checks the structure and the ANAF rules; it does not replace the tax review: a field without a source is not filled with zero just to pass validation.
For the accountant: what confirmation means
- Requirements and the links to guides come from the configuration approved on the server for each version of the return; in Odoo you edit only the company's decisions (the notes and Applicable).
- Confirmation is tied to the text of the guide in force: if the server changes the guide, the requirement returns to Needs Review so that the company checks it again.
- Confirmation does not run tax formulas and does not change returns already calculated or filed; each document keeps its own snapshot of the calculation.