Every draft goes through human review
AI drafts, summarizes, and proposes, your compliance officer decides. No suggestion becomes a decision without a human signature.
AML/CFT compliance for Mexico
The compliance operating system for regulated entities in Mexico.
KYC/KYB, watchlist screening, transaction monitoring, case management, and regulatory reporting (SITI AML/CFT) on a single multi-tenant platform, with supervised AI that never decides for you.
LFPIORPI · CNBV-UIF general provisions · Mexico
Built hand in hand with AML compliance experts from financial institutions and designated vulnerable-activity businesses.
On Mexico's LFPIORPI and the general provisions of the CNBV-UIF
Platform
One system, seven fronts of compliance.
It's not an alert tool on steroids: it's the full AML operation, from customer onboarding to the regulator's acknowledgment, in one place.
Work queue
Everything that needs attention, prioritized.
Live tenant KPIs, alerts with SLAs, active cases, pending approvals, and recent audit activity. Your compliance officer knows what to review today without opening ten tabs.
🔎 Go to… · search subject, alert, case
◆ PlatformUDGood morning
A prioritized, scoped view of the tenant. Each module loads its records on open.
1,028
Operations monitored
98%
SLAs on time
14
Cases in progress
100%
Obligations on track
My queueAllTodayPriority✕ Usuario
⚠
Triage: Restricted foreign third party with originated customers
third_party_risk · p1
⚠
Triage: Pass-through behavior
transaction_monitoring · p1
⚠
Triage: Transaction outside expected profile
transaction_monitoring · p1
⚠
Triage: Vulnerable activity above LFPIORPI reporting threshold
regulatory_obligation · p1
⚠
Triage: Transactions in high-risk geography
transaction_monitoring · p1
Pending approvals2
Case approval
Hit on the Blocked Persons List (LPB)
Requested by Usuario Demo
Open reviewCase approval
Hit on the Blocked Persons List (LPB)
Requested by Usuario Demo
Open reviewTenant pulse
3,300
audit events
100%
chain intact
42
customers reviewed
100%
obligations on track
+ Manual alertLoad transactions
Customer 360 · Third parties
The complete file in a single view.
Individuals, companies, trusts, and foreign parties, with their identity, risk, transaction activity, list hits, and documents in one Customer 360. Third parties and counterparties held to the same rigor.
🔎 Go to… · search subject, alert, case
◆ PlatformUDSummaryIdentityRiskTransactionsDocuments
Financiera SOFOM S.A. de C.V.
Company · SOFOM E.N.R.
Risk score
72High
Component breakdown
Economic activity / line of business+18
Geography (customer + beneficiaries)+15
Ownership structure / UBO+12
PEP status+6
Age / incorporation+9
Lists & screening
LPBNo match
PEPPEP beneficiary
OFAC / UNNo match
Alerts · Screening · Monitoring
Signals that arrive explained, not as raw JSON.
Screening against the Blocked Persons List (LPB), PEPs, and sanctions (OFAC/UN), transaction monitoring with four-eyes-approved rules, and a unified alert queue where every trigger is written in plain language.
Cases · Evidence
The case as the evidentiary hub.
Every investigation gathers alerts, documents, information requests, and decisions into one traceable file, ready to support a disposition before the regulator.
Obligations · Operation reports
From obligation to acknowledgment, without leaving the system.
A regulatory calendar with LFPIORPI deadlines, a queue of operations pending report, and generation of regulatory operation reports (SITI TXT) validated field by field.
Risk-Based Approach
Configurable matrices, not spreadsheets.
Edit the institutional and customer risk matrices with their weights, indicators, and mitigants; watch inherent risk, residual risk, and control-driven reduction update live, with the RBA methodology (CNBV 2019) documented inside the editor.
🔎 Go to… · search subject, alert, case
◆ PlatformUDCustomer matrixEntity matrixCatalogsRisk rulesMonitoring rules
Edit matrix · customerCustomer classification, AVISA v1.0SaveCancel
Customer score
8.9of 100Low
Level & decision
Low
Due diligenceSimplified
Composition
8 factors
Each factor’s contribution to the score · section weight × factor weight × intensity
Subject type1.2
Economic activity / line of business1.8
Geography (customer + beneficiaries)1.6
PEP status0.7
Lists & adverse media0.8
Ownership structure / UBO1.3
Age / incorporation1.0
Source of funds / wealth1.1
Data hub · Quality
Import, validate, and extract with measurable quality.
Bulk import with templates, data-quality checks, and traceability for every load. Data comes in clean or it stays out.
The automated system, end to end
From signal to report, without leaving the system.
Here's how an unusual transaction becomes a regulatory operation report, with four-eyes governance at every step.
Monitoring detects and explains.
A customer exceeds their expected transaction profile. An alert opens with the trigger spelled out in plain language, rule, threshold, and the operations involved, not an error code.
The alert becomes a case.
The analyst escalates the alert to a case: evidence, information requests to the customer, and investigation notes all live in one traceable file.
Four-eyes-governed closure.
The disposition, reportable or not, goes through a second reviewer. Every decision is recorded in the tamper-proof audit log with who, when, and why.
The file goes out validated, with acknowledgment.
The operation report is generated field by field against the SITI specification, validated before submission, and the acknowledgment is tied back to the file in the regulatory calendar.
🔎 Go to… · search subject, alert, case
◆ PlatformUDTransaction monitoring
The customer's series vs. their expected profile, the spike fires the alert.
Monthly amount (MXN)
Red flags
+380% spike over the moving average
Concentration in a high-risk counterparty
Structuring below the threshold
Risk-Based Approach
A real RBA, not a box you tick once.
Parametrize the customer and institutional matrices with weights, indicators, and overrides, each with its own justification; the assessment recalculates live across your portfolio, and any change goes through four-eyes approval before it takes effect.
- compliance modules you can enable per tenant
17 - compliance modules you can enable per tenant
- Mexican regulatory regimes covered
9 - Mexican regulatory regimes covered
- versioned policy packs for Mexico
6 - versioned policy packs for Mexico
🔎 Go to… · search subject, alert, case
◆ PlatformUDCustomer matrixEntity matrixCatalogsRisk rulesMonitoring rules
Edit matrix · customerCustomer classification, AVISA v1.0SaveCancel
Customer score
8.9of 100Low
Level & decision
Low
Due diligenceSimplified
Composition
8 factors
Each factor’s contribution to the score · section weight × factor weight × intensity
Subject type1.2
Economic activity / line of business1.8
Geography (customer + beneficiaries)1.6
PEP status0.7
Lists & adverse media0.8
Ownership structure / UBO1.3
Age / incorporation1.0
Source of funds / wealth1.1
Supervised AI
AI that assists. Never decides.
AVISA PLD puts AI where it speeds your team up most, drafting, context, cited regulatory criteria, and keeps the decision where the law requires it: with your compliance officer. AI speed, human judgment.
Four eyes on every sensitive approval
Case closures, dispositions, and rule changes require a second reviewer. Governance is not optional, it lives in the workflow.
An auditable record of every suggestion
What the AI proposed, who accepted or corrected it, and when, all captured in the log. The regulator sees the reasoning, not a black box.
Security and audit
Evidence that holds up before regulators.
Tamper-proof audit log
Every event is sealed into a hash chain with integrity anchors, verifiable in seconds. Your evidence is always intact and ready to prove it.
Multi-tenant with real isolation
Each institution lives in its own data space, with users pinned server-side. No leakage between tenants.
Four-eyes governance
Sensitive decisions, closures, risk overrides, rule changes, require a second approver, with quorum and recusal.
Retention and controlled access
Role- and field-level access control, document retention policies, and a sealed file ready for inspection.
Supported regimes
Built for Mexico's regulated entities.
It's not a generic product in translation: each regime carries its own obligations, thresholds, and reporting formats before the CNBV, UIF, or SAT.
- Banks
- SOFOM
- SOFIPO
- IFPE
- ITF
- FX houses
- FX exchange centers
- Money transmitters
- Vulnerable activities (LFPIORPI)
Compliance that meets the CNBV bar.
Banks, SOFOMs, SOFIPOs, IFPEs, ITFs, and FX houses operate under the general AML/CFT provisions. AVISA PLD ships that regime ready to go, not a generic product you have to adapt.
Institutional and customer RBA
A risk matrix by product, customer, geography, and channel, with differentiated classification and due diligence following the CNBV methodology.
UIF reporting via SITI
Relevant, unusual, internal-concern, and international-transfer operations, generated and validated for SITI with a traceable acknowledgment.
Compliance structure
Compliance officer, committee, training, and audit, with traceable evidence and four-eyes approvals at every ceremony.
Monitoring and lists
Screening against the LPB, PEPs, and sanctions (OFAC/UN), plus transaction monitoring with approved rules and per-regime thresholds.
Regimes covered
BanksSOFOM (regulated / non-regulated)SOFIPOIFPEITFFX housesCredit unions
LFPIORPI without spreadsheets or a scramble on the 17th.
Real estate, virtual assets, precious metals and jewelry, vehicles, notaries, leasing, and more identify clients, build the file, and file their reports with the SAT. AVISA PLD automates it end to end.
Threshold identification (UMA)
Recognizes when an operation crosses the identification or reporting threshold, measured in UMA, and requires the file before proceeding.
SAT filings on the 17th
Generates and validates the monthly filing in the official SPPLD format, with an acknowledgment tied to each operation and its file.
Single file and KYC
Customer identification, ultimate beneficial owner, and documents, with custody and retention as the law requires.
Activity catalog
The Article 17 vulnerable activities, each parametrized with its own threshold and filing frequency.
Activities supported
Real estateVirtual assetsMetals and jewelryVehiclesNotariesArtworkLeasingDonationsValuables transport
Public-facing surfaces
What your customers see is part of compliance too.
Whistleblower channel
AVISA PLD
New reportTrack
An anonymous report keeps the authenticated identity in a sealed vault. Only an authorized, audited break-glass action can reveal it.
ExternalCustomers, operations, counterparties, or leads tied to third parties.
InternalEmployee conduct, controls, authorizations, or undue pressure.
Category
Suspicious customer or operation
Initial priority
By category
AnonymousThe identity is encrypted and kept out of normal views.
IdentifiedThe identity is tied to the file under confidentiality.
Account of events
Describe what happened, who was involved, dates, amounts, accounts…
Submit report
AVISA PLD records a reference, canonical hash, and audit for every channel event.
Whistleblower channel
Your reporting channel, under your brand.
A white-label link where your employees and staff report anonymously or on the record. Every report enters the triage flow and can escalate to a case, fully traceable.
AVISA · Identity
Identity verification
Hi. We'll guide you to verify your identity in a few minutes.
Here's what we'll do
• Accept the privacy notices
• Upload your government ID
• Take a selfie
Have ready
📄 A valid government ID (INE or passport)
Start
Your data is processed under Mexico’s LFPDPPP. Secure connection.
Identity verification
Frictionless KYC for your end customer.
Capture flows configurable by customer type: the prospect verifies from their phone, you review, and the file is sealed. Invite, capture, review, no email with PDFs.
For integrators
A public API per regime, documented.
Watchlist screening, customer intake, and file lookups over an API with scoped keys. The spec is narrowed to your regime: your team only sees the endpoints that apply to your operation.
View the API docs →POST /api/v1/screening
{
"name": "Empresa 1 S.A. de C.V.",
"rfc": "XAXX010101000"
}
HTTP/1.1 200 OK
{
"matches": [
{
"list": "LPB",
"confidence": 96,
"requiresReview": true
}
]
}