A build-to-order Odoo module that prints clean, paginated PDF reports of journal entries and their move lines. ECOSIRE designs, builds, installs, and supports it for your Odoo 17, 18, or 19 accounting workflow. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.
Manifeste de l'app
Conçu autour de votre flux de travail
A build-to-order Odoo module that prints clean, paginated PDF reports of journal entries and their move lines. ECOSIRE designs, builds, installs, and supports it for your Odoo 17, 18, or 19 accounting workflow.
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
ECOSIRE la développe, la configure et l'installe sur votre Odoo.
Vous êtes en ligne en 2–4 semaines environ, avec une période d’assistance après le lancement.
Finance teams running Odoo constantly need a hard copy of what actually posted to the ledger — for a reviewer, an external auditor, a tax officer, or an internal control file. Out of the box, Odoo shows journal entries (account.move) and their lines (account.move.line) beautifully on screen and lets you export lists to spreadsheet, but there is no first-class, print-ready PDF of a batch of journal entries with their full debit/credit line detail, running totals, and a professional header. People end up screenshotting the form, exporting raw CSV that no auditor wants to read, or hand-building a spreadsheet that immediately drifts out of sync with the books. That gap is where a purpose-built printout earns its keep.
This is a build-to-order module that ECOSIRE designs, builds, installs, and supports for your specific Odoo instance — it is not an existing download you install yourself in five minutes. Technically, we ship a proper QWeb PDF report bound to account.move (and, where you need a batched digest, to account.journal or a lightweight TransientModel wizard). The report iterates each entry's line_ids, printing account code and name, partner, label, analytic tags, debit and credit columns, and a per-entry balance check, then rolls up totals per journal and per selection. We wire it into the standard Print menu via an ir.actions.report record so users trigger it exactly where they expect — from a single entry, a filtered list of entries, or a wizard that takes a date range, journal(s), posted/draft state, and company. The layout is a real report.external_layout document with your company header, currency-aware formatting, and pagination that survives 5 lines or 5,000.
Under the hood we keep it clean and upgrade-safe: a small __manifest__.py declaring the report and views, no monkey-patching of core accounting logic, access governed by ir.model.access.csv plus record rules so users only print entries their accounting group and company allow, and compute fields (@api.depends) for any derived totals rather than stored duplicates that can go stale. If you need the same output pulled by another system, we expose it through Odoo's XML-RPC/JSON-RPC API so a script can render the PDF on demand. The build targets Odoo 17.0, 18.0, and 19.0, and we account for Community vs Enterprise differences up front — the report itself relies only on the accounting models present in both editions, so it works whether or not you run Enterprise.
Delivery is build-to-order: after a short scoping call we confirm the exact columns, grouping, filters, and branding you want, then build against a staging copy of your database, run UAT with your finance team, and deploy to production with a rollback path. Typical delivery is 2-4 weeks from confirmed scope, depending on how bespoke the layout and filtering rules are and your review turnaround. Pricing starts from $299 (indicative, single-company base scope); multi-company consolidation, extra grouping/analytic breakdowns, deeper localization of the layout, or integration that renders the report for an external system increases the quoted scope.
Need a clean, print-ready PDF of posted journal entries with full line detail for month-end review, board packs, and internal control files — not a raw CSV export.
Want a consistent, header-branded document showing each entry's debit/credit lines and balance so audit samples can be pulled and filed without hand-formatting.
Prefer an additive, upgrade-safe module governed by `ir.model.access.csv` and record rules over a fragile in-house customization that breaks on the next Odoo upgrade.
Require a durable printed ledger extract, filtered by journal and date range, that maps to statutory record-keeping expectations across their operating companies.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Fits your exact columns & branding | Built to your confirmed spec on staging | Fully bespoke but you own all the effort | Fixed layout, limited configuration | |
| Batch journal-entry PDF with line detail | Core deliverable — QWeb report over move lines | Possible if your devs build QWeb correctly | Usually yes, but rigid formatting | |
| Filtering (date/journal/company/state) | Wizard tailored to your filters | Whatever you spec and maintain | Basic preset filters | |
| Upgrade safety across 17/18/19 | Additive, no core patching, migration on request | Depends on in-house discipline | Depends on vendor's next release | |
| Access control | `ir.model.access.csv` + record rules to your policy | You design and test it | Generic, often all-or-nothing | |
| Support & accountability | Post-go-live window + git handover | Your team owns every bug | Ticket queue, no context on your setup | |
| Time to working solution | 2-4 weeks from confirmed scope | Weeks to months of internal dev | Fast install, then fight the constraints | |
| External-system (API) rendering | XML-RPC/JSON-RPC callable, quoted as add-on | Buildable with extra effort | Rarely supported |
This is built to order. Typical delivery is 2-4 weeks from confirmed scope — the timeline depends on how bespoke your columns, grouping, filters, and branding are, and on your team's UAT turnaround. We build against a staging copy of your database and deploy to production only after you sign off.
No. It is a productized service: we design, build, install, and support the module specifically for your Odoo instance. There is no instant download. After a scoping call we confirm exact requirements, then build, test on staging, and deploy with a rollback path.
Pricing starts from $299 (indicative, single-company base scope). After a short scoping call we issue a fixed quote for your exact requirements. Drivers such as multi-company consolidation, extra analytic breakdowns, deeper layout localization, or external-system integration increase the quoted scope.
Every build includes a post-go-live support window for defect fixes and adjustments, plus a git handover so you own the code. Because the module is additive and avoids patching core accounting, it is designed to survive Odoo upgrades; we can also quote an ongoing maintenance or version-migration retainer if you want us to keep it current across 17.0/18.0/19.0.
Both. The report depends only on accounting models (`account.move`, `account.move.line`, `account.journal`) that exist in both editions, so it works whether or not you run Enterprise. We confirm your exact version and edition during scoping.
Yes. A selection wizard lets you print by date range, one or more journals, company, and posted/draft state, or you can print a single entry or a multi-selected list directly from the Print menu. Sort and grouping options (by journal, date, or entry number) are chosen at print time.
Yes. The report is exposed through Odoo's XML-RPC/JSON-RPC API, so an external script or integration can request the rendered PDF for a given selection on demand. That integration path is an add-on scope driver we cover in the quote.
A build-to-order Odoo module that prints clean, paginated PDF reports of journal entries and their move lines. ECOSIRE designs, builds, installs, and supports it for your Odoo 17, 18, or 19 accounting workflow.