Anti-money laundering software (AML) and FIU filings

Q: What happens in months with no operations?

With one click the system creates the no-activity filing (Article 27 Bis of the LFPIORPI General Rules) for every branch that does not yet have a filing for the month, and generates its XML. It can also be scheduled to happen automatically every month.

Q: Did anything change with the July 2025 reform?

Yes. The reform published in the DOF on July 16, 2025 extended record retention to ten years, strengthened beneficial owner identification and toughened the late filing rule: after thirty days it is penalized as an omission. Fines range from 200 to 65,000 times the UMA.

Reform of July 16, 2025

The anti-money laundering law changed, and it changed toward more demands

The reform to the LFPIORPI published in the Official Gazette of the Federation (DOF) is the deepest since the law has existed. Four figures sum it up.

17

The deadline of each month

Filings are submitted no later than the 17th of the month following the operation that gives rise to them (art. 23).

10 years

Of record retention

The information and documentation supporting each vulnerable activity must be kept for at least ten years, in paper or electronic form (art. 18, sec. IV).

25 %

Beneficial owner

Anyone who holds the vote over more than 25% of the share capital counts as a beneficial owner and must be identified.

30 days

And it is already an omission

A filing that arrives more than thirty days late is no longer penalized as late, but as omitted (art. 53, sec. III).

The reform also introduced a risk-based approach, registration in the Registry of vulnerable activities and the ability to suspend operations with a customer. Compliance stopped being "upload a file once a month": it is proving, with evidence, that you identified, measured and reported.

Own work based on the current text of the LFPIORPI (Chamber of Deputies, last reform published July 16, 2025).

The problem

Six pains of the compliance officer

What happens every month in a company with several branches that carries out vulnerable activities.

Spreadsheets per branch

Each branch sends its Excel its own way, and someone puts them together by hand in the last week before the 17th.

Thresholds that move

Thresholds are set in multiples of the UMA, the UMA changes every year, and nobody keeps track of the six-month accumulation per person.

The rejected XML

One accent, one lowercase letter or a 17-character CURP and the portal rejects the whole file, when there is no time left.

The zero month that gets forgotten

A branch with no operations must also file. It is the easiest omission to commit and the one nobody checks.

Who is the real owner?

Representatives, attorneys-in-fact and beneficial owner scattered across ID copies and emails.

Ten years of evidence

When the inspection visit comes, you have to reconstruct operations from years ago, with the receipt of each filing.

A single branch without a filing for the month is an omission, and omission is the costliest infraction in the law: up to 65,000 times the UMA or 100% of the value of the operation.

The case

What it costs not to comply with the LFPIORPI

Fines are set in multiples of the daily UMA value, and falsehood in a filing is already a crime, even if by carelessness.

Up to $7.6 MFor omitting a filing, or 10% to 100% of the value of the operation if greater.

2 to 8 yearsIn prison for false, altered or illegible data in a filing (art. 62).

SuspensionOf operations with a customer while the proceeding is resolved (art. 54 Bis).

Infraction	Legal basis	Fine	In pesos (UMA 2026)
Omitting filings, or submitting them more than 30 days lateAlso taking part in prohibited cash operations (art. 32)	Art. 54, sec. III	10,000 – 65,000 UMA	$1.17 – $7.63 Mor 10 – 100% of the value of the act
Beneficial owner of commercial companiesObligations under arts. 33, 33 Bis and 33 Ter	Art. 54, sec. II	2,000 – 10,000 UMA	$234,620 – $1.17 M
Submitting filings late, within 30 daysArt. 53, sec. III	Art. 54, sec. I	200 – 2,000 UMA	$23,462 – $234,620
Filings without the requirements of art. 24Data of the obligated party, the customer, the beneficial owner and the operation	Art. 54, sec. I	200 – 2,000 UMA	$23,462 – $234,620
Failing art. 18 obligationsIdentify the customer, their activity and the beneficial owner, keep records for 10 years, register in the Registry	Art. 54, sec. I	200 – 2,000 UMA	$23,462 – $234,620
Not responding to requests from the authorityArt. 53, sec. I	Art. 54, sec. I	200 – 2,000 UMA	$23,462 – $234,620

Amounts using the 2026 daily UMA of $117.31 (INEGI, 2026); these are the legal ranges and the authority sets the amount for each case. The fine applies per infraction: ten branches without a filing are ten omissions. Article 55 allows no penalty, one time only, if the situation is spontaneously regularized before the inspection. Bars on a logarithmic scale.

Vulnerable activities

The thresholds for your line of business, preloaded and up to date with the UMA

Each activity in article 17 has a threshold to identify the customer and another to file the report. The system stores them in multiples of the UMA and recalculates the peso amounts when the UMA changes.

Activity	XML code	Identify from	Report from
Real estate leasingArt. 17, sec. XV · per month	ARI	1,605 UMA · $188,282.55	3,210 UMA · $376,565.10
Real estate: construction, development and brokerageArt. 17, sec. V	INM	Always	8,025 UMA · $941,412.75
Air, sea and land vehiclesArt. 17, sec. VIII	VEH	3,210 UMA · $376,565.10	6,420 UMA · $753,130.20
Precious metals, stones, jewelry and watchesArt. 17, sec. VI	MJR	805 UMA · $94,434.55	1,605 UMA · $188,282.55
Loans, credit and guaranteesArt. 17, sec. IV	MPC	Always	1,605 UMA · $188,282.55
Donations received by non-profit associationsArt. 17, sec. XIII	DON	1,605 UMA · $188,282.55	3,210 UMA · $376,565.10
Betting games, contests and rafflesArt. 17, sec. I	JYS	325 UMA · $38,125.75	645 UMA · $75,664.95
Service or credit cardsArt. 17, sec. II	TSC	805 UMA · $94,434.55	1,285 UMA · $150,743.35
Prepaid cards, vouchers and couponsArt. 17, sec. II	TPP	645 UMA · $75,664.95	645 UMA · $75,664.95
Reward wallets and cardsArt. 17, sec. II	TDR	645 UMA · $75,664.95	645 UMA · $75,664.95
Independent professional servicesArt. 17, sec. XI · accounts, companies, real estate, outsourcing	SPR	Always	When operating on behalf of the customer

Amounts using the 2026 daily UMA of $117.31. Thresholds are edited under Catalogs → Business lines and thresholds, and the "Recalculate" button brings them up to date with the current UMA. The system also includes the shielding XML format (BLI).

What it looks like

The month-end close at a glance

Screenshots of the platform running with fictitious demo companies and people; RFCs, CURPs and receipt numbers are blurred. Click any of them to see it larger.

admin/antilavado

Period dashboard. What has been captured, what remains to be sent and how many days are left until the 17th, by business line and by branch.

The month to reportBy default, the previous month, with the due date and the days remaining.
Pending to sendCaptured filings that have not yet gone into an XML, by activity and by branch.
Branches without a filingThose with nothing for the month, with the button to create their zero filing.

How it works

From customer to receipt, in five steps

The same routine every month, for all branches and all activities.

1

Identify

Register the individual, company or trust, with representatives, attorneys-in-fact and their branches.

2

Capture

The month's filing and its operations, with the form the activity dictates, or by upload from Excel.

3

Measure

Identification threshold, filing threshold, foreign currency and six-month accumulation per person.

4

Generate and validate

One XML per branch, validated against the official XSD; if something fails, you know the line and the reason.

5

File and acknowledge

It is uploaded to the SPPLD, the SAT receipt number is recorded and the filing is marked as sent.

Filings

All filings from all branches, in one list

Filters by activity, company, branch, month, year, priority, sent, accumulated and 27 Bis.
For each filing, whether it is subject to filing and whether it is subject to identification, calculated with the thresholds of its activity.
Regular and 24-hour filings, with the alert type from the official catalog.
Amending filings with the receipt number returned by the FIU and the description of the change.

admin/antilavado/notices

Filing record

The reported person, the other roles and their operations

Only persons registered at that branch can be reported: the file and the filing never contradict each other.
Beneficiaries, guarantors and other roles the activity requires, each with their own file.
The amount and VAT of the filing are calculated from the sum of its operations, never by hand.
A filing that has been sent is closed; reopening it is an explicit action and is recorded in the audit log.

admin/antilavado/notices/notice/11

Operations

The activity dictates the form, not a programmer

Each activity asks for exactly the fields of its format: property type, real folio, lease term, vehicle make and model, type of asset…
Payment method, monetary instrument and currency come from the official catalogs.
A cash payment above the threshold is stopped before it is saved.
Partial payments and in-kind payments for the activities that allow them.

admin/antilavado/notices/operation/11/11

FIU XML

The XML comes out validated, or it doesn't come out

The step that costs the most each month, turned into two buttons: preview and generate.

admin/antilavado/xml/generate

Generate XML. The preview shows which filings go into each file, and what data is missing, without generating anything yet.

Only what has to be reportedFilings for the period that reach the threshold of their activity or carry a currency other than pesos are included.
Six-month accumulationIt adds up, per person and branch, the filings of the last six months that together reach the threshold, even if none reaches it alone.
Nothing half-doneIf a representative, a date or an instrument is missing, the system says what and in which filing, and generates and marks nothing.

Against the official schemaEach file is validated against the XSD of its activity, the same one the portal uses to decide whether to accept it.
Line and reasonUp to ten errors per file with the exact line: an accent, a lowercase letter, an incomplete CURP.
Validate any XMLIncluding those that come from another system: you upload it, it is validated and it is not saved.

admin/antilavado/xml/validate

Validate XML. The test file has a name in lowercase with an accent: the validator finds it on line 18, before the portal rejects it.

XML files

Each file with its period, its validity and its SAT receipt number

Name with activity, RFC, period and time, as the portal expects it.
Download, revalidate, mark as sent and record the receipt number returned by the SAT.
Each XML is stored and linked to the filings it contains: ten years of evidence, in one place.
Storage on your server or in the cloud (S3, R2, SFTP, OneDrive, Google Drive), with optional AES-256 encryption.

admin/antilavado/xml/files

Zero filing · art. 27 Bis of the Rules

The zero month, without anyone having to remember

The General Rules of the LFPIORPI (art. 27 Bis) require filing even when there were no reportable operations in the month. The system works out which active branches have no filing for the month and creates theirs in one click:

Preview by activity and period: those that already have operations, those that already have 27 Bis and those that are missing.
The server checks again on confirmation: nobody creates the same filing twice from two screens.
The zero filing's XML is generated like the rest, with its validation.
Scheduled task: on the 1st of each month it can create the previous month's zero filings, generate the XML and validate it on its own.

admin/antilavado/notices/bis27

Know your customer

A file for each person, with their history

The identification required by article 18, ready for the filing and for the inspection visit.

admin/antilavado/persons

Persons. Individuals, companies and trusts, with the branches and activities they operate in.

admin/antilavado/persons/person

File. Identity, official ID, address, representative, relationships and history.

Three types of person

Individual, company and trust in the same file, with the data each one carries in the XML.

Representatives and attorneys-in-fact

The system will not generate the filing for a company without its representative, or for a trust without its attorney-in-fact.

Relationships

Beneficiaries, guarantors and other roles in a filing, and the relationships between persons.

Change history

A snapshot of the file at every change: what data the person had when each filing was submitted.

Reports

The questions an auditor asks, answered

All reports respect the scope of whoever views them and can be exported to CSV.

admin/antilavado/reports/missing

Missing by month. Which branches have no filing sent for the month, and how many have captured filings not yet sent.

admin/antilavado/reports/six_months

Six months. What each person adds up to in the six-month window against the thresholds of their activity.

Branches without a filing Six-month filings Accumulation per person CSV export

AML Compliance

Generating the filing is half of it. The other half is proving you comply

Almost every system ends at the XML. Here there is also a screen for the compliance officer: it reads what the module already captures, compares it with the current LFPIORPI and leaves the evidence ready for the SAT inspection visit. It does not change the filings, the XML or their validations.

7

Tabs, one single screen

Command center, accumulation, snapshot at a date, monitoring, inspection visit, record and parameters.

$

Estimated fine in pesos

With the current UMA and grouped by infraction, as the authority individualizes it: it doesn't count a hundred customers as a hundred fines.

30/06

Any past date

"How were we doing on June 30?" What was filed after that date doesn't count.

0

Changes to your filings

It reads, compares and warns. Nothing corrects itself: the decision belongs to the compliance officer.

Command center

How each company and each branch is doing, today

Traffic light per branch: on time, at risk or non-compliant, with the month's filings and their due date.
Findings by severity (critical, high, medium, low), each with its article of the law, its penalty and its estimated fine in pesos.
The missing zero filings or reports, and the trend of the last twelve months.
Each finding is marked as reviewed, justified or false positive, with its note: the mark is kept separate and does not alter the evidence.
What the previous system does not allow to be asserted appears separately as "no data", with no fine and outside the traffic light. A violation is never invented.

admin/antilavado/compliance

Command center. Fictitious data from a demo installation.

Accumulation

The six-month accumulation, operation by operation

Choose one or several persons, or a filing: you see what was operated month by month and by year, with the UMA and the thresholds of each date.
Which operations were identified, the period of up to six months, when the filing threshold was crossed and when it was due.
Whether it was filed, with what date and receipt number, and whether it was on time; with the SAT receipt date when it was uploaded.
It states the criterion applied and its sources (LFPIORPI, Regulations art. 7, SAT guide). To hand over in CSV and PDF.

admin/antilavado/compliance/accumulation

Provable accumulation. The criterion and its sources are on the screen itself.

Snapshot at a date

What you knew about a customer on a specific day

Identification and its validity, representatives, beneficiaries, branches, documents, screening and verification, rebuilt from the change history.
The screen compares "on the chosen day" with "today" and says what can be asserted and what cannot, and why.
It is the answer to the inspector's question: "did they have valid identification when this operation was made?"
Print it or download it as a PDF.

admin/antilavado/compliance/snapshot

Snapshot at a date. RFCs and CURPs are blurred.

Transaction monitoring

What does not fit a customer's profile, explained

Every day the transactional profile of each customer with each company is rebuilt: how many operations, usual amounts, cash, activities and branches.
It looks for amounts far above the usual, several operations just under the threshold within a few days, cash close to the limit, a new customer with a large operation, sudden changes in frequency, third parties and list matches.
Each alert comes with its explanation and evidence, with buttons to go to the accumulation or the profile, and is marked as handled, escalated or dismissed.
They are best-practice rules, configurable, not a legal requirement: an alert is something to review, not a violation. And a daily or weekly summary goes to the officer.

admin/antilavado/compliance/monitoring

Monitoring. An alert with its explanation, not a number without context.

Inspection visit

What the SAT usually asks for, with its answer and its list

A card for each thing requested, with the article, the system's answer as of the date and its status: nothing pending or to review.
Customer registry with identification, beneficial owner, file and risk; filings submitted and their deadline; zero filings by month; evidence of filing (XML, receipt number, acknowledgment).
Compliance representative, policy manual, training, risk assessment, audit, record retention, cash operations and list matches.
Each item with its CSV list ready to hand over, and the export is recorded in the audit log.

admin/antilavado/compliance/visit

Inspection visit. Each item is answered with data, not from memory.

Compliance record

Appointment of the compliance representative, training, policy manual with its versions, risk assessment and audits, each with its file. Nothing is deleted: a new version closes the previous one.

Up-to-date parameters

The daily UMA of each year (2016 to 2026 with its DOF date), thresholds per activity in multiples of the UMA with their section and validity, and each rule with its severity, its fine and when it becomes enforceable.

Deadlines as the SHCP publishes them

If the 17th is a non-business day, it falls due on the next business day; and filing on the day assigned by the sixth digit of the RFC also counts as on time, but only that day. Non-business days are entered by you.

Ask Bastino

"How much did X accumulate between January and June?", "did they have valid identification on March 3?", "where do I have fine risk?" The copilot answers by only reading, and with the same scope as you.

Data quality

After migrating, the same person is often there twice

A duplicated person splits their accumulation in two and can leave a filing unsubmitted. This screen finds them, compares them and merges them without rewriting what you already filed.

Possible duplicates

It finds them even when they are not spelled the same

Same RFC or CURP, RFC with and without homoclave, the name with or without accents, with or without "S.A. de C.V.", with reversed surnames or with one letter changed.
The same ID number, email, phone or address as supporting evidence.
Each group with its score and its confidence (high, medium, low), the criteria that matched and what hangs from each record: filings, operations, relationships and representatives.
They are possible duplicates: you decide. "Not a duplicate" (with a reason) and it does not come back. Weights and thresholds are adjusted under Parameters.

admin/antilavado/duplicates

Possible duplicates. Fictitious data; RFC and CURP blurred.

Compare and fix

Records side by side, and a merge you can undo

The two records with the differences highlighted; the system suggests which one stays (the one with the most filings and relationships).
Copy fields from one to the other, or merge: filings, relationships (without duplicating them), representatives, branches, case files, files, screening, identity verification and the link to the customer all move to the good record.
Filings already submitted are not rewritten: their XML and receipt do not change; the filing moves to the good record so the accumulation adds up together, and it remembers which record it was reported with.
Everything can be undone as long as nothing it touched has changed since; if something changed, it says so and does not undo halfway. Each merge is kept in the person's change history.

admin/antilavado/duplicates/compare

Compare and fix. Who stays, who is merged and what changes.

Within a person

The same beneficiary or related party added twice, a representative repeated or who already exists as an individual. Legitimate cases appear as informational and do not count as errors.

Links

Who is a beneficiary or representative of several persons at once: what is worth knowing for the real owner.

Calculated automatically, every night

With a scheduled task and a "Recalculate now" button. Also from the console (aml:duplicates) and with Bastino: "do I have repeated persons?" Bastino only reads: it never merges.

Import without losing anything

The import from the previous system says what it was silently combining, does not discard repeated persons and, when finished, calculates the report and says how many remained.

Part of a platform

Connected with the rest of Fisher Platform

The module works on its own, but each link you turn on saves the compliance officer a step. Everything comes switched off until you decide otherwise.

Persons and customers

The persons you report are your customers: from the record the customer is created, linked to an existing one or imported, without duplicating by RFC.

Screening against lists and PEPs

When a person is registered or changed, it is automatically checked against sanctions lists and politically exposed persons. See Fisher Comply.

Identity verification

The person's ID and liveness check are read and, only if you mark it, applied to their file.

Alerts to the obligated company

Internal notice to whoever handles each person when their ID expires, there is a list match or a filing is about to fall due.

Configurable

When the FIU changes a format, you configure it

What in other systems is a software update, here is a screen.

admin/antilavado/catalogs/engine

Form engine. Each activity declares its products and each product its fields and valid lists.

admin/antilavado/catalogs/activities

Business lines and thresholds. In multiples of the UMA and in pesos, recalculated with the current UMA.

Bulk uploads from Excel

Professional services, outsourcing, real estate and brokerage from .xlsx templates: a preview of what will be created and the per-row errors before anything is written.

Official catalogs

Alert types, ID types, economic activity, business line, countries, currencies and collegiate bodies, editable.

UMA history

Each year the new UMA is entered and the thresholds are recalculated; what was already filed keeps its own.

Internal control

Everyone sees their branch; whoever generates is not whoever captures

Branch-level scopeWithout permission for all branches, each person sees only their own, and without an assigned branch sees nothing.
Separate permissionsCapturing filings, generating XML, validating and marking as sent are different permissions, assignable by role.
Protected accessSecond factor, passkeys, sign-in with your identity provider and an activity log.

admin/antilavado/companies

Obligated companies. One or several legal entities, each with its activity and its branches.

Benefits

What each person gains

Compliance officer

Closes the month in hours

All branches on one dashboard, with what is missing.
XML validated before opening the SAT portal.
Zero filings without doing them one by one.

Management and board

Sleeps soundly

Compliance evidence by company and branch.
Less exposure to fines for omission or lateness.
Ten years of filings, XML and receipt numbers in one place.

Branches

Capture once

A form that asks only for what its activity requires.
The system warns if a cash payment exceeds the threshold.
Or an Excel template, if that is how they work today.

The underlying benefit: anti-money laundering compliance stops depending on one person and one rushed week a month, and becomes a process with evidence that any auditor can follow.

Migration

Your history comes with you

Switching systems cannot mean losing ten years of evidence.

1

We export

Companies, branches, persons, filings, operations and XML from your current system, including SISPRE.

2

We keep the reference

Each migrated filing keeps its number: it is the reference that travels in the XML and the one the FIU returns in its acknowledgments.

3

We revalidate

Historical XML files are brought in with their content and can be revalidated against the current schema.

Anti-Money Laundering is a module of Fisher Platform: it shares users, roles, the customer record, document storage, email, artificial intelligence and the REST API with the rest of the platform. The obligated company can be a customer of your firm, with its Anti-Money Laundering tab inside the record.

Next step

How we get started

Four steps to reach the next 17th with everything in order.

1

Demo

We show you a complete month-end close with your vulnerable activity: from filing to validated XML.

2

Proposal

Based on your obligated companies, branches and activities, and whether you need to migrate your history.

3

Implementation

Setting up companies and branches, migration, role permissions and training.

4

Operation

Your first month-end close on the platform, supported by our team.

Frequently asked questions

What we are usually asked

Does the system file the reports with the SAT for me?

No. The system generates the XML for each branch and validates it against the official schema; uploading it to the SPPLD portal is done by the obligated party with their e.firma. The receipt number returned by the SAT is then recorded and the filings are marked as sent.

Which vulnerable activities does it cover?

Real estate leasing, real estate and developments, vehicles, metals and jewelry, loans, donations, gaming and raffles, service and credit cards, prepaid cards and vouchers, reward wallets and cards, and professional services, plus the shielding format.

What happens in months with no operations?

With one click the system creates the no-activity filing (article 27 Bis of the General Rules of the LFPIORPI) for every branch that does not yet have a filing for the month and generates its XML. It can also be scheduled to happen automatically on the 1st of each month.

How does it know which operations have to be reported?

Each activity has its identification and filing thresholds in multiples of the UMA. Operations of the month that reach the threshold or that are in a currency other than pesos are included in the filing, and the accumulation adds up, per person and branch, the last six months.

Can I use the system to prepare for a SAT inspection visit?

Yes. AML Compliance compares filings, operations, submitted XML and files with the current law: a command center with the estimated fine, provable accumulation operation by operation, a snapshot of the file at a past date, and the list of what is usually requested during the visit, with its answer and its CSV.

Does it detect unusual transactions?

Yes. Monitoring rebuilds each customer's profile every day and alerts on amounts well above the norm, operations just under the threshold, cash close to the limit, sudden changes in frequency, third parties and list matches. Each alert comes with its explanation and its evidence.

What do I do about duplicate persons after migrating?

Data quality finds them (same RFC or CURP, RFC with and without homoclave, name with or without accents or with reversed surnames), compares them side by side and merges them without rewriting filings already submitted: the XML and receipt do not change. Everything can be undone and is kept in the person's change history.

Did anything change with the July 2025 reform?

Yes. It extended record retention to ten years, strengthened beneficial owner identification, added registration in the Registry of vulnerable activities and toughened the late filing rule: after thirty days it is penalized as an omission. Fines range from 200 to 65,000 times the UMA.

Can I bring my data from SISPRE or another system?

Yes. We migrate companies, branches, persons, filings, operations and XML, keeping the number of each filing, which is the reference that travels in the XML.

Can you operate it for us?

We can support the implementation, the migration and the first month-end closes. Legal responsibility for submitting the filings remains with the obligated party.

Book a demo

See it close a full month of your vulnerable activity: filings, thresholds, 27 Bis and validated XML.

Fisher Networks ventas@fishernetworks.net 442 138 8102

Request a demo on WhatsApp Send an email

Supporting documents and references (APA, 7th edition)

Federal Law for the Prevention and Identification of Operations with Resources of Illicit Origin. (2025, July 16). Last reform published in the Official Gazette of the Federation. Chamber of Deputies of the Honorable Congress of the Union. https://www.diputados.gob.mx/LeyesBiblio/pdf/LFPIORPI.pdf
National Institute of Statistics and Geography. (2026). Value of the Measurement and Update Unit. Official Gazette of the Federation, January 9, 2026. https://dof.gob.mx/
Tax Administration Service. (n.d.). Money Laundering Prevention Portal (SPPLD): XML formats and schemas for vulnerable-activity filings. https://sppld.sat.gob.mx/
Legal basis: LFPIORPI, arts. 17 (vulnerable activities and thresholds), 18 (identification, beneficial owner, ten-year retention and Registry), 23 (the 17th-day deadline), 24 (content of filings), 32 (prohibited cash operations), 53 and 54 (infractions and fines), 54 Bis (suspension), 55 (spontaneous regularization) and 62 (crimes). Equivalents using the 2026 daily UMA of $117.31; these are legal ranges and the authority sets the amount in each case.
Ministry of Finance and Public Credit. General Rules referred to in the Federal Law for the Prevention and Identification of Operations with Resources of Illicit Origin, art. 27 Bis (no-activity filing for the month). Official Gazette of the Federation.

The screenshots are from a demo environment with fictitious companies and people; no data corresponds to a real customer, and RFCs, CURPs and receipt numbers are blurred. This page is informational and does not constitute legal advice.

Every filing to the FIU, on time and validated, before the 17th.