Project Management - Project Setup is where ERP discipline either begins or breaks.
Project Setup with Work Breakdown Structure (WBS) and Budget Baseline 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: Budget baseline locked within one business day of project approval; cost variance visible to project manager within one hour of cost posting.
The control flow a finance team actually needs.
Step 1
WBS Minimum Five Hierarchy Levels
Step 2
Budget Baseline Is Version-Controlled...
Step 3
Cost Categories Include Labor,...
Step 4
Variance Reporting Shows Actual Vs....
Step 5
WBS Elements Map To GL Cost Codes
The ERP surface involved.
Module
Project Management - Project Setup
Actors
Project Manager, Finance Controller, ERP
Tier
Tier 1
Finance area
Project & Service Management (PSA) and Revenue Recognition
Region lens
US and UK finance teams
Publication date
June 3, 2026
WBS supports minimum five hierarchy levels; budget baseline is version-controlled and immutable after approval; cost categories include labor, material, subcontractor, travel, and overhead; variance reporting shows actual vs. budget vs. EAC in real-time; WBS elements map to GL cost codes; baseline changes require change-order workflow approval.
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 | WBS supports minimum five hierarchy levels | Given a project created with a five-level WBS and budget allocated per WBS element by labor, material, and overhead categories |
| Control 2 | budget baseline is version-controlled and immutable after approval | when the finance controller approves the budget baseline |
| Control 3 | cost categories include labor, material, subcontractor, travel, and overhead | then the baseline is locked (immutable), subsequent cost postings are compared against it in real-time, and variance reports show actual vs. budget vs. EAC |
| Control 4 | variance reporting shows actual vs. budget vs. EAC in real-time | negative) when a direct baseline edit is attempted on an approved baseline without a change-order workflow then the system rejects with 422 and error code BUDGET_BASELINE_LOCKED. |
| Control 5 | WBS elements map to GL cost codes | Budget baseline locked within one business day of project approval; cost variance visible to project manager within one hour of cost posting. |
| Control 6 | baseline changes require change-order workflow approval. | Budget baseline locked within one business day of project approval; cost variance visible to project manager within one hour of cost posting. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A project manager creates a new client project, defining the WBS with up to five levels of tasks and sub-tasks. Budget is allocated per WBS element by labor category, material, and overhead. The finance controller approves the budget baseline, which locks it in the ERP. Subsequent actual costs posted to the project compare against the approved baseline, and variances are highlighted in real-time dashboards. |
| Control rules | WBS supports minimum five hierarchy levels; budget baseline is version-controlled and immutable after approval; cost categories include labor, material, subcontractor, travel, and overhead; variance reporting shows actual vs. budget vs. EAC in real-time; WBS elements map to GL cost codes; baseline changes require change-order workflow approval. |
| Acceptance proof | Given a project created with a five-level WBS and budget allocated per WBS element by labor, material, and overhead categories; when the finance controller approves the budget baseline; then the baseline is locked (immutable), subsequent cost postings are compared against it in real-time, and variance reports show actual vs. budget vs. EAC; (negative) when a direct baseline edit is attempted on an approved baseline without a change-order workflow then the system rejects with 422 and error code BUDGET_BASELINE_LOCKED. |
| 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
`project` { external_id: string, name: string, status: enum(DRAFT,ACTIVE,ON_HOLD,CLOSED), budget_baseline_id: string, entity_id: string }; `wbs_element` { external_id: string, project_id: string, parent_id: string, level: int, name: string, cost_code: string }; `budget_baseline` { external_id: string, project_id: string, version: int, approved_by: string, approved_at: timestamp, status: enum(DRAFT,APPROVED) }; `budget_line` { baseline_id: string, wbs_element_id: string, cost_category: enum(LABOR,MATERIAL,SUBCONTRACTOR,TRAVEL,OVERHEAD), amount_minor: int64, currency_code: char(3) }; (reference, product may differ).API and events
`POST /v1/projects` { external_id, name, entity_id } -> 201 { project_id }; `POST /v1/projects/{id}/wbs-elements` { external_id, parent_id, level, name, cost_code } -> 201 { wbs_element_id }; `POST /v1/projects/{id}/budget-baselines` { lines: [{wbs_element_id, cost_category, amount_minor, currency_code}] } -> 201 { baseline_id }; `POST /v1/budget-baselines/{id}/approve` -> 200 { approved_at }; `GET /v1/projects/{id}/variance-report`; emits `project.baseline_approved` event; idempotent via `external_id`.State transitions
`DRAFT -> APPROVED` (on finance controller approval); terminal `SUPERSEDED` (when a change order creates a new baseline version); guard: APPROVED baseline cannot transition back to DRAFT; cost posting against a CLOSED project is blocked with PROJECT_CLOSED 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.