ERP integration
Connect Zylio to all your ERP systems: invoice control in read-only mode, without changing tools
Connecting Zylio to an ERP requires no add-on, no development and no write. Zylio reads the orders, receipts, invoices and master data your system already exports (read-only API, scheduled export, SFTP or e-mail inbox) and checks every line against your contracts. The result comes back with its evidence; your ERP remains the source of truth.
Principle
One principle, whatever the vendor: read, check, return the evidence
Your ERP runs the process: order, receipt, invoice, payment. It remains the source of truth and the place where decisions are made. What it cannot do is check every invoiced line against the contract that was signed, the price schedule that runs to thousands of lines, the amendment that changed a discount, or what the same supplier invoiced to another entity. That is exactly, and only, what Zylio adds.
To do so, Zylio needs to read two things: what the ERP knows (orders, receipts, invoices, suppliers, items, entered terms) and what it does not (contracts, price schedules and rate cards as PDFs, invoices received outside the circuit). The first comes from the ERP through the channels described below; the second comes from your e-mails, shared folders and scans. The agents check the two against each other, line by line, and return every discrepancy with its evidence.
The integration mode does not depend on the vendor. SAP, Sage, NetSuite, Microsoft Dynamics 365, Oracle, Pennylane or an in-house system: Zylio reads, does not write into the core of the system, and returns its results in a form your teams can pick up. A less common or home-grown ERP is handled through export or file drop, like the others, with the same traceability.
The key message, the six intake channels and the environments covered, vendor by vendor.
Connection mode
Three ways to connect your ERP, from the simplest to the most frequent
The channel is chosen with your IT team, according to what it is willing to open. All three feed the same analysis and leave the same trace.
Scheduled export, file drop or SFTP
Your ERP already produces exports: flat file, spreadsheet, structured feed. A recurring export dropped on an SFTP server or a shared folder is enough. No network opening, no new right, no development. It is the most common channel, and it gives the same result as the API.
Read-only API
When your ERP exposes an API and your teams agree to open it, a technical account limited to reading the agreed scope allows more frequent reads. No write permission is requested. Zylio, for its part, exposes a documented API to push documents or retrieve results.
Dedicated mailbox and scan
For documents that do not live in the ERP: contracts, price schedules, amendments, invoices received by e-mail, paper documents. The Capture agent reads them line by line, including poor scans and schedules of several thousand lines, and links them to the supplier and entity concerned.
What comes back
What Zylio returns to you, and what it changes
The outcome of the control always takes the same form: for every invoiced line, a status, the quantified discrepancy, its reason (price above the negotiated rate, volume discount not applied, revision outside its due date, quantity or unit mismatch, off-contract service, duplicate, credit note never applied) and the evidence: the contract clause and the invoice line, highlighted side by side, linked to the page and line they come from. All of it is viewable in the Zylio interface, exportable, and time-stamped in an audit trail.
What changes for your teams: compliant invoices go through on their own, the others arrive qualified with the person who has to decide. Accounts payable stops checking by sampling; procurement gets the actual compliance of what was paid against what was negotiated, supplier by supplier, and starts renegotiations from the invoiced history. Between 1 and 7% of margin recovered on the scope analysed: that is the order of magnitude observed, measured by the diagnostic on your own data before any commitment.
What does not change: nothing is written into your ERP, no invoice is approved, no payment is triggered, no supplier is contacted. The decision, whether to block, claim or approve with full knowledge, is taken and executed in your tool, by the person entitled to do so. The data read stays hosted in France and is never used to train a model. Zylio investigates; a human decides.
We do not touch the ERP. We commit to nothing without approval. We contact no supplier.
SAP
SAP S/4HANA and ECC: orders, receipts, invoices and conditions, without ABAP
On SAP, Zylio reads purchase orders, goods receipts, invoices in verification, outline agreements, purchasing info records and condition records, through read-only OData services or a scheduled export of purchasing reports and tables. No ABAP development, no custom transaction, no add-on. Multi-company scopes are handled, including when material master data differs from one entity to another, and the result comes back in a form your team picks up.
What is read, the channels, what is never changed, how a rollout unfolds.
Sage
Sage X3, 100 and 1000: several installations, one control
On Sage, the most common channel is the accounting or purchasing export each installation already knows how to produce, complemented by a read-only API when the version exposes one. Zylio reads orders, invoices, purchase ledger entries, supplier and item records, reconciles suppliers and items across installations and versions, and checks the whole against the agreements that apply, group or local. No write into your ledgers.
Sage X3, Sage 100, Sage 1000: what is read, the exports, the rollout, the boundaries.
NetSuite
NetSuite: saved searches or REST API, OneWorld subsidiaries included
On NetSuite, your administrator schedules the export of saved searches on purchasing transactions and master data, or opens the REST API to a role limited to read access. Zylio reads purchase orders, item receipts, vendor bills, vendor credits and records, subsidiary by subsidiary, and reconciles the same vendor and the same item across subsidiaries. No SuiteScript, no bundle, no workflow modified.
Saved searches, read-only API, OneWorld subsidiaries, what is never changed.
Microsoft Dynamics 365
Dynamics 365 Finance and Business Central: data entities or OData
On Dynamics 365, the most common channel is the data entity export scheduled from the data management framework of Finance & Supply Chain Management, or a periodic export of Business Central purchase documents; OData endpoints and APIs are opened in read mode when you prefer more frequent reads. Zylio reads orders, receipts, invoices, trade agreements and master data, and its results export to Power BI.
Finance & Supply Chain Management and Business Central: what is read, the channels, the boundaries.
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
Our ERP is not on any list. Can we still connect Zylio?
Yes. The integration mode does not depend on the vendor. A recurring export in the format your tool knows how to produce (spreadsheet, flat file, structured feed), dropped on an SFTP server or a shared folder, is enough. The result and the traceability are identical to those of an API read.
Do we need development or an add-on in the ERP?
No, in no case. Zylio reads what the ERP already knows how to produce or expose in read mode. No add-on, no extension, no script, no added table, no configuration to redo at the next update. Your IT teams have nothing to maintain.
Does Zylio write the result into the ERP?
Never. The result (status per line, quantified discrepancy, reason, evidence) is viewable in the Zylio interface and exportable. Your teams pick it up in their approval workflow or import it by their own means. The decision stays in your tool, with the person entitled to take it.
We run several different ERPs across the group. How does that work?
Each system is read through its own channel, in its own format. Zylio reconciles suppliers, items and units across systems in its own repository, then checks the whole against the agreements that apply, group or local. Prices become comparable from one entity to the next, whichever ERP carries them.
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
- All ERP integrationsThe read-only integration principle, the intake channels and the environments covered.
- Capture agentCollection and line-by-line extraction, whatever the channel and the document format.
- Security and complianceHosting in France, ISO 27001, SOC 2 Type II, full audit trail.
- See Zylio on your ERPA demonstration on a scope close to yours, 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

