Funded organisations rarely fail an audit because the accounting is wrong — they fail because the grant story lives outside the accounting. ERPNext core gives you a Chart of Accounts, Cost Centers, a Budget DocType and Project accounting, and for a single-funder organisation that is often enough. It stops being enough the moment one expense must be split across three awards on different funder fiscal years, a funder asks for spend against their line items rather than yours, or a drawdown claim must reconcile back to the exact invoices and timesheets that justified it. At that point the real system becomes a spreadsheet: an award tracker in Excel, a budget-versus-actual pivot rebuilt by hand each quarter, and a finance officer reconstructing an acquittal from bank statements weeks after the fact. The Budget DocType is anchored to a fiscal year and a Cost Center, Project has no notion of an agreement period or a reporting calendar, and nothing in ERPNext knows what a drawdown, a match requirement or an eligible cost category is.

We build a proper Frappe app — its own module, its own DocTypes, installed alongside ERPNext rather than patched into it. A Grant Award DocType holds the funder, agreement reference, award value, period start and end, currency, indirect-cost rate and the eligibility rules for the award, with child tables for the funder's own budget line structure and for the reporting calendar. A Grant Budget Line maps each funder line to one or more ERPNext Accounts, Cost Centers or Project tasks, so a single posting is attributed correctly without duplicating the ledger. Grant Allocation records the split of a source document — a Purchase Invoice, an Expense Claim, a Journal Entry, a Timesheet detail row — across awards by percentage or fixed amount, validated so the allocated total never exceeds the source amount and never posts against a closed award period.

Technically the app hangs off hooks.py doc events rather than modified core code: on_submit and on_cancel handlers on Purchase Invoice, Sales Invoice, Payment Entry, Journal Entry, Expense Claim and Timesheet keep grant actuals in step with the General Ledger, and on_trash unwinds allocations cleanly. Committed spend is captured from submitted Purchase Orders and Material Requests so a budget line shows spent, committed and remaining rather than a lagging actuals-only figure. A scheduler event runs the period roll: it opens the next reporting period, snapshots budget-versus-actual, and raises a ToDo or Notification for any report pack falling due inside the notice window you configure. Drawdowns are their own document — a Grant Drawdown claim assembles the eligible spend for a period, locks the underlying allocations, produces the funder-format claim, and on receipt links to the Payment Entry so the receivable position against each funder is visible in ERPNext rather than in a side ledger.

Client scripts drive the allocation UI so a finance officer splits a cost inline on the invoice form instead of navigating away, and whitelisted methods exposed over the Frappe REST API let a grants portal, a BI tool or a funder-facing dashboard pull position data without direct database access. Permissions are delivered as Role Profiles — Grant Manager, Programme Lead, Finance Officer, Funder Read-Only — with User Permissions scoping each programme lead to their own awards, and a Grant Acquittal document assembles the final financial and narrative report pack with the source documents linked for audit.

Because every funder's rules differ, this is built to order rather than downloaded. We start with a scoping call, then work from your actual awards: two or three real agreements, the report formats your funders demand, your existing Cost Center and Project structure, and how you currently apportion staff time and indirect costs. From confirmed scope, typical delivery is two to four weeks. You get the app built against your Frappe/ERPNext version — v15 or v16 — installed on a staging bench for UAT with your own data, then a supervised production go-live with a documented rollback. The source is yours: a git repository handover, so nothing you rely on is locked behind us.