| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 4221 |
| Technical Name |
l10n_ro_declaration_sale_journal |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 4221 |
| Technical Name |
l10n_ro_declaration_sale_journal |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
| Versions | 18.0 19.0 |
Romania - Account Report Sale Journal
Romania - Account Report Sale Journal
Overview
Generates the Romanian Jurnal de vânzări (Sales Journal Report) required by ANAF auditors as part of the monthly VAT documentation file. Posted customer invoices, credit notes and receipts are listed chronologically, signed by document type, and broken into the columns mandated by the fiscal code: invoice header (date, partner name, VAT ID), invoice totals (Total Invoice, Total Base, Total VAT), per-rate VAT bases and amounts (21 %, 11 % plus the legacy 19 / 9 / 5 % aggregate columns), inverse-taxation, special-treatment supplies, VAT-on-cash payments (number, date, total/base/VAT), not-exigible base/VAT, intra-Community supplies with and without deduction, exports exempt under art. 143 al. 2 lit. a+d and lit. b+c, an Others bucket and a paired Intra-Community / Inverse Base + VAT column for the purchaser-collected operations. A trailing Total row sums the numeric columns.
The report is rendered through Odoo's account.report engine, so the
same data is available as on-screen HTML, downloadable XLSX, and PDF
print-out — all from the report toolbar. Two variants ship together: a
current VAT-rate version (21 / 11 %) and a legacy one (19 / 9 / 5 %)
for historical periods.
Built & supported by NextERP Romania
Romanian Odoo specialists, here for the long run — from implementation to localization and day-to-day production support.
What we do
Odoo Solutions
From quick-start rollouts to multi-company deployments and custom modules built for your processes.
Romanian Localization
SAF-T (D406), e-Factura, e-Transport, D300 / D390 / D394, ANAF integration, full chart of accounts and fiscal positions.
Our Services
Implementation, customization, migration, integration, support and consultancy — Romanian-speaking, SLA-backed.
Features
- Romanian Jurnal de vânzări structured to ANAF audit conventions: one row per posted sale document, sorted by invoice date and then by number.
- Picks up
out_invoice,out_refund,out_receiptplus any vendor document carrying a sale-extra tax tag (for example triangulation or self-billed sales), so the listing matches the D300 sales boxes. - Native
account.reportintegration: on-screen HTML drill-down to the originating invoice, PDF print and XLSX export available from the same toolbar — no separate wizard. - VAT split across the rates in force (21 % and 11 %) with a separate aggregate column covering the historical 19 / 9 / 5 % postings, so a single sheet can carry mixed periods.
- Dedicated columns for inverse taxation, special-treatment supplies and the paired Intra-Community / Inverse Base + VAT used to mirror the purchaser-collected lines on the buyer side.
- Intra-Community supplies (with and without deduction), exports exempt under art. 143 al. 2 lit. a+d and b+c, and an Others bucket cover the non-domestic flows.
- Period filter defaults to the previous month and obeys the multi-company tax-unit scope; draft entries can be included while closing a period.
Configuration
The report relies entirely on data already present in the Romanian
chart of accounts and on the VAT tax tags installed by
l10n_ro_declaration. There is no module-specific configuration
screen.
-
Install Romania - Account Report Sale Journal (
l10n_ro_declaration_sale_journal). The dependencyl10n_ro_declarationis pulled in automatically and brings the Romanian fiscal positions, taxes and account tags. -
Confirm the company has Romanian fiscal data set under Accounting → Configuration → Settings: VAT ID (CIF), trade registry number (NRC) and full address. These appear in the PDF header.
-
Check that the Romanian taxes are mapped to the correct ANAF tags. Open Accounting → Configuration → Accounting → Taxes, pick a sale tax (e.g. TVA colectata 21%), and verify the Tax Grids on the invoice / refund repartition lines reference the expected
+/-D300-style tags. The sale journal reads these tags to attribute each move line to a column. -
For triangulation, self-billed sales or purchaser-collected operations booked outside of the sale journals, set the sale-extra tax tags on the relevant tax repartition lines so the entries are picked up by the sale-extra selector and land in the Intra-Community / Inverse columns.
-
Optional: if VAT-on-cash applies, enable it on the relevant journals so that collected amounts feed the Payment Number / Date / Total / Base / VAT columns.
-
Grant Accounting / Read-Only (
account.group_account_readonly) to anyone who has to download the journal. The menu Accounting → Reporting → Romania → Sales Journal Report then becomes visible.
How it works
-
Open Accounting → Reporting → Romania → Sales Journal Report. The report opens directly — there is no intermediate wizard.
-
In the top filter bar, set the Date range. The default is the previous calendar month, which matches the monthly ANAF filing cycle. Custom ranges (any month, quarter, year, or arbitrary from/to dates) are accepted.
-
Use the Companies / Tax Unit filter when a Romanian tax unit groups multiple companies — the report consolidates all members. The Include Draft toggle adds unposted moves while you are still closing the period; remove it for the final filing copy.
-
Use the variant selector on the right of the title to switch between the current report (21 / 11 % VAT plus a legacy 19 / 9 / 5 % aggregate column) and the older Sales Journal Report OLD variant kept for historical periods.
-
The body lists one row per sale document — Date, Number, Name, VAT, totals, per-rate base/VAT, inverse taxation, special treatment, payments, not-exigible, intra-Community and exempt columns — followed by a single Total row that sums every numeric column.
-
Click any line to drill down to the originating customer invoice. From the toolbar, use PDF to print the audit-ready layout and XLSX to download the spreadsheet kept on file.
Screenshots
Captured from a running Odoo instance.
Jurnal4
Jurnal6
Jurnal7
Versions
19.0.0.1.0 (2026-05-24)
- Changelog tracking starts at this release.
Discover the NextERP suite
Other modules from the same publisher, built to work together.
NextERP Romania
Odoo implementation, customization, Romanian localization and long-term support since 2018.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module