Requests and quotes
Bring together the need, identified supplier, line items and quote. Planned AI uses support document reading and structuring, depending on the chosen configuration.
Explore procurement automation ↗The Sourcing Force solution
Your tail spend procurement.
Within your rules.
A third-party application to organise tail spend requests, suppliers and tracking. Your ERP or S2P remains the system of record for rules, approvals, commitments and purchase orders.
Class C purchasesTail spendAlongside your existing systems
Your ERP / S2PDecide · approve · commit · order
Sourcing ForcePrepare dispersed purchases and track their progress
Sourcing Force + Buy Made Easy
A portal for purchases outside major contracts.
Non-strategic purchases multiply across sites without a workflow as structured as that used for recurring purchases.
Sourcing Force brings these flows into a P2P application with AI assistance, catalogues and ERP/S2P data exchanges.
Buy Made Easy acts as the single supplier for purchases assigned to its outsourcing service.
Inside Sourcing Force
A look at the workflow in the application.
A defined scope
Organise procurement
for your tail spend.
Managing class C purchases means adapting the way you handle items with a small share of total spend, often numerous and varied. The challenge involves requests and data as much as supplier relationships. Assess how critical a need is separately from its value.
Sourcing Force brings this scope into a specialist application. For procurement and IT teams, the starting questions are practical: which requests should pass through the application, which data must return to the system of record, and which operations stay in-house?
A focused scope
From one-off purchases
to tracked operations.
Choose the workflows your organisation needs, then define their data, access rights and exchanges.
Catalogues and PunchOut
Offer hosted catalogues or access to the supplier's website. The cart enters the workflow agreed with your ERP/S2P for approval and ordering.
Compare PunchOut and hosted catalogues ↗Procurement controls
Spending limits, approval workflows and restrictions on suppliers or categories apply your procurement policy within the application's agreed scope.
Client master data
Cost centres, projects and categories structure the information. Their configuration or exchange via API is organised around the system of record and agreed fields.
Prepare your procurement ERP integration ↗Discussions and status updates
Centralise supplier discussions and track operations and payments. A payment status provides information about progress; it does not execute a bank payment.
Reporting and KPIs
Custom dashboards put spend, suppliers and activity into context. Define indicators around the decisions you need to make.
Analyse procurement spend ↗How the functions are shared
Three specialist functions.
Your system of record stays in place.
The client's ERP / S2P — procurement policy, approvals, commitments and orders. The client's rules determine the steps and data exchanges.
Prepare
Request, quote and cart
↓ Structured data enters the agreed workflow
Track
Suppliers, discussions and status updates
↔ Information on assigned operations
Monitor
Spend, activity and KPIs
↑ Information to support procurement decisions
This division defines functional responsibilities. Work with your IT team to specify the data objects, direction and frequency of exchanges for the agreed scope.
Inside the application
A documented request,
ready for approval.
The pre-order brings together the supplier, branch, contacts, quote and items. It prepares the next steps in the purchasing workflow.
Application and services
Two ways to support your team.
Combine them to suit your needs.
Sourcing Force structures workflows, data and tracking. Your team can use the application for operations it handles in-house.
BME handles the assigned operations
BME Consulting delivers outsourcing services for the purchases assigned to it. The application and services can be used together or separately; your teams define the scope.
Outsourcing: BME's responsibilities ↗Documented use cases
A project with a defined scope.
Roche Diabetes Care France
The 2016–2017 case describes a customised solution, including a supplier portal, contracts and spend mapping. It illustrates a project over a defined period, with support for users.
Accor head office — 2021
The BME account describes digital procurement outsourcing and catalogues accessible from the ordering system. It shows how the application and services work together for one-off purchases.
Read the BME customer story (French) ↗Build your workflow
Explore the right topic.
Spend analysis ↗Identify tail spend prioritiesBME outsourcing ↗Define the operations to assignCatalogues and PunchOut ↗Organise supplier selectionIntegrations ↗Prepare exchanges with the system of recordAutomation and AI ↗Review tasks and controlsCustomer stories ↗Find comparable situationsProcurement budget management ↗Link requests to cost allocationsSupplier evaluation ↗Choose useful criteria and evidenceSupplier contract management ↗Connect documents with operationsPrivate B2B marketplace ↗Organise access to supplier offerings
Prepare your project
Implementation questions.
Can we start with a single purchasing workflow?
You can start with a limited scope: catalogues, quote-based requests or tracking purchases assigned to BME. Define the users, data and exchanges needed before expanding. The demonstration and deployment should reflect that scope.
Who defines access rights and approval rules?
The client remains responsible for its procurement policy and ERP/S2P system of record. Limits, workflows and restrictions configured in Sourcing Force must follow the agreed framework. Procurement and IT teams define the detailed access rights and data exchanges.
Your next step
Make room
for the purchases that matter.
Let's discuss your class C purchases and how your organisation works.
Request your free assessment.