Purchase orders are supposed to be the control point of your procure-to-pay process. They’re the moment when spend gets committed, budgets get checked, and downstream accounts payable (AP) work gets easier. In practice, they’re often the opposite: a backlog of half-completed records, mismatched receipts, and approval chains that slow the business down instead of protecting it.
If your team is spending more time chasing POs than using them, the problem usually isn’t NetSuite. It’s how POs are structured, approved, and matched. Get those three things right, and the PO becomes the single most valuable record in your AP cycle. Get them wrong, and every downstream process (receiving, matching, accruals, payment) inherits the mess.
Here are three best practices that consistently separate finance teams who run a clean PO process from those who don’t.
1. Design PO data for matching, not just for issuance
Most PO problems show up when matching, whether that is two or three-way match; but they originate at PO creation. A purchase order that looks complete to a buyer is often missing the structure the AP team needs to match an invoice cleanly weeks later.
The ultimate aim is to design your PO data model around what has to reconcile downstream (line-level detail, units of measure, expected receipt dates, and GL coding), not just what’s required to send the order to the vendor.
A few specific practices result in pay-off:
- Enforce line-level itemization. Lump-sum POs (“Services, $50,000”) are the single biggest cause of match failures and manual coding work. Break services into deliverables, milestones, or time-based lines so invoices can match against something real.
- Standardize units of measure at the item level. When the PO says “case” and the invoice says “each,” your match logic breaks and your AP clerk becomes a translator. Lock units of measure at the item record so it’s consistent across every PO.
- Code the PO, not the bill. General ledger (GL) accounts, departments, classes, and locations should be set when the PO is issued, not negotiated later when the invoice arrives. This is also when budget owners are paying attention; after the fact, no one remembers.
- Capture expected receipt and invoice dates. These fields drive accrual logic, aging reports, and cash forecasting. Leaving them blank is a quiet but expensive habit that will eventually cost you time.
The rule of thumb is: if AP has to interpret the PO to process the invoice, the PO wasn’t finished or set up correctly.
2. Build approval workflows around risk, not hierarchy
The most common PO approval design is also the most flawed. Every PO routes up the org chart until it hits someone senior enough to sign off. It feels safe, but it creates two problems at once: low-risk POs get stuck behind executive inboxes, and high-risk POs get rubber-stamped by approvers who don’t have time to actually review them.
A better approach is to route based on risk attributes (amount, vendor, category, entity, budget status) and reserve human judgment for the decisions requiring that level of sign-off.
What this looks like in practice:
- Tier by spend and category, not just dollar amount. A $25,000 software renewal with a strategic vendor is a different decision than a $25,000 one-time purchase from a new supplier. Route them differently.
- Use budget checks as a gating step, not an afterthought. If the department is already over budget, the PO shouldn’t reach an approver until finance has weighed in. Catching this upstream prevents the awkward conversation downstream.
- Separate new-vendor POs from repeat-vendor POs. First-time vendors carry compliance, tax, and fraud risk that recurring vendors don’t. They deserve a different path, usually one looping in procurement or finance ops.
- Make approvals frictionless for approvers. If your VPs have to log into NetSuite to approve a $2,000 PO, they’ll batch their approvals once a week, and your PO cycle time will reflect it. This is exactly the gap Charted Approval Automation is built to close: approvers can act on POs directly from their email, on any device, without needing a NetSuite license, and every decision is still logged to the NetSuite record in real time. Complex approvals are managed with sophisticated routing by amount, entity, department, vendor, or any NetSuite field, all configured without scripting so finance can re-tier flows without an IT ticket.
- Audit approval patterns quarterly. Look for approvers who approve 100% of POs in under 30 seconds. That’s not a workflow. That’s a stamp. Re-assess those flows.
The goal isn’t more approvals. It’s the right approval at the right time, by the person closest to the decision. All tracked in NetSuite, maintained directly within your audit trail.
3. Close the loop with receiving and three-way match
A PO that never gets matched is just a wish. The final discipline, and the one that’s most often neglected, is closing the loop between the PO, received goods or services, and the invoice.
Three-way match is the control that protectings your business from overbilling, duplicate payments, and unauthorized spend. But it only works if all three documents exist, are accurate, and are reconciled in real time. In too many organizations, receiving is treated as optional, match exceptions pile up in a queue no one owns, and AP ends up paying off the invoice and “trueing up” later, hoping everything aligns after the fact.
These best practices hold the line:
- Make receiving non-negotiable for goods, and milestone-based for services. Every line on a PO needs a receipt event, even if it’s a confirmation that a service was delivered. No receipt, no payment.
- Match in real time, not at month-end. Batch matching at close is how exceptions become emergencies. Charted 3-Way Match validates the PO, receipt, and invoice at the line level the moment a bill is captured, so variances surface while the context is still fresh, not three weeks later in a reconciliation spreadsheet.
- Define tolerance thresholds explicitly. Decide in advance what variance is acceptable, by dollar, by percentage, by category, and let the system auto-approve within tolerance and escalate outside it. Tolerance policies that only exist in someone’s head don’t scale. Configurable tolerances at the subsidiary, vendor, or item level let you encode the policy directly into the match logic.
- Assign ownership for exceptions. Match failures are not an AP problem. They’re a procurement problem, a receiving problem, or a vendor problem, and they need a named owner with a service-level expectation for resolution.
- Track match rate as a KPI. First-pass match rate is one of the cleanest indicators of process health you have. If it’s below 80%, the issue is almost always upstream, in PO creation or receiving, not in AP.
When the loop closes consistently, accruals get more accurate, month-end gets shorter, and audit prep stops feeling like an archaeology project.
The throughline
These three practices share a common thread: they treat the purchase order as a financial control, not an administrative form. The PO is where spend gets committed, where budget gets reserved, and where the data that drives the rest of the AP cycle gets created.
Investing in PO discipline pays compounding returns: cleaner invoices, faster close, fewer exceptions, and a procure-to-pay process that scales with the business instead of slowing it down. The teams who run this well don’t have more rules. They have better-designed ones, applied consistently, and built around how the work flows.
If you’re rethinking how POs, approvals, and three-way match should work together inside your NetSuite instance, see how Charted brings these controls together to live directly inside NetSuite.
