Source-to-pay was built for a procurement world that needed standardization above all else. It gave organizations a structured way to move from sourcing to contracting, purchasing, invoicing, and payment, and it helped create consistency where there had been fragmentation. But procurement’s priorities have changed. Today, teams are expected to do more than run controlled workflows. They’re expected to surface insight, manage risk earlier, and connect procurement data to financial outcomes in real time. McKinsey’s recent work on AI-driven procurement clearly reflects that shift, describing a function that’s becoming more strategic, more agile, and more intelligence-led.
That’s why the question now is not whether S2P was useful. It was. The real question is what replaces it. The answer is not another suite built around the same phase-based logic. It’s a different architecture, one built around connected data, structured intake, and live operational intelligence.
By Lihi Lutan, Co-Founder and CEO, Opstream
Co-Founder and CEO of Opstream, previously COO of StokeTalent (acq. Fiverr) and VP Operations at Taboola where she helped scale the company from $8M to $1B in revenue.
Key Takeaways
● S2P organized procurement technology around process phases, which helped standardize work but also fragmented the data procurement now needs.
● The main fracture points are structural: system handoffs, post-hoc compliance, and analytics that lag behind live operations.
● What replaces S2P is a shared financial data model that connects intake, approvals, contracts, POs, invoices, and payments.
● The next defining layer in ProcureTech isn’t just automation, but agentic intelligence built on live operational data.
● The organizations best positioned for what comes next are the ones with the most connected data, not just the most tools.
What Was S2P Built to Solve?
To understand what comes next, it helps to remember what S2P was built for. In the early 2000s, many organizations had decentralized buying behavior, weak spend visibility, inconsistent approval practices, and limited supplier data. S2P addressed that by breaking procurement into defined stages, each supported by its own workflow and system logic. That created structure, improved auditability, and gave procurement a stronger operational backbone. The critique isn’t that S2P got the original problem wrong. It’s that the original problem is no longer the whole story. Gartner’s own market definition reflects how tightly the model was scoped: “an integrated set of solutions to source, contract, request, procure, receive and pay for goods and services across an enterprise.”1
That’s also why the conversation has shifted from phase coverage to data continuity. If you want procurement to act strategically, it’s not enough to have a sourcing tool, a contract tool, a purchasing tool, and an AP tool. You need the underlying records to stay connected across the lifecycle. That’s much closer to the model behind Opstream’s Procurement platform, where requests, vendors, contracts, budgets, and renewals live in a single, connected environment rather than being stitched together later.
Where Does S2P Break Down?
The weaknesses in S2P have become more obvious as procurement has taken on more responsibility for cash flow, compliance, supplier risk, and business decision support. Even after two decades, adoption remains fragmented. According to a 2025 Gartner survey, the most commonly deployed S2P modules are spend analytics (42% fully deployed), P2P (37%), and sourcing (33%).2
The Data Handoff Problem
S2P creates handoffs between sourcing, contracting, purchasing, and AP systems. At each handoff, data must be transferred, translated, or re-entered. That isn’t just inefficient. It weakens the link between records that should stay permanently connected, such as the original request, the approved budget, the contract terms, the PO, and the invoice. KPMG’s 2025 data research highlights the same broader problem: many organizations still operate in functional silos, and poor integration into decision-making remains one of the biggest reasons data fails to create value.
The Compliance Enforcement Problem
Traditional S2P systems tend to treat compliance as something you enforce through workflow sequence and audit later. That works for straightforward scenarios, but it breaks down when users find workarounds or when the workflow cannot anticipate the real complexity of organizational spend. In practice, compliance becomes reactive. It’s checked after the request has already moved rather than being designed into the intake point itself.
The Intelligence Gap
S2P platforms generate a lot of transaction data, but many still rely on snapshots, exports, and retrospective reporting to make sense of it. That means procurement often gets descriptive reporting instead of live decision support.
Deloitte’s 2025 Global CPO Survey describes procurement as being at an inflection point driven by digital transformation, GenAI, and agentic AI, and finds that more digitally enabled procurement organizations are much more likely to outperform on cost savings, supplier performance, and innovation support.
What Architecture Replaces S2P?
What replaces S2P is not just a better workflow stack. It’s a connected data architecture.
A Shared Financial Data Model
The foundational shift is from separate phase-specific records to a shared financial data model. In that model, the initial request, approval, budget context, contract, PO, invoice, and payment are not isolated records joined later. They are connected parts of the same operational history. That is the foundation of a modern procure-to-pay architecture, and it gives procurement and finance a clearer, more trustworthy view of what is happening across the lifecycle.
Structured Intake as the Control Point
In the replacement model, intake becomes the real control point. That’s where policy, budget logic, supplier context, and approval design are applied before spend becomes a downstream clean-up problem. It shifts compliance from post-hoc enforcement to pre-commitment design. If you want a practical view of why that matters, Procurement Tech Stack Assembly: Tips and Tricks is a useful companion read.
Agentic Intelligence From Live Data
The next layer is intelligence. Not just dashboards and exported reports, but systems that surface anomalies, predict likely outcomes, and recommend action while the workflow is still live. McKinsey’s 2026 work on agentic AI in procurement makes this point directly, arguing that procurement is moving beyond transaction processing toward a function that can shape growth, resilience, and decision quality through agentic systems.
What Does This Shift Mean for Procurement Teams?
The shift from S2P to connected procurement data changes what procurement teams can do.
From Compliance Monitoring to Compliance by Design
Teams spend less time checking whether policy was followed after the fact and more time building intake and approval structures that make non-compliant behavior harder to initiate.
From Reporting to Real-Time Visibility
When procurement and finance work from live operational data instead of periodic extracts, they can make better decisions on commitments, accruals, supplier exposure, and cash flow.
From Transaction Processing to Strategic Analysis
As more of the repetitive process work becomes connected and automated, procurement professionals can shift time toward supplier strategy, category planning, and risk analysis. That’s the real upside McKinsey points to when it describes AI-driven procurement as more efficient and increasingly strategic.
What Are Forward-Looking Organizations Doing Now?
The organizations moving fastest are not necessarily the ones ripping out every legacy system. They are the ones restructuring the data layer underneath procurement. In practice, that means consolidating fragmented tools where possible, investing in structured intake, linking contract and PO data to invoice workflows, and using analytics that operate on live process data rather than exported records.
CIPS’ guidance on procure-to-pay also reinforces this direction, pointing to integrated purchasing and accounts processes as a source of better efficiency and visibility.
Why Does This Matter More Than Another S2P Refresh?
Because the next procurement bottleneck isn’t a lack of workflow, it’s a lack of connected context. If the request, budget, supplier, contract, PO, invoice, and payment all live in different systems with weak continuity, procurement will keep spending time reconstructing reality after the fact. A connected architecture changes that. It makes procurement events visible, auditable, and analytically useful from the moment they begin.
That’s also the direction we’ve taken at Opstream. The goal isn’t another isolated layer of workflow automation. It’s to connect intake, vendors, contracts, budgets, approvals, and downstream execution into a single live operating model so that you can act earlier and with better data.
See how Opstream connects procurement data and workflows across the full procure-to-pay lifecycle.
FAQs
What does S2P stand for in procurement?
S2P stands for source-to-pay. It covers the procurement lifecycle from sourcing and contracting through purchasing, invoicing, and payment.
Why is the traditional S2P model considered outdated?
Because it was built around a phase-based workflow and system handoffs rather than a shared live data model, this makes visibility, intelligence, and control harder as procurement becomes more complex.
What is a shared financial data model in procurement?
It’s a connected structure in which requests, approvals, budgets, contracts, POs, invoices, and payments remain linked within the same transaction history, rather than being split across separate systems.
What is agentic analytics in procurement technology?
It’s the use of live operational data to surface patterns, identify anomalies, predict likely outcomes, and recommend actions, rather than simply reporting what happened after the fact.
How is procure-to-pay different from source-to-pay?
Procure-to-pay focuses on the operational flow from request through payment. Source-to-pay is broader and also includes upstream sourcing and contracting activities.
1 Source: Gartner, “Magic Quadrant for Source-to-Pay Suites,” Micky Keck, Kaitlynn Sommers, Lynne Phelan, Magnus Bergfors, Alex Brady, 21 January 2026.
2 Source: Gartner, “Critical Capabilities for Source-to-Pay Suites,” Magnus Bergfors, Micky Keck, Lynne Phelan, Kaitlynn Sommers, Alex Brady, 26 January 2026. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved.
About the Author
Lihi Lutan
Co-Founder and CEO, Opstream
Lihi Lutan is the Co-Founder and CEO of Opstream, changing the way companies buy. Throughout her career, Lihi built and scaled business operations at startups and large corporations. Early in her career, Lihi was with Cyota (acq. RSA Security) as a team leader and project manager before moving to Thomson Reuters and Fundtech to manage global projects. Later, Lihi joined Taboola (NSDQ: TBLA) as employee 15, as VP Professional Services and Operations, leading the department as the company scaled from $8M to $1B in revenue. Transitioning from Taboola to StokeTalent (acq. Fiverr), Lihi served as the company’s COO. Lihi holds an LLB of Law and BSc of Computer Science from Tel Aviv University.
