Grant-funded organisations lose money and reputation in the gap between the award letter and the acquittal. The award terms live in a PDF on someone's drive, the budget lives in a spreadsheet, the actual spend lives in Odoo journal entries, and the funder report is assembled by hand every quarter by an overworked finance officer who has to remember that this funder allows 12% indirect costs but that one caps them at 8%. Odoo out of the box has no concept of a grant. analytic.account and analytic.plan will carry cost allocation, and crm.lead will track the application pipeline, but neither knows about an award ceiling, a milestone-linked drawdown, an eligible-cost rule, a reporting calendar, or an acquittal deadline. The moment a program is funded by two grants with different eligibility windows, the spreadsheet becomes the system of record and the ERP becomes a bookkeeping afterthought.

We build a grant model that sits properly inside the Odoo accounting and analytic stack rather than beside it. A new ecosire.grant model (models.Model) holds the award: funder (res.partner), reference, award amount, currency, agreement start and end dates, eligibility window, indirect-cost basis and rate, and the signed agreement as an attachment with a document-state workflow. Each grant owns budget lines keyed to an analytic account and, where you want finer control, to an account group or expense category, so a compute field with @api.depends on the posted account.move.line set gives you committed, actual and remaining in real time instead of at month end. Drawdown and disbursement records track what has been requested from the funder, what has been received, and what has been paid out to sub-recipients, each linked to the underlying account.move and account.payment so the cash trail is auditable rather than asserted. Timesheet lines and vendor bills allocate to grants through the analytic distribution Odoo already understands, which means salary apportionment across three funders stops being a monthly reconstruction.

The reporting layer is where funders are actually satisfied or annoyed. We build QWeb report templates for the pack each of your funders demands — expenditure by budget category against approved budget, variance with narrative fields, drawdown history, staff time allocation summary — rendered as PDF and, where the funder insists on it, exported to their spreadsheet template. A reporting calendar on each grant drives Odoo automated actions (base.automation / ir.cron) that raise activities ahead of every interim report, drawdown window and acquittal date, so the deadline surfaces in the responsible officer's inbox rather than in an auditor's finding. Overspend and eligibility-window breaches raise warnings at the point of entry, with a configurable choice between blocking and warning, because a hard block on a legitimate accrual causes more damage than it prevents.

Access control is deliberate, not an afterthought. Program managers see their own grants, finance sees all of them, and funder-facing read-only roles see the report data without the general ledger — implemented with ir.model.access.csv for model-level rights plus ir.rule record rules keyed to the responsible user and program, and multi-company rules where you run several legal entities. Everything is exposed on the standard XML-RPC and JSON-RPC API, so a grants portal, a funder data feed or your existing BI tool can read grant balances without a second database. Views are standard Odoo XML with OWL components only where the interaction genuinely needs them, which keeps the module upgradable rather than clever. The module targets Odoo 17.0, 18.0 and 19.0 and works on Community — the Enterprise-only pieces (accounting reports engine, Documents, Approvals) are used when they are present and cleanly substituted when they are not, and we tell you in scoping which side of that line each requirement falls on.

This is a build-to-order product, not a download. You request a quotation, we run a scoping call, and we come back with a fixed written scope covering your funders, your budget categories, your indirect-cost rules and your report pack layouts. On confirmed scope, typical delivery is one working week: we build against your Odoo version and edition, install on your staging database, and run UAT against your real historical grants so the numbers can be checked against what you already reported. Nothing is a template drop — the model is shared across engagements, the funder rules and report packs are yours. You receive installable source code, a git repository handover, technical and user documentation, a training session, and a post-go-live support window for defect fixes.