Project Billing - Fixed-Fee Milestones is where ERP discipline either begins or breaks.
Milestone-Based Billing and Revenue Recognition 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: Milestone invoices issued within 24 hours of acceptance; deferred revenue balance accurate to the day; no revenue recognized before contractual trigger.
The control flow a finance team actually needs.
Step 1
Milestones Configurable With...
Step 2
Customer Acceptance Document Upload...
Step 3
Deferred Revenue Auto-Calculated When...
Step 4
Invoice Generated Automatically On...
Step 5
Milestone Status Visible On Project...
The ERP surface involved.
Module
Project Billing - Fixed-Fee Milestones
Actors
Project Manager, Billing Clerk, Customer, Revenue Accountant
Tier
Tier 2
Finance area
Project & Service Management (PSA) and Revenue Recognition
Region lens
US and UK finance teams
Publication date
June 5, 2026
Milestones configurable with independent billing amounts and recognition triggers; customer acceptance document upload required before recognition; deferred revenue auto-calculated when billing precedes recognition; invoice generated automatically on milestone approval; milestone status visible on project dashboard; support partial milestone billing with pro-rata recognition.
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 | Milestones configurable with independent billing amounts and recognition triggers | Given a project with five milestones each having a billing amount and a customer-acceptance recognition trigger |
| Control 2 | customer acceptance document upload required before recognition | when the PM marks a milestone complete and the customer acceptance document is uploaded |
| Control 3 | deferred revenue auto-calculated when billing precedes recognition | then the invoice is auto-generated, deferred revenue is adjusted if billing preceded recognition, and revenue is recognized at acceptance date not invoice date |
| Control 4 | invoice generated automatically on milestone approval | negative) when revenue recognition is attempted without customer acceptance document then the system rejects with 422 and error code ACCEPTANCE_DOCUMENT_REQUIRED. |
| Control 5 | milestone status visible on project dashboard | Milestone invoices issued within 24 hours of acceptance; deferred revenue balance accurate to the day; no revenue recognized before contractual trigger. |
| Control 6 | support partial milestone billing with pro-rata recognition. | Milestone invoices issued within 24 hours of acceptance; deferred revenue balance accurate to the day; no revenue recognized before contractual trigger. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A software implementation project has five contractual milestones (design, development, UAT, go-live, warranty). Each milestone is defined in the ERP with a billing amount and a revenue recognition trigger (customer acceptance vs. delivery). When the PM marks a milestone complete and the customer signs acceptance, the ERP automatically generates the milestone invoice and schedules revenue recognition. Revenue is recognized at the point of customer acceptance, not invoice date, with deferred revenue adjusted if billing preceded recognition. |
| Control rules | Milestones configurable with independent billing amounts and recognition triggers; customer acceptance document upload required before recognition; deferred revenue auto-calculated when billing precedes recognition; invoice generated automatically on milestone approval; milestone status visible on project dashboard; support partial milestone billing with pro-rata recognition. |
| Acceptance proof | Given a project with five milestones each having a billing amount and a customer-acceptance recognition trigger; when the PM marks a milestone complete and the customer acceptance document is uploaded; then the invoice is auto-generated, deferred revenue is adjusted if billing preceded recognition, and revenue is recognized at acceptance date not invoice date; (negative) when revenue recognition is attempted without customer acceptance document then the system rejects with 422 and error code ACCEPTANCE_DOCUMENT_REQUIRED. |
| 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_milestone` { external_id: string, project_id: string, name: string, billing_amount_minor: int64, currency_code: char(3), recognition_trigger: enum(CUSTOMER_ACCEPTANCE,DELIVERY), status: enum(PENDING,COMPLETE,INVOICED,RECOGNIZED), due_date: date }; `milestone_acceptance` { external_id: string, milestone_id: string, accepted_by: string, accepted_at: timestamp, document_url: string }; `deferred_revenue_entry` { external_id: string, contract_id: string, milestone_id: string, deferred_amount_minor: int64, currency_code: char(3), recognized_at: timestamp }; (reference, product may differ).API and events
`POST /v1/project-milestones` { external_id, project_id, name, billing_amount_minor, currency_code, recognition_trigger, due_date } -> 201 { milestone_id }; `POST /v1/project-milestones/{id}/complete` -> 200; `POST /v1/project-milestones/{id}/acceptance` { document_url, accepted_by } -> 201 { acceptance_id }; `POST /v1/project-milestones/{id}/invoice` -> 201 { invoice_id }; `POST /v1/project-milestones/{id}/recognize` -> 201 { journal_entry_id }; emits `milestone.recognized` event; idempotent via `external_id`.State transitions
`PENDING -> COMPLETE -> INVOICED -> RECOGNIZED`; guard: RECOGNIZED is terminal; INVOICED before RECOGNIZED creates deferred revenue entry; recognition blocked until acceptance document exists for CUSTOMER_ACCEPTANCE trigger type.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.