For US purchasing and operations leads who want suppliers to confirm, update and ship against every purchase order inside NetSuite.
Last reviewed: 28 October 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
NetSuite order collaboration is how you and your suppliers keep one shared view of each purchase order after you send it. Send the PO with clear dates and ask the supplier to confirm it. Record any new date or quantity on the PO line, track the shipment, then match the receipt and the bill. These ten checks cover that flow.
Order collaboration is the back and forth with a supplier between an approved purchase order and a paid bill. The supplier confirms the order, agrees the dates and quantities, tells you about changes and lets you know when goods ship.
In NetSuite, all of that hangs off the purchase order. The PO carries the items, quantities, rates and the dates you need. The receipt, the bill and the payment all link back to it.
Approval comes before this flow. Our post on purchase requisition approval in NetSuite covers how a request becomes an approved PO. This checklist starts the moment that PO is ready to send.
The flow has five stages: send, confirm, change, ship and close. Each check below names the owner, the NetSuite record and why it matters.
Owner: buyer. Enter the purchase order at Transactions > Purchases > Enter Purchase Orders. Fill in Receive By on the header and the Expected Receipt Date on each line when lines arrive at different times.
Why: a supplier can only confirm a date you have asked for. A PO with no date gets a "we'll ship when we can" reply.
Owner: purchasing admin. Set the vendor's email on the vendor record and use one PO form with a clear print layout. Check To Be E-mailed on the PO so it goes out when you save.
Why: one format and one channel mean the supplier's team knows where to look. Your team also has the sent copy in the PO's communication history. Make sure the print layout shows Receive By and the line dates, so the dates you asked for are on the page the supplier reads.
Owner: buyer. Add three custom fields, built at Customization > Lists, Records, & Fields. Use a body field for Confirmation Status (Not confirmed, Confirmed, Confirmed with changes). Add two line fields for Confirmed Ship Date and Confirmed Quantity.
Keep the status list short. Three values are enough for buyers to pick quickly, and reports stay easy to read.
Why: an email that says "confirmed" sits in one inbox. A field on the PO can be searched, reported and handed to a colleague.
Owner: purchasing lead. Build a saved search of open POs where Confirmation Status is Not confirmed and the PO date is more than two business days ago. Put it on the buyers' dashboard. A SuiteFlow workflow can send the supplier a reminder email from the PO.
Why: a short list each morning is easier to work than a full inbox. It also shows which suppliers confirm slowly.
A hypothetical Ohio distributor sends 200 purchase orders a month to 25 suppliers. In the first week with the new fields, the morning search shows 60 open POs still marked Not confirmed after two business days.
The buyers split the list by supplier. Four suppliers account for 40 of the 60. Two of them say they never saw the POs, because the vendor email on their records pointed to a person who had left. The buyers fix those two email addresses and resend.
By the end of the month, the morning list is down to 15 POs. The buyers also learn which suppliers confirm within a day and which need a phone call. They use that to decide who gets Vendor Center access first.
Owner: NetSuite administrator. Set up access in four steps.
Why: the Vendor Center lets a supplier view, search and print the purchase orders you place with them, and see their payment history. That cuts the "can you resend PO 4471" emails. Remove access when a supplier contact leaves, the same way you would for an employee. If you use NetSuite OneWorld and share the vendor across subsidiaries, a customized Vendor Center role can show orders from each of them.
Owner: buyer. When a supplier moves a date, update the line's Expected Receipt Date so planning sees the new date. Keep the first confirmed date in its own custom line field, such as Original Promise Date.
Why: planners need the latest date. Supplier reviews need the first one. With both on the line, you can measure on time delivery fairly and still plan from the latest date.
A simple saved search shows every open line where the Expected Receipt Date is later than the Original Promise Date. Sort it by days moved and you have the list for your next supplier call. Add the customer orders that depend on those items, and sales can warn customers early instead of after the date has passed.
Owner: purchasing lead. Set a rule your team agrees on. For example, any change to rate, or a quantity change over 5 percent, goes back through approval before the PO is updated. The System Notes subtab on the PO records who changed which field and when.
Why: a date change rarely changes what you pay. A price or quantity change does. Our guide to reapproving changed purchase orders in NetSuite shows how to test those rules.
Owner: logistics or receiving lead. Turn on Inbound Shipment Management at Setup > Company > Enable Features, in the Shipping & Receiving section of the Transactions subtab. Then create a record at Transactions > Purchases > Create Inbound Shipment.
Enter the External Document Number from the shipper, the Expected Shipping Date, Expected Delivery Date and Bill of Lading. Click Add PO Items to pull lines from one or more POs. You can split a line's quantity across two shipments.
Why: the inbound shipment is the single place to see goods in transit. When a container holds lines from six POs, the receiving team works one record instead of six. You can receive and bill from it, and apply landed costs such as freight and duty to the whole shipment. It keeps its own Expected Delivery Date, so agree who also updates the PO line date.
Owner: procurement manager. For office supplies and other indirect buying of non inventory items, the SuiteProcurement SuiteApp connects NetSuite to supplier stores through Oracle Business Network. Approved purchase requests go to the supplier electronically.
The supplier's PO acknowledgment, shipping details and bill then come back into NetSuite. You can see the acknowledged and accepted quantities on the SuiteProcurement Transactions subtab of the purchase request.
Why: confirmations that arrive as data need no rekeying. Start with suppliers who already trade on the network. For direct materials and stock items, checks 3 to 8 still do the work, so keep both routes in the same reports.
Owner: receiving, then accounts payable. Receive goods at Transactions > Purchases > Receive Orders, against the PO lines. Bill at Transactions > Payables > Bill Purchase Orders so the bill copies the PO lines.
AP then checks three things agree: what you ordered, what arrived and what the supplier billed. Our post on three way match exceptions in NetSuite covers the cases that need a person to decide.
Why: when checks 1 to 9 are done, most bills match on the first try. The ones that don't usually point to a change that was never recorded.
If suppliers email their bills as PDF files, NetSuite Bill Capture can read each file. AP reviews the suggested details before the bill is created. In the 2026.2 release, Bill Capture preferences gained clearer options for how tax and shipping costs are saved. The match against the PO and the receipt still decides whether the bill is paid.
If your group also runs a Singapore subsidiary, its customer invoices have their own GST print rules. Our explainer on the NetSuite tax invoice template for Singapore covers them.
| Team | Checks they own | What they watch each week |
|---|---|---|
| Buyers | 1, 3, 6 | Open POs without a confirmed date |
| Purchasing lead | 4, 7 | Changes waiting for approval |
| NetSuite administrator | 2, 5 | Vendor Center access requests |
| Logistics and receiving | 8 | Shipments past their expected delivery date |
| Procurement manager | 9 | Indirect orders with no acknowledgment |
| Accounts payable | 10 | Bills that did not match |
If I could only do three of these next month, I would pick 1, 3 and 4. A need date on every line, a confirmation field and a morning list of unconfirmed POs take little time to set up. They fix a common reason goods arrive late, which is that nobody asked the supplier to commit to a date.
I would then give your ten largest suppliers Vendor Center access and see how many "resend the PO" emails stop. Inbound shipments and electronic suppliers can follow once the basics hold. Review the table above with each team lead once a month for the first quarter. Drop any check nobody uses, and tighten the ones that keep catching problems.
CuriousRubik's NetSuite optimization team can set up these fields, searches and workflows in your account and train your buyers to use them. You can also read how we support NetSuite customers in the United States.
How to measure supplier lead time from the dates NetSuite records.
How a supplier portal fits around purchase orders and receipts.
Why the order, the receipt and the bill are separate records, and how they connect.