Resource Management is where ERP discipline either begins or breaks.
Resource Planning, Capacity Management, and Utilization Tracking looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Resource utilization report available in real-time; over-allocation resolved before project start; billable utilization target variance visible weekly.
The control flow a finance team actually needs.
Step 1
Capacity Calendar At Daily Granularity...
Step 2
Soft Vs. Hard Booking Distinction
Step 3
Skill-Based Search And Filter For...
Step 4
Utilization Report Shows Billable,...
Step 5
Over-Allocation Alerts Trigger On Booking
The ERP surface involved.
Module
Resource Management
Actors
Resource Manager, Project Manager, Finance Controller
Tier
Tier 2
Finance area
Project & Service Management (PSA) and Revenue Recognition
Region lens
US and UK finance teams
Publication date
June 6, 2026
Capacity calendar at daily granularity per resource; soft vs. hard booking distinction; skill-based search and filter for resource matching; utilization report shows billable, non-billable, and available hours by week/month; over-allocation alerts trigger on booking; standard cost rate versioned by effective date; integration with timesheet module for actuals; target utilization threshold configurable per role.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Capacity calendar at daily granularity per resource | Given a resource roster with skills, cost rates, and capacity calendars, and project resource requests by role and skill |
| Control 2 | soft vs. hard booking distinction | when a resource manager assigns a staff member to a task |
| Control 3 | skill-based search and filter for resource matching | then the capacity calendar is updated, utilization report reflects the booking, over-allocation alerts fire if the resource is double-booked, and actual hours from approved timesheets feed into utilization actuals |
| Control 4 | utilization report shows billable, non-billable, and available hours by week/month | negative) when a resource is booked beyond 100% capacity for a period then the system returns a 409 with error code RESOURCE_OVER_ALLOCATED. |
| Control 5 | over-allocation alerts trigger on booking | Resource utilization report available in real-time; over-allocation resolved before project start; billable utilization target variance visible weekly. |
| Control 6 | standard cost rate versioned by effective date | Resource utilization report available in real-time; over-allocation resolved before project start; billable utilization target variance visible weekly. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Resource managers maintain a skills-based roster of all billable staff with standard cost rates. Project managers submit resource requests specifying role, skill, and duration. The resource manager assigns staff, and the ERP updates their capacity utilization calendar. Actual hours from approved timesheets feed back into utilization reports. Finance uses utilization data to forecast revenue and labor cost, comparing planned versus actual billable utilization percentages by period. |
| Control rules | Capacity calendar at daily granularity per resource; soft vs. hard booking distinction; skill-based search and filter for resource matching; utilization report shows billable, non-billable, and available hours by week/month; over-allocation alerts trigger on booking; standard cost rate versioned by effective date; integration with timesheet module for actuals; target utilization threshold configurable per role. |
| Acceptance proof | Given a resource roster with skills, cost rates, and capacity calendars, and project resource requests by role and skill; when a resource manager assigns a staff member to a task; then the capacity calendar is updated, utilization report reflects the booking, over-allocation alerts fire if the resource is double-booked, and actual hours from approved timesheets feed into utilization actuals; (negative) when a resource is booked beyond 100% capacity for a period then the system returns a 409 with error code RESOURCE_OVER_ALLOCATED. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`resource` { external_id: string, name: string, entity_id: string, standard_cost_rate_minor: int64, currency_code: char(3), rate_effective_date: date }; `resource_skill` { resource_id: string, skill: string, proficiency_level: enum(BEGINNER,INTERMEDIATE,EXPERT), certified: bool }; `resource_booking` { external_id: string, resource_id: string, project_id: string, task_id: string, start_date: date, end_date: date, booking_type: enum(SOFT,HARD), hours_per_day: decimal }; `utilization_record` { resource_id: string, period: date, planned_billable_hours: decimal, actual_billable_hours: decimal, available_hours: decimal }; (reference, product may differ).API and events
`POST /v1/resources` { external_id, name, entity_id, standard_cost_rate_minor, currency_code } -> 201 { resource_id }; `POST /v1/resource-bookings` { external_id, resource_id, project_id, task_id, start_date, end_date, booking_type, hours_per_day } -> 201 { booking_id }; `GET /v1/resources/{id}/utilization` { period_start, period_end }; `GET /v1/resources/search` { skill, availability_start, availability_end }; emits `resource.over_allocated` and `resource.booking_created` events; idempotent via `external_id`.State transitions
`SOFT -> HARD` (booking confirmation); terminal `CANCELLED`; guard: HARD booking cannot be cancelled without PM approval; over-allocation raises alert but does not auto-block SOFT bookings (only HARD bookings trigger capacity conflict error).Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.