--- title: "Vigía Legal + SAP — REPSE data for Accounts Payable in S/4HANA · Vigía Legal" source: https://www.vigialegal.mx/en/plataforma/integraciones/sap language: en site: "Vigía Legal" --- P.06 Integration · Vigía Legal + SAP # REPSE data for your SAP flow, via API. There is no native connector for SAP; the connection is made over the Vigía API. Your Basis team or ERP partner consumes, over that API, each vendor's compliance state —RFC, REPSE validity, documents and periods— from S/4HANA or another SAP instance. The Accounts Payable business rule is yours to define. Vigía API · your team or partner builds the integration 01 Who builds the integration ## No native connector; there is the Vigía API. There is no native connector for SAP; the connection is made over the Vigía API. A generic example: a check in Accounts Payable invoice verification calls Vigía Legal by RFC before authorizing payment. Vigía responds with REPSE status and the file context for the period. What SAP does with that answer —release, escalate or hold per your policy— is up to your flow. Vigía does not itself block purchase orders or payments inside SAP. Endpoints documented on the site live in the integration resource; a literal JSON request/response sample is not published in this repository. ### What Vigía exposes Vendor RFC, REPSE status, file documents and periods. Scheduled queries to the public STPS registry; never as "real time" and never as an official authority API. ### What you build The call from S/4HANA (or your middleware), the match to your vendor master and the condition in your workflow. Your SAP partner can implement 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. The endpoint, stage and webhook map lives in the technical resource; this page does not duplicate it. The OData service-entry sheet for service records is a separate topic, documented in the service-records platform pages. Step 01 ### Vendor by RFC Your SAP flow sends the RFC. Vigía Legal responds with compliance status and the relevant documents/periods from the file. Step 02 ### STPS registry: documented frequency At vendor onboarding, then every day; if registration is not valid, every few hours. Not an official STPS API and not a real-time query. Step 03 ### Your SAP workflow decides Accounts Payable applies 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 paying without seeing the REPSE file. It does not guarantee or eliminate joint-and-several liability; it leaves a diligence trail. 03 More technical detail ## Without duplicating the integration resource. For the API payment gate, invoice stages and the role of Coupa, Ariba, SAP and Oracle in one thread, use the dedicated resource. Here only the frame: Vigía's API, an integration built by you or your partner, 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 Basis team. In the demo we show what Vigía Legal returns by RFC and how it fits an Accounts Payable flow in SAP. The OpenAPI reference lives inside the application; ask for it if you want to review it before signing. [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/sap 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`.