Grant hub · budgets · donor reporting

Your grant hub — budgets, amendments, and donor-ready reporting

Grants are the operational centre of your NGO workspace: structure budget lines, document amendments, monitor burn rate, and connect procurement and finance on one UUID grant record per donor award.

Operational centre

Procurement, travel, programmes, and finance attach to the same grant record.

Budget lines

Structure spend by category and line code with grant currency validation.

UUID everywhere

APIs, exports, and deep links use public UUIDs — not internal numeric IDs.

Everything donors expect on one grant record

From award metadata to line-level budgets and amendment history — built for NGO programme and finance language.

Grant records

Donor, period, currency, funding type, status, attachments, and archive — scoped per organisation tenant.

Budget lines

Line codes, categories, amounts, and sort order. Procurement and finance commitments map to the right line.

Amendments

Effective dates, summaries, and structured change JSON — who recorded what, when, for audit response.

Spending & exports

Burn rate and spending views when finance is enabled. Export packs for donor reporting without shadow spreadsheets.

The grant hub connects your NGO

Other modules do not duplicate grant master data. They reference the same UUID grant and budget lines your programme team maintains.

  • Nested APIs: budget lines and amendments under `/api/grants/{uuid}`
  • Depends on `grants` + `budgets` modules; programmes and finance extend the hub
  • Tenant isolation — cross-organisation access returns 404
  1. 1

    Create the grant

    Load donor award, currency, dates, and initial budget structure. Import bulk lines when migrating from spreadsheets.

  2. 2

    Operate on lines

    Purchase requests, travel, and payments pick grant lines at source — approvals show financial impact before commit.

  3. 3

    Report with confidence

    Programme indicators and finance spending read from one structure. Amendments document donor-approved changes.

Programme–finance alignment

Country teams and HQ share one version of the budget — reducing wrong-grant coding after the fact.

Step 1

Programme owns structure

Programme managers maintain lines and delivery context; finance monitors committed and actual spend on the same rows.

Step 2

Spend ties to lines

Procurement PR/PO lines and travel can reference grant budget lines when those modules are on.

Step 3

Approvals & audit

Budget changes and high-value spend route through your tenant approval definitions with step history.

Modules that plug into grants

Enable the hub first, then turn on extensions as your NGO matures.

Programmes & M&E Finance & spending Procurement Approvals

Frequently asked questions

Common questions from NGO programme, finance, and IT teams evaluating this module.

What is the grant hub used for?

Grants are the operational centre for donor funding: budget lines, amendments, spending views, attachments, and exports that programme and finance teams share.

Can procurement reference grant budget lines?

Yes. When procurement is enabled, purchase request and order lines can link to grant budget lines so committed spend maps to the correct funding.

Are grant identifiers safe for external links?

Public APIs and deep links use UUIDs, not internal integer primary keys, so integrations and bookmarks stay stable.

Pilot grant tracking

Create your organisation and load your first grant structure.