When this matters
A supplier says a milestone is complete and sends an invoice. Your team needs to understand what can actually be used, what still needs acceptance and what supporting access the supplier has provided.
Evidence to bring
- The agreed deliverables, acceptance criteria, reporting period and commercial inputs.
- Supplier-provided work records and linked code or release evidence you are authorized to access.
- Acceptance records and unresolved questions from the people using the delivered work.
See which tools connect directly and which import by CSV on the Integrations page. Check integration availability.
How to work through it
- Define the engagement and review period. Agree with the supplier which records can be shared.
- Connect claimed delivery to source records. Distinguish ticket completion, code merge, release and acceptance.
- Review supplier spend alongside supported delivery and scope movement. Take unresolved evidence questions into the partner review.
An illustrative review
Example figures for illustration.
| Recorded evidence or stated assumption | What it supports |
|---|---|
| Eight items are marked complete in a synthetic supplier report. | Eight completion claims to reconcile with source evidence. |
| Six items have release records; two have only merged code. | Six supported releases; deployment remains unverified for two. |
| Acceptance exists for four of the six releases. | Four accepted items and two awaiting a recorded decision. |
The next decision
Agree the evidence needed to resolve the remaining items and the next delivery commitments. Use the shared record to support the invoice discussion without automatically rejecting or approving charges.
What the evidence cannot tell you
Missing access means unknown coverage, not proof that work was not done. A release record does not establish fitness for purpose; acceptance criteria and the buyer’s review still matter.
AI analysis in ScopeWorth is optional and billed in credits. Evidence, cost attribution and reports work without it. Compare plans and limits.
Questions about this workflow
Do I need access to the supplier’s entire repository?
Use only records you are authorized to access. Discuss a suitable connector, supported import or shared evidence with the supplier; incomplete access must remain visible.
Does a completed ticket prove production delivery?
No. Completion, code merge, deployment and acceptance are different milestones and need their own evidence.