Approved is not the same as verified.
The contractor uploads every estimation — the service record, the HES, the period's progress — with its evidence. Vigía Legal puts it in front of the facilitator with the mandatory checklist, the same service's history in view, and flags that surface whatever deserves a second look: an amount out of pattern, a reused photo. On approval, the record travels to your SAP and the vendor invoices with the document number it returns; every step is recorded.
The record says it's done. At what price?
Most estimations get approved against a contract that lives in another folder, and without seeing what was already billed for the same service. An advance charged twice, an inflated line item or a unit price that went up without explanation slip through — not for lack of judgment, but because whoever approves doesn't have the pattern in front of them.
And the evidence is rarely compared: reusing a previous period's photo to justify the new one is easy, and by hand it's nearly undetectable. The overrun and the reuse surface late, in the reconciliation — once the payment is already out.
Every input to the decision, in one view.
Estimation in context
Purchase order and line item, period and contract in one view, with this estimation's amount set against what has already been billed for the same service.
Unit-price breakdown
Concept, unit, quantity and unit price of the last three approved estimations of the same service, in view while the new one is reviewed.
Amount-out-of-pattern flag
The system marks for review any estimation above the service's 12-month high by more than a configurable threshold. It's a heads-up, not a stop.
Reused-evidence flag
The system compares the progress photos with those of the same service. It flags repeated or near-identical ones, even rescaled or with different brightness. It doesn't verify authenticity. The comparison can be reinforced with vision models.
It flags, it doesn't block. The facilitator decides.
The flags are advisory: they surface the context and mark what's doubtful, they never stop the approval. What does gate it is the mandatory checklist — until it's complete, the record can't be approved. A rejection returns it to the contractor with the reason documented. The vendor invoices with the ERP document number, which only exists once the record is approved and posted. Every step is in the audit log, with owner and date. The system flags; your team decides.
From the approved record to the document number.
On approval, the record travels to your SAP S/4HANA through the OData service and comes back with the document number. The vendor sees it in the portal and is told they can now invoice. The connector is set up during onboarding and tested first in your quality environment.
Maintenance order closed
Before review, the facilitator confirms the maintenance order is closed. The confirmation lands in the log with who and when.
Retry without duplicates
If the ERP fails, the approval stands. On retry, the system first checks whether the document already exists, so it isn't created twice.
Manual capture, segregated
Without a connector, the approved record waits in a capture queue for Procurement. Whoever approved it can't record its number.
Estimates in progress
A report groups every open record by purchase order, with the subtotal: the money committed that doesn't have a document number yet.
See the control running on a real estimation.
Send us a contract and a sample estimation from one of your contractors. We'll show you the review with the history, the breakdown and the flags — on your own documents.