Purchasing software
Purchasing management software: what it should verify before you pay, and where to find each answer
Purchasing management software organises requests, orders and approvals. It rarely verifies that what is invoiced matches what was negotiated. This page describes the controls such software should cover (document reading, quote comparison, contract compliance, matching, exceptions) and points to the Zylio page that handles each one.
Definition
What purchasing management software does, and what it generally does not
The term covers two families of tools. The first manages the flow: purchase request, tendering, order, approval, receipt. That is procure-to-pay, often carried by the ERP or a dedicated suite. The second controls spend once the flow is over: does the invoice match the contract, the order, and what was actually delivered?
Most companies are equipped for the first family and unequipped for the second. The ERP’s matching compares totals, tolerates variances, and does not read the contract. Contracts, rate cards and quotes remain PDFs that nobody opens at the moment of payment.
Zylio belongs to the second family: a platform of AI agents for procurement spend control, sitting alongside your existing tools. It does not replace your ordering software. It reads what that software produces and verifies what it does not verify. The sections below detail each control, and the page that owns it.
First control
Read purchasing documents line by line, in every format
No control is possible if the documents are not read. Purchasing management software must accept what your suppliers actually send: native PDFs, scans, photos, spreadsheets, emails with attachments, structured feeds. And it must extract every line (item, quantity, unit price, discount, tax, terms), not just a total and a date.
The point to verify: does each extracted value stay linked to the exact place in the document where it was read? Without that link, a wrong value cannot be corrected, and a control based on it cannot be defended. At Zylio, this reading is the role of the Capture agent.
What Capture reads, line by line, and how each value stays linked to its source.
Second and third controls
Compare the offers, then check the invoice against what was negotiated
Two distinct checks, before and after the signature. Each has its own page.
Before the signature: compare what is comparable
Two quotes never compare line by line as they are: different units, options included on one side only, ancillary fees buried in the total. The software must put them on the same grid before ranking them. That is the role of the Compare agent.
After the signature: check every line against the contract
Framework contract, rate card, price list, amendment, indexation clause: every invoiced line must be checked against the condition that governs it. Price, discount, volume tier, revision date. That is the role of the Compliance agent.
DiscoverIn both cases: show the proof
The clause and the line, side by side. A discrepancy without a document is only an opinion; with the document, it is a claim you can put to the supplier.
The pillar of invoice control against the contract, by the Compliance agent.
Fourth and fifth controls
Match order, receipt and invoice, and handle what fits no standard flow
Three-way matching exists in every ERP. It works on clean invoices and gets stuck on the rest: partial receipts, grouped deliveries, units to convert, item references that differ from one document to the next, fees missing from the order. Purchasing management software must match at line level, with tolerances per supplier and per category, and let only the compliant cases through on their own.
Then there is what fits no flow at all: invoices without an order, several orders on one invoice, disguised duplicates, credit notes never applied. These exceptions are the real cost of processing: three people, two emails, four days. The software must take them on, not hand them back to the team.
Order, receipt, invoice and credit note, matched by the Matching agent.
Integration
Sit alongside the ERP, without writing to it
The integration question often decides the project. Software that requires modifying the core of the ERP, migrating data or changing approval flows will never be deployed across the whole scope. The right criterion is the reverse: what does it read, and what does it leave untouched?
Zylio reads the exports or the API of SAP, Sage, Oracle, Microsoft Dynamics 365, NetSuite, Cegid and Workday, and writes nothing back. Investigated discrepancies go back to your teams, who decide in their usual tools. Nothing is committed without validation; no supplier is contacted; no data is used to train a model.
What we read and what we never modify, ERP by ERP.
Choosing
Six questions to ask before selecting purchasing management software
Does it read the contract?
Not just the invoice: the framework contract, the rate card, the amendment. Otherwise it cannot know what was negotiated.
Does it control at line level?
A correct total can hide ten wrong lines that cancel each other out. Control applies to unit price, quantity, discount.
Does it show the proof?
Every discrepancy must come up with the document, the page and the line. An alert without proof cannot be claimed.
What does it do with exceptions?
Invoices without an order, duplicates, credit notes. If it hands them back to the team, it has changed nothing about processing cost.
Does it write to the ERP?
If it does, your IT department and your integrator will have a say, and deployment will drag on. If it only reads, they will not.
Who decides?
The software builds the case; a human makes the call. Any promise of “automatic” payment or claims should put you on guard.
Getting started
Measure before choosing: a three-week diagnostic
The surest way to know whether control software concerns you is to measure what your current set-up lets through. The Zylio diagnostic runs on your own documents, over three weeks: a scope chosen together, the contracts and invoices for the period, a deliverable discrepancy by discrepancy, quantified and sourced. It is billed on success, on the discrepancies recovered.
Scope, documents requested, deliverable, success-based billing.
Capture
Gather and consolidate all your procurement data.
Collection by dedicated mailbox, upload, SFTP, scan, API or ERP export. Reads every format (native PDF, scan, photo, spreadsheet, structured feed), then extracts line by line: supplier, references, quantities, unit prices, discounts, taxes, terms.
The end of re-entry. A procurement history you can finally query.
What Capture detects
- Long documents and multi-page tables
- Unknown layouts
- Several languages and currencies
- Poor scans and handwriting
Nothing is lost. Everything can be checked, everything can be proven.
- The contract clause and the invoice line, highlighted side by side.
- Every extracted value stays linked to the exact place in the document where it was read.
- The same case produces the same decision, today as in six months: the rules are applied deterministically.
- No discrepancy is set aside in silence. Anything that matches no rule is raised, with its reason.
- The agent records what it did, in the order it did it: who, what, how much, when.
Frequently asked questions
Is Zylio purchasing management software?
Not in the sense of an ordering tool. Zylio does not handle purchase requests, approvals or orders: it is a platform of AI agents that controls what those tools produce. It sits alongside your ERP or your procure-to-pay suite and verifies that what is paid matches what was negotiated.
Do you need a procure-to-pay tool already in place to use Zylio?
No. Zylio reads documents where they are: mailbox, file drop, ERP exports, supplier portal. An ERP is enough; so is a simple folder of PDFs, for a diagnostic. The ordering tool, if there is one, is one more source, not a prerequisite.
How long does set-up take?
It depends on the scope and on access to documents, not on development. Since Zylio writes nothing to the ERP, there is no migration and no change to the core system. The three-week diagnostic is the first milestone: it produces real discrepancies on your data before any commitment.
Which controls does Zylio cover, and which does it not?
Zylio covers document reading, quote comparison, compliance with what was negotiated, order-receipt-invoice matching, exceptions, master data and analysis. It does not cover order placement or payment: those acts stay in your tools, under your validation.
Measurable impact in every environment
More than 5 million procurement documents analysed
Between 1 and 7% of margin recovered
on the scope analysed
From 15 to 45% of time given back to teams, per FTE
depending on the scope and on data maturity
Zylio fits into your existing ecosystem.
The ERP runs the process. Zylio handles the exception and recovers the value that escapes it: invoices without a purchase order, line-by-line price discrepancies, duplicates and overbilling, off-contract spend.
Your data under high security.
Zylio meets the most demanding standards, and nothing is committed without your approval.
- Certifications
- Hosting
- Encryption
- Access
Going further
- Purchasing management as a profitability leverThe management angle: what is lost after the signature, and what control gives back.
- ERP exception management with AIInvoices without an order, duplicates, credit notes: what the Exception agent takes on.
- All solutions, by problemThe catalogue of use cases, from price control to month-end close.
- See the platform in a demoOne concrete case, agents and evidence on screen.
See what this looks like on your own data
Twenty minutes, on a spend category of your choosing. We show you what the agents detect, with the evidence behind it.
- No commitment, on your own data
- Result in 3 weeks
- 20 minutes, no sales pitch
- Your data stays hosted in France
- No change of tool or process