Progress claim workflow

NEOM's progress claim engine is SOPA-aware (Security of Payment Act). It runs the full lifecycle — draft, served, scheduled, certified, paid — and rolls every line into the project's final account view.

The claim lifecycle

A progress claim moves through these states. Each transition writes an audit entry with the actor, timestamp, and contractual day count.

1. draft — the claim is being built. Lines can be added, edited, or removed.
2. served — claim has been sent to the principal/superintendent. The SOPA clock starts; due dates are computed off this date.
3. scheduled — payment schedule received. The scheduled amount per line drives the variance column.
4. certified — payment certificate has been issued. Net amounts and retention are pinned.
5. paid — payment received and reconciled against the certificate.

Reverting a state is possible but writes a claim.status_reverted audit entry that surfaces in the §21.30 retention queue.

Building a claim

Open the project commercial workspace at /projects/<id>/commercial/claims and click New claim. The form picks the next period (default: month boundary) and seeds lines from the contract schedule of values. Each line shows:

• Item code — from the schedule of values; immutable once the claim is served.
• Previous claimed % — auto-populated from the prior period's certified value.
• This claim % — what you are claiming this period. Cannot be less than previous claimed.
• Retention % — pulled from the contract retention configuration; can be edited per line if the contract specifies graded retention.
• Variation references — variation orders certified this period appear as additional lines, grouped under the Variations sub-header.

The cashflow snapshot view (/projects/<id>/commercial/cashflow) recalculates as you edit lines in draft state, so you can see the impact on the cashflow forecast before serving.

Serving the claim

Click Serve to lock the line set and start the SOPA clock. NEOM:

• Renders a PDF payment claim using the project's letterhead template.
• Pushes a job to the email outbox addressed to the contract's recipients.
• Sends a claim.served event to the audit log with the served date and contract response window.
• Writes a cashflow snapshot so the recalc audit can replay the day's commercial state.

The detail page now shows the due-by date for the payment schedule and a countdown.

Scheduling and certifying

When the payment schedule arrives, click Apply schedule. The form accepts per-line scheduled amounts (or "scheduled = claimed" for a single-tick flow) and a reason field for any reduction. Certifying converts the scheduled amounts into the payment certificate; the net retention movement is calculated automatically.

If the principal certifies less than the claim, NEOM flags the variance for review and surfaces it on the executive dashboard.

Reconciling payment

When payment hits the bank, mark the claim paid with the bank reference and date. The accounts receivable register reconciles automatically; cashflow forecasts pull in the actual receipt instead of the projection.

Rollup to final account

Every certified claim feeds the final account view (/projects/<id>/commercial/final-account). It tabulates contract sum, certified variations, certified claims, retention released, and the projected outstanding balance. When the project closes, the final account is the single page that summarises the financial position.

For the formal SOPA reference timeline, see the variation workflow topic.