REPSE data for your Coupa flow, via API.
There is no native Coupa connector on this page: the connection is made over the Vigía API. Your IT team or procurement partner consumes RFC, REPSE validity, documents and periods. Public proof of endpoints is in the site's integration resource —not only behind a demo—.
Your team or partner, on the Vigía API.
A generic example: an invoice or purchase-order approval step in Coupa calls Vigía Legal by RFC. Vigía responds with REPSE status and the file context for the period. Release, escalate or hold stays in your workflow policy. This page does not claim automatic PO or payment blocking as a shipped native connector.
Query (pull)
Documented in the public resource: the flow can query status by RFC (`GET /api/v1/providers/{rfc}/status`) and ask for an invoice or PO verdict (`POST /api/v1/decisions/invoice` · `/po`).
Webhook (push)
Also documented there: on invoice stage changes Vigía emits `invoice.stage_changed` (signed webhook). Pull and webhook coexist; they are not exclusive.
Payment hold
Optional and off by default. By default Vigía notifies; it only holds payment in Accounts Payable if you turn that on.
From RFC to the Accounts Payable decision.
An illustration without naming clients. Path and typed-reason detail is in the resource linked below; this page does not duplicate it.
Vendor by RFC
Your Coupa flow sends the RFC. Vigía Legal responds with compliance status and file documents/periods.
STPS registry: documented frequency
At vendor onboarding, then every day; if registration is not valid, every few hours. Not an official API and not real time.
Your Coupa workflow decides
Procure-to-Pay and Accounts Payable apply the policy you configure. Any hold inside Vigía, if you use it, is optional and starts off.
Vigía Legal reduces the risk of moving an invoice forward without seeing the REPSE file. It does not guarantee or eliminate joint-and-several liability.
Read the resource before the demo.
The article "Integrate REPSE with Coupa, Ariba, SAP and Oracle" on /recursos documents the query (pull) paths and the stage webhook on the site. Use it to assess technical fit without waiting for a demo. The full OpenAPI spec lives inside the application and is not published as a file in this marketing repository.
Review the resource and, if needed, book the demo.
Start with the public resource linked above (pull and webhook documented). The demo is for seeing the answer on your roster; it is not the only place where path documentation exists.