Grant tracking for nonprofits on Dynamics 365

A grant is a restricted fund with a contract attached. It has a funder, an award period, a budget by category, allowable and unallowable costs, reporting deadlines, and often a reimbursement mechanism where the nonprofit spends first and claims later. Tracking it means answering, at any moment, how much has been spent against each budget line, how much has been claimed, what is due to the funder and when, and whose time has been charged to it. Dynamics 365 has no grants module for nonprofits; it has projects, funds, and Dataverse, and the working pattern assembles them. This guide sets it out. The fund accounting guide covers the ledger side that this builds on.

Two halves: relationship and money

Grant tracking splits naturally between the CRM side — the funder relationship, the application pipeline, the award and its reporting obligations — and the ledger side — budget, spend, and claims. Keep them distinct and link them by grant identifier.

On the CRM side, the funder is an account, the programme officer a contact, and each application an opportunity or a custom application record moving through a business process flow: identified, letter of intent, submitted, awarded or declined. The award itself is a record with the award period, total, reporting schedule, and conditions. Reporting deadlines become activities or a journey that reminds the grant manager. This is a small model to build and pays for itself the first time a report is not missed.

On the ledger side, the award becomes a project and a fund.

Grant as project

In both Business Central and Finance, the project (job) is the natural container for a grant's budget and spend:

• Project per grant, with the grant identifier in the project number, linked to the fund dimension and the programme dimension.
• Project tasks or categories per budget line — personnel, travel, equipment, subawards, indirect — matching the funder's approved budget so that budget-versus-actual reads in the funder's language.
• Project budget loaded from the award, by task and period where the funder budgets by year.
• Every cost posted to the project: purchase invoices coded to the project task, expense claims, and — the important one — staff time.

Finance's public-sector configuration adds a grant entity that links to projects and funds and carries the funder, CFDA or equivalent programme reference, and billing terms. It is designed for government grantees and works well for nonprofits with large federal or state awards; the public sector features guide covers it. Nonprofits without that scale get the same result from a plain project with a fund dimension.

Staff time across grants

Personnel is usually the largest budget line, and funders expect it to be supported by time records, not by a fixed allocation set at the start of the year. That means timesheets against projects. Business Central time sheets and Finance's project timesheets both post hours to the project at the employee's cost rate, producing the personnel cost per grant that a claim is built on.

What neither product provides is effort certification — the periodic signed confirmation that reported effort is accurate, required under US federal Uniform Guidance and by some other funders. It is handled with a Power Automate approval over the period's timesheet totals, an ISV, or paper. Decide which before the first federal award, not at the first audit.

Payroll cost itself arrives from the payroll system as a journal; allocating it to projects by the timesheet percentages is either a payroll-system feature, a Finance allocation rule, or a monthly journal. The allocation basis must be the actual time, and the documentation must survive an audit.

Indirect costs

Most funders allow an indirect cost recovery — a negotiated rate applied to direct costs, or a de minimis percentage. Model it as a project task for indirect, with the charge calculated monthly from direct spend by an allocation rule or a recurring journal. Finance's public-sector grant setup can hold the rate; elsewhere it is a parameter the finance team applies. Track recovered indirect against the ceiling in the award, because exceeding it is a disallowance.

Claims, drawdowns, and revenue

Reimbursement grants are invoiced to the funder after the spend. The project's unbilled cost by category is the claim; the project invoice — sales invoice from the project in BC, project invoice proposal in Finance — is the document; the funder is the customer. Advance-funded grants are the reverse: cash received up front as deferred revenue, released as spend occurs. Both patterns are standard project accounting; the discipline is running the claim on the funder's cycle and reconciling claimed-to-date against the award total.

Revenue recognition for grants follows the restriction: conditional grants are recognised as conditions are met, unconditional ones when awarded. In practice most nonprofits recognise reimbursement grants as costs are incurred, which the project's revenue-with-cost treatment supports. Agree the policy with the auditor and configure the project's posting accordingly.

Funder reporting

Each funder wants a financial report in its own format — budget, spend to date, this period, remaining — sometimes by year of a multi-year award. The project's budget-versus-actual by task is the source; the format is a financial report in BC, a Power BI paginated report, or Excel over the project data. Build one template per major funder rather than one per grant. Narrative reports are documents; store them against the award record in the CRM with the submission date.

Grants made, briefly

Foundations and intermediaries that make grants have the opposite process: applications in, review and scoring, award, disbursement schedule, grantee reporting. That is a Dataverse application with Power Pages for the grantee portal and Power Automate for the review workflow, or a grant-management ISV. The finance side is payables with a project or fund per grant. It is a different product from what this guide covers, although organisations that both receive and make grants often want the same constituent records underneath.

Where it breaks

Grant tracking fails when spend is coded to the fund but not the project, when time is not recorded against projects, or when the claim is built in a spreadsheet from the ledger export because the project setup was too coarse. Set the projects up in the funder's budget structure, make the project code mandatory on every cost, and the claim and the report become queries rather than reconstruction.