Platform · Integrations
Procurement integration that returns the order to your ERP
A requisition raised in your ERP arrives in Proconomy on its own. Sourcing, negotiation and award happen here. The purchase order goes back into your ERP, which stays the golden record throughout.
Nothing about the round trip asks your ERP to stop being the system of record. It keeps the demand it raised and the commitment that comes back, and what happens in between — the RFx, the rounds, the comparison, the award — happens somewhere built for it.
- Requisition
- REQ-48219
- Raised by
- Maintenance, Plant 2
- Line
- 40 bearing housings, no contract behind it
- Raised in
- SAP S/4HANA, where it always is
A requisition, where the person always raises it.
The work moves. The record does not.
Replacing the core system is expensive, slow and solves the wrong problem. The ERP records the transaction perfectly well. It was never built to run a negotiation.
The round trip
Out of your ERP. Back into it.
Eight steps, in the order they happen, with the system of record never changing hands.
Someone raises it where they always have — in SAP, Oracle Fusion or Dynamics 365 — and it is ingested into Proconomy automatically, without anyone rekeying it.
Suppliers, materials, purchase orders with their lines, goods receipts and invoices, read from the same system so the requisition arrives with the data it needs around it.
The event, the invitation list, the questions, the line items and the supplier responses — in a system built to run them rather than one built to post them.
Auctions, best-and-final rounds and comparison across responses, with the sourcing policy your organisation set deciding what has to go to market and on what terms.
The threshold, the minimum bid count, how an off-approved-list supplier is handled and whether an award is advisory or automatic are all set by your administrators.
The order that comes out of the award is pushed into your ERP, so the commitment lands in the system that holds your budgets and your release rules.
The same order is issued to the supplier by email, or transmitted to their punch-out order address where that is configured.
It raised the demand and it holds the commitment. Proconomy ran the work in between and holds the history of how the award was reached.
Where this already runs
In operations like yours. Not vendor scenarios.
A pharma manufacturer brings new indirect categories under contract
A regulated multi-plant manufacturer running on SAP HANA 5–6new indirect categories brought under contract1workflow from request to purchase order0SAP validations replaced Read the story
A Leading Steel Manufacturer Unifies Procurement Operations
Multi-site manufacturer handling 6,000+ purchase requisition lines a month 6,000+requisition lines a month through one entry point4 → 1systems to raise a request, down to one0SAP modules replaced Read the storyHow it works
Six things that are true of every connection.
An administrator sets the connection up once. After that the demand finds its way here, and the commitment finds its way back.
-
01
Human
An administrator creates the connection
The system being connected, its address, the sign-in details, and which data domains the connection covers. One connection per system, and more than one per organisation where a group runs several.
-
02
System
Requisitions arrive from your ERP
A requisition raised in SAP, Oracle Fusion or Dynamics 365 is ingested into Proconomy automatically. Nobody retypes it, and nobody has to remember to go and fetch it.
-
03
System
The context arrives with it
Suppliers, materials, purchase orders with their lines, goods receipts and invoices are read from the same system, so the demand lands next to the records it depends on.
-
04
Human
The sourcing happens here
The RFx, the invitation list, the rounds, the auction, the comparison and the award — run under the sourcing policy and approval rules your organisation configured.
-
05
System
The purchase order goes back
The order produced by the award is pushed into your ERP, and issued to the supplier by email or to their punch-out order address.
-
06
System
The run is written down
One history row per domain per run: what triggered it, whether it succeeded, how many records moved, how many failed, how long it took, and the error detail.
Core capabilities
What procurement integration has to get right.
Demand that arrives on its own
The step that decides whether anybody actually uses the sourcing tool
- A requisition raised in your ERP is ingested into Proconomy automatically
- It arrives beside the supplier, material and order records it refers to
- Nobody rekeys a line, a quantity, a plant or a cost centre
- Requisitions can also be brought in from an ERP export where that suits the process better
- From there it is an ordinary Proconomy record, usable in intake, sourcing and approvals
The commitment that goes back
Because an award nobody posts is an award nobody acts on
- The purchase order produced by an award is pushed into your ERP
- Your ERP keeps the budget, the release rules and the posted record
- The same order is issued to the supplier by email
- Or transmitted to the supplier’s punch-out order address where that is set up
- Some documents move in both directions, so the two systems stay in step
The domains you choose to read
Five kinds of record, picked per connection rather than taken wholesale
- Suppliers, with the name, status, country and payment terms the source system holds
- Materials and parts, which become the catalogue procurement works from
- Purchase orders with their lines, so open commitment sits beside new demand
- Goods receipts, each attached to the purchase order it belongs to
- Supplier invoices, matched to the supplier and the order they belong to
A record of every run
So the question “did it come across?” has an answer on screen
- One row per domain per run: trigger, outcome, records moved, records failed, duration and start time
- The error detail for a run kept with it, naming the records that did not come across
- The last twenty runs on the connection, with the history behind them retained
- A status and a last sync time on the connection itself
- A connection test to run before you rely on it
The systems around the ERP
Because a procurement decision is rarely made from ERP data alone
- Engineering items from Dassault 3DEXPERIENCE, arriving as parts
- Contracts sent for signature through DocuSign or Adobe Acrobat Sign
- Alerts into a Microsoft Teams channel, or as a direct message to a person
- Supplier messaging over WhatsApp Business, and company-credit lookup through Creditsafe
- Master data, purchase orders and contracts imported from CSV and Excel
Features
Procurement integration that closes the loop.
Five groups of features, and not one of them depends on someone remembering the policy.
The requisition arrives on its own
Raised where the person always raises it, and in Proconomy without anybody rekeying it.
- A requisition raised in SAP, Oracle Fusion or Dynamics 365 is ingested automatically
- It lands beside the supplier, material and order records it refers to
- No line, quantity, plant or cost centre is retyped
- Requisitions can also be brought in from an ERP export where that suits the process
- From there it is an ordinary Proconomy record, usable in intake, sourcing and approvals
Sourcing and negotiation, in a system built for them
The part the ERP was never designed to run.
- The RFx, the invitation list, the questions and the line items
- Auctions, best-and-final rounds and comparison across responses
- The sourcing policy deciding what has to go to market and on what terms
- Approval rules by amount, category and emergency, with named approver roles
- The award, and the history of how it was reached
The commitment returns to your ERP
Because an award nobody posts is an award nobody acts on.
- The purchase order produced by an award is pushed into your ERP
- Your ERP keeps the budget, the release rules and the posted record
- The same order is issued to the supplier by email
- Or transmitted to the supplier’s punch-out order address where that is set up
- Some documents move in both directions, so the two systems stay in step
Five kinds of record, picked per connection
They arrive as ordinary Proconomy records and are usable from that point on.
- Suppliers, with the name, status, country and payment terms the source system holds
- Materials and parts, which become the catalogue procurement works from
- Purchase orders with their lines, so open commitment sits beside new demand
- Goods receipts, each attached to the purchase order it belongs to
- Supplier invoices, matched to the supplier and the order they belong to
So “did it come across?” has an answer on screen
One history row per domain per run, kept with the connection it belongs to.
- What triggered the run, and whether it succeeded
- How many records moved, and how many failed
- How long it took, and when it started
- The error detail, naming the records that did not come across
- The last twenty runs on the connection, with the history behind them retained
What holds on every connection
Five things. True of every system you connect.
- Nothing moves until an administrator has created a connection and chosen its domains.
- Every run is written to the connection’s history with what moved, what failed, how long it took and the error detail.
- A goods receipt is attached to the purchase order it belongs to, and an invoice to its supplier and order.
- An edit a buyer made by hand in Proconomy survives the next read on the fields they changed.
- Your ERP holds the demand it raised and the commitment that comes back to it.
Three situations. Three different shapes.
A requisition that needs a market
A plant raises a requisition in SAP for something with no contract behind it. It arrives in Proconomy on its own, with the supplier and material records it refers to already alongside. An RFx goes out, three suppliers respond, a round narrows it, and the award is made under the sourcing policy the organisation set. The purchase order goes back into SAP, and out to the supplier. SAP holds the demand and the commitment; Proconomy holds how the award was reached.
A group running two different ERPs
A holding company on SAP S/4HANA with a subsidiary on Microsoft Dynamics 365 creates a connection under each company, each with its own address and sign-in. Demand arrives into the organisation whose connection raised it, and the order returns to the system it came from, which is what keeps each company’s records attributed to that company.
A system nobody has built a connector for
A company running something older or in-house points a REST connection at an address of its own and describes the field names, and purchase orders and invoices come across from it. The same route covers an ERP reached through middleware the customer already operates.
Platform fit
It sits beside the system you run. It replaces none of it.
Your ERP stays the golden record
Budgets, release rules and the posted transaction stay where they are. It raised the demand, and the commitment comes back to it.
Procurement work runs on the data that arrives
Requisitions, suppliers, parts, open orders and invoices are ordinary records in Proconomy, so intake, sourcing, contracts, supplier management and approvals all work from them.
A group connects each company where it belongs
Connections are made per organisation, so a group running different systems in different companies sets each one up under the company it serves.
Locations line up by code
A location code in the connected system is matched against the location codes in the organisation it belongs to.
Connects to Multi-entity management · Intake & orchestration · Sourcing & RFx
Bring the system your ERP team says nobody can touch.
Nothing about connecting it changes a record inside it. We will read a sandbox of it and show you what comes across, and the run behind what did not.
Security, compliance and recognition
Checked by auditors. Judged by the industry.
Where each compliance programme stands, and what the procurement industry has given us so far.
Security and compliance
Awards
Five, presented on stage at three industry events.
- Autonomous Procurement Platform of the Year
- Procurement Technology Innovation Award
- Unified Procurement and Supplier Management Platform
- Procurement Startup of the Year
- AI in Procurement or Supply Chain Award — Solution Provider
Before you book anything. Answered honestly.
What is procurement integration?
It is how a procurement platform works with the system a business already runs instead of replacing it. In Proconomy a requisition raised in your ERP is ingested automatically, the sourcing, negotiation and award happen here, and the purchase order that results is pushed back into your ERP. Your ERP stays the golden record — it raised the demand and it holds the commitment — while the work in between runs in a system built for it.
Which systems can Proconomy connect to?
SAP S/4HANA, Oracle Fusion and Microsoft Dynamics 365 on the ERP side. SAP Ariba, Coupa and GEP SMART among procurement suites. Dassault 3DEXPERIENCE for engineering part data. Alongside those, contracts go out for signature through DocuSign or Adobe Acrobat Sign, alerts go to Microsoft Teams, supplier messaging runs over WhatsApp Business, and company-credit checks run through Creditsafe and Australian ABN lookup. Anything with a REST interface that returns purchase orders and invoices can be reached by a REST connection.
What moves between the two systems?
Inward: requisitions, and from the domains you pick per connection, suppliers, materials, purchase orders with their lines, goods receipts and invoices. Outward: the purchase order produced by an award. Some documents move in both directions so the two systems stay in step.
Does the purchase order really land in our ERP?
Yes. The order that comes out of an award is pushed into the connected system, so the commitment sits where your budgets and release rules already are. The same order is issued to the supplier by email, or transmitted to their punch-out order address where that is configured.
What happens when a record cannot be brought in?
It is counted as a failure on that run and named in the run’s error detail, and the run’s row in the connection history shows how many records moved and how many failed. The most common reason is a reference that is not in Proconomy yet — a purchase order naming a supplier that has not come across. Reading the domain it depends on first resolves it.
Do we need to install anything?
No. Proconomy reaches your system over the internet through the interface that system already publishes, using a sign-in you create on your side. Choosing which domains a connection covers is done in the product.
Your system. Read in front of you.
No slides. We connect a sandbox of the system you run, start a read, and open what arrived and the run behind it.
Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.
Not ready to talk to anyone?
Fair enough. Both of these work without giving us your email.
Explore the next step
Intake & orchestration
What happens to the demand once the catalogue is in place
Procure to pay
Requisition to order to receipt, on the data that came across
Supplier management
The supplier records a connection reads, put to work
Multi-entity management
A connection per company, each under the organisation it serves