NetSuite Purchase Order: setup, key fields & best practice
The NetSuite Purchase Order is a non-posting commitment to buy from a vendor - it starts the procure-to-pay chain that flows to item receipt and vendor bill. It does not hit the general ledger until receipt or billing. In OneWorld the subsidiary sets the vendor, currency and approval routing.
Setup
- Enable Purchase Orders (and Receiving for a three-way match) under Setup > Company > Enable Features, and set approval routing or SuiteFlow approvals for purchase orders above a threshold.
- Configure vendor records, items with purchase information, and per-subsidiary currencies and approval limits before raising live purchase orders.
Key fields
- Vendor (Entity). The supplier. Drives default currency and terms, and in OneWorld the subsidiary the purchase order belongs to. Must be a vendor shared with the purchase order subsidiary.
- Subsidiary. In OneWorld, sets the legal entity, base currency and approval routing. The vendor and items must be shared with this subsidiary.
- Items / Expenses. Item lines (with quantity and rate) or expense lines. Item lines enable receiving and three-way matching; expense lines book straight to a GL account on billing.
- Currency & Exchange Rate. Comes from the vendor and converts to the subsidiary base currency. The purchase order is non-posting, so the rate that matters for the GL is the one on the receipt and bill.
- Expected Receipt Date. Drives demand planning and receiving. Accurate dates keep supply planning and accruals meaningful.
- Status / Approval. A purchase order moves Pending Approval to Pending Receipt to Received or Billed. Approval routing controls who can release it; status drives what can be received or billed.
Best practice
- Receive against the purchase order (item receipt) and bill from the receipt so three-way matching (PO, receipt, bill) holds.
- Use approval routing and per-subsidiary limits so commitments are authorised before they reach the vendor.
- Keep item purchase information and expected dates accurate so demand planning and accruals are reliable.
Common errors
Frequently asked questions
- Does a purchase order post to the general ledger?
- No. A purchase order is a non-posting commitment. The GL is hit when you receive the items (item receipt, which posts to an accrual) and when you enter the vendor bill. The purchase order drives those downstream postings but creates none itself.
- How does three-way matching work from a purchase order?
- Receive the items against the purchase order to create an item receipt, then transform the receipt into a vendor bill. NetSuite matches quantities and pricing across PO, receipt and bill, so discrepancies surface before payment.
- How does the subsidiary affect a OneWorld purchase order?
- The subsidiary sets the legal entity, base currency and approval routing, and limits which vendors and items are available - they must be shared with that subsidiary. The vendor currency converts to the subsidiary base currency on the downstream receipt and bill.
Last reviewed: by Wouter Nortje, CA