Define the payment issue
A project team may ask why an invoice remains unpaid. Identify the amount, period, deliverable, and contractual basis before searching the whole folder.
Collect the agreement, amendments, schedules, and relevant correspondence. Record gaps in the document set.
Extract the trigger sequence
Capture the steps described in the contract, including delivery, inspection, acceptance, certification, invoice, or other conditions where relevant. Preserve exact wording and source references.
Do not assume that these steps are interchangeable. The sequence and legal effect depend on the actual agreement and applicable law.
Test a signed delivery note
Suppose a delivery note is signed but the contract refers to a separate acceptance procedure. Record what the note proves and what still requires review.
Ask the project team about the factual process and counsel about the contractual effect. Avoid an automatic conclusion that any signature establishes entitlement to payment.
Map objections and responses
Include defect notices, reservations, revised invoices, and responses. Distinguish a factual dispute over performance from an issue about the meaning of the payment clause.
Keep amounts, currencies, and calculations traceable. Technical valuation questions may require specialist review.
Prepare the action note
Give the team the trigger map, evidence, open questions, and approved next steps. Identify who must obtain missing records or provide advice.
When drafting a demand or response, use only the verified facts and approved legal position. Preserve the evidence file behind the final communication.
Sources and next steps
This is an editorial workflow guide for legal professionals. The suggested checks are our practical recommendations, not a statement that a regulator requires a particular software workflow.
Explore Review Matrix and Timeline Builder, or review Judicio's regional coverage and limitations. Check the underlying source and your organisation's approved process before relying on an output.