ıVigíaLegal
P.06The platform · Integrations

If REPSE lapses, the PO doesn't ship.

Vigía Legal connects bidirectionally with your procurement system or ERP. When a vendor loses validity, the block propagates: no new POs, no processed invoices, until the file is in good standing again.

vigialegal.mx / integrations / canvas
OAuth2 · API REST · Webhooks
Regulatory sources
  • REPSE
    STPS Registry · REPSE
    Certificate validation 4128/2022
  • SAT
    SAT API
    32-D, NOM-151, e.firma
  • IMSS
    IMSS API · IDSE
    Opinion + SISUB + ICSOE
  • INFON
    INFONAVIT API
    Opinion + RCV payment
Vigía
Core
Chain of custody + NOM-151 seal
ERPs and procurement
  • COUPA
    Coupa Suite
    PO block on lost validity
  • ARIBA
    SAP Ariba
    Vendor sync + REPSE status
  • ORACLE
    Oracle iSupplier
    Score per vendor
  • S4
    SAP S/4HANA
    Status webhook · OData
Bidirectional sync · 4 production connectorsSSO · Azure AD · Okta · Google Workspace
01Production connectors

Four connectors, one vendor truth.

Coupa Suite

Production

Supplier Information Management + Procure-to-Pay

PO block, payment hold, compliance scorecard

SAP Ariba

Production

Supplier Lifecycle & Performance (SLP)

Vendor sync, REPSE status as qualification flag

Oracle iSupplier

Production

Procurement Cloud

Score per vendor, validation prior to PO release

SAP S/4HANA

Production

ME31N / MIRO · OData

Bidirectional webhook, vendor master data sync

02How it connects

OAuth2, real-time events, no data migration.

A

OAuth2 + scoped permissions

Only the necessary permissions: read vendor master, read/write compliance flags, reject PO. No access to financial data.

B

Real-time events

Outbound webhooks when a vendor status changes: valid → expiring → expired → blocked. Your ERP reacts in under a second.

C

No migration

The vendor master stays where it already lives. Vigía consults and enriches; it doesn't ask you to replace your procurement system or replicate master data.

Enterprise SSO
Azure AD · Okta · Google Workspace
Vendor identity
Magic link · SAT e.firma
Data
Mexico residency
SLA
99.9% · 24/7
03CFDI ↔ File ↔ AP

Payment is released when the file permits it.

When an expense CFDI lands in AP, Vigía already has the association: CFDI UUID ↔ Coupa PO ↔ vendor's REPSE file. AP doesn't have to search — the system shows "compliant" or "hold on expired document X". Payments to non-compliant vendors are blocked before they reach the bank.

Step 01

CFDI receipt

CFDI 4.0 UUID enters AP. Vigía consults the registry and matches it with the originating Coupa PO.

Step 02

REPSE validation

Checks the vendor status at the moment of payment: quarterly signed file, valid REPSE, positive opinions.

Step 03

Decision

Green: payment released. Amber: hold with remediable reason. Red: block. If there's a Legal-approved exception with validity, it passes.

Step 04

Audit log

Every processed CFDI is recorded with: UUID, amount, decision, rationale, actor, timestamp. Ready for SAT or STPS auditor.

→Let's talk

We connect your ERP in 14 days.

Guided deployment with your IT and procurement teams. Sandbox first, production after. Technical documentation and dedicated support during rollout.

Request a proposalBook a demo (30 min)