This month's report, validated before it goes out.
PLDUnity generates the XML reports for all 17 vulnerable activities from your transactions, validates them against the SAT's 19 schemas (XSD), produces the nil report when there are no transactions and links each acknowledgment to its report.
SAT SPPLD XML ENGINE · 2026 XSD CONFORMANCE
Instant SAT XML generation, zero schema errors.
Inspect how PLDUnity automatically calculates UMA thresholds, escapes special characters, generates cryptographic SHA-256 hashes, and prepares compliant ZIP packages for mass filing before the 17th of each month.
<?xml version="1.0" encoding="UTF-8"?>
<archivo xmlns="http://www.sat.gob.mx/esquemas/servicios/pld/inmuebles" version="2026.1">
<sujetoObligado rfc="DES180914XYZ" claveActividad="INM" numFolio="PLD-INM-2027-00412" />
<aviso tipoAviso="1" mesReportado="202702">
<personaMoral razonSocial="DESARROLLADORA DEL BOSQUE S.A. DE C.V." rfc="DBO150322AB1">
<beneficiarioControlador rfc="ROGM801124HDF" porcentaje="65.0" />
</personaMoral>
<operacion fechaOperacion="2027-02-14" montoOperacion="4850000.00" moneda="MXN" formaPago="03">
<bienInmueble tipoInmueble="01" folioReal="189422" valorOperacion="4850000.00" />
</operacion>
</aviso>
</archivo>SAT Validation Engine
Art. 17 · Fracc. V
SAT Pre-Filing Diagnostics
Valid XML schema hierarchy matching SAT SPPLD specs.
Valid RFC length, structure and checksum verification.
Ampersands, quotes and XML reserved symbols safely encoded.
Tamper-proof hash generated for SAT audit trails.
Ready for monthly bulk filing before the 17th day deadline.
Day 17 Agenda & Reminders
Reminders for the 17th in the compliance officer's agenda and monthly closing email, plus zero-activity report generation and preview of what will enter the notice.
Agenda & monthly closing emailDeposits, Withdrawals & SPPLD Guide
Generates the XML by activity and period (with deposits and withdrawals in separate files where applicable) and includes a submission guide for the SPPLD portal.
Optional BDU managed filing availableLinked Receipts with SHA-256
Link SAT receipts with a SHA-256 cryptographic fingerprint, maintain records of previous periods, and reconcile reached thresholds against filed notices.
10-year retention (Art. 18 IV LFPIORPI)Validated Against Official SAT Schema
Validated against the official SAT schema before download. Note: For Fracción XIV (Foreign Trade), the SAT does not receive XML notices on the SPPLD.
No recharge for regenerating XML of same recordPlatform Architecture
Features
XML per vulnerable activity
With the SAT's official structure and catalogs.
Validation against the official schema
No file is marked as filed unless it validates.
Nil report
One click for months with no transactions to report.
Gaming and betting
Deposit and withdrawal files, with cashier instruments from the SAT catalog.
Validator and importer
Validate XML built outside the platform and import your historical XML.
Linked acknowledgments
The SAT portal acknowledgment is uploaded and linked to the report, with an integrity fingerprint.
Aggregation reports
Adds up the same client's transactions over the month and the semester and includes them once they cross the threshold.
The 17th deadline
Watched in the compliance officer's agenda, with reminders.
Currencies and instruments
Transactions in several currencies and instruments, according to each activity's catalog.
Platform Architecture
Advantages
Structure checked before the portal
The file is validated with the same schema (XSD) the SAT publishes, before you download it.
Traceability
Every report knows which transactions it came from and which acknowledgment closed it.
No re-keying
The same transactions feed monitoring, the EBR and the report.
Ready for schema changes
When the SAT publishes a new XSD, it is updated in the platform, not on your computer.
How it works
- ETAPA 01
Upload
You upload the month's transactions or receive them by API.
- ETAPA 02
Detect
The platform flags those that cross the threshold, alone or by aggregation.
- ETAPA 03
Generate
You generate the XML; it is validated against the official schema and downloaded ready for the SAT portal.
- ETAPA 04
Close
You upload the acknowledgment and it is linked to the report, with a SHA-256 fingerprint.
Who it is for
For all 17 vulnerable activities in Article 17.
- Art. 17 · Fracc. INotice: 645 UMA
- Art. 17 · Fracc. VIIINotice: 6,420 UMA
- Art. 17 · Fracc. VNotice: 8,025 UMA
- Art. 17 · Fracc. XVNotice: 3,210 UMA
- Art. 17 · Fracc. XIIPublic faith acts
- Art. 17 · Fracc. IVNotice: 1,605 UMA
- Art. 17 · Fracc. VINotice: 1,605 UMA
- Art. 17 · Fracc. IX–XNotice: 4,815 UMA
- Art. 17 · Fracc. XVINotice: 645 UMA
- Art. 17 · Fracc. XIVCustoms brokers
FREQUENTLY ASKED QUESTIONS
Frequently asked questions about the SAT XML Report Generator
Does the platform submit the XML directly to the SAT or how is it filed on the SPPLD portal?
Mexican regulations require the reporting entity to sign filings inside the SAT SPPLD portal using its digital tax signature (e.firma). PLDUnity generates the 100% XSD-validated XML file so you upload it to the SPPLD portal with zero structural rejections, and then stores the resulting SAT acknowledgment PDF/XML in your 10-year archive.
How does it prevent the SAT portal from rejecting my XML file on the 17th of the month?
Our engine pre-validates every record against all 19 official SAT/UIF XSD schemas: checking RFC/CURP formats, 5-digit postal codes, ISO country and currency codes, activity-specific catalogs, and mandatory Beneficial Owner nodes. If any required field is missing, it pinpoints the exact client and field before you export.
What if we had no transactions exceeding the notice threshold during the month?
You must still file a monthly report even with zero reportable transactions. With one click, PLDUnity prepares your Zero-Activity Report (Article 25 of the General Rules) for the period and archives the SAT receipt.
How does the XML generator handle transactions triggered by 6-month rolling accumulation?
When a client's identified transactions across a rolling 6-month window reach or exceed your activity's notice threshold (using the 2026 UMA of $117.31 MXN), the engine automatically bundles the qualifying transactions from that window into the XML notice.
Can I validate an XML file built in another system before uploading it to the SAT?
Yes. You can upload external XML files to PLDUnity's validator to verify compliance with the official SAT XSD schema for your vulnerable activity and catch catalog or formatting errors before filing.
Does it support corrective notices and urgent 24-hour unusual transaction notices?
Yes. In addition to standard monthly filings due by the 17th, the platform structures corrective notices referencing prior SAT receipt folios and generates urgent 24-hour notices linked directly to adjudicated Unusual Transaction cases.
How long are submitted XML files and SAT receipts retained?
Every generated XML, official SAT acknowledgment receipt, and underlying KYC file is stored encrypted for the 10-year retention period mandated by amended Article 18 of the LFPIORPI.
Generate your first report in the free trial.
Book 30 minutes with the BDUnity team · info@pldunity.com