Morsa publishes this guide. Morsa is software with an AI agent that works in your ERP, email and Teams; it chases suppliers for PO confirmations and ship dates from the buyer’s own mailbox and writes the confirmed dates into the ERP, and a person approves what goes out. Sources read 17 November 2026.
Quick answer
What it covers: requisition, approval, PO creation, sending, the supplier’s acknowledgement, follow-up on ship dates, receiving and three-way match.
Where the time goes: after the PO is sent. ISM reports supplier deliveries to US manufacturers slowed for the 11th month in a row in October 2026, with production materials on an 87-day average lead time [1].
What to automate first: reading acknowledgements and chasing unconfirmed and late lines, then receiving and invoice matching, then requisition approvals.
What a late PO costs: in our example, an 8-day slip found 10 days ahead costs $600 to absorb; found 2 days ahead it costs $9,600.
What is purchase order automation?
Purchase order automation is software that creates, sends and tracks the POs you send to suppliers, and matches what comes back. An automated purchase order system, PO automation and automated purchase orders all name the same thing.
It is the buying side of a trade. Your PO is your supplier’s sales order; the seller’s side is sales order automation.
Two kinds of PO work share the name. Indirect spend, such as office supplies, services and equipment, starts with an employee’s request and needs an approval. Direct material for a manufacturer, or stock for a distributor, starts in the ERP, where MRP or a reorder point creates the PO. This guide covers both and spends most of its time on the second.
What an automated purchase order system does
Stage | What gets automated | What a person still decides |
|---|---|---|
Requisition | A request form with the item, quantity, budget code and supplier | Whether the company needs it |
Approval | Routing by amount, department or item type, with reminders | Anything over the approver’s limit |
PO creation | The PO is raised from an approved request, or by the ERP when stock falls below a reorder point or MRP shows a shortage | Which supplier, when the planned quantity looks wrong |
Sending | The PO goes to the supplier’s order contact by email, through a portal, or as an EDI 850 (the standard PO message) | Nothing, once the contact is right |
Acknowledgement | The supplier’s reply, an EDI 855 or more often an email or PDF, is read and compared line by line with the PO: price, quantity, date | Whether to accept a higher price, a short quantity or a later date |
Follow-up | Lines with no confirmed date, a date about to pass or a date already missed get a message, and the reply updates the ERP | What to do when a slip hits a work order or a customer order |
Receiving | The packing slip or the advance ship notice (ASN) becomes a receipt against the PO | Damaged or wrong goods |
Three-way match | The invoice is checked against the PO price and the received quantity, inside a tolerance | Disputes outside the tolerance |
The four types of purchase order
Standard PO: one purchase, items, prices and dates all known.
Planned PO: items and prices agreed, delivery dates released later.
Blanket PO: a supplier, a price list and a spending cap for a period; releases are called off against it. Common for MRO and distributor stock.
Contract PO: terms agreed with a supplier; separate POs reference the contract.
Automation applies to all four. Blanket and planned POs add one thing to watch: each release has its own date.
How to automate purchase orders, step by step
Count your PO work for one week. Open lines, lines with no confirmed date, acknowledgements that changed a price, quantity or date, and hours spent chasing. That count tells you where to start.
Clean the supplier records. Every supplier needs an order contact email, your item mapped to its part number, the unit it sells in and a current lead time.
Let the ERP create the replenishment POs. Set reorder points or run MRP so the POs for stock and production material start in the ERP, where planning can see them. Use a request form for indirect spend.
Write approval rules by exception. Dollar limits for indirect spend. For direct material, approve the exceptions instead: a price above last cost, a quantity above the plan, a supplier off the approved list.
Send from the ERP and ask for a confirmation by a date. Each PO asks the supplier to confirm price, quantity and ship date per line within a set number of days.
Read every acknowledgement and chase by rule. Compare the reply with the PO line, write the confirmed date into the ERP, and send a follow-up when a line is unconfirmed, about to pass its date or late. Our guide on automating supplier follow-up on open POs sets out the trigger rules, and the free PO acknowledgement reader turns one reply into the PO update.
Receive and match against the PO. Receipts post from the packing slip or ASN; invoices match three ways with a price and quantity tolerance you set, so small differences pay and large ones stop.
Measure monthly. Share of lines with a confirmed date, days from PO to confirmation, lines that arrived late with no warning, and invoices held.
Why the follow-up after the PO is where the time goes
Raising, approving and sending a PO happen once, inside your own systems. Reading the reply and chasing the date happen again and again for every open line, and they depend on someone outside your company answering. What your ERP already does for POs, and what it leaves to people, is set out in our guide to purchase order software.
ISM’s October 2026 report puts the average lead time for production materials at 87 days, 3 days more than in September; supplier deliveries were slower for the 11th consecutive month, and “longer lead times” came up in 41% of the negative comments from purchasing executives [1]. An 87-day PO has twelve weeks in which its date can move.
A distributor’s version has more lines and shorter lead times. For scale, manufacturers told ISM their MRO supplies, the kind of stock many distributors carry, averaged 46 days [1]. The work is volume, hundreds of open lines with a customer order waiting behind each backorder. Large manufacturers often answer with an EDI 855 and an 856 ship notice, or post status on their own dealer portal; smaller suppliers answer by email. The job is the same either way: a confirmed date on every PO line, and the customer told when it moves.
Our example of the buyer’s week: 300 open PO lines, of which 90 a week need a touch (no confirmation, a changed date, a date about to pass). At 6 minutes each to write the email, read the reply and update the ERP, that is 90 × 6 = 540 minutes, or 9 hours a week. Over 50 weeks it is 450 hours. At a loaded buyer hour of $53.50 (the May 2025 median for buyers and purchasing agents in manufacturing, $77,890 [2], is $37.45 an hour over 2,080 hours; divided by 0.70, the wage share of private-industry employer costs [3]), that is 450 × $53.50 = $24,075 a year for one buyer, before any slip is caught late.
Should you wait for your ERP’s own agent?
Microsoft has built one. Its Procurement Agent for Dynamics 365 Supply Chain Management, in production-ready preview, does three jobs, in Microsoft’s words:
Follow-up. It finds POs that vendors have not confirmed or that are late, and “can automatically send the emails right away, or it can save them as drafts that require human review before they can be sent” [4].
Reading replies. It reads vendor emails and their PDF and Excel attachments, can “determine what each email is about”, such as a confirmation or a change request, and which PO it applies to, and proposes the field changes for the purchaser to apply [4][5].
Impact. Its impact analysis “evaluates whether and how supplier changes affect inventory levels, production schedules, and customer deliveries” [6].
Microsoft’s page lists scenarios it does not yet support, among them a supplier splitting one PO line into several deliveries, and the agent is charged in Copilot Studio credits, a fixed cost per run plus a variable cost [4]. If your POs live in Dynamics 365 Supply Chain Management, test it on last month’s late POs, with Morsa on the same POs beside it.
Morsa does the same job on the ERP you run today: Dynamics 365, Prophet 21, Eclipse, Business Central, NetSuite, SAP Business One, Odoo and others, by API, database, export or the email trail, and on several ERPs at once. It chases from each buyer’s own mailbox, writes to overseas suppliers in their language timed for their morning, and carries a moved date through to the customer orders it hits: it tells the rep and drafts the customer’s update.
What to automate first
Order | Stage | Why |
|---|---|---|
1 | Acknowledgements and follow-up | The most hours, and the stage where a slip is caught early or late |
2 | Receiving and three-way match | Every PO ends here; a price change missed on the acknowledgement is caught on the invoice |
3 | Requisitions and approvals | Matters most for indirect spend; direct material POs already start in the ERP |
The cost of one late PO: a worked example
Our example: a 100-person manufacturer orders 1,200 aluminum housings at $18.50 on one PO, $22,200 in all. They go into 1,200 assemblies for a customer order worth 1,200 × $80 = $96,000. The supplier slips the ship date by 8 days. All costs below are our assumptions; replace them with yours.
Found 10 days before the line needs the parts | Found 2 days before | |
|---|---|---|
What the plant can still do | Move another job forward, split the shipment, ship by ground | Pay for air freight and overtime, ship the customer late |
Extra freight | $600 (our assumption) | $4,800 air freight (our assumption) |
Overtime to catch up | $0 | 6 people × 10 hours × $48 = $2,880 |
Customer late-delivery charge | $0 | 2% × $96,000 = $1,920 |
Total | $600 | $4,800 + $2,880 + $1,920 = $9,600 |
The slip was the same; the 8 days of warning were worth $9,600 - $600 = $9,000. Moving another job forward has a cost of its own, the other job’s slack; with 10 days’ notice the planner can pick a job that has some. JRG Automotive, a Morsa customer, caught 5 of 8 production-stopping material shortages early enough to act, and saved the plant $2 million [7].
Chasing the housing PO before it costs $9,600
The housing PO is due in 25 days and the supplier has not confirmed it. Morsa chases from the buyer’s mailbox, reads the reply (“ships 8 days late”), moves the PO line and shows the assembly work order and the $96,000 customer order it hits. Then it:
Proposes the fixes, each with its cost: move another job forward, or split the shipment and ship by ground, about $600 in our example, against $9,600 if the slip is found late.
Sends the buyer the choice in Teams, where she approves one with a single tap.
Sends the supplier the split-shipment request from her mailbox and drafts the customer’s update for the rep.
A person approves each kind of message once; after that it runs under that rule. Anything outside the rule, or anything Morsa is unsure of, goes to the person you name.
How to choose purchase order automation software
Ask every vendor these five questions, with your own POs in front of you:
Does it work on the POs your ERP already creates, or does it want POs raised in its own system?
Can it read an acknowledgement that arrives as an email or a PDF, in another language, and update the confirmed date on the ERP line?
What does a supplier have to do: log into a portal, set up EDI, or just reply to an email?
When a date moves, does it show which work orders and customer orders are affected?
What does a person approve before anything goes to a supplier?
What to do this week
Run your open-PO report and count lines with no confirmed date and lines already late.
Time one afternoon of chasing: emails sent, replies read, ERP lines updated.
Fix the order contact email on your 20 biggest suppliers.
Pick one supplier group and ask Morsa to run their confirmations for two weeks.
Sources
Institute for Supply Management, October 2026 ISM Manufacturing PMI Report: https://www.ismworld.org/supply-management-news-and-reports/reports/ism-pmi-reports/pmi/october/ and the same report on PR Newswire, 2 November 2026: https://www.prnewswire.com/news-releases/manufacturing-pmi-at-55-5-october-2026-ism-manufacturing-pmi-report-302925617.html (read 17 November 2026)
US Bureau of Labor Statistics, Occupational Outlook Handbook, Purchasing Managers, Buyers, and Purchasing Agents (pay tab, May 2025): https://www.bls.gov/ooh/business-and-financial/purchasing-managers-buyers-and-purchasing-agents.htm (read 17 November 2026)
US Bureau of Labor Statistics, Employer Costs for Employee Compensation, June 2026: https://www.bls.gov/news.release/ecec.nr0.htm (read 17 November 2026)
Microsoft Learn, Supplier communications features of the Procurement Agent (production-ready preview): https://learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/procurement-agent-supplier-com-overview (read 17 November 2026)
Microsoft Learn, Review and apply purchase order changes received in vendor emails (production-ready preview): https://learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/procurement-agent-supplier-com-apply-email-changes (read 17 November 2026)
Microsoft Learn, Impact analysis overview (production-ready preview): https://learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/procurement-agent-impact-analysis-overview (read 17 November 2026)
Morsa, pricing page: https://morsa.ai/pricing (read 17 November 2026)

