What goes in the package

When the automation sends a month, the accountant receives two attachments: a zip of the month folder’s files, and a one-page summary PDF named Resumen MM-YYYY.pdf that lists what is inside. This page explains how both are built, so you know what to put in the folder — and what to keep out of it.

Which files are included

Everything directly inside the month folder goes into the zip, except:

• Subfolders and their contents — deliberately left out. If something must be sent, it needs to sit at the top level of the month folder.
• Zip files — never included, so an old package sitting in the folder can’t end up nested inside a new one.
• Housekeeping files — the HOLD/SEND control files, hidden files, temporary files, and the automation’s own record file are all skipped automatically. You don’t need to tidy these away.

How the bank statement is recognized

The automation opens each PDF in the folder and reads its text. A file counts as the bank’s monthly statement when the text names the bank and says estado de cuenta, and its stated period matches the month being sent. Because recognition works on the contents, the filename doesn’t matter — save the statement under whatever name it downloads as.

Two consequences worth knowing:

• The bank’s small fee invoices are not mistaken for the statement — the automation tells them apart.
• A statement for the wrong month doesn’t trigger a send. The status email will point out that the statement in the folder belongs to another month.

If the bank ever changes its statement layout so the period can’t be read, the file is still accepted as the statement — it just can’t be matched to the month, and the summary PDF notes the period as unreadable rather than failing.

Invoices (CFDIs) and the summary PDF

For each invoice, the folder normally holds a PDF and its matching XML file. The automation reads every XML and builds a table in the summary PDF showing each document’s type, issuer, folio, date and total, plus the total of the month’s invoices. Files without an XML twin (photos, receipts, the statement itself) are listed under “other documents”.

The summary also answers, up front, the two things the accountant asks every month:

• Airbnb income: whether an Airbnb withholding certificate (constancia de retención) is in the package, whether there is only an Airbnb invoice without one, or whether there was no Airbnb activity at all. Airbnb documents are recognized by their contents too, so it doesn’t matter that they often arrive with meaningless filenames. The bank statement is ignored for this check — a payout line in it is not an invoice.
• The bank statement: its filename and period, or a clear “PENDING — will be sent separately” when the month had to go out without it.

If something is off — an XML that can’t be read, or a withholding certificate that belongs to a different month — the summary PDF flags it in a warnings section instead of silently including it. If you see a warning, check that file.

The email itself

The package is sent as a reply-all on the accountant’s own monthly request thread (their “Solicitud de Documentación” email for that month), so it arrives in the conversation they are tracking. If no such thread can be found for the month, a fresh email goes to the accountant addresses set in the automation’s configuration instead — and your confirmation email tells you which of the two happened.

The message body is written for the accountant, in Spanish: what is attached, the Airbnb situation, and — when the month was sent without the statement — a line saying the statement will follow.

Size limit

Email can carry about 25 MB. If the month’s package would exceed that, the automation refuses to send it rather than have the email bounce. See the troubleshooting page for what to do.