--- title: "Vigía Legal + Oracle — REPSE data for your Accounts Payable flow · Vigía Legal" source: https://www.vigialegal.mx/en/plataforma/integraciones/oracle language: en site: "Vigía Legal" --- P.06 Integration · Vigía Legal + Oracle # REPSE data for your Oracle flow, via API. Vigía Legal does not ship a native Oracle connector. It exposes, over the API, each vendor's compliance state —RFC, REPSE validity, documents and file periods— so your IT team or ERP partner can consume it from Fusion Cloud, ERP Cloud or another Oracle instance. How your Accounts Payable workflow uses that answer is yours to define. Vigía API · your team or partner builds the integration 01 Who builds the integration ## Your team or partner, on the Vigía API. The pattern is the same as with any procurement system or ERP: Vigía Legal answers compliance questions; whoever runs Oracle decides where to call and what to do with the answer. A generic example: an invoice-approval process in Accounts Payable checks the vendor's status by RFC before releasing payment; if the file is not in good standing, the workflow escalates or holds according to the policy you configure. Vigía does not itself block purchase orders or payments inside Oracle. ### What Vigía exposes Vendor RFC, REPSE status, file documents and related periods. The public STPS registry is queried when the vendor is onboarded, every day, and every few hours if the registration is not valid. Not real time and not an official authority API. ### What you build The call from your Oracle instance, the mapping to your supplier master and the business rule in your workflow. Your implementation partner can do it on the same API. ### Payment hold Optional and off by default. By default Vigía notifies; it only holds payment in Accounts Payable if you turn that on. 02 Generic path example ## From RFC to the Accounts Payable decision. An illustration without naming clients or real instances. Endpoint, stage and webhook detail lives in the technical resource; this page does not duplicate it. Step 01 ### Vendor identified by RFC Your Oracle flow sends the vendor's RFC. Vigía Legal responds with compliance status and the file context for the period. Step 02 ### STPS registry: documented frequency At vendor onboarding, then every day; if registration is not valid, every few hours. If the product exposes the date of the last query by RFC, that is the date Accounts Payable should read —not a real-time promise—. Step 03 ### Your workflow decides With the typed answer, Accounts Payable releases, escalates or holds according to the policy you configure in Oracle. Any hold inside Vigía, if you use it, is optional and starts off. Vigía Legal reduces the operational risk of paying without seeing the file. It does not guarantee or eliminate joint-and-several liability; it leaves a diligence trail for when STPS or SAT asks for it. 03 More technical detail ## Without duplicating the integration resource. If you need the payment-gate call map, invoice stages and the role of Coupa, Ariba, SAP and Oracle in one thread, read the dedicated resource. This page only sets the frame: Vigía's API, an integration built by you or your partner, compliance data for Accounts Payable. [Read: Integrate REPSE with Coupa, Ariba, SAP and Oracle →](https://www.vigialegal.mx/en/recursos/repse-integracion-coupa-ariba-sap-oracle) → Let's talk ## Review the API with your IT team. In the demo we show what Vigía Legal returns by RFC and how that answer fits an Accounts Payable flow. The OpenAPI reference lives inside the application; if you want to review it before signing, ask for it in the conversation. [Request a proposal](https://www.vigialegal.mx/en/contacto) [Request a demo](https://www.vigialegal.mx/en/contacto?intent=demo) --- Fuente / source: https://www.vigialegal.mx/en/plataforma/integraciones/oracle Guía para agentes: https://www.vigialegal.mx/llms.txt · Índice: https://www.vigialegal.mx/sitemap.xml · Contacto: contacto@vigialegal.mx Cualquier URL de este sitio responde en Markdown con `Accept: text/markdown` o agregando `.md`.