Every credit controller knows the pain: Odoo's stock Aged Receivable and Aged Partner Balance reports give you fixed 30/60/90/120 buckets, a partner ledger you have to read line by line, and a PDF that is stale the moment it prints. When the CFO asks "who should we chase first?" or "what is our overdue exposure in USD across three companies?", the native reports can't answer — the aging thresholds don't match your credit terms, there is no priority ranking, and multi-currency balances are shown at posting rate with no consolidated view. Teams end up exporting to spreadsheets every week, which is exactly where the numbers stop being trustworthy.

Aged Receivable / Payable Analytics is a build-to-order Odoo module that turns aging into an operational tool instead of a month-end artifact. We add a dedicated model (for example ecosire.aged.analytics.line) that reads directly from account.move.line — filtered on account_id.account_type in asset_receivable / liability_payable, parent_state = 'posted' and reconciled = false — and computes the residual per invoice using amount_residual and amount_residual_currency. Aging days are derived from date_maturity (falling back to invoice_date_due) against a configurable "as-of" date, and each open item is dropped into buckets you define in a settings model rather than the hard-coded native ranges. Compute fields use @api.depends so drill-downs stay live, and the whole set is exposed through Odoo pivot, graph, list and OWL dashboard views.

On top of the raw aging we build the two things native Odoo lacks. First, a collection-priority score: a stored compute that weights overdue amount, days-past-due, days-to-credit-limit and payment history into a single rankable figure, so the collections list opens already sorted by who to call today. Second, real multi-currency handling — every open item carries its currency amount and a company-currency conversion via res.currency._convert() at your chosen rate date, so a multi-company group sees one consolidated exposure number and each entity keeps its own currency detail. Overdue-trend charts snapshot bucket totals over time (via a small history model populated by a scheduled ir.cron automated action) so you can see whether your DSO is drifting week over week. Everything is secured with ir.model.access.csv plus record rules that respect res.company multi-company boundaries, and the same data is reachable over XML-RPC/JSON-RPC for BI tools or a treasury portal.

Because it is build-to-order, nothing here is a generic download. We start from your real chart of accounts, credit terms and currency setup, confirm the bucket definitions and scoring weights that match how your business actually chases money, and only then build. You get the module scoped to your Odoo edition and version — it works on Community and Enterprise, and we adapt to the accounting differences (Enterprise's dynamic financial reports vs Community's list-based reports) so the analytics sit naturally alongside what you already run. Typical delivery is one working week from confirmed scope, validated on a staging copy of your database before it ever touches production.