How to Follow Up Overdue PO Acknowledgments in Oracle Fusion Cloud Procurement
When a purchase order requires supplier acknowledgment, every order past its acknowledgment due date is a delivery risk nobody has confirmed. Often the supplier did reply, by email, and the ERP was never updated; sometimes the reply is vague or cites an old revision; sometimes there is no reply at all.
This guide follows a conceptual walkthrough set in Oracle Fusion Cloud Procurement: working the pending-acknowledgment queue in the Purchase Orders work area, checking document history, matching each email reply to the current PO revision schedule by schedule, recording a clean acknowledgment on the supplier's behalf with evidence, sending an ambiguous reply to the buyer, reminding a silent supplier and sending an escalation list.
- Who does itBuyer or procurement operations analyst; the responsible buyer decides ambiguous replies
- How oftenDaily
- Steps12 steps · 5 systems
Watch the full workflow
a conceptual walkthrough of the agent's run, with sample data.
In this conceptual walkthrough, an AI agent runs a daily overdue-acknowledgment check under policy ACK-07 for the US1 Business Unit. The pending-acknowledgment queue shows four orders, three overdue: US1-20409 (6 days), US1-20417 (4 days) and US1-20422 (3 days). For US1-20417, document history shows revision 1 was communicated 10/29 with no acknowledgment accepted; Halden Electronics' emailed acknowledgment SO-HE-7712 cites revision 1, says 'Accepted as issued' and matches all three schedules, so the agent records it on the supplier's behalf with the email attached and verifies it by reopening the order. Corvane Plastics' reply for US1-20422 cites revision 0, 1,000 EA instead of 1,200 EA and a 'TBC' date, so the agent sends it to buyer01, who says to keep it pending. Ostrander Metals never replied on US1-20409, so the agent sends one reminder to the flagged order-desk contact. It refreshes the queue to confirm only US1-20417 left it and emails buyer01 an escalation list.
Conceptual walkthrough: the screens are generic stand-ins modeled on how Oracle Fusion Cloud Procurement 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.
- 0:28Scan supplier replies in the mailbox
- 0:48Open the pending-acknowledgment queue
- 1:12Read the order's revision and schedules
- 1:28Check document history first
- 1:48Match the reply to the PO number and revision
- 2:13Does every schedule match exactly?
- 2:40Record the acknowledgment on the supplier's behalf
- 3:00Reopen the order and verify
- 3:31Check an ambiguous reply against the current revision
- 4:14Buyer decides on the ambiguous reply
- 4:43Remind a supplier that never replied
- 5:38Refresh the queue and send the escalation list
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.
- Oracle Fusion Cloud Procurement – Purchase OrdersPending-acknowledgment queue, order schedules and document history, acknowledge-on-behalf flow, supplier contacts
- Microsoft Outlook (web)Procurement mailbox with supplier replies; reminder and escalation emails
- Exceloverdue-ack-escalation-2026-11-03.xlsx escalation list
- Microsoft TeamsProcurement buyers channel for the ambiguous reply and the buyer's decision
- LaunchAI agent run panelRun steps, policy in force and closing summary
What you start with
- Pending-acknowledgment queue for the procurement business unit
- Supplier replies in the procurement mailbox (SO-HE-7712.pdf, CP-31907-draft.pdf)
- Each order's current revision, schedules and document history
- Acknowledgment policy ACK-07: record on the supplier's behalf only with written evidence; one approved reminder to the flagged contact
What you end with
- Supplier acknowledgment recorded for US1-20417 revision 1, with evidence, verified on reopen
- Buyer review of US1-20422 in Teams; order left pending
- Reminder email to orders@ostrander-metals.test for US1-20409
- Escalation list emailed to buyer01
The workflow at a glance
Action Decision Human review Select a step to jump to how it's done.
- 01 Action · Microsoft Outlook (web) Scan supplier replies in the mailbox
- 02 Action · Oracle Fusion Cloud Procurement – Purchase Orders Open the pending-acknowledgment queue
- 03 Action · Oracle Fusion Cloud Procurement – Purchase Orders Read the order's revision and schedules
- 04 Action · Oracle Fusion Cloud Procurement – Purchase Orders Check document history first
- 05 Action · Microsoft Outlook (web) and acknowledgment PDF Match the reply to the PO number and revision
- 06 Decision · Acknowledgment PDF and Oracle Fusion Cloud Procurement Does every schedule match exactly? Yes Record the acknowledgment on the supplier's behalf, with the written evidence. No Don't record it; send the mismatch to the buyer and leave the order pending.
- 07 Action · Oracle Fusion Cloud Procurement – Purchase Orders Record the acknowledgment on the supplier's behalf
- 08 Action · Oracle Fusion Cloud Procurement – Purchase Orders Reopen the order and verify
- 09 Action · Microsoft Outlook (web) and Oracle Fusion Cloud Procurement Check an ambiguous reply against the current revision
- 10 · Human review · Microsoft Teams Buyer decides on the ambiguous reply
- 11 Action · Oracle Fusion Cloud Procurement and Microsoft Outlook (web) Remind a supplier that never replied
- 12 Action · Oracle Fusion Cloud Procurement, Excel and Microsoft Outlook (web) Refresh the queue and send the escalation list
Step-by-step: how to do it
-
Action · Microsoft Outlook (web) · 0:28 in the video
Scan supplier replies in the mailbox
Open the procurement mailbox and note which messages look like acknowledgments and which order each one mentions. Treat each email as a lead only; the ERP queue decides which orders are overdue, and replies are matched to it afterwards.
In the video- Halden Electronics · 'Acknowledgment — PO US1-20417 rev 1'
- Received
- Mon 8:47 AM
- Attachment
- SO-HE-7712.pdf
- Corvane Plastics · 'RE: PO 20422'
- Received
- Mon 2:15 PM
- Attachment
- CP-31907-draft.pdf
- Pellam Fasteners · 'PO US1-20431 received'
Acknowledgment to follow by 11/06
-
-
Action · Oracle Fusion Cloud Procurement – Purchase Orders · 0:48 in the video
Open the pending-acknowledgment queue
In the Purchase Orders work area, open the queue of orders pending supplier acknowledgment for your business unit. Sort by acknowledgment due date and pick out the orders that are past due; leave orders that are not yet due alone.
In the videoFour orders pending, three overdue (as of 11/03/2026 08:31).
- US1-20409 · Ostrander Metals
- Rev
- 0
- Ack due
- 10/28/2026
- Overdue
- 6 days
- US1-20417 · Halden Electronics
- Rev
- 1
- Ack due
- 10/30/2026
- Overdue
- 4 days
- US1-20422 · Corvane Plastics
- Rev
- 1
- Ack due
- 10/31/2026
- Overdue
- 3 days
- US1-20431 · Pellam Fasteners Not overdue, left alone
- Ack due
- 11/06/2026
-
-
Action · Oracle Fusion Cloud Procurement – Purchase Orders · 1:12 in the video
Read the order's revision and schedules
Open the overdue order and note the revision, what level of acknowledgment is required (document, schedule or both), the due date, and each schedule's item, quantity, price and requested date.
In the video- Order
- US1-20417, revision 1
- Supplier
- Halden Electronics
- Acknowledgment required
- Document and schedule
- Due
- 10/30/2026
- Line 1 · Sched 1 · PCB-4410
- Qty
- 250 EA
- Price
- 38.60
- Requested
- 11/24/2026
- Line 2 · Sched 1 · CBL-220
- Qty
- 500 EA
- Price
- 4.15
- Requested
- 11/24/2026
- Line 2 · Sched 2 · CBL-220
- Qty
- 500 EA
- Price
- 4.15
- Requested
- 12/08/2026
-
Action · Oracle Fusion Cloud Procurement – Purchase Orders · 1:28 in the video
Check document history first
Before recording anything, open the order's document history. Confirm no acknowledgment has already been accepted, and find the latest revision communicated to the supplier; that is the revision the supplier must acknowledge.
In the video- 10/29/2026 11:40 · Rev 1 · Change order approved
- By
- mgr03 (test)
Line 2 split into 2 schedules
- 10/29/2026 11:42 · Rev 1 · Communicated
- To
- orders@halden-elec.test
- No acknowledgment entry: only approvals and sends
-
-
Action · Microsoft Outlook (web) and acknowledgment PDF · 1:48 in the video
Match the reply to the PO number and revision
Open the supplier's reply and its attachment. Check that the PO number and revision both match the current revision in the ERP, and that the document is an explicit acceptance, not a draft or a 'should be fine'.
In the video- Document
- SO-HE-7712 Purchase Order Acknowledgment
- Customer PO
- US1-20417
- PO revision
- 1 (matches ERP)
- Ack date
- 11/02/2026
- Status
- Accepted as issued
-
Decision · Acknowledgment PDF and Oracle Fusion Cloud Procurement · 2:13 in the video
Does every schedule match exactly?
Put the acknowledgment next to the order and compare schedule by schedule: quantity, price, and promised date against requested date. Only a reply that matches the current revision on every schedule is a clean acknowledgment.
- If yes Record the acknowledgment on the supplier's behalf, with the written evidence.
- If no Don't record it; send the mismatch to the buyer and leave the order pending.
In the video- PCB-4410 Match
- Ack
- 250 @ 38.60 by 11/24
- CBL-220 sched 1 Match
- Ack
- 500 @ 4.15 by 11/24
- CBL-220 sched 2 Match
- Ack
- 500 @ 4.15 by 12/08
-
Action · Oracle Fusion Cloud Procurement – Purchase Orders · 2:40 in the video
Record the acknowledgment on the supplier's behalf
If your policy and role allow buyers to acknowledge for the supplier, open the acknowledge action on the order. Enter the revision acknowledged, the supplier's reference and the evidence (the email and its attachment), accept each schedule with its promised date, and submit.
In the video- Revision acknowledged
- 1
- Supplier reference
- SO-HE-7712
- Evidence
- Email 11/02 08:47 orders@halden-elec.test + SO-HE-7712.pdf
- Promised
- 11/24/2026, 11/24/2026, 12/08/2026
- Submitted
- 08:37:41
-
Action · Oracle Fusion Cloud Procurement – Purchase Orders · 3:00 in the video
Reopen the order and verify
A submit message isn't proof. Go back to the queue, search for the order and reopen it. Check the status shows the acknowledgment accepted, each schedule has its promised date, and the document history has a new acknowledgment entry.
In the video- Status
- Open · supplier acknowledgment accepted
- Promised dates
- 11/24, 11/24, 12/08
- History
- 11/03/2026 08:37 · Acknowledged (on behalf of supplier) · agent-buyer
-
Action · Microsoft Outlook (web) and Oracle Fusion Cloud Procurement · 3:31 in the video
Check an ambiguous reply against the current revision
For a vague reply, read exactly what it commits to. Compare the revision it cites and its quantities and dates with the order's current revision and document history. A reply to an older revision, or one with unconfirmed dates, is not an acknowledgment.
In the videoCorvane: 'should be fine on our end… line 2 might slip a week or so.'
- PO revision Mismatch
- ERP
- 1 (qty 1,000 → 1,200 on 10/28)
- Reply
- 'PO 20422', draft CP-31907, rev 0
- Quantity Mismatch
- ERP
- 1,200 EA both lines
- Reply
- 1,000 EA
- Line 2 date Not confirmed
- ERP
- 11/20/2026
- Reply
- TBC
-
-
Human review · Microsoft Teams · 4:14 in the video
Buyer decides on the ambiguous reply
Send the buyer the specific mismatches and say the order has not been changed. Wait for the buyer's decision and leave the order pending in the ERP meanwhile.
In the video- Posted
- 8:42 AM · Procurement buyers
- Card
- US1-20422 · Buyer review: rev 1 vs reply rev 0, 1,000 vs 1,200 EA, line 2 TBC
- Buyer reply
- 8:51 AM, don't record it; buyer01 will get a formal ack on rev 1; keep pending
-
Action · Oracle Fusion Cloud Procurement and Microsoft Outlook (web) · 4:43 in the video
Remind a supplier that never replied
Confirm there really is no reply: check the order's history and search the mailbox for the PO number and supplier name since it was sent. Look up the supplier contact flagged for purchasing communication and send one reminder using your approved template, with the PO attached and a reply-by date.
In the video- Order
- US1-20409 · Ostrander Metals · sent 10/23, due 10/28
- Mailbox search
- '20409' or 'Ostrander': no replies
- Flagged contact
- Order desk · orders@ostrander-metals.test
- Subject
- Acknowledgment overdue — PO US1-20409 (due 10/28)
- Reply by
- 11/05
- Sent
- 8:54 AM with US1-20409.pdf
-
Action · Oracle Fusion Cloud Procurement, Excel and Microsoft Outlook (web) · 5:38 in the video
Refresh the queue and send the escalation list
Refresh the pending-acknowledgment queue and confirm only the order you recorded has left it, and that the held order's history has no acknowledgment entry. Then list each overdue order with its status after the run, owner, next action and escalation date, and send it to the buyer.
In the video- US1-20417 · Halden Electronics Acknowledged · verified
- Next
- None
- US1-20422 · Corvane Plastics Pending · buyer review
- Owner
- buyer01
- Next
- Formal ack of rev 1 (qty 1,200)
- Escalate on
- 11/05
- US1-20409 · Ostrander Metals Pending · reminder 11/03
- Owner
- supplier
- Next
- Reply by 11/05, else buyer01
- Escalate on
- 11/05
- Sent to buyer01@bluestone-med.test at 8:58 AM: 'Overdue acknowledgments 11/03 — 1 recorded, 2 still pending'
-
Rules, exceptions and controls
Rules to follow
- The ERP's pending-acknowledgment queue decides which orders are overdue; an email is a lead, not a status.
- Check document history before recording anything, so an acknowledgment is never recorded twice.
- A reply counts only if it cites the current PO revision and explicitly accepts it.
- Every schedule must match on quantity, price and promised date against requested date.
- A buyer may record an acknowledgment on the supplier's behalf only with written evidence attached (ACK-07 in the walkthrough).
- A silent supplier gets one reminder, from the approved template, sent only to the contact flagged for purchasing communication.
When something doesn't match
- Reply cites an older revision or different quantities: not recorded; the buyer reviews and the order stays pending.
- Reply has an unconfirmed date ('TBC', 'might slip'): not an acknowledgment of that schedule.
- No reply at all: one reminder with a reply-by date, then escalation to the buyer.
- Order not yet past its acknowledgment due date: left alone in this run.
- Acknowledgment already in document history: nothing to record.
Controls and audit trail
- Every recorded acknowledgment carries the supplier's reference and the email evidence.
- Each recorded acknowledgment is verified by reopening the order and reading status, promised dates and history.
- Queue refreshed after the run to confirm only recorded orders left it.
- Held orders checked to have no acknowledgment entry.
- Buyer decisions on ambiguous replies are recorded in the team channel.
- Escalation list gives each overdue order an owner and an escalation date.
Practitioner tips
- Work from the queue, not the inbox: the inbox can't tell you which orders are overdue or what revision is current.
- When an order has been revised, confirm the supplier is acknowledging the latest communicated revision, not the original.
- Treat 'should be fine' as a question, not an answer; ask for a formal acknowledgment of the specific revision.
- Check which supplier contact is flagged for purchasing communication before sending a reminder.
- Give every pending order a dated next step so escalation happens on schedule.
About this walkthrough
In the walkthrough, the agent recorded and verified one clean acknowledgment (US1-20417), sent an ambiguous reply to the buyer without recording it, reminded a silent supplier and emailed an escalation list, leaving two orders pending on purpose.
Documented the way you'd train a new hire — and the same way an agent learns it.
Frequently asked questions
How do I find overdue PO acknowledgments in Oracle Fusion Cloud Procurement?
Use the pending-acknowledgment queue in the Purchase Orders work area. It lists orders awaiting supplier acknowledgment with their due dates; anything past the due date without an accepted acknowledgment is overdue.
Can a buyer acknowledge a PO on behalf of the supplier?
Where your setup and policy allow it, yes, provided you have the supplier's written acknowledgment. In the walkthrough, policy ACK-07 requires the evidence (email and PDF) to be attached and the result verified by reopening the order.
What if the supplier acknowledges an older PO revision?
Don't record it. The acknowledgment must match the current revision's quantities, prices and dates. Send the mismatch to the buyer and ask the supplier for a formal acknowledgment of the current revision.
What should I do when a supplier hasn't replied at all?
Check the order history and search the mailbox to confirm, then send one reminder from your approved template to the contact flagged for purchasing communication, with the PO attached and a reply-by date. Escalate if it passes.
How do I know an acknowledgment really saved?
Reopen the order and read it: the status should show the acknowledgment accepted, each schedule should carry a promised date, and document history should have the new entry.
Can an AI agent follow up overdue acknowledgments in Oracle Fusion?
This walkthrough shows how one could: it works the queue, mailbox and team channel a buyer uses, records only clean acknowledgments and leaves the rest pending for people. It is a conceptual walkthrough with sample data, not a recording.