Finance teams running Odoo constantly need the three classic ledgers accountants and auditors ask for first: a cash book (all cash receipts and payments with a running balance), a day book (a chronological journal of every posted entry for a period), and a bank book (per-bank-account movement with explicit opening and closing balances). Odoo core ships the General Ledger, Journals, and Partner Ledger, but it does not provide these named statements in the layout most bookkeepers, auditors, and regional tax reviewers expect — a running-balance column per account, opening/closing framing, and a single click that filters to just cash journals or one specific bank journal. Teams end up exporting the GL to a spreadsheet and rebuilding these reports by hand every month, which is slow, hard to audit, and easy to get wrong.

This is a build-to-order module that ECOSIRE designs, builds, and installs for you — it is not an existing app you download and run today. Technically, the reports read directly from your posted account.move.line records (never a parallel copy), so every figure reconciles back to the General Ledger and Trial Balance. We implement the report engine as a TransientModel wizard (models.TransientModel) that captures the criteria — date range, company (or companies), journals or specific cash/bank accounts, target moves (posted only vs. all), and optional partner or analytic filters — then computes opening balance, period movements, and a carried-forward running balance. Heavy aggregation is done with read_group and targeted SQL-safe ORM reads rather than row-by-row Python loops, so the reports stay responsive on databases with millions of journal items. Presentation is delivered as both an interactive list/pivot view (OWL/XML) and a paginated QWeb PDF plus an XLSX export, all sharing one computed dataset so the on-screen figures and the printout can never disagree.

Under the hood the module is a proper Odoo app: a versioned __manifest__.py declaring dependencies on account, security through ir.model.access.csv and multi-company record rules so users only see journals for companies they are assigned to, menu items and actions wired into the Accounting → Reporting area, and the wizard/report views in XML. Drill-down is real — each report line links back to the originating account.move so an auditor can open the source entry in two clicks. Where you need it, we expose the same computed data over the JSON-RPC/XML-RPC API so an external BI tool or an Odoo Studio dashboard can pull the cash-book or bank-book figures programmatically. The module works on Community and Enterprise; on Community we render the reports with standard QWeb (no dependency on the Enterprise report engine), and we target Odoo 17.0, 18.0, and 19.0, building against whichever version your production database runs.

Delivery is build-to-order. After a short scoping call we confirm the exact report layouts, filters, running-balance rules, and any localization your auditors require, then build and test on a staging copy of your database before touching production. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full installable source, documentation, and a support window. Pricing starts from $299 (indicative, single-company base scope); multi-company consolidation, extra localization/audit-format depth, and integration into external BI or reporting pipelines increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise on the invoice.