ERP integration
Zylio integration with SAP: every invoiced line checked against your contracts, with no write into S/4HANA
The Zylio integration with SAP is read-only. Zylio receives purchase orders, goods receipts, supplier invoices and pricing conditions from S/4HANA or ECC, through an API opened in read mode or a scheduled export. It checks every line against your contracts, quantifies the discrepancy and returns the evidence. Nothing is written into SAP, and no ABAP development is required.
Data read
What Zylio reads in SAP, and nothing else
The scope is the purchasing module. Zylio never asks for access to the general ledger, payroll or HR data.
Zylio reads the objects your procurement team already handles: purchase orders with their lines, quantities and unit prices; goods and service receipts posted against those orders; supplier invoices recorded in invoice verification, including any blocks; outline agreements and scheduling agreements with their conditions. It also reads purchasing info records and condition records, because that is where the negotiated prices the ERP applies to an order actually live.
Alongside this structured data, Zylio reads the documents themselves: the invoice PDF archived or received by e-mail, the signed framework contract, the amendment, the unit-price schedule nobody ever keyed into SAP because it runs to thousands of lines. Confronting the two, what SAP knows and what the contract says, is what makes discrepancies visible. An order price can be perfectly consistent in SAP and still be wrong against the contract that was signed.
Purchase orders
Headers and lines, purchasing organisation, company code, supplier, material, quantity, unit, net price and applied conditions.
Receipts
Goods receipts and service entry sheets, quantities received, dates, partial or consolidated deliveries.
Supplier invoices
Posted or parked invoices, lines, amounts, discrepancies already blocked by SAP and the blocking reason.
Contracts and conditions
Outline agreements, scheduling agreements, purchasing info records, condition records, quantity scales.
Master data
Supplier and material records, units of measure, material groups, payment terms.
Supporting documents
The PDF of the invoice, contract, amendment or price schedule, read line by line and linked to its SAP record.
Connection mode
Three ways to hand over your SAP data
The channel depends on what your SAP team is willing to open. All three feed the same analysis, with the same traceability.
Read-only API
If your team exposes the standard OData services or APIs of S/4HANA with a technical user restricted to read access, Zylio queries orders, receipts, invoices and master data at the agreed frequency. No write permission is requested and no existing role is changed.
Scheduled export
An extraction of purchasing reports or tables, in the format SAP already produces (flat file, spreadsheet, structured feed), dropped on an SFTP server or a shared folder. This is the most common channel, because it requires no network opening and no change to authorisations.
Documents outside SAP
Invoice PDFs, contracts and price schedules that do not live in the ERP arrive through a dedicated mailbox, a file drop or a scan. The Capture agent reads them and links them to the matching SAP order or supplier.
API, file drop, SFTP, e-mail inbox, export, scan: the Zylio integration principle.
Boundaries
What Zylio never changes in SAP
No writes. Zylio does not create purchase orders, does not post invoices, does not release blocks, does not release payments and never touches a supplier or material record. No ABAP development, no custom transaction, no add-on to install in your system, no configuration to redo at the next upgrade. Your core model stays yours, and your integrator has nothing to maintain.
The outcome of the control comes back in a form your team can pick up: a status per line, the quantified discrepancy, its reason and a link to the document. It can be reviewed in the Zylio interface or picked up by an import flow your teams control. What you do with it, block, request a credit note, approve with full knowledge, is decided and executed in SAP, by the person entitled to do so. Zylio investigates; a human decides.
The data read stays hosted in France, is never shared between customers and is never used to train a model. Every read is time-stamped in an exportable audit trail, including for your SAP team when they want to know what was consulted, through which channel and when. If a technical user was created for the API, its rights are limited to reading the agreed scope and can be revoked on your side at any time.
Hosting in France, ISO 27001, SOC 2 Type II, encryption, full audit trail.
Mechanism
What is checked against what, line by line
SAP compares totals and tolerances. Zylio compares every invoiced line with what the contract allows, and shows the evidence.
Take an invoice blocked in invoice verification for a price variance. SAP knows the invoiced price differs from the order price. It does not know whether the order price itself complied with the framework contract, whether the volume discount for the tier reached this quarter was applied, or whether the price revision the supplier invokes was due on that date and on that index. Zylio reads the contract, the price schedule and the amendment, finds the clause, and places the invoiced line next to it.
The same mechanism applies to the invoices SAP lets through: a price that matches the order but exceeds the negotiated rate, an off-catalogue service, a unit of measure converted the wrong way, a one-cent discrepancy repeated across thousands of lines. The evidence is always the same: the contract clause and the invoice line, highlighted side by side, linked to the page and line they come from.
Compliance
Checks the invoiced price against the framework contract, the price schedule, the amendment, discount tiers and indexation clauses.
DiscoverMatching
Matches order, receipt and invoice at line level, with your tolerances per supplier and per purchasing category.
DiscoverException
Handles invoices without an order, multi-order invoices, duplicates and credit notes never applied.
Discover
How it unfolds
How a rollout on SAP proceeds
Four steps, run with your procurement team and your SAP contact. None of them requires development on your side.
- 01
Scoping
Company codes, purchasing organisations, categories and suppliers in scope; choice of the read channel with your SAP team; inventory of the contracts and price schedules to gather, often outside the ERP.
- 02
First extraction and field mapping
Zylio receives a first set of orders, receipts and invoices, maps the fields (supplier number, material, unit, currency) and verifies that every value stays linked to its source.
- 03
First pass on history
The agents check the selected history. Your teams review the discrepancies raised, adjust tolerances and rules, and decide what deserves a claim.
- 04
Steady state
The extraction repeats at the agreed frequency. Qualified discrepancies reach your approvers with their evidence; compliant cases do not disturb them.
On your real SAP data, no commitment, success-based fee.
For your teams
What changes for procurement and accounts payable
Accounts payable stops clearing blocks one by one in the dark. Every blocked invoice arrives with its diagnosis: the discrepancy comes from the order, the receipt, the contract or the supplier, and the document proving it is already attached. Clean invoices go through without anyone looking at them. The time saved is not spent re-keying anything: it goes to the cases that actually need a decision.
Procurement gets what SAP never gave it: the actual compliance of what was paid against what was negotiated, supplier by supplier, line by line. A renegotiation starts from the invoiced history, not from the theoretical rate. When a supplier disputes, the file is already built, with the clause and the line. And when a framework contract comes up for renewal, the buyer knows what it really cost, discounts applied or not.
The controlled scope moves from a sample to every selected line, without hiring and without changing tools. Between 1 and 7% of margin recovered on the scope analysed: that is the order of magnitude observed, and the 3-week diagnostic measures it on your own SAP data before any commitment. If your scope does not justify it, the diagnostic says so too, and you leave with the list of discrepancies found.
We do not touch the ERP. We commit to nothing without approval. We contact no supplier.
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
Do we need ABAP development or an SAP add-on to connect Zylio?
No. Zylio reads data through the standard services exposed in read mode or through a scheduled export of purchasing reports and tables. No development, no custom transaction, no add-on to install. Your system stays exactly as it is, including at the next upgrade.
Does the integration work with SAP ECC as well as S/4HANA?
Yes. The objects read (orders, receipts, invoices, contracts, conditions, master data) exist in both. On ECC the most common channel is the scheduled export; on S/4HANA, read-only OData services are an additional option. The result and the traceability are identical.
What happens when Zylio finds a discrepancy?
It quantifies and qualifies it (price, quantity, discount, revision, off-contract) and attaches the evidence: the clause and the invoice line side by side. The file reaches the person you designated. Blocking, claiming or approving is decided and executed in SAP, by you.
How are several company codes or purchasing organisations handled?
The scope is set during scoping: company codes, purchasing organisations, suppliers. Zylio handles multi-entity scopes, including when material master data differs from one entity to another: the same item under several references is recognised and prices become comparable across entities.
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.
- Compliance with your negotiated pricesChecking every invoice against the contract, the price schedule and the price list.
- Order, receipt and invoice matchingLine-level matching with your tolerances, beyond the ERP three-way match.
- See Zylio on an SAP caseA 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