An ERP for a nonprofit is a finance and operations system that tracks every income and expense line by fund, grant and programme as well as by account, so restricted money is spent and reported as donors and funders intended. Its core is fund accounting; around it sit grant management, purchasing, payroll allocation and donor or funder reporting.
Many charities and nonprofits start with a standard accounting package and a spreadsheet per grant. That works until the number of funders, programmes or countries grows and month-end becomes a reconciliation exercise between thirty spreadsheets.
What is fund accounting and why do nonprofits need it?
Fund accounting tags transactions with the fund they belong to, so the organisation can show what each restricted gift or grant received, spent and has left. Commercial accounting asks "how much profit?"; fund accounting asks "was each pot of money used for its purpose?"
The reporting categories come from the framework you report under:
- In the US, FASB Accounting Standards Update 2016-14 (Not-for-Profit Entities, Topic 958; checked at fasb.org in October 2026) presents net assets in two classes: net assets with donor restrictions and net assets without donor restrictions.
- In the UK, charities preparing accruals accounts follow the Charities SORP. The Charity Commission's guidance, checked in October 2026, states that the Charities SORP 2026 applies to reporting periods starting on or after 1 January 2026. The SORP separates unrestricted, restricted and endowment funds.
- In the UAE, requirements depend on how and where the organisation is licensed. Confirm reporting rules with your auditors.
Your accountants decide policy; the ERP's job is to record transactions with enough dimensions that any of these views can be produced without rework.
What should a nonprofit ERP include?
Start with the finance core and add the modules where manual work is heaviest.
| Module | What it covers |
|---|---|
| Fund accounting ledger | Account plus fund, grant, programme, location and (if needed) donor dimensions |
| Grant management | Award, budget by line, reporting periods, eligible cost rules, drawdowns or claims |
| Allocations | Shared costs and staff time split across grants by agreed rules |
| Purchasing and approvals | Requisitions coded to grant lines, budget checks before commitment |
| Payroll allocation | Staff costs charged to grants by timesheet or agreed percentage |
| Income and donations | Gifts, restrictions, gift aid or similar schemes where applicable, integration with donor CRM |
| Reporting | Statement of financial activities or statement of activities by fund, grant reports, board packs |
| Multi-entity and multi-currency | Country offices, partner organisations, foreign currency grants |
Nonprofits whose grant rules, programme structures or country operations do not fit a package without heavy workarounds can look at custom ERP software, or at ERP modules built alongside an existing accounting system.
How should grant management work in ERP?
Treat each grant as a contract with its own budget, rules and reporting calendar, and check every commitment against it.
- Record the award: funder, amount, currency, period, restrictions and reporting dates.
- Load the approved budget by line and period.
- Code each requisition, purchase and timesheet to grant and budget line.
- Check availability before approval, so overspends are caught before money is committed.
- Apply eligible-cost rules (some funders exclude certain costs or cap overheads).
- Produce the funder report from the ledger, not from a separate spreadsheet.
- Track claims, drawdowns and receipts against the award.
Approval rules matter here; see our approval workflow design guide.
Illustrative example: one salary, three funders
A programme officer works on three grant-funded projects. The organisation agrees an allocation basis (timesheets or fixed percentages approved by the funders). Each month the ERP splits salary and related costs across the three grants and the unrestricted fund, checks each grant's staff budget line, and flags if one grant's line is close to its limit. When a funder asks for evidence, the allocation, the timesheets and the approvals are all linked.
What do donors and funders expect in reports?
Accurate spend against budget, in their format, on time. The ERP should make the standard report a click and the custom report a configuration, not a new spreadsheet each quarter.
- Spend by budget line against the approved budget, for the period and cumulative
- Variances with explanations
- Income received and balance remaining
- Supporting transaction listings when requested
- Output or impact figures, which usually come from programme systems rather than the ERP
Our guide to business dashboard KPI design helps with board and funder dashboards.
How should a nonprofit design its chart of accounts and dimensions?
Keep the chart of accounts short and put the detail in dimensions. A nonprofit that creates a new account for every grant ends up with thousands of codes and reports nobody can read.
A typical design:
| Dimension | Example values | Used for |
|---|---|---|
| Account | Salaries, travel, rent, grant income, donations | Nature of income or expense |
| Fund | Unrestricted, restricted, endowment (or with and without donor restrictions) | Statutory reporting |
| Grant or award | Each funder agreement | Funder reports and budget control |
| Programme | Education, health, emergency response | Programme reporting and boards |
| Location or country office | Each office or project site | Local management and multi-currency |
| Budget line | The funder's own budget categories | Mapping to funder report formats |
Mapping your accounts and dimensions to each funder's budget categories once, in the system, is what turns funder reporting from a spreadsheet exercise into a report.
What about country offices, partners and currency?
International nonprofits often receive a grant in one currency, spend it in several, and report back in the original currency. The ERP should record each transaction in the currency it happened in, convert it using the rate method the funder requires, and show any exchange differences separately.
Where money passes to partner organisations as sub-grants, treat each sub-grant like a mini award: an agreement, a budget, advances paid, expenditure reports received and reviewed, and the balance carried forward or refunded. Country offices that keep their own books should either work in the same system or submit trial balances in a fixed format that the head office maps automatically.
Common mistakes in nonprofit finance projects
- Creating a new account for every grant instead of using a grant dimension
- Allocating shared costs by a rule nobody wrote down, so funders challenge it
- Leaving funder budget mapping until the first report is due
- Treating the donor CRM as the source of truth for income in the accounts
Nonprofit ERP selection checklist
- Fund, grant and programme dimensions on every transaction
- Restricted and unrestricted views matching your reporting framework
- Grant budgets by line with availability checks before commitment
- Allocation rules for shared costs and staff time
- Funder-specific reporting formats
- Multi-currency grants and country office ledgers if relevant
- Integration with your donor CRM and payroll
- Audit trail and role-based access
- Data export, so you are never locked in
- Support for audit requests: transaction listings by fund and grant with source documents attached
- Year-end close that rolls fund balances forward correctly
Score each option against this list with your finance lead and at least one programme manager in the room. A system finance likes but budget holders find slow will produce poor coding, and poor coding defeats fund accounting.
How long should a nonprofit plan for the switch?
Plan around your financial year and your funder calendar rather than a fixed number of weeks. The safest cut-over is the start of a financial year or quarter, when no major funder report is due in the following weeks.
Before cut-over, agree with your auditors how restricted fund balances will be carried into the new system, and prove them: each fund's opening balance in the new ERP should equal its closing balance in the old records, and each active grant's cumulative spend and remaining budget should match what you last reported to the funder. Run the first funder report from the new system in parallel with the old method, compare the two, and only then retire the spreadsheets.
Train budget holders, not only finance staff. Programme managers who raise requisitions and approve timesheets decide whether grant coding is right at source, and most coding errors start with them.
When is custom ERP not the right approach for a nonprofit?
Smaller organisations with a few funders are usually best served by a mainstream accounting package used with disciplined fund and grant coding, or by a packaged nonprofit finance system. Custom work is a significant investment, and donors often expect overheads to stay low.
Custom fits larger nonprofits with many grants, multi-country operations, partner sub-grants, complex allocation rules or a donor and programme platform that must share data with finance. Read ERP vs custom development for the general trade-off.
How to start
Gather your chart of accounts, a list of active grants with their budgets and reporting formats, your allocation rules and the board reports you produce. The software requirements brief template gives you a structure, and the ERP reports finance teams need guide helps you define outputs before inputs.
Then discuss the project with us. Timeline Digital builds 2 to 3 key modules as a free pilot before the full project starts, for example grant budgets with commitment checks and funder reporting, so your finance team can test them on a live grant.