A build-to-order Odoo module that adds true cash book, day book, and bank book statements on top of your live accounting data — filtered, drill-down, and export-ready. ECOSIRE scopes, builds, installs, and supports it for Odoo 17/18/19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.
Uygulama manifestosu
İş akışınıza göre tasarlandı
A build-to-order Odoo module that adds true cash book, day book, and bank book statements on top of your live accounting data — filtered, drill-down, and export-ready. ECOSIRE scopes, builds, installs, and supports it for Odoo 17/18/19.
Kendiniz kurmanıza gerek yok — ECOSIRE tarafından geliştirilen, kurulan ve desteklenen çalışır bir uygulama.
Tek seferlik geliştirme fiyatıyla başlayın. Kapsamı başlangıçta sizinle birlikte belirleriz.
ECOSIRE, Odoo ortamınızda geliştirir, yapılandırır ve kurar.
Yaklaşık 2–4 haftada yayına alırsınız; lansman sonrası bir destek süresi de dahildir.
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.
Owns the monthly close and needs cash book, day book, and bank book statements in the exact format auditors and the board expect, without exporting the GL to spreadsheets and rebuilding them by hand every period.
Lives in the Accounting app day to day and wants one-click, filterable statements with running balances and drill-down to source entries, so reconciliations and audit requests take minutes instead of hours.
Requires a chronological day book and per-bank-account bank book that tie back to posted journal items, with two-click traceability from any line to the originating account.move.
Responsible for the production database and wants a properly packaged module — clean manifest, access rules, staging UAT, rollback plan, and a git handover — rather than fragile spreadsheet workarounds.
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| How you get it | Scoped, built, installed and supported by ECOSIRE | Built in-house or by a freelancer from scratch | Downloaded and self-installed, as-is | |
| Cash/day/bank book layout | Exact named statements with running balances, tailored to your auditors | Whatever you specify, if you get the spec right | Fixed vendor layout, limited configurability | |
| Reconciliation to GL | Reads posted account.move.line — ties to GL by design | Depends on developer's data model choices | Usually reads GL, but drill-down varies | |
| Odoo 17/18/19 fit | Built and tested against your exact version | You maintain version compatibility yourself | Depends on vendor's version support | |
| Multi-company & security | Record rules and access CSV scoped to your org | Must be designed and tested by you | Generic rules, may need adjustment | |
| Support & ownership | Support window + full source + git handover | You own and maintain everything | Vendor support tier, source often obfuscated | |
| Delivery time | Typically 2–4 weeks from confirmed scope | Weeks to months depending on resourcing | Instant install, but no fit guarantee | |
| Total cost profile | Fixed quote from ~$299 indicative after scoping | High and variable (developer time + maintenance) | Low sticker price, hidden fit/customization cost |
No. This is a build-to-order module. ECOSIRE scopes, builds, tests, and installs it for you against your specific Odoo version. There is no instant download — you request a quotation and we build it to your confirmed requirements.
Typical delivery is 2–4 weeks from confirmed scope. After the scoping call we build and test on a staging copy of your database, run UAT with your team, and only then deploy to production. Larger multi-company or localization requirements can extend the timeline, which we confirm in writing before starting.
Pricing starts from $299 as an indicative figure for a single-company base scope. Drivers such as multi-company consolidation, extra localization or audit-format depth, and BI/API integration increase the quoted scope. After a short scoping call we send a fixed quote — the indicative from-price is a starting point, not the final number, and you approve the fixed quote before any work begins.
Yes. The reports read directly from your posted account.move.line records rather than a separate copy of the data, so cash book, day book, and bank book totals reconcile exactly to the General Ledger and Trial Balance. Every line drills back to its source journal entry.
We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. On Community the reports render with standard QWeb and do not depend on the Enterprise-only report engine. We compile and test against whichever version your production database runs.
Every build includes a post-go-live support window for defect fixes and configuration questions. Because you receive the full source and a git repository handover, you own the code outright. Version upgrades (for example moving from Odoo 18 to 19) or new report variants are handled as a scoped follow-on engagement.
Yes. Where you need it, we expose the same computed cash/day/bank-book dataset over Odoo's JSON-RPC/XML-RPC API so an external BI tool, spreadsheet, or Odoo Studio dashboard can pull the figures programmatically. This is scoped as an optional add-on during the scoping call.
A build-to-order Odoo module that adds true cash book, day book, and bank book statements on top of your live accounting data — filtered, drill-down, and export-ready. ECOSIRE scopes, builds, installs, and supports it for Odoo 17/18/19.