Your smaller suppliers opt out
A regional fabricator with thin margins will not pay an annual fee to quote on one package a year. You lose exactly the competitive tension a sourcing event exists to create.
Pricing
What Source-to-Pay should cost.
Most of the cost of a Source-to-Pay platform is predictable. Some of it is avoidable. This page sets out which is which - starting with the charge we think nobody should be paying.
The charge worth questioning
Your suppliers should not be paying to sell to you.
Several Source-to-Pay platforms charge the supplier - a network fee, a subscription tier, a percentage of transaction value - for the privilege of responding to your RFx and invoicing you. It is presented as a network benefit. In practice it is a cost your suppliers carry, and they do not absorb it quietly.
Three things follow from it, and procurement teams feel all three:
The fee comes back in the price
Suppliers who do pay recover it somewhere, and the only place available is your line items.
Onboarding gets harder every time
Every new supplier has a commercial conversation to have with your platform vendor before they can have one with you.
procurEngine charges suppliers nothing. They view RFx, submit quotes, take part in reverse and forward auctions, upload compliance documents and use the mobile app free of charge. There is no per-supplier seat fee, no transaction fee, and no paid tier a supplier has to buy in order to respond to you. It is the single most useful question to put to any vendor you are evaluating, including us.
Cost drivers
What you are actually paying for.
| Driver | How it behaves | What to ask |
|---|---|---|
| Modules | The largest single lever. Sourcing only, or sourcing through to invoice matching, are different propositions | Can we start with one module and add the rest without re-implementing? |
| Internal users | Scales with your procurement team, not with your supplier base | Are occasional approvers charged at the same rate as daily users? |
| Integrations | Where effort genuinely accumulates. One clean ERP is routine; several instances is not | Is the connector productised, or is it a services engagement each time? |
| Implementation | A one-off, but frequently the largest first-year line | What is configuration and what needs development? |
| Suppliers | Should be zero. With us it is | Does my supplier pay anything, in any form, to transact with me? |
Being straight about it
Where our cost legitimately goes up.
A pricing page that only lists advantages is a sales page. These are the situations where our number climbs, and you should hear them before a proposal rather than after one:
Multiple ERP instances
Connecting to one SAP instance is well-trodden. Four, across entities with different master data conventions, is a project in its own right.
Heavy customisation in the incumbent
Where standard objects have been extended, mapping takes longer and needs your own team’s time as well as ours.
Categories beyond bought-out material
Services procurement with milestone-based payment terms carries more configuration than material purchasing.
Compressed timelines
Going live in six weeks instead of twelve is possible, and it costs more, because parallel effort replaces sequential effort.
We do not publish a list price, and the reason is not coyness. The honest number depends on which modules you run, how many internal users you have and what has to be integrated. A published figure would be wrong for almost everyone who read it, and the ones it flattered would find out during scoping.
FAQ
Questions about cost.
Do you charge suppliers to transact?
No. Suppliers view RFx, submit quotes, take part in auctions and use the portal free of charge. There is no per-supplier seat fee, no transaction fee and no paid tier a supplier has to buy to respond to you.
Why is there no public price list?
Because the honest number depends on which modules you run, how many internal users you have and what has to be integrated. A published figure would be wrong for almost everyone who read it.
What drives the cost up the most?
Integration depth, more than anything else. Connecting to a single clean ERP instance is routine work. Several instances, or a heavily customised one, is where effort genuinely accumulates.
How long does implementation take?
Eight to twelve weeks for a focused single-module rollout. A full Source-to-Pay programme across several modules and multiple ERP instances takes longer, and any vendor telling you otherwise should be asked for a reference.
More detail on how scoping works is on the pricing page, and the evaluation criteria we recommend are set out on how procurEngine compares.
Get a number scoped to what you actually run.
Tell us your modules, your users and your ERP, and we'll come back with a scoped quote rather than a range.