Features

• Two RO-scoped reports — RO Aged Receivable and RO Aged Payable, registered as variants of the stock Aged Receivable / Aged Payable (root_report_id points to the stock reports) and country-scoped to Romania (country_id = base.ro).
• Romanian aging buckets — six fixed columns: At Date, 1 - 30, 31 - 90, 91 - 270, 271 - 365, Older. Column labels are set in _custom_options_initializer; the stock aging-interval filter is removed in the OWL view via AgedPartnerBalanceFilters inheritance.
• Custom SQL engine — the abstract model l10n.ro.account.aged.partner overrides _aged_partner_report_custom_engine_common to build the six-row period_table and the per-bucket CASE columns. Receivable and payable variants share the same engine, parametrised by internal_type (asset_receivable vs. liability_payable).
• Reconciliation-aware balances — debit / credit amounts are netted against account_partial_reconcile rows whose max_date <= date_to, so partially reconciled invoices land in the correct bucket for the residual amount only.
• Foreign-currency column — each row exposes amount_currency and the line's currency, alongside the company-currency totals.
• Drill-down to journal items — open_journal_items extends the stock action with the opposite-side account_type so a customer drill-down also shows the matching vendor lines (and vice versa).

Configuration

The module is plug-and-play: no master data has to be created specifically for the RO Aged Partner Balance reports. A few prerequisites have to be in place so the reports yield the expected result:

1. Romanian fiscal company — the variants are country-scoped to Romania (country_id = base.ro). Make sure the active company's account_fiscal_country_id is Romania so the reports appear in the variant selector of the stock Aged Receivable / Aged Payable.
2. Romanian chart of accounts — install the Romanian chart so account.account.code is populated and so trade receivable (411x) / trade payable (401x) accounts carry the correct account_type (asset_receivable / liability_payable).
3. Partner records on invoices — only account.move.line rows carrying a partner_id aggregate under the partner grouping; for manual journal entries set the partner so they appear in the right bucket.
4. Reconciliation discipline — the SQL engine nets balances against account_partial_reconcile rows whose max_date <= options['date']['date_to']; reconciling payments against invoices is what shifts amounts out of the buckets, so keep customer / vendor reconciliation up to date.
5. Aging-date basis — pick the aging basis at run time from the report's filter bar (base_on_invoice_date vs. date_maturity); the engine reads options["aging_based_on"] and bases the bucket placement on whichever date was chosen.

Access follows the stock account_reports model — any user with read access to account.report can open the reports.

How it works

Opening the reports

The two variants are exposed as Odoo client actions registered in views/report_data.xml:

• RO Aged Receivable — action tag account_report, path ro-aged-receivable.
• RO Aged Payable — action tag account_report, path ro-aged-payable.

They appear in the variant selector of the stock Aged Receivable / Aged Payable reports (Accounting → Reporting → Partner Reports) for companies whose fiscal country is Romania, and can also be opened directly via their path.

Columns

The aging-interval filter is hidden via an OWL inheritance so the Romanian buckets stay fixed; the rest of the standard AccountReportFilters (date, partner, account, multi-company, draft, search bar) remains available.

Behind the scenes

1. The custom handler model (l10n.ro.account.aged.receivable or …aged.payable) overrides _aged_partner_report_custom_engine_common and builds a six-row period_table (date_start, date_stop, period_index).
2. The SQL joins account_move_line to itself via account_partial_reconcile (debit and credit sides) and assigns each line to its bucket through a join on period_table. The open amount per bucket is then summed with a sign multiplier of -1 for payables so the printout displays positive values.
3. The engine collapses the result per grouping key (partner_id, then id when unfolding a partner), and the Aged Partner Balance OWL component renders the columns and the partner / line drill-down tree.
4. Drill-down from a line (open_journal_items) extends the stock action with the opposite-side account_type filter so the user immediately sees both sides of the partner's transactions.

Versions

19.0.0.1.0 (2026-05-24)

• Changelog tracking starts at this release.