Skip to Content

Romania - Journal Registry (Registrul-jurnal)

by
Odoo

$ 2329.20

v 19.0 Third Party
This module requires Odoo Enterprise Edition.
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Discuss (mail)
Community Apps Dependencies
Lines of code 2362
Technical Name l10n_ro_account_report_journal_registry
LicenseOPL-1
Websitehttps://www.nexterp.ro
Versions 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Discuss (mail)
Community Apps Dependencies
Lines of code 2362
Technical Name l10n_ro_account_report_journal_registry
LicenseOPL-1
Websitehttps://www.nexterp.ro
Versions 18.0 19.0
Romania - Journal Registry (Registrul-jurnal) icon

Romania - Journal Registry (Registrul-jurnal)

Tipizat Romanian Journal Registry (Cod 14-1-1) — chronological per-line printout with debit / credit accounts, exportable as PDF, Excel and CSV.

v 19.0.1.0.0 Accounting & FinanceOPL-1

Overview

This module produces the Romanian standardised Registrul-jurnal (Form Code 14-1-1) as a printable tipizat A4 form, plus Excel and CSV exports for archival or further processing.

The register is a strict one-row-per-account.move.line chronological listing of every posted accounting entry within the selected period. Each row carries the entry date, the document type and reference, a free-text description, the debit and credit account codes (the line's own account on its natural side and the counterpart on the opposite), and the debit / credit amounts in company currency. A TOTAL row sums the debit and credit columns across the whole period.

How it differs from the General Ledger / Journal Registry view in l10n_ro_account_report_sheet (which is a debug-friendly per-account ledger): this report is strictly chronological and exports one row per line, formatted to match the official tipizat.

Depends on l10n_ro_account_counterpart so the SQL fetcher can read account_move_line.l10n_ro_counterpart_id and populate the Cont debitor / Cont creditor columns from the per-line counterpart already computed by that module.

NextERP Romania

Built & supported by NextERP Romania

Romanian Odoo specialists, here for the long run — from implementation to localization and day-to-day production support.

10+
Years of Odoo experience per team member
80%+
of Romanian Localization maintained on Odoo Apps
19.0
Tracking every Odoo major release

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

  • Tipizat Form Code 14-1-1 — ten-column layout (No., Entry Date, Doc. Type, Doc. No., Doc. Date, Description, Debit Account, Credit Account, Debit, Credit) with the company header (name, Tax ID, Trade Register) and the standard "Prepared by / Management" signature footer on the PDF.
  • Strict one-row-per-AML chronological scope — every posted account.move.line in the period appears as its own row, ordered by date, move name, line id.
  • Counterpart-aware debit / credit columns — the line's own account is shown on its natural side and l10n_ro_counterpart_id on the opposite; lines with a zero debit and zero credit still print both sides so the row stays interpretable.
  • Friendly document-type labels — Customer Invoice, Vendor Bill, Bank Statement, Cash Register, etc., derived from move type or journal type and wrapped in env._ for Romanian translation.
  • Three output formats — PDF (chunked at 1000 rows per render and merged via PyPDF2 / pypdf for large periods), Excel (xlsxwriter low-memory) and CSV (;-delimited, UTF-8 BOM).
  • Optional journal filter and continuable numbering — leave the journal list empty to cover every journal of the company; the starting No. chains periods into one uninterrupted sequence.

Configuration

The module is plug-and-play: no master data has to be created specifically for the Journal Registry. A few prerequisites have to be in place on the company so the print output matches the legal form:

  1. Romanian chart of accounts — install the Romanian chart so account.account.code is populated; the wizard reads the code from account.account.code_store keyed by the active company.
  2. Counterpart computation — install l10n_ro_account_counterpart (listed as a dependency, installed automatically). The wizard reads account_move_line.l10n_ro_counterpart_id for every line; if the counterpart is empty on some lines the corresponding column is left blank, but the row still prints.
  3. Posted entries only — the SQL fetcher filters on parent_state = 'posted', so only validated moves appear. Draft moves are ignored on purpose to keep the printout reproducible.
  4. Company header data — set the company's vat (Tax ID) and company_registry (Trade Register / "Nr. Registrul Comerțului") on Settings → Companies; the PDF prints both in the top-left block alongside the company name.
  5. Multi-company — the wizard defaults to env.company; the company field is only shown to users in base.group_multi_company. Each journal selector is filtered by the active company.

Access to the wizard is granted via account.group_account_user (declared in security/ir.model.access.csv); no further role configuration is required.

Journal Registry print wizard

How it works

Opening the wizard

Go to Accounting → Reporting → Romania → Journal Registry. The menu item is registered under the Romania-scoped statements menu contributed by l10n_ro_account_enterprise and is visible to users holding account.group_account_readonly.

Journal Registry wizard - opening

Wizard fields

Field Meaning
Company Defaults to the active company; selector only shown in multi-company mode
Date from / Date to Inclusive period covered by the register; defaults to current year-to-date
Journals Many2many tags; leave empty to include every journal of the company
Starting number First value of the Nr. crt. column — chain to the last entry of the previous period
Output format PDF (tipizat A4), Excel or CSV

What happens on Generate

  1. The wizard validates the period (date_from <= date_to) and runs a single raw SQL query against account_move_line joined to account_account, account_move, account_journal and res_partner. The counterpart join reads l10n_ro_counterpart_id. Only parent_state = 'posted' lines in the period are kept, ordered by (date, move.name, aml.id).
  2. Each row is decorated with a friendly document-type label (Customer Invoice, Vendor Bill, Bank Statement, etc.) derived from move.move_type or journal.type, and the Nr. crt. counter is bumped from the user-supplied starting number.
  3. For PDF output the rows are split into chunks of PDF_MAX_ROWS_PER_CHUNK = 1000, each chunk rendered against the QWeb template and merged with PyPDF2 (or pypdf if PyPDF2 is not installed). The footer carries the standard "Prepared by / Management" signature block.
  4. XLSX output goes through xlsxwriter in constant_memory mode, with date columns formatted yyyy-mm-dd, money columns #,##0.00 and a TOTAL row in light gray. CSV is ;-delimited with a UTF-8 BOM so Excel opens it directly.
  5. The generated file is streamed back to the browser through /web/content for immediate download.

If no line matches the filter the wizard raises a UserError instead of producing an empty form.

Versions

19.0.1.0.0 (2026-05-24)

  • Changelog tracking starts at this release.

Discover the NextERP suite

Other modules from the same publisher, built to work together.

RO
Romania - Inventory Register (Registrul-inventar)
Accounting & Finance

Tipizat Romanian Inventory Register (Form Code 14-1-2) — balance-sheet snapshot at fiscal year end, grouped in Assets / Liabilities sections per account type, exportable as PDF, Excel and CSV.
RO
Romania - Payment Register
Accounting & Finance

Tipizat Romanian Payment Register (Cod 14-1-1/b) — chronological listing of bank and cash transactions split into receipts / payments × bank / cash, with monthly subtotals; exportable as PDF, Excel and CSV.
RO
Romania - Account Sheet / Journal Registry
Localisation

Romanian account sheet & journal registry on top of Odoo's account.report engine, with counterpart column
RO
Romania - Aged Partner Balances
Localisation

Romania - Aged Partner Balances
AC
Account Compensation
Accounting & Finance

Compensate partners debits and credits
RO
Romania - Partner Balance Confirmation
Accounting & Finance

Generate and send partner balance confirmation requests by email
RO
Romania - Account Asset
Localisation

Adapts Romanian Account Asset
RO
Romania - Account Counterpart
Localisation

Romania - Define Counterparts and calculate them automatically

NextERP Romania

Odoo implementation, customization, Romanian localization and long-term support since 2018.

nexterp.ro
All apps 
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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.