ERP integration
Zylio integration for NetSuite: your vendor bills checked against your agreements, with no write into NetSuite
The Zylio integration for NetSuite is read-only. Zylio receives purchase orders, item receipts, vendor bills and vendor and item records, through saved search exports or the REST API with a role restricted to read access. It checks every line against your contracts, quantifies the discrepancy and returns the evidence. No SuiteScript, no bundle, no write.
Data read
What Zylio reads in NetSuite
The scope is the NetSuite procure-to-pay cycle: purchase orders with their lines, items, quantities, units and rates; the item receipts linked to them; vendor bills, whether pending approval or already approved, with their lines and status; vendor credits. Added to that are vendor records, item records with their purchase prices, OneWorld subsidiaries and currencies, because that is what links an invoiced line to the right entity and the right contract.
What NetSuite generally does not contain, Zylio reads elsewhere: the signed framework contract, the unit-price schedule, the amendment that changed a discount, the rate card the supplier sent as a PDF. These documents arrive through a file drop or a dedicated mailbox, are read line by line by the Capture agent and linked to the matching NetSuite vendor. Confronting the two is what makes discrepancies visible.
Transactions
Purchase orders, item receipts, vendor bills, vendor credits, with lines, approval status and subsidiary.
Master data
Vendors, items and purchase prices, units of measure, subsidiaries, currencies, payment terms.
Supporting documents
The invoice PDF attached to the transaction or received by e-mail, the contract, the price schedule and the amendment, read line by line.
Connection mode
Saved search or API: two routes, one trace
The channel depends on what your NetSuite administrator prefers to open. Both feed the same analysis.
Saved search export
Your administrator creates one or more saved searches on purchasing transactions and master data, and schedules their export as CSV to an SFTP server or a shared folder. It is the simplest channel: it uses a standard NetSuite mechanism and requires no new permission.
Read-only REST API
If you prefer more frequent reads, a dedicated role limited to viewing the records in scope, with token-based authentication, lets Zylio query the API. No create or edit permission is requested, and the role can be revoked at any time.
Documents outside NetSuite
Contracts, price schedules, rate cards and invoices received outside the circuit arrive through a dedicated mailbox, a file drop or a scan. They are linked to the vendor and subsidiary concerned.
API, file drop, SFTP, e-mail inbox, export, scan: the Zylio integration principle.
Boundaries
What Zylio never changes in NetSuite
No writes. Zylio does not create vendor bills, approves nothing, changes no status, touches neither vendor records nor item purchase prices, and triggers no payment. No SuiteScript to deploy, no bundle to install, no approval workflow to modify. Your NetSuite account stays as it is, and your releases happen without us. Nothing you customised is affected, and nothing needs retesting because of us.
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, viewable in the Zylio interface or exportable. What you do with it (reject the bill, request a vendor credit, approve with full knowledge) is decided and executed in NetSuite, in your workflow, 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: your administrator knows what was consulted, through which channel and when. If a dedicated role was created for the API, its rights are limited to viewing the agreed scope, and you can revoke it at any time without telling us.
Hosting in France, ISO 27001, SOC 2 Type II, encryption, full audit trail.
Mechanism
What the agents check, and what they raise
Native NetSuite matching compares the bill with the order. Zylio adds what the order does not know: the contract.
A vendor bill pending approval in NetSuite carries an amount per line. Zylio places next to it the order, the receipt, and above all the contract or rate card that applies to this vendor, this subsidiary, this date. It applies your tolerances and qualifies every discrepancy with its evidence: the contract clause and the invoice line, highlighted side by side, linked to the page and line they come from. No discrepancy is dropped silently.
Price above the negotiated rate
The line matches the order, but the order did not match the contract. Compliance finds the clause.
DiscoverVolume discount forgotten
The tier was reached this quarter, across subsidiaries, and the discount appears on no invoice.
Revision outside its due date
The supplier applied an increase before the agreed date, or on a different index from the contract.
Quantity or unit discrepancy
Matching matches order, receipt and bill at line level, units converted, partial receipts included.
DiscoverBill without an order, duplicate
Exception handles what fits no standard circuit, instead of sending it back to the team.
DiscoverVendor credit never applied
The credit promised during a dispute never arrived, or was never matched to its original bill.
How it unfolds
How a rollout on NetSuite proceeds
- 01
Scoping
Subsidiaries, purchasing categories and vendors in scope; choice of channel with your NetSuite administrator; inventory of the contracts and rate cards to gather.
- 02
First extraction and field mapping
A first saved search export, or a first read through the API. Zylio maps the fields (vendor, item, unit, currency, subsidiary) 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, adjust tolerances per vendor and per category, and decide what deserves a claim.
- 04
Steady state
The export or the read repeats at the agreed frequency. Qualified discrepancies reach your approvers with their evidence; compliant bills do not disturb them.
On your real NetSuite data, no commitment, success-based fee.
For your teams
What changes for your approvers and your buyers
Your approvers stop approving in the dark. A bill pending in NetSuite arrives with its diagnosis: compliant with the contract, or not, and why, document attached. Clean bills go through on their own; the others arrive qualified, with the discrepancy already quantified. The time given back is not spent re-keying: it goes to the cases that need a decision, and the queue of blocked bills stops growing.
Your buyers get what NetSuite never gave them: the actual compliance of what was invoiced against what was negotiated, subsidiary by subsidiary, line by line. A renegotiation starts from the invoiced history. Between 1 and 7% of margin recovered on the scope analysed: that is the order of magnitude observed, and the diagnostic measures it on your own data before any commitment.
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 to install a bundle or deploy a SuiteScript in NetSuite?
No. Zylio reads saved search exports scheduled by your administrator, or queries the REST API with a role limited to read access. Nothing is installed in your account, no script is deployed, no workflow is modified. Your NetSuite releases happen without us.
How are several OneWorld subsidiaries handled?
The scope is set during scoping, subsidiary by subsidiary. Zylio reads the subsidiary of each transaction, reconciles the same vendor and the same item across subsidiaries, and applies the contract that governs: group agreement or local terms. Prices become comparable from one subsidiary to the next, in one currency or several.
Does the result of the control go back into NetSuite?
Zylio never writes into NetSuite. 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 with you, in your tool.
What if our contracts and rate cards are not in NetSuite?
That is the general case. You hand over contracts, price schedules, amendments and rate cards as PDFs, by file drop or dedicated mailbox. The Capture agent reads them line by line, including schedules of several thousand lines, and Compliance checks them against the bills read in NetSuite.
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.
- Order, receipt and invoice matchingLine-level matching with your tolerances, beyond the ERP three-way match.
- Compliance with your negotiated pricesChecking every invoice against the contract, the price schedule and the price list.
- See Zylio on a NetSuite 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