Link Supplier Payment Milestones to Verifiable Order Evidence

A payment stage works only when the event, evidence, reviewer, and authorization are defined before the supplier submits an invoice. “Production complete” can mean machining ended, inspection finished, the lot was accepted, or simply that a progress photo was sent. Those are different events, and one does not automatically prove the next.

This framework builds a milestone-to-evidence schedule for custom or long-lead parts. The signed purchase order, contract, approved changes, governing law, and authorized finance process control actual rights and payment. It does not recommend a deposit percentage, interpret entitlement, or tell a buyer to release or withhold money. For supplier and order context beyond the schedule, see bulk undercarriage-parts sourcing.

Freeze the order, payment baseline and total

Begin with the current signed purchase order or contract and its revision. Record the buyer and supplier legal entities, covered order lines and quantities, part numbers, drawing and specification revisions, currency, and the source of applicable tax treatment. Link every approved change order to the resulting commercial and technical baseline.

List each stage number, amount or percentage as the agreement states it. Recalculate the monetary amount and confirm that stages, approved adjustments, advance, and retention where used reconcile to the amended net order total. Keep tax, freight, tooling, optional work, and other components in separate fields when the documents treat them separately. A schedule whose original percentages still add neatly can still be wrong after a scope change.

Infor's current 2025.x supplier stage-payment documentation illustrates original and change-request fields linked to purchase-order lines. It is a software example, not a universal process or a statement of legal payment entitlement.

Record the source for due-date calculation, invoice requirements, payee identity, and controlled bank-detail verification. A change of payee or payment instructions requires the buyer's approved fraud-control process and independent verification using known contact routes. Do not place sensitive bank details in a widely shared milestone register. Name the baseline owner, version, approval date, and repository so reviewers use the same schedule.

Define each milestone as an observable event

For each stage, define the covered order line, quantity, event, location, target date or window, preconditions, completion criteria, exclusions, and the next dependent stage. “Production complete” is ambiguous until it states whether it covers all agreed operations for a named quantity and revision, and which records demonstrate that boundary.

Distinguish design-document approval, material availability, tooling completion, first-piece review, production completion, test completion, readiness for inspection, shipment, receipt, and another contract-defined event. These may support separate stages or simply be evidence inside one stage. The schedule must reflect the actual agreement, not a generic template.

Infor's stage-payment process documentation illustrates events such as design documents, test results, and receipt or inspection, along with planned, released, invoiced, and processed states. It also shows that goods receipt and stage-payment release can be separate in that software. Those labels do not establish acceptance or rights in another order.

Define supplier notice, evidence issue date, and any agreed partial-completion rule. If only part of a lot reaches the event, record the exact quantity and status. Do not prorate or authorize a partial amount unless the governing documents and authorized reviewers provide that path. Link any change in quantity, revision, process, or schedule to its approved change record.

Specify the evidence package and its issuer

Create an evidence list beside each event. Name every record, issuer or creator, authorized signer or reviewer, part and PO reference, drawing revision, lot or serial identity, quantity, issue date, required original or electronic format, and controlled repository. One document should prove only what its scope and issuer support.

A supplier progress photograph can show a dated view of items at a location. It cannot by itself prove quantity, dimensional conformity, material, completed processing, shipment, delivery, or buyer acceptance. An inspection report needs its method, characteristic scope, result, sample or lot identity, and responsible issuer. Transport evidence establishes the event within its own terms; it does not automatically prove technical acceptance.

The World Bank Group's current vendor invoicing and payment page illustrates invoice traceability to a purchase order or contract and fields such as goods, quantity, price, total, and supporting documents. These are organization-specific instructions, not universal invoice or milestone rules.

The Asian Development Bank's standard bidding document index shows that goods templates sit inside a defined procurement framework and have current and earlier variants. Its procurement of goods guide separates supply schedules, general and special conditions, and contract forms. These examples reinforce that evidence and payment conditions must come from the specific procurement documents; their clauses cannot be imported into a private parts order.

Maintain draft, issued, reviewed, and final states. If an agreed issuer, signature, quantity, or report is missing, mark it missing. If the document contradicts the order or another record, mark it conflict. Never invent a certificate, signature, inspection result, or KTSU capability to fill the row.

Separate completion, inspection, acceptance and payment authorization

Use separate status fields for supplier completion declaration, inspection, technical acceptance, commercial receipt, invoice validation, payment authorization, and bank processing. Name the role responsible for each one and link its decision to the applicable criterion and evidence.

Supplier completion means the supplier states that the defined production boundary has been reached. Inspection evaluates stated characteristics within its scope and records nonconformities. Technical acceptance, conditional acceptance, partial acceptance, or rejection exists only if the governing order defines the decision and authority. Delivery or receipt is another commercial or logistics event. None of these automatically substitutes for the others.

Accounts payable should validate the invoice against the applicable order, evidence package, accepted quantity and amount using its authorized controls. Tax and finance checks remain separate. The payment approver records authorization under the actual approval matrix; the bank's later processing status is not the same event.

Consider a stage labeled production complete when inspection has failed or remains incomplete. The completion evidence may be valid, while the inspection row is conflict or missing. Whether the contractual payment event occurred is a transaction-specific decision for the authorized parties. The register must show the two states without deciding legal acceptance or instructing payment action.

Define exception and change paths before they occur

Write an operating path for missing evidence, conflicting documents, partial milestones, nonconformity, rework, reinspection, delay, and changes to quantity or specification. Name who opens the issue, the affected order line and stage, immediate status, required evidence, reviewer, decision authority, revised date, and closure record.

A nonconformity should connect to the applicable quality process. Preserve the failed result, affected lot, containment, approved disposition or rework instruction, reinspection evidence, and final decision. Do not edit the original report to make the milestone appear complete. A corrected record should retain traceability to what changed and why.

Scope and price changes require an approved change order before the schedule baseline and stage amounts are changed. Preserve the original, requested and approved values. If part of a lot passes and part fails, hold the row open until the agreement's partial treatment and evidence are recorded. Do not infer a prorated payment rule.

Define invoice correction, credit-note, duplicate-invoice, and duplicate-payment controls with finance. Route disputed items through the named procurement, finance, quality, technical, and legal contacts. Reservation, waiver, set-off, withholding, amendment, or termination questions require authorized case review; a checklist cannot choose those remedies.

Reconcile closeout and retained obligations

At closeout, reconcile every stage amount, invoice, approved payment, credit note, and adjustment with the amended order total. Show the remaining balance. Separately reconcile ordered, delivered, accepted, rejected, reworked, and outstanding quantities. A zero financial balance does not prove all technical or documentary obligations are closed.

List open nonconformities, rework, final reports, certificates, as-built or traceability records, and any agreed final document pack. Route tooling or material title questions to their own commercial and legal owner. Record warranty start evidence, retention and release conditions only as the actual documents state them. Do not derive these rights from final payment.

Compare the supplier statement, buyer AP ledger, purchase order history, receiving records, quality status, and authorized schedule. Resolve duplicates, unmatched invoices, quantity differences, and old commitments. Obtain the required closeout approvals and retain the schedule and supporting records under the applicable policy.

Use the milestone-to-evidence schedule to expose three states

Schedule field	Normal	Missing	Conflict
Baseline and amount	Current order, change orders, currency and stage total reconcile	Latest change or tax/amount source is absent	Stage total differs from the amended order
Milestone event	Covered line, quantity, location, completion criteria and date are observable	“Complete” has no defined process boundary or quantity	Supplier status and current production record disagree
Evidence and issuer	Required report, issuer, signature, revision and item identity are traceable	Agreed inspection record or signature is absent	Report quantity, part revision or result contradicts the milestone claim
Review and acceptance	Completion, inspection, acceptance and receipt show separate authorized results	Required reviewer or criterion is not identified	Production is complete while inspection failed or remains open
Invoice and authorization	Invoice, supporting evidence, amount, approver and authorization status align	Invoice support or approval is absent	Invoice covers a quantity or stage different from the approved evidence
Closeout	Payments, quantities, open quality items, documents and retained obligations reconcile	Final document or closure owner is missing	Financial balance is zero while technical work remains open

Each row should also record the impact, owner, next evidence or decision, and target date. A normal row means the current baseline, observable event, required evidence, review result, invoice, and authorization align. A missing row remains open. A conflict must not be converted into approval through a total score or informal invoice edit.

The schedule succeeds when every stage can be traced from the signed order to a defined event, objective records, distinct technical and finance decisions, and a reconciled closeout. It supports authorized review; it does not itself release payment, create acceptance, or decide contractual rights.