Procurement & Source-to-Pay
Procurement Transformation Best Practices: 10 Actions for Lasting Change
Practical actions for your people, processes, data and suppliers.
10 practices 12 minute read
Free practical guide
10 Steps to a Successful S2P Digital Transformation
Plan your Source-to-Pay transformation with our free, practical ten-step guide.
In this article
A supplier receives an invitation to a new procurement platform but cannot find the right training. A buyer follows the new process until an exception sends them back to email. The project dashboard shows completed tasks, while invoices still arrive through the old channels.
These are the practical details a procurement transformation needs to address. Processes, data, responsibilities and support must work together for employees and suppliers to adopt a new way of working.
This article sets out ten procurement transformation best practices for teams preparing, delivering or improving digital Source-to-Pay change. Each practice includes a concrete action or deliverable your team can use.
What does procurement transformation involve?
Procurement transformation is a coordinated change to how an organisation buys, works with suppliers and manages spend. It can involve its operating model, sourcing approach, processes, people, data and technology.
Digital Source-to-Pay (S2P) transformation is one part of that broader programme. It connects activities across sourcing, contracting, purchasing, invoicing and payment. Supplier enablement helps suppliers participate in the intended processes and use the relevant digital channels.
The practices below focus on delivering that operational change, with particular attention to supplier readiness and adoption. Several activities need to run in parallel. Your procurement transformation roadmap should establish their timing and dependencies.
1. Give sponsors specific decisions to own
Executive sponsorship becomes useful when the team knows which decisions the sponsor will make, what they can approve and when to escalate an unresolved issue.
Agree who owns process design, supplier data, policy changes and adoption. Include procurement, finance, IT and the business teams affected by the change. Confirm who can approve exceptions and resolve competing priorities.
The same discussion should establish the people and time required. If a process expert needs to attend workshops and validate designs, agree how their operational workload will be covered.
Put it into practice: create a decision and ownership register. For each important decision, record the accountable person, required contributors, deadline and escalation route. Use it during governance meetings to resolve open items.
2. Prepare supplier data before launching communications
Supplier records determine who receives communications, which suppliers are in scope and how activity can be tracked. Missing contact details or duplicate records can undermine an otherwise well-planned campaign.
Bring together supplier and spend data from the relevant systems. Agree the mandatory fields, resolve duplicates and identify outdated records. Validate which suppliers remain active using a period appropriate to your business, including seasonal purchasing where relevant.
Group suppliers by factors such as transaction volume, spend, business criticality and intended purchasing or invoicing channel. Different groups may need different onboarding and training approaches.
Put it into practice: build a controlled supplier tracker with a named owner, agreed scope and data-quality checks. Keep it current as suppliers join or leave the programme; a one-off cleanse will not maintain readiness throughout delivery.
FIELD GUIDE / 01
Five checks before supplier outreach
Reliable records help the right message reach the right supplier.
- 01
Complete
Fill gaps in supplier names, contacts and required fields.
- 02
Unique
Resolve duplicate records so each supplier is counted correctly.
- 03
Consistent
Agree formats for names, addresses and key identifiers.
- 04
Current
Validate active suppliers over a period that fits the business.
- 05
Accurate
Check details with the responsible source or owner.
3. Design the process around real transactions and exceptions
Document how a request should move through purchasing, approval, supplier fulfilment, invoicing and payment. Show where information changes systems and where one team hands work to another.
Then examine the exceptions. What happens when an invoice arrives without a purchase order? Who resolves incorrect supplier details? How are urgent purchases handled? Agree the appropriate routes with the relevant process and policy owners.
Use business subject-matter experts to review the design and test representative scenarios. Include the difficult cases that generate queries today.
Put it into practice: produce process maps and an exception register that name the responsible team, required information and resolution route. Use these documents to shape testing, training and support guidance.
4. Tell each audience what they need to do
A communication plan should connect a change to a specific action. Suppliers need to know what is changing, when it affects them, what they must do and where to find help. Internal teams need to understand how to guide suppliers and handle questions.
Build communications around meaningful milestones: validating contact details, registering on a platform, attending training, changing invoice channels and accessing launch support.
Adapt the message and timing for different supplier groups, languages and locations. Track failed deliveries and unanswered requests so that sending an email does not become a substitute for reaching its audience.
Put it into practice: maintain a communication schedule with the audience, action, send date, owner and follow-up approach for each message.
5. Train people on the tasks they will perform
Design training around the work each audience needs to complete. A supplier submitting an invoice needs different guidance from an employee raising a requisition or a support colleague investigating a failed transaction.
Use realistic examples and explain the process and policy alongside the system screens. Include common exceptions and show participants how to obtain help.
Provide suitable session times, language support and accessible recordings or written guides. Leave room for questions, then update the materials using the issues participants raise.
Put it into practice: use a training needs matrix covering audience, task, format and support requirements. Check whether participants can complete the relevant activities as well as recording attendance.
6. Give suppliers one reliable place to find guidance
A supplier information hub can bring project updates, registration instructions, invoicing guidance, training materials and support contacts together.
Organise it around the supplier’s questions: How do I register? How do I submit an invoice? What should I do if something goes wrong? Make the next action easy to find.
Assign someone to maintain the content and agree how updates will be reviewed. Check that intended users can access the material and that communications point to the current version. Distinguish the information hub from any transactional portal where suppliers submit data or invoices.
Put it into practice: publish a simple content ownership list with review dates, and check links and instructions before each major supplier communication.
FIELD GUIDE / 02
A supplier hub built around questions
Put guidance where suppliers can find their next action.
How do I register?
Registration steps, required details and onboarding guidance.
How do I submit an invoice?
The agreed channel, information required and exception routes.
How do I complete this task?
Short guides, recordings and answers to common questions.
What is changing, and when?
Current project notices, milestones and policy guidance.
Where can I get help?
Contact details, support hours and escalation routes.
Keep every answer current
Assign an owner and a review date. Link communications to the current guidance.
This is an information hub. The platform used to submit invoices or supplier data may be separate.
7. Align policies and guidance with the new process
Check whether purchasing policies, supplier instructions, contract templates and operational procedures reflect the proposed ways of working.
For example, if invoice submission is changing, the policy, supplier guidance, training and support process should describe the same requirements and agreed exceptions. Involve the relevant policy owners and legal colleagues in reviewing contractual changes.
Complete these decisions early enough for training and communications to use approved guidance. Explain how updated requirements affect existing suppliers as well as new ones.
Put it into practice: maintain a policy change log showing what changes, who approves it, its effective date and which documents, systems and audiences are affected.
8. Measure adoption and operational results
Choose measures that connect programme activity to the outcomes you want. Record the baseline, definition, data source, owner and review frequency for each measure.
For example:
| Measure | What it helps the team understand |
|---|---|
| Supplier readiness | Whether suppliers in scope have completed the necessary preparation |
| Use of the intended invoice channel | Whether the new process is being adopted |
| Invoice exceptions and their causes | Where process, data or training problems remain |
| Supplier onboarding time | Whether onboarding is becoming easier to complete |
| Purchase order compliance | Whether purchasing follows the agreed controls |
| Support response and resolution times | Whether users can obtain timely help |
Define the population behind each figure. A supplier registration measure answers a different question from the proportion of invoices submitted successfully through the intended channel.
Put it into practice: use a small dashboard to identify issues and assign actions. Agree reporting frequency around delivery needs, with more frequent operational reviews where launch conditions require them.
FIELD GUIDE / 03
Three views of transformation progress
Read readiness, adoption and results together to decide what needs attention.
Readiness
Are suppliers prepared?
- Validated contacts and scope
- Onboarding tasks completed
- Training and support needs
Adoption
Is the new process being used?
- Use of the intended invoice channel
- Purchase order compliance
- Successful task completion
Operational results
Is day-to-day work improving?
- Invoice exceptions and causes
- Supplier onboarding time
- Support resolution times
9. Prepare launch support and agree when it can end
Hypercare is a period of increased support after go-live. Plan its staffing, issue reporting, escalation routes and communication before launch.
Include people who understand both the new solution and the ongoing operation. Give suppliers and employees clear ways to raise problems, and make ownership visible when an issue crosses team boundaries.
Agree exit criteria based on readiness to operate sustainably. These could include acceptable service performance, critical issues resolved or under agreed control, updated guidance and an operational team ready to take ownership. Duration should reflect the programme’s scale and performance.
Put it into practice: create a hypercare plan with named support owners, issue priorities, review meetings, escalation routes and an agreed handover checklist.
FIELD GUIDE / 04
Make hypercare a managed handover
Plan the support cycle before go-live, then use issues and evidence to guide the transition.
- 1
Assign
Name the support team and give each issue an owner.
- 2
Listen
Make it easy for suppliers and employees to raise issues.
- 3
Triage
Prioritise issues and agree when to escalate.
- 4
Resolve
Fix the cause and update guidance or training.
- 5
Hand over
Confirm the operational team can take ownership.
10. Make continuous improvement someone’s responsibility
Decide who will maintain supplier guidance, manage system changes, review adoption and investigate recurring problems after the project team leaves.
Use support queries, process measures and stakeholder feedback to build an improvement backlog. Prioritise changes according to their likely operational benefit, risk, effort and dependencies.
Keep process documentation and training materials aligned with approved changes. Review whether each improvement has addressed the original problem, and share the findings with the teams affected.
Put it into practice: establish a recurring improvement review with accountable owners and a maintained action list. Include both business process and system support colleagues so that changes are considered together.
FIELD GUIDE / 05
Keep improvement moving after go-live
Treat improvement as an ongoing responsibility with a named owner and a maintained backlog.
- 1
Review
Use support queries, process measures and feedback to find recurring issues.
- 2
Prioritise
Assess the likely benefit, risk, effort and dependencies.
- 3
Improve
Make an approved change and update the process and training.
- 4
Verify
Check whether the original problem improved, then feed back the learning.
Look beyond cost alone. Review process reliability, user experience, supplier relationships and control as well as efficiency.
Denova in practice
What these practices look like in delivery
In a Denova procurement engagement involving Zip, a global business faced broken integrations, inconsistent approvals and manual workarounds.
An embedded procurement consultant documented workflows, improved required data capture, corrected approval routing and introduced a change log for production updates. The published case describes reduced manual work and stronger governance.
The example shows how process design, data quality and ongoing ownership can be addressed through concrete delivery tasks.
Put the article to work
A readiness check for your team
Before the next major delivery milestone, check whether you can answer these questions:
- Who can resolve the outstanding decisions, and do they have time allocated?
- Is the supplier scope agreed, with reliable contacts and clear ownership of data?
- Have users tested representative transactions and agreed exception routes?
- Do communications, policies and training describe the same process?
- Can suppliers and employees find current guidance and obtain support?
- Are adoption measures, launch support and ongoing responsibilities agreed?
Use gaps in these answers to assign specific actions. If decisions or delivery keep slipping, our article on why procurement transformation stalls examines the common barriers.
How Denova can help
Practical support for procurement transformation
Denova provides procurement and S2P support across business analysis, process mapping, data preparation, testing, supplier enablement and user adoption. Support can be delivered through embedded colleagues, managed activities or a defined project.
Talk to Denova about the work your team needs to deliver, the capacity available and the specialist support required.