Mid-market finance teams (100 to 1,000 employees) that complete this procurement software checklist go live in 3-4 weeks. Teams that skip three or more items end up re-implementing within six months.

TL;DR

The eight items below decide whether your procurement software pays back in the first quarter or stalls out by month two. Fix them before go-live, not during.

• Stabilize the accounting system first. No procurement layer on top of an in-flight ERP migration or a chart of accounts still being restructured.
• Clean the GL before import. Messy codes flow downstream into every PO and invoice. Ten hours of cleanup saves a quarter of rework later.
• Build a working vendor list. Top 50 vendors by trailing 12-month spend is enough to configure. Refine inside the first 90 days.
• Document the purchasing policy in three pages. Approval thresholds, named approvers, vendor rules. The software enforces what is written down.
• Lock the approval matrix by dollar amount and named approver. Build vacation delegation in from day one, not when the Controller is on PTO.
• Get the leadership mandate in writing before go-live. Without it, adoption tops out at 60-70%. With it, 90% inside thirty days.
• Set a clean cutover date and pick two or three power users. Train them first, let them train the rest. No parallel-process windows.

What should you do before implementing procurement software?

Stabilize your accounting system, clean your chart of accounts, document your purchasing policy and approval matrix, get a written leadership mandate, train your power users, and set a clean cutover date. The eight items below are the readiness work that determines whether your procurement software pays back in the first quarter or stalls out by month two.

This checklist covers the organizational readiness work that comes before the implementation project starts. Configuration, data migration, user acceptance testing, change management, and go-live all run faster when these eight items are sorted first.

Most procurement software implementations that fail do not fail because of the software. They fail because the organization was not ready.

The pattern is predictable. A finance leader identifies a tool that solves 90% of the problem. The contract gets signed. The system goes live. Then employees keep emailing purchase requests because that is what they are used to. The finance team is now running two processes instead of one. Within six weeks, adoption stalls and the CFO is being asked why the investment is not paying off.

At ProcureDesk, we have onboarded hundreds of companies onto our procurement and AP automation platform. The teams that go live in 3-4 weeks (or 6-8 weeks for larger mid-market organizations) have one thing in common: they sorted out eight things before implementation day. The teams that struggle skipped at least three of them.

If you are a CPA firm advising a client on procurement readiness, or an ERP implementer preparing a client for a procurement layer, this checklist doubles as a pre-engagement assessment you can share before the software evaluation even starts.

1. Your Accounting System Must Be Live and Stable

Procurement software syncs to your accounting system. Every purchase order, every invoice, every GL code flows between the two. If your chart of accounts is under construction, your GL codes are inconsistent, or you are in the middle of an ERP migration, wait.

Implement procurement software after your accounting system is stable, not during the transition. This applies whether you are running QuickBooks Online, QuickBooks Enterprise, NetSuite, Sage Intacct, Xero, or Microsoft Business Central. ProcureDesk imports your chart of accounts, suppliers, departments, and cost codes directly from your accounting system. If that data is messy or in flux, the import inherits every inconsistency.

The most common timing mistake we see at the CFO level: a company decides to upgrade from QuickBooks to NetSuite and add procurement software at the same time. Both projects compete for the same finance team’s attention, and both suffer. Finish one, then start the other.

“Stable” does not mean perfect. It means your team has been on the system for at least a few months, your chart of accounts is not changing week to week, and your finance team is not actively debugging integration issues. If your last GL restructure was more than 90 days ago and you are not planning another, you are stable enough.

2. Clean Up Your Chart of Accounts First

Your chart of accounts is the financial backbone for every report your procurement system produces over the next year. If GL codes are disorganized, departments are missing, projects are miscoded, or classes are not set up, the procurement system inherits that mess and makes it harder to fix later.

Here is why this matters at the CFO level. When an employee creates a purchase request in ProcureDesk, the system assigns GL codes, departments, and cost centers automatically based on rules you configure. If those codes do not exist or are mapped incorrectly, every PO and every invoice that flows downstream carries the wrong data. You spend Q1 fixing coding errors instead of running the system.

Spend one week cleaning this up before implementation. It is a 10-hour job that saves 100 hours of post-implementation cleanup.

What to check:

• Are all active departments represented in your chart of accounts?
• Are GL codes consistent across similar expense types?
• Are inactive or legacy accounts marked inactive, not just floating in the system?
• If you use classes, projects, or locations, are they current?

Companies that come into implementation with a clean accounting structure go live faster. Metabolon, a biotech company on Sage Intacct, is a good example. Their finance team had the accounting structure organized before they started, and the implementation moved quickly because ProcureDesk could import clean data from day one.

3. Build a Basic Vendor List

You need a starting vendor master before you can configure the system. At minimum: company name, primary contact, payment terms, and whether each vendor is preferred or just allowed.

It does not need to be perfect. It needs to exist. Fifty vendors is enough to start. You will add more during rollout and in the first 90 days after go-live. The goal is to have your most-used suppliers ready so the system can be configured with real data, not placeholders.

ProcureDesk imports vendor data from your accounting system automatically. But someone still has to make decisions about which vendors are approved for self-service purchasing and which are restricted. That is a policy decision, not a software task.

If you are starting from scratch, pull every vendor you have paid in the last 12 months from your accounting system. Sort by total spend. Your top 50 by spend volume are your starting list.

Three decisions to make while you build the list:

• Preferred vs. allowed vendors. Preferred vendors are the ones employees should default to. Allowed vendors are acceptable but not the first choice.
• Restricted vendors. Personal Amazon accounts are a common compliance problem. You may want employees on Amazon Business through ProcureDesk’s punchout catalog instead.
• Vendor contact accuracy. A working email for each vendor’s order desk. POs go out electronically. Wrong email, no PO.

Build a working vendor database, not a perfect one. You will refine it in the first 90 days as you see which vendors employees actually use.

4. Write Your Purchasing Policy (Even a Basic One)

The software enforces your rules. If you have not decided the rules, the software cannot enforce them.

Three things need to be documented before you start configuring a procurement system:

• Approval thresholds by dollar amount. For example: self-approval up to $250, manager approval $250-$5,000, Controller or CFO approval above $5,000.
• Who approves at each level. Names and roles, not just titles. The system needs to know where to route each request.
• Vendor rules. Can employees buy from any vendor, or only from preferred suppliers? Are there vendors that require additional approval?

Three pages is enough. You are not writing corporate bylaws. You are documenting the decisions that will drive your approval workflows. If you do not have a purchasing policy today, ProcureDesk offers a free template you can use as a starting point.

If you are a CPA advising a client, the purchasing policy template is a useful resource to share before the software conversation even begins. It helps clients think through their rules before they try to automate them.

5. Define Your Approval Matrix

Who can approve what amount at what level? This sounds simple. It is the single most common reason implementation stalls during configuration.

The approval matrix lives in people’s heads. The Controller knows that purchases over $10,000 need CFO sign-off. Department heads know certain categories need a second look. None of it is written down. When the implementation team asks “what are your approval rules?”, the answer is usually “well, it depends.”

Get it out of everyone’s head and into a document before implementation. The software maps directly to this matrix. If the matrix is not defined, configuration stalls while everyone debates rules they have never formalized.

A simple starting point:

• Under $250: self-approval, no routing needed
• $250 to $5,000: department manager approval
• $5,000 to $25,000: Controller approval
• Above $25,000: CFO approval

Your matrix may be more complex. Some companies route by department, project, or vendor category. Start with dollar thresholds, agree on them, document them. Add complexity after go-live.

One CFO-level lesson from hundreds of implementations: do not over-engineer the approval matrix at the start. Companies that build five-level chains with conditional routing by department, vendor category, and budget code before they have used the system simplify it within 60 days. Start with two or three levels by dollar threshold. Add department-specific routing after a month of live data shows the real bottlenecks.

Build a delegation rule in from day one. If your Controller is the sole approver for purchases over $5,000 and is out for a week, what happens? ProcureDesk supports approval delegation, but you decide who the delegate is before configuration.

6. Get Leadership Buy-In Before Go-Live

The Controller can implement the software. Only leadership can mandate its use.

This is the item most teams skip, and the one that causes the most adoption failures. The system works. The workflows are configured. Training is done. But the CEO or VP of Operations never told the team that purchase requests are now required. So half the company keeps buying the old way, and the Controller is stuck chasing compliance instead of running the system.

Before go-live, get a written or verbal commitment from leadership that purchase requests are required for any purchase above the threshold. An email from the CEO works. A one-paragraph policy announcement works. It does not need to be formal. It needs to be clear.

At myDNA, leadership commitment was a key factor in the results. With the right mandate in place, they reduced their month-end close from 7 to 8 days down to 3 days. The tool mattered. The leadership mandate is what drove adoption across the organization.

What the mandate looks like in practice:

• A company-wide email from the CEO or CFO stating that all purchases above the defined threshold require a PO through the new system
• A specific start date. “Starting November 1st” is clear. “Over the coming weeks” is not.
• A named contact for questions, typically your power user or Controller, not the software vendor

The mandate also protects the Controller. Without it, the Controller becomes the enforcer, chasing employees who bypass the system. With it, the Controller is executing company policy, not playing procurement police. Without the mandate, expect 60-70% adoption. With it, 90%+ within the first month.

7. Identify Your Power Users

Every successful rollout follows the same pattern: two or three employees become internal experts before everyone else touches the system.

These are your power users. They use the system daily. They create the most purchase requests or process the most invoices. They are trained before go-live, and they become the internal resource other employees ask for help.

Do not run company-wide training before go-live. Train power users first, then let them train others. Company-wide training before anyone has actually used the system creates confusion, not competence. People forget what they learned because they have not applied it.

The better sequence:

• Identify 2-3 power users in the first week of implementation
• Include them in configuration decisions so they understand why the system works the way it does
• Let them test the system with real purchase requests before go-live
• After go-live, position them as the first point of contact for questions

At ProcureDesk, our onboarding team trains power users during setup, whether that is 2-3 weeks for smaller mid-market companies or 6-8 weeks for larger ones. By go-live they are comfortable with the system and can help colleagues get started.

8. Plan Your Cutover Date

Set a specific date when the old process stops and the new one starts. Not a gradual rollout. A clean cutover.

Employees who know “after October 1st, all purchases need a PO” adapt quickly. Employees who hear “we are transitioning over the next few months” keep using the old process indefinitely. Gradual rollouts sound reasonable, but they create a window where two processes run in parallel, and the old one always wins because it is easier.

What a clean cutover looks like:

• Two weeks before: Announce the go-live date company-wide. Name the date, explain the new process in one paragraph, identify the power users who can help.
• One week before: Send a reminder with a short FAQ. What do I do when I need to order something? Where do I go? Who do I ask if I am stuck?
• Day one: Turn off the old process. No more email-based purchase requests. No more Slack approvals. Everything goes through the system.
• Week one: Expect questions. This is normal. Power users handle the routine ones. The Controller handles edge cases.

A clean cutover does not mean every purchase goes through the system on day one. You may start with POs for goods and add services or recurring subscriptions in week two or three. The key is that the old process (email, Slack, spreadsheets) stops on the cutover date. Anything new goes through the system.

Pick a cutover date that aligns with a natural business break: the start of a fiscal quarter, the beginning of a budget period, or the Monday after a company all-hands where the CEO announces the new process. Give yourself 2-3 weeks of lead time for communication and power user training.

What to Do If You Are Not Ready

If you are missing more than two items on this list, fix them before evaluating software. A procurement tool is not a substitute for organizational readiness. Most implementation failures are readiness failures.

This is not meant to slow you down. The opposite. Spending two weeks on items 1-4 saves you months of rework after go-live. Companies that skip the prep work end up re-implementing three months later, after the original rollout did not stick.

A quick self-assessment:

• 6-8 items checked: Ready to evaluate software and start implementation. Above-average readiness.
• 4-5 items checked: Close. Spend 1-2 weeks on the gaps. You can start software demos while you finish the prep work.
• Fewer than 4 items checked: Pause the software conversation. Focus on accounting system, chart of accounts, vendor list, and purchasing policy first. These are foundational. Everything else builds on them.

If you are a CPA or ERP implementer advising clients, share this checklist before the software evaluation starts. It qualifies readiness better than any demo. Clients who complete it before the first sales call make faster, more confident decisions because they have already done the organizational thinking.

For CPA firms running CAS engagements, this also serves as a scoping tool. If a client can check off items 1-5, you can confidently recommend they start evaluating procurement software. If they are stuck on items 1 or 2, the engagement should focus on getting their accounting system and chart of accounts right first. The procurement conversation comes after the foundation is solid.

The good news: none of these items require software. They require decisions. Most finance teams can work through the full checklist in two to three focused weeks. That investment of time pays back many times over in a smoother, faster implementation.

FAQ: Procurement Software Implementation

Resources to Complete This Checklist

Everything you need to work through the eight items on this list. All resources are free.

• Purchasing Policy Template — A ready-to-use template for CFOs, Controllers, and finance leaders without a formal purchasing policy. Covers approval authority, vendor rules, and purchasing process guidelines. Download the template
• Purchase Order Policy Template for Nonprofits — A compliance-focused version for charter schools, grant-funded organizations, and nonprofits with restricted budget requirements. Download the nonprofit template
• Purchase Order Approval Process Guide — Step-by-step walkthrough for defining your approval matrix, setting threshold levels, and configuring routing rules. Useful for items 4 and 5. Read the guide
• Spend Control Playbook — A full framework for building spend controls from scratch, including approval authority matrices, vendor management, and budget tracking. Covers the organizational foundation that supports everything on this checklist. Read the playbook
• Procurement System Integration Guide — If you are connecting procurement software with your accounting system (QuickBooks, NetSuite, Sage Intacct, Xero, or Microsoft Business Central), this guide covers integration use cases, data mapping, and what to prepare before configuration. Read the integration guide
• AP Automation for QuickBooks — For teams running QuickBooks who want to understand how procurement software and AP automation work together. Covers invoice capture, 3-way matching, and how approved invoices sync to QuickBooks for payment. Read the guide

---