Manufacturing · SAP S/4HANA

How to Handle a Supplier Confirmation with Price and Date Changes in SAP S/4HANA

When a supplier confirms a purchase order on different terms, such as a higher net price or a later delivery date, the confirmation can't simply be keyed in. Each item has to be compared with the PO, measured against the company's price tolerance and need-by dates, and either accepted through the normal PO change workflow or held for a buyer to decide.

This guide follows a conceptual walkthrough set in SAP S/4HANA: reading the supplier's order confirmation, finding the PO in Manage Purchase Orders, writing down every delta, applying tolerance policy PRC-TOL-05, confirming the items that fit, repricing one item through the change workflow, holding an out-of-tolerance item for buyer review, alerting the MRP planner and leaving a before-and-after audit sheet.

  • Who does itBuyer or purchasing agent, with a senior buyer (and manager above a threshold) deciding out-of-tolerance changes
  • How oftenEach time a supplier confirmation arrives with terms that differ from the PO
  • Steps12 steps · 6 systems

Watch the full workflow

a conceptual walkthrough of the agent's run, with sample data.

In this conceptual walkthrough, an AI agent picks up Vectra Castings' order confirmation OC-VC-55871 for PO 4500018832 from the purchasing inbox and opens the PO in Manage Purchase Orders, filtered by PO, supplier 300417 and plant 1100. It compares the three items and writes each delta to a variance sheet: item 10 is up 1.41% (+240.00 USD), item 20 is up 9.62% (+700.00 USD) and moves from 11/20 to 12/04, and item 30 matches. Under tolerance policy PRC-TOL-05 and the PO change workflow rules, it confirms items 10 and 30, changes item 10's net price to 43.10 (released by rule WF-CHG-01 with no approver), and verifies the saved values by reopening the PO. Item 20 is left unchanged and sent to buyer01 as review request RV-2207; the buyer replies to keep it on hold. The agent emails the planner a late-delivery alert for production order 1004417, reads the approval history and change log, and writes a before-and-after audit sheet.

Conceptual walkthrough: the screens are generic stand-ins modeled on how SAP S/4HANA lays out this work, not the product's own interface, and every company, vendor and value is sample data. Workflow and screens vary by ERP version and configuration. No vendor partnership is implied.

  1. 0:23Read the supplier confirmation
  2. 0:39Find the PO and read what it says today
  3. 1:26Compare the confirmation with the PO, item by item
  4. 1:58Write down every delta before applying any rule
  5. 2:43Is each change within tolerance?
  6. 3:37Record confirmations for the items that fit
  7. 4:05Change the in-tolerance price on the PO
  8. 4:22Reopen the PO and prove it saved
  9. 4:45Hold the out-of-tolerance item and request review
  10. 5:21Buyer decides on the held item
  11. 5:42Alert the planner about the late date
  12. 6:08Check approval history and change log, then write the audit sheet

Systems involved

You need access to each of these before you start. In the walkthrough the agent works in all of them from one desktop, signed in as the user.

  • SAP S/4HANA – Manage Purchase OrdersFind and open the PO, edit item net price, request review, read approval history and change log
  • SAP S/4HANA – supplier confirmation entry and PO change workflowRecord confirmed quantities and dates; workflow rules that release or route price changes
  • Microsoft Outlook (web)Purchasing inbox with the supplier confirmation; late-delivery alert to the planner
  • ExcelPO-4500018832-variance.xlsx: variance and before-and-after audit tabs
  • Microsoft TeamsCastings buyers channel where the review request is posted and the buyer replies
  • LaunchAI agent run panelRun steps, policy in force and closing summary

What you start with

  • Supplier order confirmation email and PDF (OC-VC-55871.pdf) for PO 4500018832
  • Purchase order 4500018832 in SAP S/4HANA (3 items, net value 29,160.00 USD)
  • Price tolerance policy PRC-TOL-05: increase ≤ +2.00% and ≤ 500.00 USD; delivery on or before need-by
  • PO change workflow rules WF-CHG-01 to WF-CHG-03
  • Production order 1004417 start date (11/23) for the need-by check

What you end with

  • Supplier confirmations recorded for items 10 and 30 (reference OC-VC-55871)
  • Item 10 net price changed 42.50 → 43.10, released by workflow rule WF-CHG-01
  • Review request RV-2207 for item 20, pending with buyer01; item 20 unchanged
  • Late-delivery alert email to planner03
  • Variance and audit sheet PO-4500018832-variance.xlsx

The workflow at a glance

Action Decision Human review Select a step to jump to how it's done.

  1. 01 Action · Microsoft Outlook (web) Read the supplier confirmation
  2. 02 Action · SAP S/4HANA – Manage Purchase Orders Find the PO and read what it says today
  3. 03 Action · Confirmation PDF and SAP S/4HANA Compare the confirmation with the PO, item by item
  4. 04 Action · Excel Write down every delta before applying any rule
  5. 05 Decision · Excel and SAP S/4HANA PO change workflow Is each change within tolerance? Yes Record the confirmation and, for a price change, change the PO so the workflow can release it. No Hold the item: change nothing on it and request buyer review.
  6. 06 Action · SAP S/4HANA – supplier confirmation entry Record confirmations for the items that fit
  7. 07 Action · SAP S/4HANA – Manage Purchase Orders Change the in-tolerance price on the PO
  8. 08 Action · SAP S/4HANA – Manage Purchase Orders Reopen the PO and prove it saved
  9. 09 Action · SAP S/4HANA – Manage Purchase Orders Hold the out-of-tolerance item and request review
  10. 10 · Human review · Microsoft Teams Buyer decides on the held item
  11. 11 Action · Microsoft Outlook (web) Alert the planner about the late date
  12. 12 Action · SAP S/4HANA – Manage Purchase Orders and Excel Check approval history and change log, then write the audit sheet

Step-by-step: how to do it

  1. Action · Microsoft Outlook (web) · 0:23 in the video

    Read the supplier confirmation

    Open the purchasing inbox and find the supplier's confirmation for the PO. Read the email for what the supplier says changed, then open the attached confirmation PDF, which carries the actual prices and dates you will compare.

    In the video

    Vectra Castings, 'Order confirmation OC-VC-55871 — your PO 4500018832 (revised terms)'.

    Received
    Tue 11/3, 7:18 AM
    Attachment
    OC-VC-55871.pdf (96 KB)
    Email says
    Items 10 and 20 repriced (alloy surcharge); item 20 delivers later

  2. Action · SAP S/4HANA – Manage Purchase Orders · 0:39 in the video

    Find the PO and read what it says today

    Open the Manage Purchase Orders app and filter by purchase order number, supplier and plant. All three must match the confirmation; if the search returns nothing or a different supplier, stop. Open the PO and note the header values and each item's net price, delivery date and confirmation status before anything changes.

    In the video
    PO
    4500018832
    Supplier
    300417 Vectra Castings
    Purchasing org.
    1000 Granite Ridge US
    Plant
    1100 Hamilton
    Net value
    29,160.00 USD
    • Item 10 · MAT-77102 Pump housing casting Not confirmed
      Qty
      400 EA
      Net price
      42.50
      Delivery
      11/20/2026
    • Item 20 · MAT-77140 Impeller blank Not confirmed
      Qty
      400 EA
      Net price
      18.20
      Delivery
      11/20/2026
    • Item 30 · MAT-77155 Seal plate Not confirmed
      Qty
      800 EA
      Net price
      6.10
      Delivery
      11/20/2026

  3. Action · Confirmation PDF and SAP S/4HANA · 1:26 in the video

    Compare the confirmation with the PO, item by item

    Put the confirmation next to the PO. First check the header references (PO number, supplier number, ship-to plant). Then compare each item's quantity, unit price and delivery date with the PO line, and read the supplier's notes for the reason behind any change.

    In the video

    OC-VC-55871 rev 1, stamped REVISED TERMS.

    • Item 10 Price differs
      Price
      43.10 vs 42.50
      Delivery
      11/20 unchanged
    • Item 20 Price and date differ
      Price
      19.95 vs 18.20
      Delivery
      12/04 vs 11/20

      Supplier note: delivery moved due to core-box rework

    • Item 30 Identical to PO
      Price
      6.10
      Delivery
      11/20

  4. Action · Excel · 1:58 in the video

    Write down every delta before applying any rule

    In a variance sheet, record for each item the PO value, the supplier's value and the exact difference: unit price change in amount and percent, extended value change, and delivery date change in days. Note anything the date change affects downstream, such as a production order start.

    In the video
    • Item 10 · Net price
      PO
      42.50
      Supplier
      43.10
      Delta
      +0.60 (+1.41%)
    • Item 10 · Extended
      PO
      17,000.00
      Supplier
      17,240.00
      Delta
      +240.00
    • Item 20 · Net price
      PO
      18.20
      Supplier
      19.95
      Delta
      +1.75 (+9.62%)
    • Item 20 · Extended
      PO
      7,280.00
      Supplier
      7,980.00
      Delta
      +700.00
    • Item 20 · Delivery
      PO
      11/20/2026
      Supplier
      12/04/2026
      Delta
      +14 days

      PO 1004417 starts 11/23

    • Item 30 · Price and date
      Delta
      none

  5. Decision · Excel and SAP S/4HANA PO change workflow · 2:43 in the video

    Is each change within tolerance?

    Check your company's PO change workflow rules and written tolerance policy. A price increase is acceptable only if it is within both the percentage and the amount limit, and a confirmed date is acceptable only if it is on or before the need-by date. Mark each item within, outside or matching.

    • If yes Record the confirmation and, for a price change, change the PO so the workflow can release it.
    • If no Hold the item: change nothing on it and request buyer review.
    In the video
    WF-CHG-01
    Increase ≤ 2.00% and ≤ 500.00 USD extended: no approver, auto-release
    WF-CHG-02
    Increase > 2.00% or > 500.00 USD: buyer01 (test)
    WF-CHG-03
    Extended change > 1,000.00 USD: + mgr02 (test)
    • Item 10 WITHIN
      Percent
      1.41% ≤ 2.00%
      Amount
      240.00 ≤ 500.00
      Date
      11/20 ≤ 11/20
    • Item 20 OUTSIDE · CONFLICT
      Percent
      9.62% > 2.00%
      Amount
      700.00 > 500.00
      Date
      12/04 > 11/20
    • Item 30 OK
      Result
      match, confirm as ordered

  6. Action · SAP S/4HANA – supplier confirmation entry · 3:37 in the video

    Record confirmations for the items that fit

    Open the confirmation entry screen your role uses for the PO, enter the supplier's confirmation number as the reference, and key the confirmed quantity and date for each accepted item. Leave held items blank so nothing is accepted on them by accident, then save.

    In the video
    Reference
    OC-VC-55871
    Item 10
    400 EA on 11/20/2026
    Item 30
    800 EA on 11/20/2026
    Item 20
    not entered · under review
    Saved
    07:51:14

  7. Action · SAP S/4HANA – Manage Purchase Orders · 4:05 in the video

    Change the in-tolerance price on the PO

    Back on the PO, edit the accepted item's net price to the confirmed price and save. Let the PO change workflow decide whether an approval step is needed; do not approve your own change. Read the message after saving to see which rule applied.

    In the video
    Item 10 net price
    42.50 → 43.10
    Rule applied
    WF-CHG-01: no approval step required, released
    PO status
    Released
    Saved
    07:52:40

  8. Action · SAP S/4HANA – Manage Purchase Orders · 4:22 in the video

    Reopen the PO and prove it saved

    Close the PO, search for it again and reopen it. Read the stored values rather than trusting the save message: the changed price, the confirmed dates, the new net value, and that held items are exactly as they were.

    In the video
    • Item 10 Confirmed (AB)
      Net price
      43.10
      Confirmed
      11/20/2026
    • Item 30 Confirmed (AB)
      Confirmed
      11/20/2026
    • Item 20 Not confirmed (untouched)
      Net price
      18.20
      Delivery
      11/20/2026
    • Net value
      Before
      29,160.00 USD
      After
      29,400.00 USD

  9. Action · SAP S/4HANA – Manage Purchase Orders · 4:45 in the video

    Hold the out-of-tolerance item and request review

    Select the held item and send a review request to the buyer named in your workflow rules, with the escalation approver if the amount crosses their threshold. Put the full facts in the reason: old and proposed price, percent and extended deltas, old and proposed date, and what the date affects. Then reopen the PO and check the request shows in the approval history and the item is still unchanged.

    In the video
    Reviewer
    buyer01 (test)
    Escalation
    mgr02 (test) · > 500.00
    Proposed by supplier
    19.95 USD · 12/04/2026
    Request
    RV-2207, pending buyer01
    Item 20 after reopen
    18.20 / 11/20, unchanged

  10. Human review · Microsoft Teams · 5:21 in the video

    Buyer decides on the held item

    Post the same facts in the buyers' channel so the decision is quick, then wait for the buyer's recorded decision. Do not approve or accept the change yourself while it is pending.

    In the video
    Posted
    7:55 AM · Castings buyers
    Card
    Held · review RV-2207: 18.20 → 19.95 (+9.62%), +700.00 USD, 11/20 → 12/04
    Buyer reply
    8:06 AM, not accepting item 20 as proposed; keep on hold, calling Vectra, decision by Thu

  11. Action · Microsoft Outlook (web) · 5:42 in the video

    Alert the planner about the late date

    A proposed late date threatens production whatever the buyer decides, so tell the planner straight away. Email the material, quantity, proposed date, the production order it affects and that the date is not accepted yet, and attach the supplier's confirmation.

    In the video
    To
    planner03@graniteridge-mfg.test
    Subject
    Late delivery risk — MAT-77140 for PO 1004417 (supplier proposes 12/04)
    Attachment
    OC-VC-55871.pdf
    Sent
    8:08 AM

  12. Action · SAP S/4HANA – Manage Purchase Orders and Excel · 6:08 in the video

    Check approval history and change log, then write the audit sheet

    Reopen the PO one more time and read the approval history and change log from the record itself. Confirm every change is attributed (rule or person) and that held items have no change entries. Finish with a before-and-after sheet listing each field, whether it changed, who or what changed it and the evidence.

    In the video
    • Approval · item 10 Released
      Rule
      WF-CHG-01 · price +1.41%
      By
      auto (rule)
    • Approval · item 20 Pending · hold
      Request
      RV-2207 · price +9.62% · date +14 d
      By
      buyer01 (test)
    • Change log
      Entries
      3, all on items 10 and 30
      Item 20
      no entry
    • Audit · net value
      Before
      29,160.00
      After
      29,400.00
      By
      item 10 only

Rules, exceptions and controls

Rules to follow

  • Filter the PO by PO number, supplier and plant; all three must match the confirmation.
  • Every difference is written down with its exact amount, percent and day delta before any rule is applied.
  • A price increase is permitted only if it is ≤ +2.00% and ≤ 500.00 USD extended (PRC-TOL-05 in the walkthrough).
  • A confirmed delivery date later than need-by is never auto-accepted; it needs buyer review.
  • Price changes go through the ERP's PO change workflow; the person or agent making the change never approves it.
  • Out-of-tolerance changes above 500.00 USD go to the buyer, with a manager added above 1,000.00 USD.

When something doesn't match

  • Price increase over the percent or amount limit: the item is held unchanged and a review request goes to the buyer.
  • Confirmed date later than need-by: held for buyer review, and the planner is alerted to the production risk immediately.
  • Confirmation references a different PO, supplier or ship-to plant: stop before comparing items.
  • Buyer keeps the item on hold pending a supplier call: nothing on that item is confirmed or changed until a recorded decision.
  • Save message and reopened values disagree: treat the change as not made and investigate before continuing.

Controls and audit trail

  • Variance sheet records each delta before any decision.
  • ERP workflow rules, not the person keying the change, decide whether a price change needs approval.
  • Every change is verified by closing and reopening the PO.
  • Review request and buyer decision are recorded in the PO's approval history.
  • Change log shows no entries on held items.
  • Before-and-after audit sheet lists who or what changed each field and the evidence.

Practitioner tips

  • Record the supplier's confirmation number as the reference on every confirmation you enter, so the change can be traced to the document.
  • Check both the percent and the amount limit; a small percent on a high-value line can still exceed the amount limit.
  • Compare a late date with the production order start, not just the PO delivery date, so the planner knows how much slack is left.
  • Leave held items completely blank in confirmation entry rather than entering the PO values.
  • Send the planner alert as soon as the late date is known; don't wait for the buyer's price decision.

About this walkthrough

In the walkthrough, the agent confirmed items 10 and 30, repriced item 10 through the PO change workflow, held item 20 for buyer01 on RV-2207 without changing it, alerted the planner and verified every change by reopening the PO.

Documented the way you'd train a new hire — and the same way an agent learns it.

See it on your workflow

Frequently asked questions

How do you handle a supplier confirmation with a different price in SAP S/4HANA?

Compare each item with the PO in Manage Purchase Orders, calculate the percent and extended difference, and check it against your tolerance policy. If it is within tolerance, record the confirmation and change the net price so the PO change workflow can release it; if not, leave the item unchanged and request buyer review.

What price tolerance should apply to supplier confirmations?

That is your company's policy. In the walkthrough, policy PRC-TOL-05 allows an increase only if it is no more than +2.00% and no more than 500.00 USD extended, and the ERP workflow rules mirror it.

What if the supplier confirms a later delivery date?

Don't accept it automatically. Compare it with the need-by date and any production order it supplies, hold it for buyer review and alert the planner right away so they can check coverage.

Should a buyer approve their own PO price change?

No. The change goes through the PO change workflow, which either releases it by rule or routes it to an approver. In the walkthrough, the +1.41% change was released by rule WF-CHG-01 and the +9.62% change went to buyer01.

How do you prove a PO change actually saved?

Close the PO, search for it again, reopen it and read the stored values, then check the approval history and change log. The walkthrough does this after each change.

Can an AI agent process supplier confirmations in SAP S/4HANA?

This walkthrough shows how one could: it works the inbox, ERP and spreadsheet screens a buyer uses, applies only changes the rules allow and holds the rest for a person. It is a conceptual walkthrough with sample data, not a recording.

More manufacturing workflows