If your team spends hours downloading invoices and matching bank payments every month, those repeated tasks are a useful place to start automating. Keep a reviewer responsible for transactions the system cannot explain and for the tax treatment used in your returns.
Review one recent monthly close before choosing software. Identify where the team retypes information, waits for documents or investigates differences. Use that list to choose the first task to automate and measure whether it improves the next close.
Map the current process
Document the path of each record before choosing an automation:
| Record | Source | Required output | Owner |
|---|---|---|---|
| Issued CFDI | Invoicing system and SAT | Valid XML, status and accounting entry. | Billing and accounting. |
| Received CFDI | SAT and supplier files | Approved expense, tax treatment and payment link. | Accounts payable and accounting. |
| Bank transaction | Bank feed or statement | Matched invoice, transfer or explained exception. | Treasury. |
| Payroll | Payroll system and CFDI | Payroll entry, withholding and payment support. | Payroll and accounting. |
| Tax return | SAT service | Submitted return, payment reference and acknowledgment. | Tax preparer and approver. |
| Tax Mailbox item | SAT Tax Mailbox | Downloaded act, deadline, owner and response file. | Legal or tax owner. |
Give each transaction an identifier and a review status in a shared record. The team should be able to see what is pending without searching through individual inboxes or asking the person who handled it.
What to automate first
- Retrieve issued and received CFDI by period.
- Store the XML and metadata, including cancellation status.
- Import bank statements without overwriting the original file.
- Match exact references, amounts and dates under documented rules.
- Keep a review list of unmatched or conflicting records.
- Track filing deadlines and assigned reviewers.
- Save returns, payment references, bank receipts and acknowledgments in the period folder.
The SAT offers services to retrieve and cancel CFDI and a web service for bulk XML recovery. An internal system should preserve the SAT status and retrieval date instead of treating a previously downloaded invoice as permanently valid.
Use matching rules with limits
| Rule | Safe automated action | Review trigger |
|---|---|---|
| Exact UUID and bank reference | Link payment and CFDI. | Duplicate reference or amount mismatch. |
| Repeating bank fee from the same bank | Suggest account and tax code. | New concept, unusual amount or missing CFDI. |
| Customer collection with payment complement | Match collection to receivable. | Partial payment, foreign currency or missing complement. |
| Supplier payment | Suggest invoice settlement. | Several invoices, credit note or withholding. |
| Canceled CFDI | Block normal posting or flag existing entry. | Replacement CFDI or accounting reversal required. |
A suggested account is not an approved entry. Set amount thresholds and confidence rules, and require human approval for new vendors, unusual transactions, related parties, tax credits and manual overrides.
Keep tax decisions under review
Automation should not make the final decision on:
- whether a deposit is taxable income;
- whether an expense is deductible;
- whether input VAT is creditable;
- the period in which a cash-basis transaction belongs;
- treatment of canceled or substituted CFDI;
- withholding rates and obligations;
- an amended return;
- a response to a SAT notice.
The reviewer should record the conclusion, evidence and date. Free-text notes such as *checked* or *looks fine* do not explain the tax treatment.
Keep track of unresolved records
When a record cannot be matched or classified, keep it on a shared review list. Include enough information for someone to investigate:
| Field | Purpose |
|---|---|
| Period and source | Locate the original record. |
| Amount and currency | Measure exposure and prioritize. |
| Exception type | Missing CFDI, mismatch, duplicate, cancellation or unknown transaction. |
| Assigned owner | Establish responsibility. |
| Due date | Prevent an open item from passing the tax filing deadline. |
| Resolution | Record the entry, correction or supporting document. |
| Approver and timestamp | Preserve the audit trail. |
Keep an item open until someone resolves the difference and attaches the supporting record. For an unidentified deposit, that might mean obtaining the customer's payment reference and linking it to the correct invoice.
Protect credentials and changes
- Assign named user accounts instead of shared logins.
- Apply the least access needed for each role.
- Keep SAT Password and e.firma files out of shared folders and automation logs.
- Require approval for rule changes, vendor master changes and manual journal entries.
- Record who imported, modified, approved and submitted each item.
- Export data and configuration regularly in a format the business can recover.
- Test restoration instead of assuming a backup works.
An integration should never expose the private key or its password to staff who do not need to sign a filing.
Monitor the Tax Mailbox correctly
Email and SMS are alerts that information is pending in the Tax Mailbox. They are not the administrative act or its acknowledgment.
When an alert arrives:
- enter the SAT Tax Mailbox;
- open the pending item under the applicable authentication flow;
- download the act and notification acknowledgment;
- record the legal deadline from the document and applicable rules;
- assign an owner and review route;
- retain the response, attachments and submission acknowledgment.
Under article 17-K of the Federal Tax Code, taxpayers must consult the mailbox within three days after receiving an electronic alert. Calendar automation can remind the team, but legal review determines how the notification date and response period apply.
Monthly close workflow
| Stage | Completion evidence |
|---|---|
| Cutoff | Period locked or later changes listed. |
| CFDI | Issued and received files retrieved with status. |
| Banks | Every transaction matched or assigned as an exception. |
| Accounting | Entries posted and control accounts reconciled. |
| Tax | ISR, VAT and withholding workpapers approved. |
| Filing | Return submitted and payment completed when due. |
| Archive | Acknowledgments and support stored under the period. |
The closing reviewer should be able to move from a declared figure to its workpaper, ledger entries, CFDI and bank evidence without relying on the preparer's memory.
Metrics that reveal control problems
Measure a small set of operational results:
- days from month-end to close;
- unmatched bank transactions at filing date;
- CFDI exceptions by type;
- manual entries after close;
- returns amended because of internal errors;
- filings or payments completed after deadline;
- Tax Mailbox items without an owner;
- time required to retrieve support for a sample transaction.
A falling close time is useful only if exceptions, late entries and amendments do not increase.
Example implementation schedule
This eight-week schedule is an example, not a deadline. Adjust it to your transaction volume and the time needed to investigate differences. Use copies of a closed period in a separate test environment so the trial cannot duplicate live entries or submit tax returns.
Weeks 1 and 2: inventory
List systems, exports, access requirements, deadlines, users and current folders. Select a recent closed month and trace a sample of transactions from source to return, including partial payments, replaced invoices, and unidentified deposits where available. Keep passwords and private keys out of the list.
Weeks 3 and 4: organize the records
Organize folders by period and agree on file names, responsible reviewers, and retention rules. Import copies of the CFDI and bank files while preserving the originals.
Weeks 5 and 6: matching and exceptions
Start with matching rules you can explain. Put uncertain records on the review list and investigate why they did not match. Compare results with the approved close, but check the cause of each difference: the earlier close may also contain mistakes.
Weeks 7 and 8: approvals and evidence
Add approvals, change logs, filing checklists, and acknowledgment storage. Complete a trial close using the copied data, then test export and recovery before deciding whether to retire the former process.
Frequently asked questions
Does accounting automation replace the accountant?
No. It reduces collection, matching and filing administration. Classification, tax judgment, exceptions and approval still require accountable reviewers.
Should the business download CFDI only once?
No. CFDI status can change through cancellation or substitution. Preserve retrieval dates and refresh status under a defined schedule.
Can an email alert prove that a Tax Mailbox notice was handled?
No. The team must enter the mailbox, review the act and retain the applicable acknowledgment.
What should an SMB automate first?
CFDI retrieval, original bank imports, exact matching, an exception queue and a complete period archive usually provide the clearest starting point.
Official sources
- SAT: retrieve and cancel electronic invoices.
- SAT: CFDI bulk recovery service.
- SAT: Tax Mailbox.
- Chamber of Deputies: Federal Tax Code.
Automate only after defining the exception
Before connecting tools, decide which transactions may post automatically and which must stop for review. Missing CFDI, duplicate charges, mixed payments and unusual tax rates should enter an exception queue with an owner. Automation is useful when it makes uncertainty visible instead of moving it faster.
