Service entries.
The contractor submits their estimate in a portal, the platform validates it against a checklist, the supervisor approves or rejects — and on approval the entry sheet is created in your ERP.
Four steps, from portal to your ERP.
Contractor portal
The contractor submits their estimate with its evidence: the record, the period's progress, the photos. No emails, no shared folders.
Checklist validation
The platform validates the estimate against the mandatory checklist. Until it's complete, the record doesn't move forward.
Approval with context
The supervisor approves or rejects with the service history, the breakdown and the flags in view. A rejection goes back to the contractor with the reason documented.
Entry sheet in your ERP
On approval, the entry sheet is created in your ERP, against the purchase order and its line item.
Controls that today don't exist.
Six controls on every estimate. The flags are advisory: they flag, they don't block — the facilitator decides.
Mandatory, configurable checklist
Your team defines the checklist per service type. Until it's complete, the record can't be approved.
Line-by-line breakdown
Concept, unit, quantity and unit price, set against the last approved estimates of the same service. The line gets compared, not just the total.
Amount-out-of-pattern flag
When the estimate exceeds the service's history above a configurable threshold, the system marks it for review.
Reused-photos flag
The system compares the progress photos with those already uploaded for the same service and marks the similar ones, with the reference to which.
Segregation of duties
Whoever submits doesn't approve; whoever approves doesn't key in the entry. Roles are separated by design, not by habit.
Complete audit log
Every step lands in the log, with owner, date and reason. The approval can be reconstructed afterward.
The entry sheet, in your system.
The approval lands where your operation already works. The definitive connector to your ERP is implemented at go-live, as part of the project.
On approval, the service entry sheet is created in your SAP (ML81N), against the purchase order and its line item.
The service receipt is recorded in your Oracle instance when the record is approved.
The approval is reflected in Coupa, referred to the corresponding purchase order.
Without a connector, the approved record is delivered with its breakdown, ready to key into your system.
The detail, chapter by chapter.
Service entries is a solution of the Vigía Legal platform. It can be contracted on its own or together with REPSE Compliance and Foreign trade — on the same portal and the same contractor roster.
From the portal to the entry sheet, on your documents.
Send us a contract and a sample estimate from one of your contractors. We'll show you the full flow: the checklist, the approval with context and the entry sheet.