Finance leaders running Odoo usually have all the data they need and no single place to see it. Cash-on-hand lives in the bank journals, receivables aging sits behind the Aged Receivable report, payables due dates hide in vendor bills, and month-over-month revenue means exporting the pivot to a spreadsheet. Odoo core gives you account.move, account.move.line, and solid accounting reports, but it stops short of a live, at-a-glance operational dashboard scoped to one company — the CFO view that answers "how much cash, who owes us, what do we owe, and are we trending up" in one screen. The Accounting dashboard tiles that ship out of the box are journal-centric, not KPI-centric, and they don't roll aging into actionable buckets or expose the compute logic you can trust and extend.

We build a dedicated Financial Dashboard module for your Odoo database. At its core is a set of compute fields on a lightweight dashboard model (and dedicated read models) that aggregate directly from account.move.line and account.account, so numbers reconcile to the general ledger rather than a parallel data store. Cash position sums posted entries across your liquidity accounts by journal; AR and AP aging classify open account.move.line residual amounts into 0-30 / 31-60 / 61-90 / 90+ day buckets using date_maturity, computed with @api.depends so they refresh when entries post or get reconciled. KPI tiles — revenue, gross margin proxy, overdue receivables, DSO, top debtors — are rendered in an OWL/JavaScript client action with QWeb templates, driven by read_group aggregations for performance rather than looping records in Python. Every figure is drill-through: click a bucket and land on the filtered list of underlying moves.

The build is scoped to your reality. We map the KPIs to your actual chart of accounts and analytic structure, respect multi-currency by reading company-currency amounts, and enforce visibility with ir.model.access.csv plus record rules so the dashboard honors company boundaries and the finance-vs-viewer access split you define. Where you want a scheduled digest, we wire an automated action / ir.cron to email a snapshot; where you want to pull figures into another system, the models are readable over the standard XML-RPC / JSON-RPC API. We test against your data on a staging database, confirm the aging totals tie out to Odoo's native Aged Partner Balance to the cent, and ship clean, reviewable source with a proper __manifest__.py, security files, and views. It targets Odoo 17.0, 18.0, and 19.0, Community or Enterprise — we confirm which edition-specific accounting features (like Enterprise's consolidation or budgets) your version exposes before we depend on them.

Because this is build-to-order, nothing is downloaded and switched on the same day. After a short scoping call we confirm the KPI list, aging buckets, access model, and target Odoo version, then deliver on a typical timeline of 2 to 4 weeks from confirmed scope, including UAT on your staging instance before go-live. Pricing starts from $299 (indicative, single-company base scope); multi-company consolidation, additional custom KPIs, currency-conversion depth, and integrations that push figures to external BI or ERP systems increase the quoted scope. You get a fixed quote after the scoping call — the from-price is a starting point, not a firm total.