Mexico’s PSM registry after CTA: what filings still matter

Mexico’s Public Registry of Commerce still runs through state-level implementation. Look up the same company twice and historical coverage can shift depending on which Registro Público de Comercio office actually digitised its books. That causes friction in cross-border diligence work.

Mexican entities turn up constantly in North American ownership structures, though plenty of compliance teams still rely on stale aggregator exports instead of checking Secretaría de Economía source records. The distinction that matters for legal and AML analysis sits between what the PSM exposes under commercial registration law and what lives elsewhere under tax, banking, or beneficial-ownership regimes.

Mexico does not maintain a public UBO register comparable to the EU access model that existed before C-601/20. If you are testing ownership under OFAC’s 50% rule or UK sanctions guidance, the Registro Público de Comercio rarely settles the question by itself.

Querying the Registry via MCP

OpenRegistry exposes the Mexican register through MCP, which means queries run against the registry flow directly. No browser automation needed. The MX jurisdiction is active on the server.

A typical search_companies request looks like this:

{ "jurisdiction": "MX", "query": "GRUPO BIMBO" }

For existence checks, merger history, or authority review, get_company_profile tends to matter more:

{ "jurisdiction": "MX", "company_number": "N-2023045678" }

Common Fields in Responses

Response structure changes depending on the upstream office, though several fields appear regularly under jurisdiction_data. You will usually see:

• razon_social
• folio_mercantil
• estado
• fecha_constitucion
• capital_social
• objeto_social

administradores appears often too. That last field gets misread all the time. Appointment as administrador único or board member establishes registered authority. It does not establish beneficial ownership under FATF-style control analysis. In deposition work and transactional disputes, that distinction carries weight.

Notarial Metadata and Filing Sequences

Mexican filings also come with quirks around notarial intervention. Constitutive acts and amendments are commonly tied to protocolo numbers and notary references rather than the tidier filing identifiers seen in UK or Nordic registers. When tracing authority through mergers or capital increases, preserving the original notarial metadata matters.

list_filings helps reconstruct the sequence:

{ "jurisdiction": "MX", "company_number": "N-2023045678" }

Depending on the office, filing descriptions may expose constitutive deeds, merger registrations, bylaw amendments, liquidation entries. Some are sparse. Others contain surprisingly detailed references pulled from older index systems.

A few filings expose both inscription dates and protocol execution dates. Those dates are not interchangeable. Under Mexican commercial practice, the execution date before the notary and the later registration date can change priority analysis.

Limitations for Beneficial Ownership

The register also does not solve beneficial-ownership diligence on its own. Mexico’s AML framework under the Ley Federal para la Prevención e Identificación de Operaciones con Recursos de Procedencia Ilícita imposes separate reporting duties for vulnerable activities, though those records are not publicly exposed through PSM queries.

That limitation shows up fast when foreign counsel try mapping Mexican entities into Corporate Transparency Act workflows. FinCEN BOI reporting under 31 CFR 1010.380 is a US federal obligation. It does not create reciprocal public access to Mexican ownership records.

Teams still combine registry material with shareholder registers, notarised corporate books, sometimes local counsel certifications. OpenRegistry does not infer ownership or rebuild hidden control chains. The MX integration returns upstream registry fields exposed by the source office. Nothing more.

Officer Review and Historical Coverage

For officer review, get_officers can help establish who held registered authority at a particular point in time:

{ "jurisdiction": "MX", "company_number": "N-2023045678" }

Results vary sharply by state office and filing depth. Some entities expose detailed officer names with appointment dates attached. Others expose little beyond current management references pulled from the latest inscription.

Historical coverage stays uneven. Older filings sometimes survive only as scanned ledger pages or partial index entries. Some registries digitised aggressively during the 2010s. Others still expose fragmented archives with obvious gaps. If a matter depends on pre-digital amendments, expect missing pieces. Direct registry access helps more than polished aggregator summaries in those cases.

Document Retrieval

For sanctions analysis or acquisition diligence, counsel often need the exact wording attached to a filing. A translated summary can miss whether a capital increase was authorised, merely proposed, or recorded subject to conditions.

fetch_document retrieves source material where the registry office exposes it:

{ "jurisdiction": "MX", "document_id": "DOC-884421" }

Document availability is inconsistent. Some offices expose PDFs directly. Others return only metadata or filing references. A few still point back to manual retrieval workflows. The evidentiary distinction matters here.

Conclusion for Practitioners

The Mexican commercial register establishes notice and registration status for corporate acts. It is not a complete AML transparency system. After C-601/20, many lawyers became more careful about conflating commercial registration with beneficial-ownership disclosure. Mexican registry work demands the same discipline.

For KYB tooling, the useful part of the MCP model is that an assistant can query the register live during a workflow instead of relying on cached exports from the legacy paid databases. The source remains the registry office of record.

OpenRegistry’s MX endpoint is available through the remote MCP server at https://openregistry.sophymarine.com/mcp.