If REPSE lapses, the PO doesn't ship.
Your procurement system or ERP asks Vigía Legal before issuing a purchase order or releasing a payment. If the vendor is out of compliance, the answer is hold or rejected, with the reason, until the file is back in good standing.
- REPSESTPS Registry · REPSEPublic Registry of Contractors, checked periodically
- SATSATCFDI, tax certificate, lists 69 and 69-B
- IMSSIMSS opinion · SISUBValidated automatically on upload
- INFONINFONAVIT opinionValidated automatically on upload
- GATEPayment gateYour Coupa, Oracle, Ariba or SAP asks
- HOOKSigned webhooksHMAC-SHA256 · within minutes
- FILEFile layoutsPOs in · payment out
- S4SAP S/4HANAService entry sheet · OData
Your ERP asks. Vigía Legal answers.
Payment gate API
RESTPOST /api/v1/decisions/invoice · /po
Your Coupa, Oracle, Ariba or SAP asks before issuing the PO or releasing the payment. Vigía Legal answers approved, hold or rejected, with typed reasons.
Signed webhooks
HMAC-SHA256X-Vigia-Signature
Your system learns within minutes that a vendor or an invoice changed status, without polling.
File layouts
LayoutPurchase orders in · payment out
Purchase orders come in by file or by API. The payment proposal goes out in your bank's layout.
Service entry sheet in SAP
ODataSAP S/4HANA
When a service record is approved, the service entry sheet is created in your SAP and the document number comes back to Vigía Legal. Set up during onboarding.
Scoped API keys, signed events, no data migration.
Keys with scopes
Each key declares what it can do: ask the payment gate, read vendor status, send invoices, load purchase orders. One key per integration; deactivating one leaves the others untouched.
Signed events
Vendor status changed, invoice on hold or released, stage changed, payment proposal exported, service record posted to the ERP. Each delivery is HMAC-SHA256 signed, with up to three attempts.
No migration
The vendor master and the purchase orders stay in your ERP. Vigía Legal receives what it needs to answer; it doesn't ask you to replace your procurement system.
Payment is released when the file permits it.
The vendor's invoice reaches AP. Vigía Legal matches it against the SAT, the purchase order and the REPSE file for the period; the order comes in by file or by API. Your team sees "compliant" or the reason for the hold. An invoice on hold doesn't reach the payment proposal. See accounts payable →
CFDI receipt
The CFDI 4.0 comes in through the portal or the API. Vigía Legal checks its status with the SAT and matches it with the purchase order it declares.
REPSE validation
Checks the vendor at that moment: valid REPSE, positive compliance opinions, complete file for the period.
Decision
Approved: it moves on to authorization. Hold: a reason that can be fixed. Rejected: it isn't paid. A Legal-approved exception with an expiry date releases the hold.
Audit trail
Every invoice keeps its UUID, amount, decision, reason, who and when. The evidence downloads as a PDF or ZIP for the SAT or the STPS.
Your quality environment first, production after.
Onboarding is done with your IT team: API key, signed webhook and, where it applies, the OData service-entry service. The API reference (OpenAPI) lives inside the application; to review it before signing, ask for it in the demo.