How to choose procurement software: a buyer's checklist for mid-size companies

Step 1: write down the problem before you look at products

Vendors are good at showing features. You need to be clear about outcomes first. Answer these questions in one page, with the controller, a department head and whoever places most orders in the room:

• Where does spend escape control today? Orders placed before approval, invoices without POs, card spend, contracts that auto-renew.
• What does month-end look like? How many invoices arrive without a PO, how long matching takes, how accruals are estimated.
• How many people raise purchases? Not just the finance team. Every requester is a user of the system in some form.
• How many POs and invoices a month? Roughly, and at peak.
• Which accounting system? And whether it will change in the next two years.
• How many legal entities and currencies? Now and expected in the next two years.

The answers become your requirements and, later, your success measures. If invoices without POs are the pain, the right product is the one that drives that number down, not the one with the longest feature list.

Step 2: the core functional checklist

Use this as a scoring sheet. For each line, ask the vendor to show it working, not to describe it.

Step 3: test the accounting integration properly

The accounting integration is where most rollouts either save time or quietly create a second job. Do not accept "we integrate with QuickBooks" as an answer. Ask for specifics:

• Direction. Which data flows which way: suppliers, GL accounts, classes, departments, projects, bills, payments.
• Timing. Real time, scheduled, or a manual export button.
• Coding. Does the bill arrive in accounting already coded to the right account and department, or does someone recode it?
• Errors. What happens when a sync fails: an alert with the reason, or a silent gap found at month-end?
• Your system specifically. QuickBooks Online, Xero, NetSuite and Sage Intacct each have their own objects and limits. Ask to see a sync to your system, with your chart of accounts, in the evaluation.

If you are on QuickBooks Online or Xero today and expect to move to NetSuite or Sage Intacct as you grow, check that the same product supports both, so you do not have to change procurement tools when you change the general ledger. Our QuickBooks integration page shows the level of detail worth asking any vendor for.

Step 4: understand the pricing model, not just the price

Procurement tools are priced in a few different ways, and the model affects adoption as much as cost:

When comparing, calculate the total cost over two or three years at your expected volume, including implementation, training, integration fees and any add-ons you will need (invoice capture and three way matching are sometimes sold separately). Ask for the price of the tier you will need in a year, not only the one you need today.

Step 5: judge the rollout, not the pitch

A procurement system that takes six months to launch has usually lost the organization before it goes live. For a mid-size company, a realistic target is a working process in weeks. Ask each vendor:

• What does a typical setup look like, step by step? Import suppliers, import budgets, configure approval rules, connect accounting, invite users.
• Who does the work? Your team, the vendor, or a partner, and at what cost.
• Can we import our open POs and suppliers? Starting from zero means running two systems for months.
• What does a requester need to learn? If the answer involves a training session, most requesters will not attend.
• Can we start with one department? A pilot with one or two departments proves the approval rules before the whole company joins.

Step 6: security and control requirements

Your IT and audit teams will have their own list. The items that come up for almost every mid-size buyer:

• Single sign-on with Google or Microsoft, and SAML SSO and user provisioning for larger organizations.
• Roles and permissions that separate requesting, approving, receiving, paying and supplier administration.
• Segregation of duties rules, such as no approving your own request.
• A complete audit log that cannot be edited.
• Data export in a usable format, so you are never locked in.
• Encryption in transit and at rest, a data processing agreement, and support for your security review.

Ask for the security documentation early. It takes longer than the functional evaluation.

Step 7: run the evaluation in three weeks

A structured evaluation avoids choosing on demo charisma. A simple plan:

• Week 1: shortlist. Two or three products that fit your size, accounting system and budget. Enterprise suites built for companies ten times larger tend to bring enterprise timelines; tools built for very small teams tend to run out of room in approval rules and matching.
• Week 2: hands-on test. Give each vendor the same three scenarios from your real business: a routine purchase under the first threshold, a large purchase with a new supplier that needs three approvals, and a partial delivery with an invoice at a slightly higher price. Watch each scenario end to end, from request to synced bill.
• Week 3: references and numbers. Talk to a company of similar size on the same accounting system, and complete the two or three year cost comparison.

Score each product on the checklist from Step 2, weighted by the problems from Step 1.

Red flags during evaluation

• The product cannot show your approval matrix without custom development.
• The integration is a CSV export described as a sync.
• Three way matching exists but has no tolerance settings, so every cent becomes an exception.
• Requesters need a paid seat to raise a request.
• The vendor cannot say how long setup takes for a company of your size.
• Contract terms include automatic renewal with an uncapped price increase.

A one-page scoring sheet

Adjust the weights to your Step 1 answers. For a broader overview of the category, see our guide to the best procurement software, and for the process any product has to support, the procure to pay process, step by step.