Supplier on-time delivery from purchase order receipts

Measure whether suppliers meet the date they agreed to, while keeping buyer changes and late partial deliveries visible.

Kartik Deshpande··5 min read

Calculate supplier on time delivery by comparing each due purchase order line with the receipts that meet its agreed date. State whether a line counts only when its full due quantity has arrived. If you count any receipt as on time, a vendor that ships one carton before the cutoff can look the same as one that fulfilled the line.

Keep the first accepted promise and the latest agreed date in separate fields. Oracle’s JD Edwards World procurement guide describes comparing the promised delivery date with the receipt date for supplier performance. Make the baseline, receiving event, and window explicit so buyers and suppliers can explain the same result.

Keep the date your buyer and supplier agreed to

Use the accepted supplier commitment for a score about supplier performance. Compare against the original request in a separate view if the business also wants to measure how often initial purchasing requirements are met. Retain who made a revision and when. A buyer-approved postponement and a vendor updating the date after missing it should not both erase the first commitment.

Match the expected event to the contract. If the commitment is arrival at your dock, use the accepted arrival event and record the warehouse timezone. If the commitment is a shipment date, use the handoff event instead and show transit separately. Where warehouse posting is delayed, keep observed arrival and posted receipt timestamps available for exception review.

Measure lines that were due during the period, including still-open late lines. If the denominator includes receipts posted during the period, a missing shipment never enters the calculation and the score can look better when performance worsens.

A monthly score should be reproducible after a buyer corrects a posting. Save the period cutoff and the date baseline that the report used, then show any revised result with a reason. Keep the source timezone in the evidence when two distribution centers post receipts on different business days.

Score partial shipments and missing lines

Assume three lines are due this week and the score requires full receipt by the end of the agreed date. Line A has 100 due and all 100 arrive on time. Line B has 60 due, but only 45 arrive before the cutoff and the other 15 arrive the next day. Line C has 40 due and no receipt. Assume there are no allowed early or late tolerance rules and no cancellations.

The line-based score is one out of three, or 33.3% rounded to one decimal place. A quantity-weighted view is 145 of 200 units, or 72.5% on time. Those are different signals. The first tells you how many lines reached full receipt by the date. The second helps explain why the line-based result was low and how many units were available on time.

If the buyer had approved Line C’s move to next week before the cutoff under your revision policy, report two lines due this week under the revised baseline. Keep Line C in the original-commitment view. The separate result shows how the operational expectation changed without losing the original supplier promise.

PO lineDue unitsReceived by cutoffFull line on time
A100100Yes
B6045No
C400No
Two views of the same supplier record
Promise
Original accepted date and approved revisions
Receipt
Matched line and quantity by cutoff
Measure
Full lines and on-time units
The on-time units explain the size of the shortage even when the line-based score stays unchanged.

Compare order dates and receipt records

Bring a sample of purchase orders and receipts into Permute to see which lines can be matched.

Give buyers the evidence to resolve exceptions

Check that the purchase order line, release number, item, unit, and receiving location match before counting quantities. If an invoice arrives first, keep the line open until an eligible receipt arrives. Three-way matching uses the receipt for payment review as well, but an approved invoice can’t establish arrival time.

Create one exception queue for missing promise dates, receipts with no linked line, and date changes after the cutoff. Let buyers confirm a match and retain the old evidence. Track the number of unevaluable lines beside the score so missing dates do not masquerade as successful delivery.

Add the measure to a supplier scorecard with its dates and denominator, then review the same basis with the vendor. A buyer can ask about recurring late lines on a lane and show the PO and receipt records.

Use OTIF when comparing a broader customer delivery commitment with its own order and quantity rules.

For a vendor conversation, include a small sample of on-time lines as well as misses. Check that late partials have their remaining quantities attached and that approved date changes are visible to both parties. Then review repeated exceptions by lane or item family, where a buyer can decide whether to change the order lead time or work with the supplier on the recurring shortfall.

Choose a due event for purchase orders with more than one delivery schedule on a line. If the schedules carry their own quantities and promise dates, measure them separately and report the level used. For example, a first release of 50 can arrive on time while a later release of 30 arrives late. Collapsing the releases to the last date would miss the information the buyer needs to act.

At month end, check whether a receipt reversal put a previously counted line below its full due quantity. Keep the reversal linked to the original receipt and determine whether it corrects an entry or reflects a return after acceptance. Those events may have different effects under the agreed receiving policy.

How Permute connects the evidence

Permute is the context layer we sell between business data and the AI tools people already use. Match supported purchase order and receipt sources by the identifiers buyers and warehouse staff use to discuss a delivery.

Define the date baseline, full-line test, and denominator once. A buyer can ask which lines drove the supplier’s score and inspect the original PO changes and receipt evidence they are allowed to see.

What stays in the source systems

The purchasing and receiving systems still record promises, receipts, and corrections. Permute can read and reconcile those records for analysis. It cannot verify physical arrival when no source recorded it or write a corrected receipt back.

Make the supplier score reproducible

Supplier on time delivery depends on an agreed date, a due-line population, and receipts tied to the right lines. Report full lines and units separately when partial receipts matter. Preserve revisions so a change to the schedule can be explained. Start the supplier review with the open lines and dated evidence that drove the score.

Review a supplier score with disputed lines

Bring the baseline dates, revision history, and receipt records for one reporting period.

Questions about supplier delivery measures

Should an early shipment count as on time?

Apply the agreed window. Early delivery can count when the buyer can accept and store it, while a delivery before a contracted window may count as an exception.

Should an open PO line with no receipt be included?

Include it once the due cutoff has passed if the line belongs to the score’s population. Keep it unfulfilled until an eligible receipt or approved cancellation changes its status.

Do canceled orders reduce the score?

Use a policy that distinguishes legitimate buyer cancellations from missed commitments. Preserve the cancellation reason and timing so the denominator is reproducible.