In S2P programs, technology is rarely the hardest part. The hard part is getting thousands of people to change how they buy, approve, receive, invoice, and pay—often while they are busy and under pressure. Adoption does not happen because you launched a new tool. Adoption happens when the new way of working is simpler than the old way, leaders reinforce it, and the organization fixes friction quickly.
This chapter covers the practical change mechanics that protect value: segmenting stakeholders and their impacts, reducing maverick spend with a balanced set of levers, redesigning procurement roles so the new operating model can run, enabling suppliers so invoices flow digitally, and building training and reinforcement so the change sticks beyond go-live.
22.1 Stakeholder Segmentation and Impact Assessment
Change management starts with precision. “The business” is not one audience, and generic communications create generic confusion. Segment stakeholders by their role in the transaction chain, because that is what determines behavior, pain points, and the type of reinforcement required.
Most enterprises can cover the landscape with a small set of stakeholder groups. Requisitioners and frequent buyers: people who initiate purchases and care about speed and clarity. Approvers: budget owners who need context and confidence that approvals align to policy. Receivers: teams who confirm goods and services and often see receiving as extra work. Procurement: category teams and operations teams who will run new queues for intake, catalogs, supplier onboarding coordination, and exception reduction. Accounts payable: who shift from manual processing to exception management and supplier enablement. Suppliers: who must submit invoices through the right channel and follow invoice standards.
Do impact assessment using real scenarios, not surveys. Walk through what each group does today, then replay those scenarios in the future state. The goal is to identify where work moves, where controls tighten, and where users might bypass. In S2P, most adoption risk is predictable: unclear services buying paths, slow approvals, missing catalog content, unclear responsibility for receipts, and supplier invoice behavior that does not match your match policy.
Impact assessment template:
- Role and population size: how many people, where they sit, and turnover risk.
- Top scenarios: the 3–5 transactions that represent most volume and urgency.
- What changes: steps added/removed, new data fields, and new approvals or controls.
- Friction risks: likely bypass behaviors and likely bottlenecks.
- Enablement needs: job aids, templates, training format, and support path.
- Success measures: adoption metrics that prove correct channel use.
Turn impacts into a “day one promise” that is short and credible. Promises are outcome commitments, such as target cycle times for catalog buys, clear expectations for receiving, or supplier visibility into invoice status. These promises focus design decisions and give business leaders something tangible to reinforce.
Build a change network early. A small number of engaged super users per business unit can validate scenarios, pressure-test communications, and provide feedback from the floor. The network is most effective when it is structured: named members, a weekly touchpoint during testing and hypercare, and a clear “you own feedback” charter. The network also becomes your readiness sensor. If super users cannot execute common scenarios without help, broad go-live adoption will not be better.
Design communications as a system, not as a blast. Use a predictable cadence and in-workflow messages for “at the moment” guidance. Point every message to one source of truth for buying channel rules, service levels, and where to get help. Pair communications with a feedback loop from ticket themes and super users.
Finally, identify sponsors who can actually influence behavior: business leaders who own budgets and can insist on compliant channels. Equip them with simple messages, the compliance metrics they will review, and an escalation path for legitimate friction. Local sponsorship turns change from “a procurement project” into a business operating standard.
22.2 Maverick Spend Reduction Strategy
Maverick spend is a rational response to friction. People bypass when the compliant path is unclear, slow, or unreliable. The winning strategy combines experience improvements, transparency, and targeted enforcement that tightens as readiness increases.
Start with an honest baseline: non-PO invoices, p-card categories, off-contract spend where preferred suppliers exist, and direct supplier orders. Then identify the top drivers. In most organizations, the drivers are consistent: missing catalog coverage, unclear services buying, slow approvals, slow supplier onboarding, and the belief that “procurement slows me down.” Fixing these drivers is a prerequisite to sustained enforcement.
Use a phased approach. Phase 1: make compliant buying easier—expand catalogs in high-frequency categories, improve guided buying search and routing, publish simple service levels, and stand up responsive support. Phase 2: add steering and soft controls—preferred supplier ranking, justification when selecting nonpreferred options, and targeted coaching for repeat bypass patterns. Phase 3: tighten hard controls where prerequisites are met—block invoices without POs for addressable categories, restrict new supplier requests, and enforce contract references for high-risk spend to protect compliance.
Deploy hard controls like a release, not a memo. Define readiness criteria (catalog coverage, enabled suppliers, receiving discipline), announce the enforcement date with affected categories, and provide a clear exception path with reason codes and expiry. When hard stops arrive before readiness, users create shadow routes that are harder to unwind than the original maverick behavior.
Make maverick spend visible to the leaders who own it. A monthly view by business unit should include Channel compliance: percent of addressable spend through approved channels, Non-PO invoice rate: value and volume with top categories, and Off-contract leakage: spend with nonpreferred suppliers where contracts exist. Visibility works when it is used in routine leadership conversations and when repeated patterns trigger action.
Define an escalation ladder that the business experiences as fair. Start with education and redirection, then require leader acknowledgment for repeat patterns, then tighten controls for the specific category or business unit driving the leakage. Avoid broad punishment; it creates political resistance and encourages workarounds. Targeted enforcement is both more effective and easier to sustain.
Maverick spend playbook:
- Fix friction first: address the top drivers of bypass within the first 60–90 days.
- Steer before you block: preferred defaults and soft stops build habits quickly.
- Block selectively: “no PO, no pay” only where channels and suppliers are ready.
- Make exceptions rare: time-bound, reason-coded, approved, and reported.
- Close the loop: monthly root-cause review of bypass patterns with owners and actions.
Done well, maverick spend reduction becomes self-reinforcing. As more spend flows through standard channels, catalogs improve, invoice match rates rise, approvals become predictable, and the perceived cost of compliance drops. Over time you can also shrink the “allowed” non-PO universe and reduce card leakage by moving repeat card categories into catalogs and contracts.
22.3 Procurement Role Redesign and Capability Development
S2P changes procurement’s work. It reduces low-value coordination and increases the need for disciplined operations: intake triage, catalog management, supplier enablement, and systematic exception reduction. If roles are not redesigned, category managers become transaction resolvers and adoption suffers.
Start with a deliberate separation between strategic and operational work. Category management: owns category strategies, sourcing pipelines, negotiations, and stakeholder demand alignment. Procurement operations: owns the front door (intake), channel configuration, catalog content governance, supplier onboarding coordination with finance and risk, and recurring P2P exception patterns. This separation protects senior capacity for value creation and gives the business a reliable operational engine.
Then assign ownership for the new queues the platform creates: intake requests, contract renewals, supplier registration tasks, invoice exceptions, and catalog changes. Each queue needs a named owner, SLAs, and escalation. Without that, work sits “somewhere in the system,” users lose trust, and bypass returns.
Capability development should focus on what changed, not on navigation clicks. Common gaps include writing clean intake requirements, managing catalogs and forms that drive compliance, using spend and exception data to remove root causes, running supplier enablement waves, and partnering with finance on realized savings and working capital outcomes.
Future-state capability priorities:
- Intake and triage: routing logic, service levels, and stakeholder communication.
- Catalog and channel management: content standards, supplier coordination, and search tuning.
- Supplier enablement: onboarding waves, invoice standards, and supplier support.
- P2P operations: exception taxonomy, root-cause reduction, and controls discipline.
- Value governance: compliance dashboards and finance-aligned savings evidence.
Create a small center of excellence to protect the global template and speed continuous improvement. The CoE owns standards (taxonomy, approval patterns, catalog rules), publishes “how we work” guidance, and runs the enhancement backlog with clear prioritization. It should also own adoption analytics so improvement decisions are data-driven rather than based on the loudest complaint. It should also publish release notes after each enhancement.
Finally, align incentives to the future model. Balance measures such as realized savings, channel compliance, cycle time, exception reduction, and supplier enablement progress. This is one of the fastest ways to shift procurement culture from heroic firefighting to repeatable operating discipline.
22.4 Supplier Adoption and Enablement Strategy
Supplier adoption is a business adoption issue, not a technical task. If suppliers do not submit invoices through the intended channel, automation and payment-term outcomes collapse. A supplier enablement strategy must be planned, segmented, and resourced like a customer onboarding program.
Segment suppliers by invoice volume and criticality. High-volume suppliers deliver the biggest automation gains; critical suppliers require white-glove onboarding because disruption is costly. Build enablement waves that prioritize those groups first, and be explicit about what “enabled” means: portal access established, required data completed, invoices submitted successfully with correct references, and status visibility confirmed.
Enablement depends on clear supplier communications. Communicate the benefits (visibility, fewer disputes), the required invoice standards (PO references, line detail, credit memo rules), and the transition timeline. Put invoice instructions on purchase orders, because that is when suppliers build invoices. Standardize rejection reasons so suppliers can correct quickly without email threads.
Prove transactions before you scale. For top suppliers, run a short prove-out: receive a PO, submit an invoice, resolve one exception, and confirm payment status visibility. This is the fastest way to uncover missing references, unit-of-measure mismatches, or invoice layout issues before they create thousands of blocked invoices.
Plan for both support and enforcement. Provide office hours and tiered help for onboarding questions, then enforce the channel after a defined transition window, with a controlled exception path for true constraints. Consistency drives adoption faster than repeated one-off negotiations.
Measure supplier adoption with the same rigor as internal adoption. Track the percent of invoice volume submitted through the preferred channel, first-pass match rate by supplier, dispute cycle time, and top rejection reasons. Share these metrics with high-volume suppliers and treat chronic invoice quality issues as corrective-action items. If you plan to extend payment terms, make digital invoicing part of the give-get.
Supplier enablement checklist:
- Wave plan: supplier list, volumes, owners, and target dates.
- Readiness definition: what constitutes “enabled” and how it is measured.
- Communications: instructions, timelines, and escalation contacts.
- Support: office hours, triage, and resolution targets.
- Policy enforcement: transition window and post-window rules for invoice submission.
22.5 Training and Reinforcement Model
Training is necessary, but it is not sufficient. In S2P, most failures that look like “users didn’t follow the process” are actually unclear expectations, missing job aids, and weak reinforcement. A strong enablement model treats training as one element in a broader reinforcement system.
Build role-based learning journeys and teach the few workflows that drive most volume: catalog purchase, non-catalog request, approvals, receiving or service confirmation, and exception resolution. Teach through scenarios, not menu navigation. Keep learning assets short, searchable, and easy to reuse for new hires.
Use a blended approach. Micro-learning: short in-tool guidance for “next step” tasks. Live sessions: for approvers, receivers, procurement, and AP where policy and exceptions matter. Job aids: one-page guides for each role and the top exception scenarios. Super users: a trained network in each business unit that provides local support and feedback.
Reinforcement is where adoption is won. Establish a 90-day plan after go-live. In the first two weeks, focus on rapid response: office hours, daily triage, and clear communications. In weeks three to six, shift to pattern fixes: improve catalog content, adjust approval routing, and reduce top exception drivers. In weeks seven to twelve, tighten controls where readiness criteria are met and publish compliance scorecards by business unit.
Build manager reinforcement into the model. Approvers influence cycle time and user perception more than any other role. Provide managers with simple views of approval aging, receipt timeliness, and exception volumes in their organizations, and treat persistent delays as a performance issue, not as a system issue. In parallel, keep the message consistent: fast approvals and timely receiving protect supply continuity and prevent payment disruption.
Make adoption measurable and visible. Track Channel usage: percent of addressable spend through approved channels, Cycle time: request-to-PO and invoice cycle time by stage, and Quality: first-pass match rate and receipt timeliness. Use these metrics to drive fixes, recognize strong performers, and intervene when approvals or receiving discipline are consistently weak.
90-day reinforcement plan template:
- Weeks 0–2: hypercare, daily issue triage, office hours, and rapid communications.
- Weeks 3–6: root-cause fixes, targeted retraining, supplier enablement acceleration.
- Weeks 7–12: tighten enforcement where ready, publish compliance dashboards, transition to steady-state support.
When change management is executed with this level of operational discipline, S2P stops being “a new system” and becomes “the way we buy.” That is when savings become realized, working capital improves, and controls operate without constant escalation.