eProcurement software built for UK procurement.

eProcurement and eSourcing: the boundary that matters

eSourcing is about the competition. It handles the notice, the document pack, supplier clarifications, sealed submission, evaluation, moderation, award and standstill. Its job finishes when the contract is signed. eProcurement is the broader estate of buying activity, and depending on who is speaking it can include requisitioning, catalogues, purchase orders, goods receipting, invoice matching, supplier master data and payment. Its job largely begins where eSourcing finishes.

The confusion is not academic. Authorities that buy eSourcing thinking they have bought eProcurement discover after go live that nobody can raise a purchase order in it. Authorities that buy eProcurement thinking they have covered sourcing discover that their tender process is still running on email. Both mistakes cost money and both are avoidable by writing down, before the market engagement, which of the two ends of the lifecycle you are actually trying to fix.

A useful test when reading vendor material: ask whether a feature deals with choosing a supplier or with transacting with a supplier you have already chosen. Evaluation, moderation and standstill are sourcing. Catalogues, requisitions and three way matching are procurement operations. Contract management and supplier assurance sit across the join and belong to whichever system your team will actually open every day.

Source to contract, purchase to pay, and source to pay

Three phrases dominate this market and they describe different scopes. Source to contract covers everything from identifying a need through market engagement, competition, evaluation, award and into contract management. Purchase to pay covers the transactional cycle: requisition, order, receipt, invoice, payment. Source to pay is the marketing term for both, and in practice very few organisations run genuinely unified source to pay without significant integration work.

For most public bodies the honest position is that finance owns purchase to pay because it lives inside or beside the finance ledger, and procurement owns source to contract because that is where compliance risk sits. Trying to force one owner on both usually produces a system that serves neither well. The productive question is not which system wins, but what data must flow between them and in which direction.

The essential flows are short. Awarded contracts and their terms should reach the ordering system so that buyers can only order against live agreements at agreed prices. Actual spend should flow back so that category managers can see what was really bought against each contract rather than what was forecast. Supplier records should have one master, not two. If those three flows work, the seam between systems is manageable.

• Source to contract: need, market engagement, competition, evaluation, award, contract management, performance.
• Purchase to pay: requisition, approval, purchase order, receipt, invoice match, payment.
• Shared spine: supplier master data, contract register, category taxonomy, spend analysis.

What the Procurement Act 2023 changed, and what it did not

The Procurement Act 2023 came into force on 24 February 2025. Its centre of gravity is transparency and process across the contract lifecycle: planning and pipeline notices, clearer procedures, assessment summaries, contract details and performance information. That weight falls mainly on the sourcing and contract management side of the estate rather than on requisitions and invoice matching, which are governed by financial regulations and internal controls rather than by procurement law.

The practical consequence is that Act driven pressure lands on your source to contract tooling first. If your sourcing and contract records are thin, the new notice and reporting obligations expose that quickly, because you cannot publish contract performance information you never captured. Purchase to pay systems rarely hold that information in a usable form: they know what was ordered and paid, not what was promised in a bid or agreed as a KPI.

The Act also replaced the Dynamic Purchasing System with Dynamic Markets and replaced utilities qualification systems with utilities dynamic markets. Again this is a source to contract concern. It changes how supplier pools are opened, assessed and used, and it has no equivalent on the transactional side.

How the full cycle works in practice

Start with the pipeline. A well run authority knows what is coming up for renewal in the next eighteen months, which means contract expiry data has to be reliable and visible. Most emergency direct awards trace back to an expiry nobody saw coming, so the least glamorous part of the estate, the contract register, prevents more compliance problems than any sourcing feature.

From the pipeline you plan the route to market: an open competition, a framework call off, a dynamic market competition or a below threshold quote exercise. The sourcing system runs whichever route applies and produces the award record. That record should then create the contract in the register automatically, with the key dates, values, KPIs and named owners already populated, rather than being retyped by someone weeks later.

Once live, the contract governs ordering. Requisitions reference it, prices come from it, and receipting confirms delivery. Performance data, whether from KPI returns, service reviews or complaints, attaches back to the contract record. At expiry the whole history, including what actually got spent and how the supplier performed, becomes the evidence base for the next specification. That loop is the entire point of joining the systems up.

Integration: the part that decides whether it works

Integration is where eProcurement programmes succeed or quietly fail. The temptation is to plan a comprehensive real time integration across every field. The reality in most authorities is that a small number of well defined flows, running reliably on a schedule everyone understands, delivers most of the value at a fraction of the risk. Start with supplier master, contract register and spend, and resist the urge to synchronise everything else.

Agree ownership explicitly. Which system is the master for a supplier record, and what happens when a supplier changes bank details or legal entity. Which system is the master for a contract value when a variation is agreed. Who is accountable for reconciling the two when they disagree. These are governance questions with technical consequences, not the other way round, and answering them late is expensive.

Be realistic about legacy finance systems. Many councils, NHS bodies and housing associations run finance platforms that were not designed for rich contract data. Where an interface is limited, it is usually better to accept a simpler flow and keep the richer record in the procurement system than to distort your procurement data to fit a ledger field.

Common failure modes and how to avoid them

The first failure is buying scope you will not use. A full catalogue and requisition estate is a serious operational commitment involving category managers, content maintenance and end user training. If your organisation buys mostly services under a modest number of contracts, catalogue functionality will sit idle while the real problem, contract oversight, goes unsolved.

The second is off contract spend, sometimes called maverick buying. It is rarely defiance and usually friction: the compliant route is slower or harder than picking up the phone. The remedy is to make the compliant route the easiest one, with short approval chains, clear contract visibility and a below threshold workflow that takes minutes rather than half a day.

The third is data quality. Spend analysis is only as good as the coding underneath it, and coding decays when nobody owns it. Appoint an owner for the category taxonomy and review it annually. The fourth is treating go live as the finish line. Adoption is a twelve month exercise involving training, reporting on usage, and closing off the informal routes people used before.

• Scope creep in the sales process: features demonstrated, budgeted, then never configured.
• No named owner for supplier master data, so duplicate records multiply.
• Contract register maintained by goodwill rather than process, so expiry dates drift.
• Reporting built for the board but not for the category managers who could act on it.

Sector differences worth planning for

Councils tend to have the widest category spread and the most devolved buying, so the priority is visibility across directorates and a low friction compliant route for small purchases. NHS organisations sit inside a layered environment of national frameworks and collaborative arrangements, with clinical stakeholders who must be involved in evaluation, so the sourcing and evaluation side carries more weight than the requisition side, which is often already served by established systems.

Housing associations increasingly run procurement to public sector standards, driven by regulatory expectation, building safety obligations and lender scrutiny, and they typically have concentrated spend in repairs, maintenance and development. Contract management and supplier assurance matter more there than catalogue depth. Education buyers, particularly academy trusts and colleges, are resource constrained and framework reliant, so a fast compliant call off with clean evidence beats elaborate functionality.

Utilities in water, energy and transport operate under a different rule set for dynamic markets. They may charge suppliers membership and award fees and may run member only tenders, which general contracting authorities may not do. If your organisation spans both, the system needs to hold both rule sets rather than relying on individual memory.

Buying eProcurement software: routes, evidence and budgets

Most public buyers reach software through a framework rather than a bespoke competition, because the framework has already done the heavy lifting on terms. eSourcing Data software is available to public buyers through RM1557.15 G-Cloud 15, with 28 software services listed on the Digital Marketplace plus cloud support services, and purchases are made as call off contracts. A framework listing is a route to market, not approval or endorsement, so the assessment work is still yours to do.

Budget for more than the licence. Implementation, configuration, data migration, integration and training are real costs, and support arrangements vary widely in what is included. It is worth separating one off costs from recurring costs in the business case so that finance colleagues see the full picture rather than a single headline figure that later grows.

Ask for evidence rather than assurance. Request a demonstration configured against one of your own recent procurements, including a difficult one. Ask to see the audit output an internal auditor would receive. Ask what happens to your data if you leave, in what format and over what period. Those three answers tell you more about a vendor than any feature matrix.

How eSourcing Data fits

eSourcing Data is a source to contract platform. It covers sourcing and tendering, supplier onboarding and assurance, evaluation and moderation, contract management, governance and audit, analytics and reporting, and below threshold workflows. It is deliberately positioned on the sourcing and contract side of the estate, and designed to hand clean, structured contract and supplier data to whatever purchase to pay or finance system an authority already runs.

That positioning reflects where the compliance risk and the Procurement Act 2023 obligations actually sit. Authorities rarely need to replace a working finance ledger. They frequently need to replace the spreadsheets, mailboxes and shared drives that currently carry their tender evidence, contract register and supplier assurance data.

Data is held with UK data residency and the platform is GDPR compliant, which addresses the recurring information governance questions from councils, NHS bodies and housing associations. Where an authority also wants help running the work rather than only the tooling, outsourced procurement and consulting support are available alongside the software, which keeps the process and the evidence in one place.