Features

• Tipizat Form Code 14-1-1/b — nine to eleven columns (No., Date, Doc. No., Partner, Description, Receipts Bank / Cash, Payments Bank / Cash, plus Currency / Amount in Currency when any line is in foreign currency) with the company header (name, Tax ID, Trade Register) and the standard signature footer on the PDF.
• Liquidity-account scope — only the line(s) posted on a journal's default_account_id are considered, so transfers and counter-bookings inside the same move are filtered out and each movement is counted once.
• Bank vs. cash split — derived from the journal's type (bank or cash); a single positive debit becomes Receipts, a positive credit becomes Payments, each on the matching side.
• Monthly subtotals — moves are grouped by (year, month) of the posting date, with Total luna <Luna> subtotals localised via babel.dates (Romanian by default, follows env.lang).
• 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).
• Foreign-currency column — auto-shown only when the period contains at least one foreign-currency line; the column carries the currency code and absolute amount in that currency, while the Bank / Cash columns stay in company currency.
• Continuable numbering and optional journal filter — the starting Nr. crt. chains periods into one sequence; the journal selector is restricted to bank and cash journals of the active company and can be left empty for "all".

Configuration

The module is plug-and-play: no master data has to be created specifically for the Payment Register. A few prerequisites have to be in place on the bank and cash journals so the printout matches the legal form:

1. Bank and cash journals with a liquidity account — each account.journal of type bank or cash must have a default_account_id set; the SQL fetcher reads the journal liquidity account from this field and considers only the account_move_line rows posted on it.
2. Journal types — the Bank vs. Cash column split is derived from journal.type; make sure each journal is configured as bank or cash (mixed journals will fall under "all bank / cash journals" only if at least one is of the right type).
3. Posted entries only — the fetcher filters on parent_state = 'posted', so unposted statements / payments do not appear. Validate the bank statements and the payments before running the register so the cut-off is meaningful.
4. Company header data — set the company vat (Tax ID) and company_registry (Trade Register) on Settings → Companies so the PDF header carries them alongside the company name.
5. Locale for monthly labels — the Total luna <Luna> row formats the month name via babel.dates using the active user's env.lang (defaults to ro_RO); make sure the Romanian language is loaded if you want Romanian month names.

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

How it works

Opening the wizard

Go to Accounting → Reporting → Romania → Payment Register. 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.

Wizard fields

What happens on Generate

1. The wizard validates the period and runs a single raw SQL query joining account_move_line to account_move, account_journal, res_partner and res_currency. Only parent_state = 'posted' lines posted on each journal's default_account_id (liquidity account) are kept, ordered by (date, move.name, move.id).
2. Each move is classified by journal type — a positive debit on a bank journal becomes receipt_bank, a positive credit on a cash journal becomes payment_cash, etc. Lines in a currency other than the company's also carry the foreign currency code and absolute amount.
3. The rows are grouped by (year, month) of the posting date and a Total luna <Luna> subtotal is computed per month; the month label is formatted via babel.dates using env.lang.
4. For PDF output the groups are sliced into chunks bounded by PDF_MAX_ROWS_PER_CHUNK = 1000 body rows (monthly subtotals stay attached to the last slice of their group), each chunk rendered via the QWeb template and merged via PyPDF2 / pypdf.
5. XLSX output goes through xlsxwriter in constant_memory mode, with the Currency / Amount in Currency columns shown only when at least one row in the period uses a foreign currency. CSV is ;-delimited with a UTF-8 BOM so Excel opens it directly.
6. The generated file is streamed back through /web/content for immediate download.

If no bank or cash transaction 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.