Zylio integration for Microsoft Dynamics 365: your invoices checked against your agreements, with no write

Environments

Finance & Supply Chain Management or Business Central: two products, one way of reading

Dynamics 365 covers two very different ERPs. Finance & Supply Chain Management serves multi-entity groups, with its legal entities, procurement categories and trade agreements; Business Central serves mid-sized companies, with its purchase documents, vendor cards and purchase prices per item. Many groups run both: headquarters on Finance, subsidiaries on Business Central, and vendor master data that never talks to each other.

Zylio reads both the same way, through the same channels, and reconciles what they do not reconcile between themselves: the same vendor under two codes, the same item under two references, the same framework contract applied differently from one entity to the next. Dynamics remains the source of truth for your transactions; Zylio is the control layer placed alongside it, which checks those transactions against the agreements you signed.

Connection mode

Data entities, OData or export: how the data arrives

On Finance & Supply Chain Management, the most common channel is the data entity export: your administrator schedules, from the data management framework, a recurring export of the purchasing entities (orders, receipts, invoices, trade agreements, vendors) to a storage location or an SFTP server. Zylio reads it. It is a standard mechanism of the product, requiring neither development nor any new right beyond the export itself.

When you prefer more frequent reads, the OData endpoints of Finance or the Business Central APIs are opened in read mode to an application account limited to the agreed scope. On Business Central, a periodic export of purchase documents and vendor cards is also enough. Both routes feed the same analysis and leave the same trace: every value stays linked to the export or the query it came from, with its date.

Documents that do not live in Dynamics (contracts, amendments, price schedules, rate cards, invoices received outside the circuit) arrive through a dedicated mailbox, a file drop or a scan. That is often where the negotiated price sits: Dynamics trade agreements reflect what was entered, not always what was signed. The Capture agent reads these documents line by line, including schedules of several thousand lines, and links them to the vendor and entity concerned.

Mechanism

What is checked against what, and the evidence returned

Native Dynamics matching compares the invoice with the order and the receipt, with global tolerances. It does not know whether the order price complied with the framework contract, whether the volume discount for the tier reached this quarter, across entities, was applied, or whether the price revision the vendor invokes was due on that date and on that index. Zylio places next to every invoiced line the contract, price schedule or amendment that applies, on that date, for that vendor and that entity, and applies your tolerances per vendor and per category.

Every discrepancy is raised qualified (price, quantity, unit, discount, revision, off-contract, duplicate, credit note never applied), 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, and the same case produces the same decision in six months, because the rules are applied deterministically.

The contract clause and the invoice line, highlighted side by side.

For your teams

What changes for accounts payable, procurement and management control

Accounts payable stops handling pending invoices one by one in the dark: each one arrives with its diagnosis and its document. Procurement gets the actual compliance of what was invoiced against what was negotiated, entity by entity, line by line, 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.

Management control, for its part, finds its figures in its own tools: qualified discrepancies, contract coverage rates and pending credit notes export to Power BI, every value staying linked to the lines that make it up and to their source document. A variance between the budget of a cost line and what was invoiced is then explained by price, volume or mix, not by intuition. Missing data is declared as such, never estimated.