Invoices
Submit invoices after delivery proof and track review, returned, accepted, and history states.
Milestone invoice tracker
Timber Supply Invoice
Invoice was accepted after completed community repair delivery; only closed status is visible here.
Invoice dossier
Confirm the claim, evidence, review path, and payment boundary before the invoice moves.
Invoice was accepted after completed community repair delivery; only closed status is visible here.
inv-429
Project link confirmed in invoice packet
Progress evidence, delivery proof, and inspection records are required before payment review
Closed status is visible in Register
Amount and claim basis
Invoice value, delivery basis, and milestone context stay close together so the participant can understand what is being reviewed without exposing restricted finance operations.
Accepted
| Field | What it confirms | Signal |
|---|---|---|
| Invoice value | Visible only when the participant is allowed to see the amount or approved planning signal. | Held inside the permissioned invoice file |
| Linked project | Keeps the invoice tied to the awarded project, delivery, or milestone record. | Project link confirmed in invoice packet |
| Milestone / delivery | Shows the work, material delivery, or closeout event that supports the claim. | Completed timber supply delivery for community repair works |
| Review state | Shows what the participant can do next without exposing restricted finance workflow. | Closed status is visible in Register |
Closed-loop value
Approved invoices become useful because they connect quote, order, delivery proof, invoice review, and supplier performance in one history chain.
Completed order
Accepted proof
Accepted invoice
Closed status
Performance history
Review path
The visible review path shows participant-facing progress only. Approval, release, rejection, and payment execution remain human-governed workflows.
Packet prepared
Invoice record, linked project/order, and claimant context are present.
Evidence attached
Progress evidence, delivery proof, and inspection records are required before payment review
Human verification
Reviewer checks evidence, order references, delivery proof, and inspection status.
Status visible
Supplier can see status, not restricted finance operations
Payment boundary
Register can show invoice status, supporting records, returned reasons, and payment schedule signals. It does not expose restricted finance approvals or release controls to external participants.
Human reviewer confirms evidence and linked records.
AI may summarize missing evidence but cannot approve or release payment.
Restricted finance operations stay outside Register.
Participant-facing status updates remain visible after review.
Documents and source records
Documents attached to the invoice should be readable in the Documents workspace and remain linked back to the same project, delivery, order, or milestone record.
Invoice file
Delivery proof or progress photos
Inspection note
Order or milestone reference
Tax summary where applicable
Returned correction note if needed
Closed-loop value
Approved invoices become useful because they connect quote, order, delivery proof, invoice review, and supplier performance in one history chain.
Timber supply invoice
Completed timber supply delivery for community repair works
Accepted with closed status visible
Feeds supplier history, on-time delivery score, and future matching confidence
Supplier can see status, not restricted finance operations