5. Granted

Awarded applications become Grants. This is the screen finance officers spend most of their time on.

The grant detail page

Long vertical page with several cards:

Header

• Grant title, reference (auto-generated), donor name, cycle name.
• Status pill (Awarded / Active / Closed).
• Grant amount, period, currency, contract number.
• "Edit grant" button (Finance/Admin only) for amount, currency, dates, contract number.

Projects card

One row per executing project. Each row shows its Odoo sync status (Synced / Sub-grant Draft / Sub-grant Started / Pending / Failed). Click "+ Add project" to create one — this lands the project in Odoo unless you mark it as "not in Odoo" (used for sub-grant partners that book elsewhere).

The Add / Edit modal asks for:

• Project name.
• Organisational units — the implementing organisational unit. Default for the Odoo company.
• Odoo company (optional override, F2-B+) — pick a different res.company than the organisational unit's default. Use only for joint-implementation cases where the booking entity and the executing organisational unit differ. Leave on the default in the typical case.
• Analytic code — [COUNTRY3]-[DONOR3]-[GRANT3] format. Used as the project's Plan 1 analytic account code in Odoo.

What it looks like

Illustration only — your projects card will list every project on this grant with the exact same column structure.

Budget card

The donor-facing budget. One row per category defined on the cycle template (see chapter 12.3). Each row carries:

• Description — optional note shown to the donor.
• Budget amount — what you committed to the donor. Either a manual amount (when the cycle has no detail template) or a computed SUM of detail rows (when it does).
• Allocated — total of per-project allocations for this line. Difference column highlights gaps.
• Odoo column — Plan 2 analytic account reference + a "● synced" tag once the line is pushed to Odoo.

When the cycle has a detail template, each category expands into detail rows (Country Director, International travel, etc.). You can edit units × value inline, add new rows per category, or remove rows. The SUM rolls up live to the category.

What it looks like

Illustration only — rendered with the real design-system classes so it stays in step as the app evolves. The live screen shows all 27 detail rows under HR and all six categories; the IND row carries a dashed border on the Budget cell to signal it's a computed value, not directly editable.

Budget vs Actual card

Per category: Budget, Actual (from Odoo + manual sub-grant entries), Remaining, % spent with a progress bar. Color codes: teal < 85%, amber 85–100%, red > 100%.

What it looks like

Illustration only — the Spend bar turns amber at 85–100% and red above 100%, so overspends jump out at a glance.

Action buttons (Finance/Admin)

• Save — persist budget edits.
• Save & sync to Odoo — persist + push the budget to Odoo. Creates Plan 2 + Plan 3 analytic accounts and writes per-project budget rows at both category and detail granularity.
• Refresh actuals — pull analytic lines from Odoo and update the Actual column. Per-detail amounts populate budget_detail_lines per project (visible on each project detail page and aggregated on the grant's EU export).