BPU compliance
BPU compliance: check that every invoiced unit price is the one in the schedule, revisions included
A unit price schedule (BPU in French procurement) sets the price of every service or supply, with its coefficients and revision rules. Zylio reads the schedule and its amendments, checks every invoiced line against the matching line on the service date, and shows you the gap with its proof. Public procurement, construction, maintenance: wherever the schedule governs.
The problem
Why a unit price schedule is so hard to enforce
The schedule is precise to the cent, on every line. That is exactly what makes it impossible to check by hand, invoice after invoice.
Hundreds of lines
A maintenance, cleaning or works schedule easily runs to several hundred prices, each with its own unit and description. Nobody has them in mind when approving an invoice, and nobody opens the schedule to check.
Revisions that stack up
Annual indexation, price amendment, surcharge coefficient for urgency or out-of-hours work: the applicable price depends on the date and the context of the service, not only on the line in the schedule.
Services outside the schedule
An invoiced line that matches no price in the schedule should be justified by an accepted quote or a works order. In practice, it often goes through with the rest, at whatever price the supplier chose.
Quantities to reconcile
The unit price is right, but the invoiced quantity exceeds the one on the purchase order or the signed measurement sheet. The gap is invisible at the level of the total, and the total is all anyone looks at.
Partial checks
For lack of time, a few invoices are checked, usually the largest. The small recurring jobs, where the gaps accumulate month after month, are never reread by anyone.
Traceability required
In public procurement as in front of a statutory auditor, you must be able to show what was checked, against what, by whom and when. Control by sampling cannot do that.
Where it applies
Public procurement, construction, recurring services: where the schedule governs
Three fields where the schedule is not a guideline but the contract itself, and where every invoiced line has to answer to it.
In a public call-off contract, the unit price schedule is a contractual document: every call-off order refers to it, every invoice must comply with it, and price revision follows the formula and the indices set out in the special administrative conditions. The public buyer must be able to justify every payment. An exhaustive, traceable check is not a comfort; it is an obligation.
In construction, the schedule meets progress statements: quantities actually executed and recorded on measurement sheets, unit prices from the schedule, surcharges provided for in the contract, additional works that should be covered by a works order or an amendment. Checking the statement against the schedule and the measurement sheet, line by line, is the only way to know what is due.
In the private sector, recurring services work the same way: multi-technical maintenance, cleaning, grounds, temporary staffing, transport. Dozens of invoices a month, each a few dozen lines, all supposed to follow a negotiated schedule. That is where small, repeated gaps end up weighing.
Call-off contracts, justification of payments, traceability.
How it works
What is checked against what, and the proof you see
The Capture agent reads the schedule whatever its format: PDF, spreadsheet, scan, image. It extracts every line with its reference, description, unit and price, together with the coefficients and revision rules that go with it. Amendments and revisions are attached with their effective date, so that the right price applies on the right date. Every value stays linked to the exact place in the document where it was read.
The Compliance agent then receives invoices and progress statements, read from your ERP exports or API, together with purchase orders and measurement sheets where they exist. For each invoiced line, it finds the schedule line, computes the expected price on the service date by applying revision and coefficient, then compares it with the invoiced price. It reconciles the invoiced quantity with the quantity ordered or recorded. A line with no match in the schedule is flagged as off-schedule.
Every gap is presented to you with its proof: the schedule line and the invoice line, highlighted side by side, the expected-price calculation and the amount of the difference. No gap is dropped silently; whatever matches no rule is raised, with its reason. You approve, dispute or close, and your decision is logged. Zylio issues no claim and contacts no supplier.
How a schedule of several hundred lines is extracted and verified.
The process
From schedule to control, in three steps
- 01
Digitise
You upload the schedule, its amendments and its revisions. They are read, structured and attached to the contract, with their effective dates. You review whatever was flagged as uncertain, each value next to its source.
- 02
Configure
Tolerances, special cases, handling of off-schedule lines, approval workflow and who decides what: the rules are adjusted with you, supplier by supplier if necessary.
- 03
Check and follow up
Every invoice is checked against the schedule in force on its date. You follow the compliance rate by supplier, recurring gaps and the status of settlements, from one dashboard.
What changes
What changes for the buyer and for the controller
Control becomes exhaustive. Every line of every invoice is checked against the schedule, not only the large ones, for 5% to 100% of your purchases, depending on the scope you choose and without adding headcount. Gaps on small recurring jobs, invisible at the level of the total, finally show up.
Gaps become quantified and defensible. On the scopes analysed, that is 1% to 7% of margin recovered on the scope analysed, with the schedule line and the invoiced line behind every euro. An off-schedule line is discussed with the quote that should have authorised it; an early revision, with the formula and its date; an excess quantity, with the measurement sheet.
Traceability is a given. Every check is logged: what was compared, against which version of the schedule, with what result and what decision. In front of an auditor, a statutory auditor or a public audit body, the answer is an export, not a reconstruction. And rereading time goes back to the teams: 15% to 45% of time returned, per FTE, depending on scope and data maturity.
One or two schedules and their invoices: what was paid outside them, line by line.
What we do not do
What schedule checking does not decide
Zylio blocks no payment on its own, rejects no invoice and writes nothing to the supplier: it presents you with the gap, its proof and its amount, and you decide. It does not touch your ERP, of which it only reads exports or the API. Your schedules and invoices are hosted in France, never shared between customers, never used to train a model. Every check and every decision is logged, in the order it happened.
Zylio investigates, people decide. A gap against the schedule is a proven fact, never an invoice blocked without you.
Hosting in France, ISO 27001 and SOC 2 Type II, full audit trail.
Compliance
Every invoice checked against your agreements.
Checks every invoiced line against what was negotiated: framework agreement, price list, rate schedule, amendment, discount terms, volume thresholds, indexation clauses.
A claim that is documented and enforceable against the supplier, not a hunch.
What Compliance detects
- Invoiced price higher than the negotiated price
- Revision outside its due date or on the wrong index
- Volume discount or tiered rate not applied
- Service outside the contract, item outside the catalogue
- Payment terms not honoured
- A one-cent discrepancy repeated across thousands of lines
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
What is the difference between BPU compliance and price list control?
The BPU is the contractual schedule of a contract: one price per service, fixed for a term, revised by a formula. A supplier price list is a reference list updated periodically, often for a whole catalogue. Both are checked, but not with the same rules; price list control has its own page.
How are invoiced lines that do not appear in the schedule handled?
They are flagged as off-schedule, with the invoice concerned and the amount involved. If an accepted quote or a works order justifies them, you attach it and they are checked against that document. Otherwise they remain a gap, to be disputed or settled as you decide, and your decision is logged.
Does Zylio handle index-based price revisions?
Yes. The formula, the reference indices and the effective date are extracted from the contract, then applied to compute the expected price on the date of each service, not on the invoice date. A revision applied too early, on the wrong index or with a wrong coefficient shows up as a gap, with the full calculation next to it.
Can the check be used in public procurement in front of an external audit?
Every check is logged with the version of the schedule used, the line compared, the result and the decision taken, by whom and when. That history is exportable at any time. It documents what was verified and how; the decision to pay remains that of the authorising officer or the department concerned.
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
The other situations handled by the Compliance agent
- Negotiated price complianceEvery invoiced line checked against the framework agreement, the rate schedule and the discount terms; the discrepancy costed and linked to its clause.
- Framework contract complianceCheck volumes, revisions, penalties and execution terms against the signed contract, and prove every gap.
- Check invoiced pricesThe invoiced price confronted with the negotiated price, line by line, with the gap quantified and the evidence ready to send.
- Framework contractsRead your framework contracts, check every invoice against the signed text and steer the execution of your agreements, with proof.
- Supplier price listsThe schedule of negotiated prices by reference and by period, checked against every invoice on the date of the line.
- The 3-week diagnosticWhat we measure on your schedules, and how it is billed.
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