What to Ask Your ERP Implementer About Procurement Controls

Most ERP implementations are scoped around the general ledger, financial reporting, and revenue recognition. Procurement controls get either tacked on at the end or left out entirely. By the time the ERP goes live, Controllers discover that the native PO module handles basic creation and single-level approvals but falls short on the things that actually control spend: multi-level approval workflows, punchout catalogs, automated three-way matching, and a clean audit trail.

At ProcureDesk, we onboard mid-market finance teams running NetSuite, Sage Intacct, and Microsoft Business Central every week. The pattern is consistent: the ERP handles accounting well, but procurement controls need a purpose-built layer. Across our customers, finance teams that add procurement controls during ERP go-live cut their month-end close from 10 days to 4 days on average. These are the six questions to ask your implementer before go-live, not after.

A note for ERP implementers: If you’re a NetSuite, Sage Intacct, or Business Central partner, this article is designed to be useful for your clients, too. Many implementation partners share this kind of resource during the scoping phase to help clients think about procurement controls before they become a post-go-live fire drill. If you’d like to explore a formal referral partnership, ProcureDesk offers a partner program for implementation firms.

Question 1: Does the ERP Handle Multi-Level Approval Workflows?

Most ERPs support basic PO approval. The question is whether they support conditional routing: different approvers based on dollar amount, department, cost center, or project.

Here’s what each major ERP actually offers:

NetSuite uses a PO Approval Workflow SuiteApp that routes approvals through a supervisor hierarchy based on purchase limits. If the immediate supervisor’s approval limit is lower than the purchase amount, the request moves up the chain to the next supervisor. This works for simple amount-based routing. But conditional logic, where a $12,000 lab supply order routes differently based on department, or where capital equipment purchases follow a different path than office supplies, requires SuiteFlow customization. That means consulting hours or internal SuiteScript expertise.

Sage Intacct offers more flexibility out of the box. Its purchasing approval policies support value-based routing with up to four approval levels, and you can route by department, transaction type, or amount. But setting up multi-criteria workflows (department + project + amount simultaneously) still requires careful configuration, and the purchasing module is a separate subscription from core accounting.

Microsoft Business Central provides basic workflow templates for purchase approvals, but the out-of-the-box options are limited. Complex conditional routing typically requires Power Automate integrations or custom development.

Why does this matter so much during implementation? Because approval workflows are the foundation of spend control. If you discover after go-live that your $10,000 threshold routes correctly but your department-based routing doesn’t work, you’re either paying for a customization project or reverting to email-based approvals. Neither is acceptable for a Controller who just spent six months on an ERP migration.

A standalone procurement tool like ProcureDesk lets you configure multi-level workflows (by amount, department, project, vendor, or category) without scripting or IT involvement. Changes take minutes, not consulting engagements. You can set a $500 self-approval limit for routine office supplies, require department manager approval up to $5,000, and route anything above that to the CFO, all configured through a visual interface.

You can learn more about designing these workflows in our purchase order approval process guide.

Question 2: Can Employees Submit Purchase Requests Before a PO Is Created?

There’s a critical distinction between a purchase requisition and a purchase order. A purchase requisition is an internal request: an employee says “I need to buy this” and it gets routed for approval before any money moves. A purchase order is the external document sent to the vendor after approval.

Some ERPs start at the PO stage. If employees can’t submit a purchase request that triggers an approval workflow before the PO is created, you don’t have pre-payment control. You have post-decision documentation.

NetSuite does support purchase requests through the Employee Center, and Sage Intacct includes purchase requisitions within its Purchasing module. The question isn’t whether the feature exists. It’s whether employees actually use it. If the native requisition interface is clunky, form-heavy, or requires ERP login credentials, employees revert to email, Slack, or just buying on a personal card and expensing it later. You’re back to zero pre-approval control.

The Punchout Gap: Why This Question Matters More Than You Think

This is the biggest procurement gap in mid-market ERPs, and the primary reason companies add a standalone procurement layer.

None of the three major ERPs (NetSuite, Sage Intacct, Microsoft Business Central) offer native punchout catalog integrations with vendors like Amazon Business, Thermo Fisher, Grainger, or Fastenal. Without punchout catalogs, employees face two options:

• Manually key in item descriptions, quantities, and prices into the ERP’s requisition form. This is slow, error-prone, and nobody does it consistently.
• Buy on personal accounts or company credit cards and expense it later. This means zero pre-approval control, no audit trail until after the money is spent, and a Controller who doesn’t know what the company bought until month-end.

Punchout catalogs solve this by giving employees a familiar online shopping experience. They browse vendor websites directly, add items to their cart, and the cart data flows back into the procurement system for approval, with correct pricing, item details, and vendor information already populated. No manual data entry. No workarounds.

Here’s what the difference looks like in practice. A lab manager at a biotech company needs to order reagents from Thermo Fisher.

Without punchout: The lab manager browses the Thermo Fisher website, copies item numbers and prices into a Word document or email, sends it to their manager for approval, and waits. Once approved, someone in finance keys the PO into the ERP manually, matching item details from the email. The PO gets emailed to Thermo Fisher. Total time: 2-3 days, multiple manual handoffs, and at least one data entry error per week.

With punchout: The lab manager opens ProcureDesk, clicks the Thermo Fisher catalog, browses the live site, and adds reagents to their cart. The cart transfers back into ProcureDesk with item numbers, descriptions, pricing, and quantities already populated. They submit the request. ProcureDesk routes it to the correct approver based on the amount and department. On approval, the PO is generated and sent to Thermo Fisher automatically. Total time: under an hour, zero manual data entry.

ProcureDesk supports 200+ punchout catalog integrations, including Amazon Business, Thermo Fisher, Grainger, Fastenal, VWR, and Uline. Employees shop the way they’re used to, and everything routes through approval workflows before a PO is created.

Learn more about how our purchase requisition system works.

Question 3: How Does Three-Way Matching Work in the ERP?

Three-way matching compares three documents before approving an invoice for payment: the purchase order (what you ordered), the goods receipt (what you received), and the vendor invoice (what you’re being billed for). If all three match, the invoice is valid and can be paid. If something doesn’t match, it gets flagged for review.

Ask your implementer specifically: does the system automatically match these three documents? Or does your AP team pull up the PO, find the receipt, compare line items manually, and then approve?

NetSuite supports vendor bill matching to purchase orders, but you need to create item receipts first, and matching tolerances require configuration. If your implementation team doesn’t set up item receipts as part of the receiving workflow, the three-way match has no receipt document to compare against. Sage Intacct’s Purchasing module can convert POs to vendor invoices, but automated matching at scale often requires marketplace add-ons or careful workflow setup.

Microsoft Business Central offers basic invoice matching against purchase orders and receipts, but the matching tolerances and exception handling workflows require manual configuration. For companies with high invoice volume across multiple vendors, the native matching often isn’t granular enough to handle real-world discrepancies like partial shipments, price adjustments, or split deliveries.

For companies processing more than 50 invoices per month, manual matching is not sustainable. Your AP team will spend hours each week on reconciliation that a system should handle automatically. At the Ardent Partners benchmark average cost of $9.40 per invoice, those hours add up fast.

Coast Flight, a ProcureDesk customer, reduced invoice processing time by 30% by automating three-way matching. Their AP team stopped reviewing every invoice line by line and instead focused only on exceptions, the invoices where something didn’t match.

The real follow-up question: what happens with exceptions? When quantities don’t match the PO, or the invoice price differs from what was agreed, how does the ERP route those discrepancies? Who resolves them? How long does it take? If the answer is “the AP team handles it manually,” that’s the workload you’re committing to for every mismatched invoice.

For a step-by-step breakdown of how automated three-way matching works in practice, read our 3-way match implementation guide. For a broader look at matching strategies, see our invoice matching process guide.

Question 4: What Happens to Invoices That Arrive Without a PO Number?

This is the gap most ERPs don’t handle well. A vendor sends an invoice. There’s no PO number on it. Maybe the employee placed the order over the phone and never created a requisition. Maybe the vendor forgot to reference the PO. Maybe a subscription auto-renewed and nobody remembered to create a PO for the renewal. Either way, the AP team now has to figure out who ordered this, whether it was approved, and whether the amount is correct.

These non-PO invoices create processing exceptions that eat AP time. According to Ardent Partners research, the average organization has an invoice exception rate of 22%. Top-performing organizations bring that down to around 9%. The difference between those two numbers is hundreds of hours of staff time per year for a company processing 100+ invoices monthly.

Ask your implementer three specific follow-ups:

• How does the ERP route invoices that arrive without a PO number? Is there an automated exception workflow?
• Who resolves the exception, and how are they notified?
• What’s the average resolution time for a non-PO invoice? If nobody tracks this, that’s a data point in itself.

If the answer to all three is “the AP team handles it manually by emailing around,” that’s predictable workload you’re absorbing permanently.

In a well-designed procurement system, fewer invoices arrive without POs in the first place, because the purchase request process catches spending upstream. When exceptions do happen, automated routing sends the invoice to the person who most likely made the purchase for confirmation, rather than leaving AP to investigate.

For more on how to design invoice exception workflows, see our guide on the invoice approval workflow.

Question 5: What Does the Audit Trail Look Like?

For each purchase, can you see who requested it, who approved it, when it was approved, at what amount, against which budget, and with what GL code, all in one screen?

That’s what auditors ask for. Walk through this with your implementer on a sample transaction before go-live. Ask them to show you the complete lifecycle of a single purchase, from the original request through payment. If pulling that information requires exporting from three different modules and stitching it together in a spreadsheet, the audit trail isn’t really a trail. It’s a scavenger hunt.

A ProcureDesk customer reduced their month-end close from 7-8 days to 3 days. The reason wasn’t faster data entry. It was that the audit trail was built into the procurement workflow from the start. When the month-end arrived, the data was already clean and documented. There was nothing to reconstruct.

This matters more in certain industries. Biotech companies with grant funding need to show exactly how grant dollars were spent. Charter schools with restricted budgets face board compliance requirements. Construction companies managing project-based spend need to tie every purchase back to a job cost code. If your ERP’s audit trail requires manual assembly, you’ll feel it every month-end and every audit cycle.

See how a complete procure-to-pay system builds the audit trail automatically, from request through payment.

Question 6: Is There a Standalone Procurement Layer That Integrates With This ERP?

This is where ProcureDesk belongs in the conversation. And it’s a question your ERP implementer can answer, because many of them already recommend procurement tools to their clients.

The architecture is straightforward. A standalone procurement tool sits in front of the ERP. It handles the upstream workflow: employee purchase requests, approval routing, punchout catalogs, vendor communication, receipts, and three-way matching. Then it syncs clean, matched data to your ERP for payment processing and financial reporting.

Ask your implementer: “Do you have a preferred procurement tool for companies our size?” If they do, evaluate it alongside your ERP implementation timeline. If they don’t, that’s your signal to evaluate independently.

When you evaluate, the mid-market procurement category includes Procurify, Precoro, and ProcureDesk. Procurify optimizes for requester adoption across the organization. Precoro emphasizes multi-entity centralization with self-serve setup. ProcureDesk is built for the Controller’s workflow — multi-level approval routing by department and cost center, deeper QuickBooks integration including Desktop and Enterprise editions, and done-for-you implementation in 2-3 weeks.

ProcureDesk integrates with NetSuite, Sage Intacct, Microsoft Business Central, QuickBooks (Online, Desktop, and Enterprise), Xero, and Bill.com. The NetSuite integration uses native APIs, not SuiteScript, which means no custom code to maintain and no dependency on a developer to keep the connection working. The Sage Intacct integration syncs using Intacct’s dimensions (departments, locations, projects, classes) so your chart of accounts structure carries through automatically.

The integration model works like this: ProcureDesk imports your master data (chart of accounts, vendors, payment terms, classes, and locations) from the ERP during setup. Employees create purchase requests in ProcureDesk, shopping from punchout catalogs or submitting manual requests. Approved POs sync to the ERP automatically. When invoices come in, ProcureDesk matches them against POs and receipts, and syncs the matched, approved invoice to the ERP for payment. No duplicate data entry. No manual exports.

Setup takes 2-3 weeks with white-glove onboarding. ProcureDesk’s team handles the configuration, catalog setup, workflow design, and user training. It runs in parallel with your ERP implementation. No IT resources required.

You can see how the NetSuite integration works specifically on our NetSuite integration page. For a full list of supported systems, visit our integrations page.

What to Do If the ERP Doesn’t Cover It

If the answers to questions 1 through 5 involve manual workarounds, you have two paths:

Path 1: Build the workflow inside the ERP with customizations. This means SuiteScript development for NetSuite, custom Power Automate flows for Business Central, or marketplace add-ons for Sage Intacct. Customizations are expensive, slow to build, and create technical debt. Every ERP upgrade risks breaking your custom workflows. Every change requires consultant hours. And the procurement-specific features you need (punchout catalogs, visual workflow builders, mobile approvals) simply don’t exist in ERP customization toolkits.

Path 2: Add a purpose-built procurement tool that handles approvals and hands clean data to the ERP. For mid-market companies (100–1,000 employees), this is almost always faster, cheaper, and easier to maintain. You get procurement controls without touching the ERP’s core. And if you switch ERPs later, your procurement workflows don’t need rebuilding. The procurement layer stays the same; only the integration endpoint changes.

Here’s a practical way to think about it: your ERP is your system of record for accounting and financial reporting. A procurement tool is your system of action for purchasing control. They serve different purposes and work best when they’re connected but separate.

The results from mid-market companies speak for themselves. Mid-market customers have moved from multi-day order placement timelines to under 24 hours, and from two-day approval cycles to under four hours. These aren’t enterprise organizations with large IT departments. They’re mid-market companies with small finance teams who needed procurement controls that worked from day one.

Customers like Coast Flight have seen 30% improvements in invoice processing speed through automated three-way matching.

In each case, the procurement layer did the heavy lifting on approvals, matching, and audit trails, while the ERP stayed focused on what it does best: accounting and reporting.

Frequently Asked Questions

Additional Resources

If you’re working through procurement controls alongside an ERP implementation, these ProcureDesk resources cover the specific topics referenced in this article:

• How to Design Procurement Approval Workflows for Speed: Covers multi-level routing, parallel approvals, and risk-based thresholds.
• How to Implement a 3-Way Match Process: Step-by-step guide to setting up automated matching and exception handling.
• Purchase Order and AP Automation for NetSuite: How ProcureDesk’s native API integration works with NetSuite.
• ProcureDesk for Sage Intacct: Sage Intacct Marketplace listing with integration details and feature overview.
• Guide to Purchase Order Approval Process: How to design approval workflows based on amount, category, and department.
• All ProcureDesk Integrations: Full list of ERP, accounting, and collaboration tool integrations.

Start With the Right Questions

The six questions above separate ERP implementations that deliver real spend control from ones that leave procurement gaps you’ll discover at the first month-end close. Or worse, at your first audit.

Most ERP implementers are focused on getting the accounting side right. That’s their job. Procurement controls are a complementary layer that the right tool handles better than ERP customizations.

Ask these questions during implementation, not after go-live. The earlier you identify the gaps, the easier they are to fill.

ProcureDesk is a procurement and AP automation platform built for mid-market finance teams (100–1,000 employees) running NetSuite, Sage Intacct, Microsoft Business Central, or QuickBooks (Online, Desktop, and Enterprise). It controls spending before the invoice arrives multi-level approval workflows, automated 3-way matching, and 200+ punchout catalog integrations. Setup runs in parallel with ERP go-live in 2-3 weeks, no IT project required, built specifically for mid-market, not enterprise SAP/Oracle-scale or SMB under 50 employees.