Supplier Order Confirmation: Check Delivery Date Changes

When a supplier confirmation shows a different delivery date from the PO, first check whether both dates describe the same event. Requested arrival, promised dispatch, estimated arrival and actual receipt are different milestones. Compare like-for-like dates and preserve any uncertainty about their meaning.

This guide is for buyers reviewing a supplier response to a business purchase order. It covers promised schedules, not parcel tracking or proof of actual delivery.

Check the date change in four steps

1. Identify the PO revision and affected item quantities.
2. Read each date label: dispatch, arrival, requested, estimated or confirmed.
3. Compare the same milestone for each quantity, using an explicit calendar basis.
4. Ask the supplier to clarify the change, then record the buyer’s decision separately.

Section 6 of the free exception-review worksheet captures the original text, interpreted date, affected quantity and follow-up.

Are both dates measuring the same event?

Record the field label as printed, the original date text, the order or line it applies to, and whether it is requested, estimated, confirmed or actual. Check the destination and document revision as well.

PO field	Confirmation field	Safe interpretation
Requested arrival	Confirmed arrival	Compare the two dates, retaining requested/confirmed status
Requested arrival	Planned dispatch	Different milestones; ask for the arrival commitment
Requested week	Exact ship date	Different precision and milestone; establish the basis first
Header delivery date	Several line delivery dates	Review each line and quantity; one header may not cover the order

Do not fill an absent arrival date using an assumed transit time. If a delivery term changes, record that separately rather than inferring its operational or contractual effect from the date fields.

Work through a split delivery

This standalone fictional example concerns PO-930: 100 each requested to arrive at the buyer’s warehouse on 2026-10-12. The supplier confirmation divides the order into two arrival commitments:

Confirmed quantity	Confirmed arrival	Difference from requested arrival
60 each	2026-10-12	Same date
40 each	2026-10-19	7 calendar days later

The confirmation preserves the total quantity but changes the schedule for 40 each. Marking the whole order “on time” because its first delivery matches the requested date would hide the change. Marking all 100 each “seven days late” would also be wrong.

Record the finding as “40 of 100 each confirmed seven calendar days after the requested arrival date; acceptance pending.” Use a named working calendar if you need working-day differences instead.

If the second date were labeled “dispatch” instead of “arrival,” the seven-day arrival comparison would no longer be supported. Ask for the expected arrival date and preserve the original dispatch value.

Resolve ambiguous formats before calculating

The text “10/11/2026” can be read as October 11 or November 10. A parser selecting one interpretation does not resolve the business ambiguity. Confirm the source convention or obtain an unambiguous date, retaining the original text.

“Week 42” also needs a year and week-calendar convention. “End of month” may be a window rather than a single-day promise. Record the precision actually provided instead of converting every expression into an invented exact date.

For timestamps, confirm the timezone if it affects the comparison. Do not introduce time-of-day precision to documents that only specify a calendar date.

Ask a question the supplier can answer

For the fictional split delivery:

PO-930 requests arrival of 100 each on 12 October 2026. Your confirmation lists 60 each arriving on 12 October and 40 each on 19 October. Please confirm that both dates are arrival dates at our warehouse and advise whether the remaining 40 each can meet the requested date. We have not yet recorded acceptance of the revised schedule.

Include the relevant line and revision references. Avoid characterizing a future schedule difference as an actual late delivery. Use the broader invoice and supplier discrepancy email structure to consolidate several questions in one follow-up.

Preserve the requested date and the decision

If an authorized reviewer accepts the revised schedule, record the accepted quantity, date, supporting reply and decision. Preserve the original requested date and the seven-day difference for the affected 40 each. Acceptance explains the difference; it does not erase it.

If another confirmation arrives, retain the version chain and check which lines changed. A newer file does not automatically establish that all revised terms were accepted.

Continue with the PO-to-confirmation guide for other price and quantity changes. The split-line guide covers grouping evidence when one order line becomes several source rows.

Common questions

Should I compare the latest date with the earliest date?

Only if that calculation answers a clearly stated question. For a split order, show each quantity’s schedule first; a single earliest or latest date can hide partial changes.

Is a confirmed date the same as an actual delivery date?

No. A confirmation records the supplier’s stated schedule. To check whether the delivery happened on that date, use the applicable receiving evidence and keep it separate from the earlier promise.