Most procurement technology implementations underdeliver not because the platform is wrong, but because the organisation wasn't ready for it. We've written a practical guide to getting the selection right.
Procurement technology is a significant investment. Enterprise source-to-pay platforms from vendors like SAP Ariba, Coupa, JAGGAER, Ivalua, and GEP can cost $200,000 to over $500,000 annually in licensing alone, with implementation costs of $300,000 to $1 million or more on top. Mid-market procure-to-pay tools are less expensive but still represent a material commitment of budget, time, and organisational change capacity. The Gartner Magic Quadrant for Source-to-Pay Suites in 2026 evaluated 13 providers, reflecting a market that is mature, competitive, and genuinely confusing for buyers.
The problem is not that good technology does not exist. It does. The problem is that most procurement technology selection processes are vendor-led rather than requirements-led. Organisations attend demonstrations, get drawn in by capabilities they may never use, and select a platform based on feature lists and sales presentations rather than a rigorous assessment of what their procurement function actually needs, what their organisation can realistically implement, and what level of technology matches their current process maturity.
The result, more often than anyone in the industry likes to admit, is an expensive platform that is underutilised, poorly adopted, and delivers a fraction of its promised value. The vendor blames the client for poor adoption. The client blames the vendor for overselling. Neither is entirely wrong.
This article covers how to select procurement technology properly: what to assess before you talk to vendors, how to evaluate platforms, what drives total cost of ownership, and where organisations consistently get it wrong.
What should you assess before talking to any vendor?
Start with process maturity, not technology. The single most important principle in procurement technology selection is that technology should match the maturity of the procurement function it is designed to support.
An organisation with no structured procurement processes, no spend visibility, no category management discipline, and no contract management framework does not need an enterprise source-to-pay suite. It needs to build the foundational processes first, using relatively simple tools, and then invest in technology that automates and enhances those processes once they are established.
An organisation with a mature procurement function, structured category management, active supplier management, and a well-governed contract portfolio is ready for a platform that provides spend analytics, automated workflows, supplier collaboration, and strategic sourcing support.
Buying technology ahead of process maturity is one of the most expensive mistakes in procurement. The platform sits underutilised because the organisation does not have the processes, data, or people to use it effectively.
Before talking to any vendor, assess your procurement function's maturity across five dimensions:
- Spend visibility: Do you know what you spend, with whom, on what terms?
- Process standardisation: Are procurement processes consistent across the organisation?
- Supplier management: Do you actively manage supplier performance and relationships?
- Contract management: Are contracts stored, tracked, and actively governed?
- Analytics capability: Can you generate insights from your procurement data?
Your technology selection should address the gaps identified in this assessment, not leapfrog them.
What does procurement technology actually do?
The procurement technology market is segmented into several categories, and understanding the distinctions matters for selection.
Source-to-pay (S2P) suites cover the full procurement lifecycle: sourcing events (RFx management, auctions, supplier evaluation), contract management, requisitioning and purchasing, catalogue management, invoice processing, and payment. The major enterprise players are SAP Ariba, Coupa, JAGGAER, Ivalua, and GEP SMART. These platforms are designed for large organisations with dedicated procurement teams and the implementation capacity to deploy a comprehensive suite.
Procure-to-pay (P2P) platforms focus on the transactional side: purchase requisitions, approvals, purchase orders, goods receipt, invoice matching, and payment. Tools like Procurify, Precoro, and Basware sit here. P2P platforms suit organisations whose primary need is controlling and automating the purchasing process rather than managing strategic sourcing.
Spend analytics tools provide visibility into procurement spend: what is being spent, with which suppliers, across which categories, and at what prices. Deploying standalone spend analytics before investing in a broader platform is a sensible approach, because spend visibility is the foundation for every other procurement improvement.
Specialist tools address specific procurement disciplines: contract lifecycle management (CLM), supplier risk management, e-sourcing, and catalogue management. These can be deployed as standalone solutions or integrated with a broader S2P or P2P platform.
The right choice depends on what your procurement function needs most urgently and what your organisation can realistically implement. A mid-market Australian business with $50 million in addressable spend does not need an enterprise S2P suite built for a $5 billion multinational. A P2P tool with solid spend analytics and contract tracking may deliver everything that organisation needs at a fraction of the cost and implementation effort.
How should you run the selection process?
A rigorous technology selection process separates requirements definition from vendor evaluation. Collapsing these two stages is where many organisations go wrong.
Step 1: Define requirements. Before engaging any vendor, document what you need the technology to do. Express this as business requirements, not feature requirements. "Provide consolidated spend visibility across all business units within 30 days of transaction" is a business requirement. "Must have a drag-and-drop dashboard builder" is a feature requirement. Business requirements ensure you are evaluating platforms against what matters to your organisation, not against what the vendor is best at demonstrating.
Step 2: Assess the market. Research the platforms relevant to your size, sector, and requirements. The Gartner Magic Quadrant, Spend Matters SolutionMap, and G2 reviews provide useful starting points. Shortlist three to five platforms that appear to match your requirements and request demonstrations.
Step 3: Structure the demonstrations. Do not let vendors run their standard demonstration. Provide each vendor with a scripted scenario based on your actual procurement processes and ask them to demonstrate how their platform handles it. This ensures you are comparing platforms on the same basis, and that the demonstration reflects your reality rather than the vendor's best-case scenario.
Step 4: Evaluate total cost of ownership. Licensing fees are only part of the cost. Implementation (which for enterprise platforms can take 6 to 18 months), data migration and cleansing, integration with your ERP and finance systems, training, change management, and ongoing administration all contribute to total cost. Request detailed cost breakdowns from each vendor, including professional services for implementation, and build a five-year total cost of ownership model that includes all elements.
Step 5: Check references. Speak to organisations of similar size and complexity that are using the platform. Ask about implementation experience, time to value, user adoption, ongoing support quality, and whether the platform has delivered its promised benefits. Vendor-provided references will be positive. Ask for contacts the vendor does not volunteer.
Step 6: Negotiate commercially. Procurement technology is a competitive market and pricing is negotiable. Multi-year commitments, phased rollouts, and volume-based pricing all provide levers. Do not accept the first commercial proposal.
What factors are specific to the Australian market?
Integration with local ERP environments. The Australian mid-market is heavily weighted toward SAP, Oracle, Microsoft Dynamics, and NetSuite. The procurement technology you select must integrate cleanly with your ERP for purchase order generation, goods receipt, invoice matching, and payment processing. Native integrations are always preferable to custom-built connectors, which are expensive to build and expensive to maintain through ERP upgrades. Ask vendors specifically about their integration with your ERP platform, not about their integration capabilities in general.
GST and Australian tax compliance. Procurement technology needs to handle Australian GST correctly, including the nuances of taxable and GST-free supplies, input tax credits, and the treatment of imported goods and services. Platforms designed primarily for the US or European market may not handle Australian tax requirements natively, requiring configuration or workarounds that add complexity and risk.
Local support and implementation capability. Enterprise procurement platforms are global products, but implementation and support are local. Assess whether the vendor has an Australian implementation team or relies on global partners. Time zone differences, local market knowledge, and the ability to provide on-site support during implementation all matter. Some vendors have strong Australian presence; others rely on implementation partners whose quality varies.
Government procurement requirements. For organisations that procure on behalf of government or sell into government, the technology must support Australian compliance requirements: AusTender reporting, Indigenous procurement tracking, modern slavery reporting, and the specific documentation and approval workflows required by Commonwealth and state procurement frameworks. Not all global platforms handle these requirements out of the box.
Phased implementation suits the Australian mid-market. Many Australian organisations are mid-market by global standards. Starting with spend analytics and P2P automation before expanding to strategic sourcing and supplier management allows organisations to build capability and demonstrate value before committing to the full suite. This approach also reduces implementation risk and spreads cost over a longer period, which is often more palatable to boards that are cautious about large technology investments.
Should you build or buy procurement technology?
For most organisations, buy is the better long-term decision for anything beyond basic P2P automation.
The build approach has lower upfront cost but higher long-term maintenance cost, and creates a dependency on internal developers who may move on. The buy approach has higher upfront cost but lower maintenance cost, and provides access to vendor innovation and regular feature updates.
Building your own procurement workflows using low-code platforms or custom ERP development can work for simple P2P automation: purchase requisitions, approvals, and PO generation. It rarely works for the more complex capabilities dedicated procurement platforms provide, including spend analytics, sourcing event management, contract lifecycle management, and supplier performance tracking.
The exception is organisations with genuinely unique requirements that no commercial platform addresses. This is rarer than many IT teams believe.
Where do organisations consistently get it wrong?
Buying the biggest platform because it feels safer. Enterprise S2P suites are powerful, but they are designed for organisations with the scale, budget, and internal capability to deploy and maintain them. A mid-market organisation that buys an enterprise suite because it is the market leader will pay enterprise prices, face enterprise implementation timelines, and often achieve mid-market adoption. That is a poor return.
Underestimating implementation effort. The vendor demonstration makes everything look straightforward. The reality of implementation, data migration, ERP integration, process redesign, user training, and change management is not. Organisations that budget for the licence but not for the implementation end up with a partially deployed platform that frustrates users and undermines the business case.
Ignoring user adoption. The best procurement platform delivers zero value if procurement staff, budget holders, and approvers do not use it. User adoption is driven by ease of use, quality of training, strength of change management, and whether the platform genuinely makes people's jobs easier. Platforms that are powerful but difficult to use will see low adoption, workarounds, and a return to email and spreadsheets.
Selecting technology before fixing data. Procurement technology depends on clean, consistent master data: supplier records, product catalogues, cost centres, and approval hierarchies. Implementing procurement technology on top of dirty data produces automated chaos rather than automated efficiency. Data cleansing and governance should be a prerequisite for technology implementation, not an afterthought.
Failing to plan for the ongoing operating model. Procurement technology requires ongoing administration: maintaining catalogues, managing user access, updating workflows, monitoring system performance, and managing vendor releases. Organisations that do not plan for this find that the platform degrades over time as catalogues become outdated, workflows drift from actual processes, and the system gradually loses relevance.
Letting IT drive the selection. Procurement technology should be selected by the procurement function, with IT providing input on integration, security, and infrastructure. When IT leads, the evaluation tends to prioritise technical architecture and integration elegance over the practical question of whether the platform will make procurement staff more effective. The best selection processes are led by procurement, with IT as a key stakeholder.
Underestimating supplier onboarding. Every procurement platform requires suppliers to interact with it in some way: submitting invoices through a portal, responding to sourcing events, maintaining catalogue content, or providing compliance documentation. If your key suppliers will not use the platform, its value diminishes significantly. Assess supplier readiness as part of the selection process and build supplier onboarding into the implementation plan from the start, not as a late-stage activity.
Not sure where your procurement function sits? Trace runs procurement maturity assessments that tell you what technology you're ready for, and what to fix first.
Speak to our team →
How can Trace Consultants help with procurement technology selection?
Trace Consultants helps organisations select and implement procurement technology that matches their maturity, their requirements, and their capacity to sustain it.
Procurement maturity assessment. We assess your procurement function's current maturity and identify the technology requirements that will deliver the highest value, ensuring you invest in technology that matches your readiness.
Technology selection support. We manage the end-to-end selection process: requirements definition, market assessment, vendor shortlisting, structured demonstrations, total cost of ownership analysis, reference checks, and commercial negotiation.
Implementation oversight. We provide independent oversight of procurement technology implementations, ensuring the project stays on track, integration with your existing systems is properly managed, and the change management programme drives genuine adoption.
Data readiness. We lead the data cleansing and governance workstream that ensures your master data is fit for purpose before the new platform goes live.
See how we work with procurement teams →
Where should you start?
Start by being honest about where your procurement function sits today. If you do not have spend visibility, structured processes, or clean master data, fix those first. They are cheaper to address than a technology implementation, and they are prerequisites for the technology to deliver value.
If your procurement function is mature enough for technology investment, run a proper selection process. Define your requirements before you talk to vendors. Evaluate total cost of ownership, not just licence fees. Check references. And negotiate, because this is a competitive market and every vendor wants your business.
The organisations that get the most value from procurement technology treat it as an enabler of a well-designed procurement function, not as a substitute for one.
If you're evaluating procurement technology, or wondering whether you're ready to, we'd love to chat.
Get in touch →
FAQs
What is the difference between source-to-pay and procure-to-pay?
Source-to-pay (S2P) covers the full procurement lifecycle from sourcing and supplier selection through to payment. Procure-to-pay (P2P) focuses on the transactional purchasing process: requisitions, approvals, purchase orders, invoice matching, and payment. S2P suites suit larger organisations managing strategic sourcing alongside transactional purchasing. P2P platforms suit organisations whose primary need is controlling and automating day-to-day purchasing.
How much does procurement technology cost in Australia?
Enterprise source-to-pay platforms can cost $200,000 to over $500,000 annually in licensing, with implementation costs of $300,000 to $1 million or more. Mid-market procure-to-pay tools are considerably less expensive. A five-year total cost of ownership model should account for all elements: licensing, implementation, integration, training, and ongoing administration.
How long does a procurement technology implementation take?
Enterprise platform implementations typically take 6 to 18 months. Mid-market P2P implementations can be completed more quickly, particularly when data is clean and integration requirements are straightforward. Phased implementations, starting with spend analytics or P2P before expanding to strategic sourcing, allow organisations to demonstrate value earlier and reduce implementation risk.
What is the biggest reason procurement technology implementations fail?
Poor adoption. The platform may be technically deployed, but if procurement staff, budget holders, and approvers do not use it, it delivers no value. Adoption failures are usually rooted in inadequate change management, insufficient training, or a platform that is too complex for the organisation's actual needs.
Do Australian organisations have specific procurement technology requirements?
Yes. Australian-specific requirements include GST compliance, AusTender reporting for government-connected organisations, Indigenous procurement tracking, and modern slavery reporting. Integration with locally common ERP platforms (SAP, Oracle, Microsoft Dynamics, NetSuite) is also a practical requirement that global vendors do not always handle cleanly without configuration.