Source-to-Pay platform for enterprises and large mid-market companies
From supplier catalog to requisition, approval and handover to your ERP: Ovenca covers the operational core of the source-to-pay process and connects sourcing, contract data, invoice verification and payment through open interfaces.
ERP-independent, on-premise or in a private cloud, in use worldwide at an MDAX-listed group that has worked with Onveda since 2014. This page walks through the S2P process phase by phase, separates it from procure-to-pay and source-to-contract, and lists the criteria that matter when you select software.
- ERP-independent
- On-premise or private cloud
- OCI, cXML, API
- With LANXESS since 2014
What is source-to-pay (S2P)?
Source-to-pay, or S2P, is the end-to-end procurement process from finding a supplier to paying the invoice. It joins strategic procurement (demand bundling, tendering, supplier selection, contract) with operational procurement (requisition, approval, purchase order, goods receipt) and accounts payable (invoice verification, payment).
The term describes a process first, not a piece of software. A source-to-pay platform is the system landscape that links these steps without re-keying: contract terms appear in the catalog, the purchase order refers to the catalog item, and the invoice is checked against order and goods receipt. Whether a single suite does this or several integrated systems around the ERP is an architecture decision, not part of the definition.
Source-to-settle is generally used as a synonym.
S2P at a glance
- Starts with
- A need for which there is no supplier or no valid terms yet
- Ends with
- The supplier invoice, paid and posted
- Sub-processes
- Source-to-contract (S2C) and procure-to-pay (P2P)
- Who is involved
- Strategic and operational procurement, requesters in the business units, suppliers, accounts payable, IT
- Goal
- Orders are placed on negotiated terms, every step is traceable, and data is entered only once
The source-to-pay process in eight phases
What happens in each phase, which system usually owns it, and what part Ovenca plays.
Sourcing and tendering
Procurement bundles demand, analyses spend by category, requests offers (RFI, RFQ, RFP) and selects suppliers. The outcome is negotiated prices and terms.
Ovenca's role: Tenders and auctions are not part of Ovenca. They run in the ERP's sourcing module or in a specialist tool. Ovenca contributes reporting on orders, search behaviour and catalog usage.
Contract and framework agreement
The negotiation result is recorded as a framework agreement or contract: prices, volumes, terms, delivery and payment conditions. Without a link to the ordering process, the contract stays a document nobody uses day to day.
Ovenca's role: The contract record stays in the ERP or in contract management. Ovenca takes contracts and material numbers from the ERP and shows contract items directly in product search, so requesters order on the negotiated terms.
Supplier management
New suppliers are qualified, master data and evidence are maintained, risks are assessed. Under the German Supply Chain Due Diligence Act, documenting these steps is mandatory for many companies.
Ovenca's role: In the vendor portal, suppliers go through structured onboarding with questionnaires, self-disclosures and certificates. They maintain their own catalogs; procurement reviews and approves.
Catalog and requisition
Requesters search approved catalogs, add items to a cart and turn it into a purchase requisition. Anything that is not in a catalog is entered as a free-text request.
Ovenca's role: This is where Ovenca is strongest: one search across imported catalogs (CSV, BMEcat) and punchout shops (OCI, cXML), SmartForms for configurable requests, and a single cart for catalog, punchout and free-text items.
Approval and purchase order
The requisition is routed to the responsible approvers by value, cost center or category. Once approved, it becomes the binding purchase order to the supplier.
Ovenca's role: Multi-level approvals and budget limits per cost center, user or category are configured in the platform. Ovenca hands the approved requisition or order to the ERP via API.
Goods receipt and service entry
Delivery of the goods or completion of the service is confirmed. The goods receipt is what later allows the invoice to be verified without queries.
Ovenca's role: The goods receipt is posted in the ERP. Ovenca can reconcile it with the ERP; how far this goes depends on the ERP connection in place.
Invoice verification
The supplier invoice is matched against purchase order and goods receipt (three-way match). If quantity and price agree, it can be released for payment without manual checking.
Ovenca's role: Invoice receipt and verification stay in the ERP or in the finance team's invoice processing. Ovenca provides the precondition: purchase orders with the correct price, supplier, material number and cost center.
Payment
Accounts payable pays according to the agreed payment terms and posts the transaction. That closes the process; the data feeds spend analysis and the next sourcing round.
Ovenca's role: Payment runs belong to the ERP or the finance systems. Ovenca does not trigger payments.
Source-to-pay vs. procure-to-pay vs. source-to-contract
The three terms describe differently sized sections of the same procurement process. Source-to-pay is the umbrella: S2C plus P2P.
| Criterion | Source-to-contract (S2C) | Procure-to-pay (P2P) | Source-to-pay (S2P) |
|---|---|---|---|
| Scope | Strategic procurement | Operational procurement and invoice handling | Both, connected end to end |
| Starts with | Demand analysis and supplier search | A requester's purchase requisition | Demand analysis and supplier search |
| Ends with | A signed contract | A paid invoice | A paid invoice |
| Typical steps | Spend analysis, tender, negotiation, supplier selection, contract | Catalog, requisition, approval, purchase order, goods receipt, invoice verification, payment | All S2C and P2P steps, plus supplier management |
| Main users | Strategic buyers, category managers | Requesters, operational buyers, accounts payable | Procurement, business units, finance and suppliers |
| Transactions | Few, but complex | Many, largely alike | Both |
| Typical benefit | Better terms, vetted suppliers | Shorter cycle times, less maverick buying, fewer invoice queries | Negotiated terms actually reach the purchase order |
Related terms in brief
- Source-to-settle
- Generally used as a synonym for source-to-pay. The term stresses that the process only ends once the liability has been posted and cleared.
- Purchase-to-pay
- Usually means the same as procure-to-pay and shares the abbreviation P2P: the process from demand to payment.
- Requisition-to-pay (R2P)
- Equivalent to procure-to-pay, but puts the purchase requisition forward as the starting point.
Suite, best-of-breed or ERP-native: three routes to an S2P platform
Source-to-pay software providers take different approaches. Which one fits depends on your ERP strategy, the number of legal entities and the maturity of your procurement organisation.
| Criterion | Integrated S2P suite | Best-of-breed around the ERP | ERP-native |
|---|---|---|---|
| Approach | One provider delivers sourcing, contract management, ordering and invoice processing, usually as a cloud service. | The ERP remains the system of record for purchase order, goods receipt, invoice and payment. Specialist solutions take over the phases where the ERP has gaps, such as catalog, supplier portal or tendering. | The whole process is run with the ERP's own procurement functions, without an additional platform. |
| Advantages |
|
|
|
| Drawbacks |
|
|
|
What Ovenca covers and what deliberately stays in the ERP
Ovenca is not a full suite; it is a component for the second route. The platform takes on the phases where many users, many suppliers and many catalogs meet, and hands clean data to the system of record.
Catalog and requisition
One search across all approved catalogs and punchout shops that leads straight to the purchase requisition.
- Import and validation of CSV and BMEcat catalogs
- Punchout via OCI and cXML
- Contract items and ERP material numbers in search
- Free-text items and SmartForms for needs outside the catalog
Vendor portal
Suppliers maintain catalogs and evidence themselves; procurement reviews and approves.
- Catalog maintenance in the browser or via CSV and Excel import
- Data validation on intake
- Approval process with change log
- Onboarding with questionnaires, self-disclosures and certificates
Approvals and governance
Roles, permissions, budgets and approval paths are controlled centrally, including for decentralised organisations with several legal entities.
- Multi-level approvals by value, cost center or category
- Budget limits per cost center, user or category
- Catalog and product visibility per organisational unit
- Audit trail and reporting on search, orders and usage
ERP integration
Ovenca sits in front of the ERP and hands approved transactions to the place where they are posted.
- SAP ERP and S/4HANA via OCI, cXML or API
- Microsoft Dynamics, Oracle, Infor and proprietary ERP systems
- Transfer of purchase requisitions and purchase orders
- Goods receipt reconciliation with the ERP
Not part of Ovenca
Tenders and auctions, clause-level contract management, invoice receipt and payment processing. These steps run in the ERP or in specialist systems. If you want every phase from a single provider, an integrated suite will serve you better. We say so openly in the first conversation.
In use worldwide at LANXESS
“By integrating SAP contracts and material numbers into product search, we were able to increase the automation of our purchase-to-pay processes as intended. On the clearly structured administration level we control the release and availability of content, manage user permissions and obtain the transparency we want through meaningful reports.”
LANXESS AG has worked with Onveda since 2014 and uses Ovenca worldwide as its eProcurement platform. Contracts and material numbers from SAP appear directly in product search.
Selecting S2P software: a checklist for procurement, IT and finance
Feature lists look much the same from most providers. The differences show up in integration, operations and rollout. These questions belong in every requirements document.
ERP integration
- Which documents are exchanged (requisition, purchase order, goods receipt, invoice status) and in which direction?
- Are SAP ECC and S/4HANA connected through standard routes such as OCI, cXML or API, without modifying the ERP?
- Can several ERP systems be connected in parallel, including non-SAP systems in subsidiaries?
- Which system owns the master data for suppliers, materials and cost centers?
- How are interface errors detected, logged and reprocessed?
Operating model and data residency
- Is on-premise or private cloud available in addition to public cloud?
- In which country are data and backups stored, and who has administrative access?
- Who decides when updates are applied: the provider or the customer?
- Does sign-in fit your existing identity management (single sign-on)?
- How do you get your data back when the contract ends?
Compliance and audit trail
- Is every approval, price change and catalog change logged with user and timestamp?
- Are logs protected against later alteration, and can they be exported?
- Can the approval matrix be modelled with value limits, cost centers and dual control?
- Can internal audit get read access without operational permissions?
- Does supplier management support evidence required under supply chain due diligence law?
Rollout across entities and countries
- Is the platform multi-tenant, with separate catalogs, approval paths and visibility per legal entity?
- Can central framework agreements and local suppliers be managed side by side?
- Are languages, currencies and order units supported per country?
- Can the rollout proceed entity by entity, without a single cut-over date for the whole group?
Supplier connectivity
- How do suppliers maintain catalog data: by upload, in a portal or via punchout?
- Which formats are accepted (BMEcat, CSV, Excel, cXML)?
- Do suppliers pay network or transaction fees?
- How much effort does reviewing and approving catalog changes create for procurement?
Adoption and cost
- Can occasional requesters find what they need without training?
- How are needs handled that are not in a catalog?
- Is licensing tiered by users, transactions or functional scope?
- Can you start with one module and extend later?
- Is there a reference of comparable size and system landscape?
Source-to-pay integration: how platform and ERP work together
Source-to-pay automation does not come from a single system; it comes from clean handovers. The biggest lever is the catalog: if item, price, supplier and cost center are already correct in the requisition, approval, purchase order and later invoice verification can run on rules. If that data is missing, every downstream step turns into manual clarification.
Ovenca is built as the upstream platform for exactly this. The ERP remains the system of record for purchase order, goods receipt, invoice and payment; Ovenca supplies approved, fully specified transactions. The connection runs over OCI, cXML or the API, in SAP landscapes and elsewhere alike. SAP Business Technology Platform is not required.
| Interface | Use in the S2P process | Direction |
|---|---|---|
| OCI punchout | Catalog is called from the ERP; the cart is returned as a purchase requisition | ERP → Ovenca → ERP |
| cXML punchout | Connects external supplier shops and marketplaces to the shared cart | Ovenca ↔ supplier |
| API | Transfer of contracts and material numbers from the ERP, handover of approved requisitions and purchase orders, connection of third-party systems, export of order and log data | Both directions |
| CSV, Excel, BMEcat | Import and update of supplier catalogs with validation | Supplier → Ovenca |
What can be automated in the source-to-pay process
- Catalog orders within defined value limits, with no buyer involvement
- Assignment of approvers by value, cost center and category
- Handover of the approved requisition to the ERP without re-entry
- Price and item data updates by the supplier, reviewed before release
- Invoice verification in the ERP against order and goods receipt, once the order data is right
Implementing source-to-pay: in stages, not as one big project
Changing all eight phases at once ties up procurement, IT and finance for a long time. What works is starting with the bottleneck and closing the process from there. At Ovenca, a German-speaking team handles implementation and support of the platform.
Current-state review
Record ordering routes, approvals, catalogs and interfaces. Where is data entered twice, and where do orders bypass the process?
Target picture and system boundaries
Decide which system owns which phase and which documents are exchanged between platform and ERP.
Pilot
Start with one legal entity or category: migrate catalogs, connect the first suppliers through the vendor portal, test the ERP integration.
Rollout
Bring further entities, catalogs and suppliers on board step by step; refine approval rules and reports based on actual usage.
Source-to-pay: questions and answers
Source-to-pay (S2P) is the end-to-end procurement process from finding a supplier to paying the invoice. It covers sourcing, contract, supplier management, requisition, approval, purchase order, goods receipt, invoice verification and payment. The term combines the two sub-processes source-to-contract and procure-to-pay.
S2P stands for source-to-pay. It refers to the whole procurement process including strategic procurement, not only order handling. An S2P platform or S2P software is the set of systems that supports this process.
Procure-to-pay (P2P) starts with the purchase requisition and ends with payment; it describes operational procurement. Source-to-pay starts earlier and includes tendering, supplier selection and contract. P2P is therefore a part of S2P. Purchase-to-pay is usually used to mean the same as procure-to-pay.
Source-to-contract is the strategic part of procurement: spend analysis, tendering, negotiation, supplier selection and contract signature. Source-to-contract solutions are accordingly tools for tendering and contract management. The process ends with the contract; using that contract in ordering belongs to procure-to-pay.
In practice, yes. Source-to-settle stresses that the process is only complete once the liability has been cleared and posted. The scope is the same; the term simply puts more weight on the finance side.
Typical modules are spend analysis, tendering, contract management, supplier management, catalog and requisition, approval workflow, order handling, goods receipt and invoice processing. Hardly any company introduces all modules at once. What matters is that the components in use pass their data to the next step without re-entry.
No. Ovenca covers the supplier portal, catalog management, requisition, approvals and the handover to the ERP. Tenders, contract management, invoice verification and payment run in the ERP or in specialist systems connected through interfaces. For companies that want to keep their ERP as the system of record, this is the right division of labour.
Yes. Ovenca connects to SAP ERP and S/4HANA via OCI punchout, cXML or API; SAP Business Technology Platform is not required. Microsoft Dynamics, Oracle, Infor and proprietary ERP systems are connected the same way. The ERP connection can be configured per tenant, so legal entities with different ERP systems use the same platform.
Many S2P suites are offered as a cloud service. Ovenca runs on-premise in your own data center, in a private cloud in the EU, or hybrid. This matters most to companies whose security or data protection policies determine where procurement and supplier data may be held.
Recurring transactions with clear rules automate well: catalog orders within value limits, assignment of approvers, handover of orders to the ERP, and matching invoice, order and goods receipt. The precondition is well-maintained catalogs and master data. Tenders and negotiations remain tasks that need expertise and alignment.
That depends on the scope. Starting with catalog and supplier portal is the smallest project, because the processes in the ERP remain unchanged. Replacing an existing procurement platform, including catalog migration, supplier onboarding and integration, is considerably larger. A reliable schedule is available once the system landscape, catalog inventory and interfaces have been reviewed.
Ovenca supports the implementation of its own platform with a German-speaking team: from reviewing existing catalog and approval processes through ERP integration to rollout. Vendor-neutral strategy or organisational consulting for procurement as a whole is not part of what we offer.
The components in detail
Each phase Ovenca covers has its own page with functions and examples.
Catalog Management
Import and validate supplier catalogs and link them to contracts.
Vendor Portal
Suppliers maintain catalogs and evidence themselves, with approval by procurement.
Catalog Shop
Search, cart and purchase requisition for requesters.
Admin area
Central control of roles, approval paths, budgets and audit trail.
S/4HANA procurement
Indirect procurement alongside S/4HANA, connected via OCI, cXML and API.
Supply chain act software
Supplier onboarding, questionnaires and evidence for supply chain due diligence.
See where Ovenca fits into your S2P process
In one conversation we go through your phases, systems and interfaces and tell you plainly which parts Ovenca takes on and which stay in the ERP.