Customer POs drafted as NetSuite sales orders, checked against the ones you saved.

Someone on your team opens a new sales order, picks the customer and types the PO # from the buyer's document. Then they choose a shipping address, add a line for each item and watch what rate each line picks up. The typing goes fast. The questions slow it down: is this a new address, is that the price we agreed, and will this customer's order even save?

For the test, AI reads copies of POs your team has already entered and drafts each one in the shape of a NetSuite sales order: customer, PO #, ship-to, status and every item line, with a note on how it chose each field. Nothing is created in NetSuite. Your reviewer then scores each draft against the real order.

Pending Approval or Pending Fulfillment. Your NetSuite administrator sets the Default Sales Order Status on the Order Management subtab of Accounting Preferences: Pending Approval for a company that reviews orders, Pending Fulfillment for one that doesn't. A second setting, Require Re-approval on Edit of Sales Order, sends an approved order back for review when someone changes it, and once an order is partially fulfilled it can't return to Pending Approval. Each draft states the status it would be saved in and the reason, which shows your reviewer whether a person would have seen it before the warehouse did.

Credit limits that stop the save. Under Customer Credit Limit Handling, NetSuite ignores the limit, warns whoever is entering the order, or, set to Enforce Holds, refuses a sales order that takes the customer to or past it. Every customer record also has a Hold field set to Auto, On or Off, and a box named Customer Credit Limit Includes Orders counts unbilled orders toward the limit whether they're approved or not. That preference doesn't touch estimates, so a quote that saved without a word can turn into an order NetSuite blocks. Drafts for customers your export shows on hold or close to their limit are marked before anyone types them.

New address or Custom address. When a PO names a delivery point the customer record doesn't have, Ship To Select offers New, which also saves the address to the customer, or Custom, which keeps it on that one order. Where Multiple Shipping Routes is on, Enable Item Line Shipping lets each line carry its own address and ship method, and a Ship Complete box holds the order until it can leave in one shipment. The draft names the saved address it used, or says New or Custom and why, line by line when a PO splits.

Customer part numbers, if you keep them in NetSuite. The Customer Part Number feature comes with Oracle's Supply Chain Management SuiteApp and covers inventory and assembly items only. It accepts letters, numbers, hyphens and underscores, and each pairing of customer and part number has to be unique within a subsidiary. A buyer's number printed with a slash, a period or a space can't be stored exactly as printed, so whoever set it up stored a cleaned version or left it out. The draft shows the number as the PO prints it, the stored version it matched, and every line it could not match at all.

Which rate a line picks up. NetSuite's own help sets the order: an item price on the customer's Item Pricing subtab beats a pricing group's level, and a pricing group beats the Price Level on the customer record. Quantity Pricing, where it's on, changes the rate again at each break. When someone types a rate of their own, the line's price level reads Custom. The draft names the price level each line should land on from your exports, compares it with the PO, and lists every Custom line in the sample, because each of those is a price somebody decided by hand.

If the drafts meet the success criteria, incoming POs get the same treatment for about 30 days.

Someone on your team approves, corrects or rejects each draft before a sales order exists in NetSuite. How approved drafts get in is your NetSuite administrator's choice: typed from the draft, or brought in with tools you already pay for. The scoring sheet from the test keeps running all month.