Procurement in business means the end to end process of acquiring goods and services, from defining the need to managing the supplier and contract over time. In the UK, that definition is reinforced by law, and the scale of its importance is obvious when you consider that public sector procurement spending reached £407 billion in 2023/24.
A lot of HR and IT leaders only feel the difference when something goes wrong. A team buys a system because the licence price looks sensible, the demo is polished, and the procurement conversation gets reduced to “can we get this signed off this quarter?”. Then subsequent costs arrive. Integration work. Data clean-up. Extra security reviews. User adoption issues. Contract terms that don't reflect how the business operates.
That isn't a purchasing problem. It's a procurement problem.
For a mid-market business running Microsoft 365, Dynamics 365, Power Platform, Teams, Outlook and SharePoint, the distinction matters more than is often realized. Buying software is rarely just about software. An HR platform affects onboarding, payroll inputs, document retention, manager workflows, reporting, identity controls and employee experience. An IT purchase affects architecture, support load, compliance posture and whether your systems fit together or fight each other.
When leaders misunderstand the definition of procurement in business, they often treat an important decision like a simple order. They compare headline prices, skip proper supplier evaluation, and leave contract and performance management to chance. That approach might work for stationery. It doesn't work for a core HR system, a contract management platform, or a Microsoft-integrated business application.
Introduction Why Understanding Procurement Matters
A common scenario looks like this. An HR director needs a new people system. Finance wants cost control, IT wants something secure, and the board wants quick progress. A supplier comes in with an attractive subscription price, so the decision gets pushed through as a purchase.
Six months later, the business is dealing with workarounds instead of outcomes.
The system doesn't fit the approval model. It stores key data outside the wider Microsoft environment. Reporting needs extra manual effort. The supplier's support model isn't strong enough for a lean internal team. What looked cheap at the order stage becomes expensive in time, risk and frustration.
That's why procurement matters. It protects the business from making narrow decisions with wide consequences.
Why leaders get caught out
Mid-market organisations often have capable people but limited specialist procurement capacity. HR owns the requirement. IT owns security and integration. Finance owns controls. Operations own practical impact. If nobody joins those strands early, the organisation defaults to purchasing behaviour. That means choosing and ordering, rather than analysing and structuring.
Procurement is where a business decides what problem it is actually solving, not just what product it is buying.
This matters well beyond the public sector, but public spend gives a clear sense of scale. Procurement represents the single biggest component of UK government expenditure, with total public sector procurement spending reaching £407 billion in the 2023/24 financial year, according to the House of Commons Library briefing on public procurement.
The practical consequence for HR and IT
If you're responsible for HR systems or Microsoft estate decisions, procurement should help you answer questions like these before a contract is signed:
- Business fit: Will this support the process we run, or will we bend our process around the tool?
- Technical fit: Does it work properly with Dataverse, Teams, Outlook, SharePoint and existing Dynamics workloads?
- Commercial fit: Are we comparing licence price only, or the full delivery and support picture?
- Operational fit: Who will administer it, govern it, and own supplier performance after go-live?
When procurement is done properly, those questions get answered in the right order. When it isn't, they surface later as project issues.
The True Definition of Procurement in a UK Business
In UK terms, the strongest definition isn't a loose business cliché. It has a legal foundation. Under the Procurement Act 2023, procurement is defined as the “award, entry into and management of a contract”, and that broad concept includes preparatory steps such as preliminary market engagement and continues through contract termination, including expiry, as explained in the explanatory notes to the Procurement Act 2023.
That legal wording matters because it stops people reducing procurement to the moment a supplier is chosen. In practice, procurement begins before the market is approached and continues long after the contract is signed.
Procurement is bigger than the order
A simple way to explain the definition of procurement in business is this. Purchasing is buying the bricks. Procurement is planning the house. It covers the design brief, who you trust to build, what protections you put in the contract, how you manage delivery, and what happens if the builder underperforms.
For a business system, the same logic applies. The software subscription is only one brick in the wall.
A proper procurement view asks:
- Need definition: What outcomes are required by HR, IT, finance and operational teams?
- Market understanding: Which suppliers suit a UK mid-market organisation already invested in Microsoft technology?
- Commercial design: What contract length, service model and support obligations make sense?
- Lifecycle control: How will performance, renewals, changes and exit be managed?
Why this definition matters in real decisions
This broader view is where good decisions are made. A lower priced system can still be the wrong choice if it creates heavy manual work, poor reporting, weak integration, or awkward data handling. Equally, a more capable platform can become poor value if the business hasn't defined requirements properly or lacks the governance to use it well.
Practical rule: If your evaluation only compares supplier quotes, you're still in purchasing mode. Procurement starts earlier and finishes later.
In Microsoft-centred organisations, this is especially important because systems rarely sit alone. An HR tool touches identity, workflows, documents, approvals, analytics and compliance. A procurement approach tests how those moving parts fit together. A purchasing approach usually notices them after contract signature.
The shift from transaction to control
The legal definition also reflects a wider business truth. Procurement isn't only about getting something bought. It's about controlling value, risk and accountability over the full lifecycle.
That means procurement should shape supplier conversations, contract terms, governance routes and service expectations. It should also make sure the business knows what success looks like after implementation, not just at selection stage.
The Procurement Lifecycle A Strategic Journey
Procurement works best when it follows a visible sequence. Not because process is fashionable, but because sequence prevents expensive shortcuts. In UK business procurement, organisations must first determine whether a contract is covered procurement by comparing the estimated value, including VAT, against the relevant thresholds. That decision affects whether competitive tendering, market engagement and formal evaluation become mandatory, as outlined in Amazon Business guidance on procurement in the UK.
That sounds technical, but the principle is straightforward. Before you ask suppliers to respond, you need to know the rules that apply and the route you're taking.
The lifecycle in practical terms
A sensible procurement lifecycle for a mid-market HR or IT decision usually looks like this:
-
Identify the need
Someone spots a gap. Manual onboarding is too slow. Contract records are spread across email and SharePoint folders. Expenses take too long to process. -
Define the requirement
Many teams often rush at this stage. They describe a product category instead of a business need. Good procurement translates complaints into requirements, workflows, controls and outcomes. -
Test the market
Not every supplier is right for a Microsoft-based organisation. Some tools integrate neatly with Dataverse and Power Platform. Others claim compatibility but create extra layers of complexity.
A related discipline is contract control. If supplier obligations are vague, service problems become hard to manage later. Teams evaluating platforms for governance often benefit from looking at how contracts management software supports visibility and accountability before they commit.
Moving from selection to delivery
Once suppliers are shortlisted, procurement should move through structured comparison, negotiation and contract formation.
The next stages are where value is often won or lost:
- Supplier evaluation: Compare capability, support model, delivery approach, integration fit and governance, not just price.
- Contracting: Set expectations clearly around scope, roles, service levels, change control, data handling and exit.
- Implementation oversight: Make sure what was sold is what gets delivered.
- Performance management: Review whether the supplier is meeting business needs after go-live.
A signed contract doesn't end procurement. It starts the management phase that proves whether the selection was sound.
Why structure beats speed
Fast decisions can still be good decisions, but only when the process is disciplined. What fails in practice is false speed. That's when teams skip requirement clarity, avoid stakeholder alignment and accept vague contractual language in order to “keep momentum”.
For HR and IT leaders, procurement is the route that connects business need to operational reality. It makes sure the selected solution can be governed, supported and improved after implementation. Without that discipline, the business buys a tool. With it, the business secures an outcome.
Procurement vs Purchasing Understanding the Key Difference
The two terms get used as if they mean the same thing. They don't. In UK practice, procurement is the strategic function that covers upstream decisions and downstream controls, while purchasing is the transactional execution of those decisions, such as purchase orders, receiving and invoicing, as described in Indeed's explanation of procurement vs purchasing.
That difference is more than semantics. It changes who gets involved, what gets assessed, and how risk is controlled.
Procurement vs Purchasing at a Glance
| Aspect | Procurement | Purchasing |
|---|---|---|
| Focus | Strategic and end to end | Transactional and immediate |
| Purpose | Secure value, fit, control and supplier performance | Place the order and complete the transaction |
| Timing | Starts before supplier selection and continues after contract signature | Happens once the decision is already made |
| Key activities | Requirement definition, supplier assessment, negotiation, contract management, performance review | Raising POs, receiving goods or services, processing invoices |
| Decision lens | Total value and operational fit | Price, availability and order completion |
| Typical owner | Cross-functional leadership with procurement, HR, IT and finance input | Operational buyer or finance process owner |
| Risk handling | Built into selection, contracting and management | Usually limited to order and payment controls |
What this means in a Microsoft environment
If you're buying laptops, purchasing might be enough if standards and suppliers are already agreed. If you're selecting an HR platform on top of Dynamics 365 and Power Platform, purchasing alone is nowhere near enough.
Procurement asks whether the tool will work with your environment, users and governance model. Purchasing asks how to place the order once that decision has been made.
Purchasing completes a transaction. Procurement makes sure the transaction is worth completing.
The easiest way to spot the difference
If your team is discussing approval limits, invoice matching and who raises the PO, that's purchasing.
If your team is discussing requirement clarity, integration, contract risk, supplier capability, reporting needs and long-term support, that's procurement.
Both matter. But they shouldn't be confused. When leaders collapse them into one idea, strategic decisions get treated like admin tasks.
Types of Procurement Direct Indirect and Strategic
Not all spend behaves the same way. One reason procurement feels messy in many businesses is that leaders apply one set of controls to every category. That rarely works. Spend needs to be grouped properly first.
UK procurement commonly separates spend into direct procurement and indirect procurement. Direct procurement covers goods or services tied directly to the organisation's end product. Indirect procurement covers items that support operations but don't form part of the end product, such as labour or software, as set out in Procurify's overview of procurement categories.
Direct and indirect in plain terms
For a manufacturer, direct procurement might include components or materials used in the final product. For a services business, direct procurement can include specialist capability that directly supports client delivery.
Indirect procurement is where many HR and IT leaders live day to day. Software, recruitment support, consultancy, managed services, training and office technology all sit here. They don't become the product, but they shape how effectively the business runs.
That distinction matters because indirect spend often gets fragmented across departments. One team buys a tool for convenience. Another signs a similar service elsewhere. Before long, the business has overlapping contracts, inconsistent controls and scattered data.
Where strategic procurement fits
Strategic procurement isn't a third spend type in the same way. It's an approach.
It means treating important categories as part of wider business planning rather than isolated buying events. In practice, strategic procurement asks:
- Which categories have the biggest operational impact
- Which suppliers deserve active relationship management
- Which contracts need stronger governance
- Which systems should align with Microsoft architecture rather than sit beside it awkwardly
Good category management starts with one simple question. Is this purchase routine support, or will it shape how the business operates for years?
A practical example
An HR self-service platform is usually indirect procurement. But it becomes strategic procurement when the organisation depends on it for onboarding, absence, documents, manager workflows, compliance and reporting.
The same applies to IT tools. A basic software subscription may be routine. A platform that influences security, identity, integration and data structure is strategic, even if it sits in an indirect spend category.
That's why categorisation matters. It helps leaders decide how much scrutiny, stakeholder input and supplier management a purchase needs.
Procurement in Action HR and IT System Examples
Theory becomes useful when you apply it to real decisions. HR and IT procurement often sits in the same grey area. The spend is usually indirect, but the operational consequence is high. That means a light-touch buying process rarely gives a good result.
Example one, procuring HR services
Take a recruitment partner or specialist contractor. A purchasing mindset asks for rates and availability. A procurement mindset asks tougher questions.
How do they handle candidate quality, compliance checks, communication standards and service continuity? What happens if hiring volume changes? Who owns the relationship and how is performance reviewed?
In HR, that broader view avoids the familiar problem of paying for activity instead of outcomes.
Example two, procuring an HR platform in the Microsoft stack
In business, the definition of procurement becomes very practical. An HR director may compare systems by subscription fee and feature list. An IT director may focus on security and supportability. Procurement brings those views together and forces the business to decide what matters most.
For a Microsoft-centred organisation, sensible evaluation points include:
- Platform fit: Is the solution native to Microsoft technologies or dependent on fragile connectors and duplicated data?
- Process depth: Can it support recruitment, onboarding, employee administration, approvals and reporting without excessive custom work?
- Operational burden: Will internal teams spend their time maintaining workarounds?
- Future use: Can the business extend the solution with Power Platform and reporting tools as needs evolve?
A connected process also affects finance operations. If related workflows are still manual, spend visibility gets weaker. Teams reviewing HR and back-office efficiency often see the value of automating expense management within a joined-up Microsoft environment, rather than treating each workflow as a separate buying event.
Why product fit matters more than brochure fit
Hubdrive product material is useful here because it reflects a practical reality many buyers miss. A hire-to-retire solution built for Microsoft Dynamics 365 isn't just another HR app. Its value sits in how it uses the Microsoft ecosystem the organisation already owns.
That changes the procurement discussion. Instead of asking only “what does the licence cost?”, the better questions are “how well does it fit our tenant, our workflows, our reporting needs and our governance model?” and “will this reduce complexity or add another silo?”
In HR and IT procurement, the wrong architecture choice often costs more than the wrong price choice.
That's the sort of trade-off experienced procurement should surface before a contract is signed.
Optimising Procurement for Your Mid-Market Business
Mid-market businesses don't need procurement theatre. They need enough structure to make sound decisions without slowing the business down. The best approach is usually lightweight, consistent and tied directly to risk.
What tends to work
A practical model includes a few essentials:
- Clear ownership: HR owns business requirements. IT owns architecture and security. Finance owns commercial control. One person coordinates the decision.
- Early requirement discipline: Write down must-haves, not just nice demos.
- System thinking: Judge every significant purchase by how it fits your Microsoft estate.
- Post-award management: Treat supplier performance as an active responsibility, not an annual renewal event.
Data quality matters more here than is generally appreciated. If your supplier records, contract metadata, approval history or employee data are weak, procurement decisions become slower and less reliable. That's why digna's data quality insights are worth reading alongside any procurement improvement effort.
Where technology should help
Technology should reduce friction, not hide poor process. In practice, the strongest results come when procurement workflows, contracts, HR operations and reporting sit in an environment your teams already understand. For Microsoft-based organisations, that usually means thinking beyond a standalone app and considering how procurement choices support the wider implementation of ERP in a connected business platform.
Good procurement isn't about adding layers. It's about making sure major HR and IT decisions are commercially sensible, operationally workable and technically coherent.
We are DynamicsHub.co.uk. Experience HR transformation built around your business. Hubdrive's HR Management for Microsoft Dynamics 365 is the premier hire‑to‑retire solution, more powerful, more flexible, and more future‑ready than Microsoft Dynamics 365 HR.
If you're reviewing HR transformation, Microsoft-based people systems, or the wider procurement choices around your digital estate, talk to DynamicsHub. Phone 01522 508096 today, or send us a message.
