P.00The platform · Overview

Four disciplines,
one compliance file.

Vigía Legal unifies the four fronts of REPSE compliance — live compliance file, retroactive audit, early alerts and the payment gate for your ERP — under a single system that logs every action. Deployed in 30 days.

Chapter P.01Read →

Vendor portal

Magic-link with no passwords, drag-drop uploads, clear traffic-light status. Built so the vendor's accountant gets it in 30 seconds.

passwords · magic-link
0
Chapter P.02Read →

AI ingest

The vendor drops a ZIP. AI classifies every file against the 16 REPSE types, extracts folio, RFC and expiry. Zero forms.

per file · fine-tuned AI
0.7s
Chapter P.03Read →

Live compliance file per vendor

Every vendor maintains an audit-ready REPSE file: 16 critical + 12 optional documents, live status, monitored expiries, a log of every action.

documents covered
28
Chapter P.04Read →

Retroactive audit to 2021

Quarterly reconstruction of historical compliance from the entry into force of the REPSE regime. STPS can request five years: the report shows them quarter by quarter.

auditable years
5
Chapter P.05Read →

Alerts ahead of STPS

Notice 30 / 14 / 7 days before each expiry, by email to the vendor with a rising tone. What stays pending reaches the contract owner's dashboard.

early alerts
30→7d
Chapter P.06Read →

ERP integration

Your Coupa, Oracle, Ariba or SAP asks the payment gate over the API before issuing a PO or releasing a payment. Changes reach it by signed webhook.

gate · webhooks · layouts
API
Chapter P.07Read →

Role-based views

A specific view for each team: Procurement, AP, Tax, Legal, HSE and Internal Audit. One source of truth, six perspectives.

roles · six views
6
Chapter P.11Read →

Accounts payable

The supplier invoice comes in through the portal, is matched against the SAT, the REPSE file and the purchase order, walks the approval chain and leaves as a payment proposal in your bank's layout.

stages · intake to paid
5
01Operational workflows

Five workflows cover the entire vendor lifecycle.

From the moment a vendor enters the registry until offboarding. Each workflow has specific roles, decisions and deliverables — all recorded in the audit log.

Workflow F.01

Onboarding

Vendor registration, rule assignment by entity/contract/risk, portal invitation, initial upload, AI validation, release or block.

Workflow F.02

Renewal

Expiry alert, document update by the vendor, cross-revalidation, status update.

Workflow F.03

Pre-payment

CFDI received by AP, REPSE status check, decision: payment released / on hold with a reason / approved exception.

Workflow F.04

HSE control

Verification of reported personnel and DC-3 / NOM-035 validity before authorizing site access.

Workflow F.05

Exception

Justified request, Legal approval with SoD, time-bound validity, complete audit log, auto-expiry.

02Architecture

One source of truth for your vendor base. No Excel.

REPSE data is scattered: STPS portal, SAT opinions, IMSS contributions, SISUB, ICSOE, contracts on SharePoint, DC-3 evidence in local folders. Vigía Legal consolidates those sources into a single file per vendor, checked against the SAT and the STPS registry, with every action in the audit log.

Capture

OCR of documents, CFDI ingestion, portal sync

Validation

SAT checks (CFDI status, tax certificate, lists 69 and 69-B); periodic check against the STPS Public Registry of Contractors; SAT, IMSS and INFONAVIT compliance opinions validated automatically on upload

Evidence

Audit log that can't be edited from the application; per-invoice evidence in PDF and ZIP

Distribution

Payment gate API, signed webhooks and file layouts for your ERP

→Let's talk

Start where it hurts most.

Modular deployment: start with a single quarter, a single vendor segment, or the entire registry. In 30 days you have your first compliance file.