# Supplier acknowledgments

Order receipt, business acceptance, proposed changes and the quantity/date scope of supplier responses.

Reviewed: 2026-11-02

Tags: sourcing, purchase-orders, supplier-confirmations, edi

## Meaning

A supplier acknowledgment can record message processing or communicate a business decision. An order response may accept, reject or propose changes for specific schedules. [Oracle Fusion Cloud Procurement 25C, supplier acknowledgment](https://docs.oracle.com/en/cloud/saas/procurement/25c/oaprc/supplier-acknowledgment-of-purchasing-documents.html)

Read the response against the order revision, line or schedule, confirmed quantity and promised date. A receipt or processing acknowledgment concerns the message. A business response can confirm or propose changes to the order.

## Original example: accepted quantity and promised dates

Assume an invented order requests **100 brackets**, revision C, at **$12 each**, all due **16 November 2026**. A supplier response confirms **60 brackets** for that date and proposes **40 brackets** for **23 November**. Assume the buyer has not yet approved the proposed change.

The response covers **60 + 40 = 100 brackets**, but the quantity explicitly confirmed for the original date is **60/100 = 60%**. The later proposal concerns the other **40%**. Its date is **7 calendar days** after the requested date; that is a date difference, not seven business days or proof of actual lateness. No physical delivery has yet occurred in the example.

At the assumed unchanged price, the split values are **60 × $12 = $720** and **40 × $12 = $480**, totaling **$1,200**, excluding taxes and other charges. Equal total value does not make the schedules equivalent for production planning. The later 40 could matter to an assembly that requires all 100 at once.

If a later response instead proposes **$13** for the 40 brackets, the arithmetic becomes **$720 + $520 = $1,240**, a **$40** increase. That calculation describes the proposal, not an approved purchase value. The example illustrates scope and arithmetic only; it does not determine contract formation, legal acceptance, a supplier's actual capacity or the eventual delivery outcome.

## Technical acknowledgment and business response

Walmart's published **997 Functional Acknowledgement** guide describes a response reporting syntactical analysis of electronically encoded documents. It explicitly excludes the semantic meaning of the encoded information. Successful technical processing consequently does not, by itself, establish acceptance of the order's price, quantity or delivery commitment. [Walmart supplier developer documentation, 997](https://developer.walmart.com/suppliers/docs/997-functional-acknowledgement)

X12's supply-chain explanation distinguishes the **850 purchase order**, **855 purchase order acknowledgment**, **860 buyer-initiated change request**, and **865 seller-initiated change acknowledgment/request**. The 855 follows processing of the purchase order and can affirm it or indicate changes. The same overview separates those order exchanges from the **856 ship notice/manifest**, which concerns the shipment. An order acknowledgment is therefore not evidence that the goods have physically arrived. [X12, Supply chain transaction flow, purchase-order and shipment sections](https://x12.org/flow/supply-chain)

| Evidence described here | What it establishes within its stated scope |
| --- | --- |
| Technical acknowledgment | A processing or syntax response, rather than agreement to every commercial detail |
| Business order response | Acceptance, rejection or changes concerning the identified order scope |
| Shipment notice | Information about a shipment, rather than physical receipt by the buyer |

The table is a synthesis of the cited distinctions. Actual message versions, trading-partner profiles and business arrangements determine the permitted fields and interpretation; the transaction number alone does not define a particular supplier's promise.

## Whole-order and schedule-level meaning

Oracle's 25C guide distinguishes acknowledgment of the entire purchase order from acknowledgment at document-and-schedule level. With the latter arrangement, some schedules can be accepted and others rejected while the header is accepted; in the described application, rejected schedules are canceled. Proposed changes can concern price, quantity, delivery dates or split schedules. Such a proposal enters buyer review: approval updates the base document, while rejection returns it to pending supplier acknowledgment. [Oracle, Supplier acknowledgment of purchasing documents](https://docs.oracle.com/en/cloud/saas/procurement/25c/oaprc/supplier-acknowledgment-of-purchasing-documents.html)

This example explains why a header-level “accepted” label can coexist with less than complete acceptance of the original schedules. It does not establish that every procurement system cancels rejected schedules or uses Oracle's status transitions. A proposed delivery date and an approved changed schedule also represent different stages of that product's workflow.

Oracle separately documents configurable required acknowledgment levels and an **Acknowledge Within Days** control, including supplier-site defaults. The acknowledgment response deadline is consequently a different concept from the delivery date of the goods. Its value is a configured requirement, rather than a universal number of days. [Oracle 25C, Managing documents requiring supplier acknowledgment](https://docs.oracle.com/en/cloud/saas/procurement/25c/oaprc/how-you-manage-purchasing-documents-requiring-supplier.html)

## Confirmation detail varies with the system arrangement

SAP's purchasing lesson describes an arrangement recording only a general order-confirmation reference, without separate confirmed dates and quantities. It contrasts that with several confirmation types through which date/quantity information can be recorded and used in planning. Confirmation control determines expected types, sequence and relevance to planning and goods receipt. A populated acknowledgment-reference field therefore need not represent a complete dated quantity schedule. [SAP Learning, Monitoring purchase orders, order-confirmation monitoring](https://learning.sap.com/courses/purchasing-in-sap-s-4hana/monitoring-purchase-orders)

As explanatory synthesis, “confirmed quantity” can refer to different populations: a line, a schedule, an order total, a shipment or a remaining balance. Numbers are comparable only when their units and coverage match. Two acknowledgments of different revisions likewise need not describe one simultaneously valid commitment.

## Source versions and coverage

Reviewed **2026-11-02 PST**. Oracle references are from the **25C** documentation set; that release designation is not treated as a specific issue day. The cited live SAP, X12 and Walmart pages have no separately verified technical issue date here. This article describes information meaning and named software arrangements. It does not prescribe a company approval process or establish the legal effect of an acknowledgment in a particular transaction.

Related: [Supplier documents and evidence](index.md), [certificates of conformity](certificates-of-conformity.md), and [approved supplier lists](approved-supplier-lists.md).