Key takeaways
- Ivalua names two halves. Source-to-contract: supplier management, sourcing, contract management and spend analysis. Procure-to-pay: eProcurement, AP automation and payments. Intake and direct materials come on top.
- All modules share one data model, but you license them one by one. Ivalua’s 2023 US public contract counts “the number and description of modules” in the licence.
- In nine published cases I found, six started with suppliers, sourcing or contracts. That is a handful of examples, not a market statistic.
- Each module brings its own data, interfaces and suppliers. Decide which system owns supplier data and where invoices go before you choose the order.
What modules does Ivalua have?
Ivalua has about ten modules on one platform. Supplier management, sourcing, contract management and spend analysis cover choosing suppliers and signing with them. eProcurement, AP automation and payments cover buying and paying. Intake management collects requests at the start. Separate modules serve direct materials in manufacturing. You can buy one module or the whole suite.
| Module (Ivalua’s name) | What it does | Half of source-to-pay |
|---|---|---|
| Intake Management | One place where staff ask for what they need; the request is then sent to the right process | Before buying |
| Supplier Management | Supplier records, onboarding, risk and performance. Ivalua splits it into SIM, ASIM (the supplier “golden record” across several ERPs), supplier risk (SRM) and supplier performance (SPM). The supplier portal sits here | Source-to-contract |
| Sourcing | Requests for information and proposals (RFx) and auctions, for direct, indirect, services and CapEx spend | Source-to-contract |
| Contract Management (CLM) | Contract drafting from templates and clause libraries, approvals and follow-up | Source-to-contract |
| Spend Analysis | Who spends what with which supplier, to feed sourcing and contract decisions | Source-to-contract |
| eProcurement | Requisitions, catalogues and marketplaces (SEARCH360), approvals, purchase orders and receipts | Procure-to-pay |
| AP Automation (Invoicing) | Invoice capture from PDF, XML, EDI and e-invoicing networks; matching with orders, receipts and contracts; non-PO invoices | Procure-to-pay |
| Payments | Supplier payments by ACH, virtual card, cheque or cross-border transfer, with the status shown to the supplier | Procure-to-pay |
| Expense, External Workforce, Inventory Collaboration | Employee expense claims and corporate or virtual cards; contractors and statement-of-work services; stock levels from the ERP used in buying, and stock managed by the supplier (VMI) | Procure-to-pay |
| Direct Materials (procurement, sourcing, supply chain collaboration) | Bills of materials, quality processes (APQP, PPAP, 8D), links with ERP, MRP and PLM | Manufacturing |
Four modules to choose suppliers and sign with them, three to buy and pay, plus intake and direct materials. The names change on Ivalua’s site from time to time; the split stays.
Ivalua also sells analytics, an environmental impact centre and its AI agent, IVA. According to Ivalua, every IVA action runs within the user’s permissions. The Ivalua pillar explains how the platform is built. For the neutral meaning of each process, eProcurement Toolkit has guides to supplier management, contract management, spend analysis and procure-to-pay.
What is the difference between Ivalua source-to-contract and procure-to-pay?
Source-to-contract ends when a contract is signed with a supplier. Procure-to-pay starts when someone in your company needs to buy, and ends when the supplier is paid. Ivalua puts it simply on its eProcurement page: eProcurement “manages how you buy”, while procure-to-pay adds invoices and supplier payments to it.
The two halves need different people and different data. Source-to-contract is used by buyers, lawyers and category managers, with supplier and contract data. Procure-to-pay is used by every employee who orders, and by accounts payable. It needs catalogues, cost centres, budgets and interfaces with your ERP. That is why procure-to-pay usually has more users, more interfaces and more suppliers to onboard.
Is Ivalua one platform or a set of separate modules?
Both. Ivalua says its platform “unifies Intake, Source-to-Contract, Supplier Management, and Procure-to-Pay on one data model”. A supplier created in supplier management is the same record in sourcing, contracts and orders. But you license and deploy the modules one by one.
Ivalua’s 2023 contract with the State of Maine, signed for the NASPO ValuePoint purchasing group, shows how. Its licence terms define the “Metrics” of a subscription as including “the number and description of modules”. The agreement adds that “changes to selected packages, modules or options may result in changes to price”. Public buyers can also buy parts of the platform, called workstreams, on their own.
| Workstream in the NASPO contract | Software only | Software and services |
|---|---|---|
| Supplier Portal | Ivalua | Not awarded |
| Supplier Enablement | Ivalua | Not awarded |
| Buyer Portal | Ivalua | Not awarded |
| Need Identification | Ivalua | Not awarded |
| Request through Pay | Ivalua | Ivalua |
| Catalog Capability | Ivalua | Ivalua |
| Sourcing/Bid Management | Ivalua | Ivalua |
| Contract Management | Ivalua | Ivalua |
| Vendor Performance | Ivalua | Ivalua |
| Purchasing/Data Analytics | Ivalua | Not awarded |
A US public buyer can license any of the ten workstreams alone. For five of them (ordering, catalogues, sourcing, contracts and vendor performance), Ivalua can also be hired to implement that workstream on its own.
The same contract gives maximum prices for a full scenario, by size of State. Implementation is capped at $2.34 million to $3.68 million. Licences and maintenance over ten years are capped at about $13 million to $23 million. These are ceilings for the whole platform, not prices paid. What buyers actually paid is in Ivalua implementation cost and timeline.
Which Ivalua module do organisations deploy first?
I found nine organisations whose public documents say what they put on Ivalua first. Six started with suppliers, sourcing or contracts. Nine published cases are not a statistic, and they are not a sample of all Ivalua customers. They only show that a first scope on the source-to-contract side is a common choice.
| Organisation | What went live first, or what is in Ivalua | Source and date |
|---|---|---|
| UNSW Sydney (university) | Contract management and the supplier repository, then an automated supplier import. It wanted a platform implemented “module-by-module” | Ivalua and KPMG release, March 2023 |
| HDF Energy | Suppliers, sourcing and contracts in 3 months, with no ERP interface at the start | Cyrias (integrator) case study |
| Celestica (indirect spend) | Sourcing and contracts first, then supplier management as phase 2, from 13 January 2025 | Celestica supplier information session, December 2024 |
| Cummins (direct materials) | e-Sourcing, with go-live set for 27 April 2026; then the only accepted channel for quotes | Cummins supplier portal notice |
| French state (APPACH) | Sourcing, purchase planning and performance tracking. Tenders, contract drafting and accounting run in other state systems | Direction des Achats de l’État page; BOAMP notices tie APPACH to Ivalua |
| State of Maryland (eMMA) | Supplier registration, bids and awarded contracts on the supplier side | eMMA vendor guide, May 2022 |
| European Patent Office | Supplier data, order acknowledgement and shipping notices; invoices still go to accounts payable outside the portal | EPO procurement portal FAQ, read October 2026 |
| Maxim Healthcare | Procure-to-pay in 8 weeks, with a packaged scope | Ivalua release, March 2019 |
| State of Virginia (eVA) | Purchase orders to suppliers since May 2022, replacing the Ariba Network | James Madison University procurement news, March 2022 |
Six of nine cases start or stay on the source-to-contract side. The other three put orders in Ivalua: a packaged procure-to-pay scope, a state marketplace, and order confirmations without invoices.
These sources do not say why. A likely reason: source-to-contract has fewer users, few interfaces and no impact on payments. Procure-to-pay touches every requester, the budget, the ERP and every supplier who sends an invoice. Starting with supplier management also gives clean supplier records, which every later module reuses.
What should you decide before choosing your Ivalua modules?
The module list matters less than five decisions that sit across modules. Each one changes the scope, the interfaces and the cost of every upgrade.
- Who owns supplier data. Is a new supplier created in Ivalua or in the ERP? Ivalua says it can be the master source and send approved changes to the ERP. If the ERP stays the master for payment, you need an interface in the other direction.
- Where invoices go. Ivalua often sends approved invoices to the ERP, and the ERP sends back the payment status. If you do not license AP automation, invoices are handled in the ERP or in another tool, and the portal will not show them. Decide it before you tell suppliers what the portal is for.
- What suppliers will see. The supplier portal shows only the modules you deploy. A supplier invited for a tender and later asked to confirm orders in the same portal needs to be told twice. The supplier portal guide covers this.
- In which order. Contracts need suppliers. Catalogues need contracts and prices. Orders need catalogues, cost centres and ERP interfaces. Put the modules in the order their data becomes ready.
- What you change from the standard. Each module you configure beyond the standard is tested again at every upgrade. Ivalua’s 2023 terms charge complex configuration added after go-live at each upgrade, and require an upgrade at least every two years.
The interfaces behind these decisions are in Ivalua ERP integration. The project itself is in How does an Ivalua implementation work?.
On the BNP Paribas v156 platform I worked on, the scope covered six modules: suppliers, sourcing, CLM, catalogue, BPM workflows and e-procurement. The v156 case study shows that scope. If you need a certified Ivalua consultant for one of these modules, I take senior missions.
Which guides answer the questions on each module?
This page gives an overview of the modules. Each specific question has, or will have, its own guide:
- What suppliers do in the portal, and what goes wrong at onboarding: Ivalua supplier portal.
- Supplier records, risk, performance and what SRM means at Ivalua: Ivalua supplier management.
- Connecting the modules to SAP, Oracle or another ERP: Ivalua ERP integration.
- What a project costs and how long it takes: Ivalua implementation cost and timeline.
Frequently asked questions
Short answers to the questions people ask, each one sourced above.
Can you buy only one Ivalua module?
Yes. Ivalua’s 2023 licence terms count the number of modules in each subscription, and its NASPO contract lets US public buyers license any of ten workstreams alone. UNSW Sydney first implemented contract management and the supplier repository, then added an automated supplier import.
Does Ivalua have a contract management (CLM) module?
Yes. Ivalua calls it Contract Management. According to Ivalua, it covers drafting from standard templates and clause libraries, approvals and follow-up, with an audit trail. It is part of source-to-contract. UNSW Sydney deployed it first, together with its supplier repository.
Does Ivalua do accounts payable automation?
Yes, in its AP Automation module, also called Invoicing. Ivalua says it captures invoices from PDF, e-mail, scans, XML, EDI and e-invoicing networks such as PEPPOL, and matches them with purchase orders, receipts and contracts. Payments are a separate module.
How much does one Ivalua module cost?
Ivalua publishes no price list. One aggregator, VendorBenchmark, estimates $185,000 to $340,000 a year for a single module at Fortune 500 scale, with a method that is not public. Treat it as one estimate. Public contract values are in the cost and timeline guide.
Which Ivalua modules have you worked on?
On the BNP Paribas v156 platform, the scope covered suppliers, sourcing, CLM, catalogue, BPM workflows and e-procurement. On v182, delivered and still evolving, I work on the integrations, including supplier and ERP interfaces and the catalogue. Those are the modules I can speak about first-hand.
Project already started? Check where it stands.
The health check scores your platform and your programme in three weeks.
