No customer invoice request does not mean no Mexican invoice trail
A retail sale that does not receive a customer-specific CFDI can belong in a qualifying general-public CFDI. The sale still belongs in the point-of-sale record, accounting, tax base, and reconciliation.
A foreign-owned shop in Mexico often has four different numbers at close: POS sales, card-terminal settlements, cash counted, and CFDI issued to named customers. The global CFDI is not whichever number is easiest. It is the controlled remainder of eligible general-public transactions after individually invoiced sales are removed.
Original Fintax post explaining that a sale still requires invoice treatment when the customer does not request a named CFDI.
Build the close from transactions, not deposits
| Layer | Source | Question |
|---|---|---|
| Sales universe | Consecutive POS transactions | What was actually sold? |
| Named CFDI | Customer-specific XML | Which tickets are already invoiced separately? |
| General public | Remaining eligible tickets | Which operations belong in the global CFDI? |
| Collection | Cash, cards, platforms, receivables | How and when did value settle? |
| Tax | Rates, object, IVA and IEPS | Do invoice taxes reproduce the sales system? |
Article 29 of Mexico's current Federal Tax Code requires digital tax receipts when tax law imposes invoicing for acts, activities, income, or withholding. A customer's silence does not erase the seller's tax event.
The 2026 global-CFDI framework
Rule 2.7.1.21 of the compiled 2026 Miscellaneous Tax Resolution permits a daily, weekly, or monthly CFDI containing each general-public operation and its receipt or transaction number. Rule 2.7.1.23 supplies the domestic generic RFC XAXX010101000 when the customer's RFC is unavailable.
- Choose the covered day, week, or month and close that population consistently.
- Retain the transaction identifier for every included sale.
- Submit the global CFDI no later than 24 hours after the selected period closes.
- Separate IVA and IEPS payable in the global document.
- Exclude every sale already supported by a customer-specific CFDI.
Receipt, named CFDI, and global CFDI are not interchangeable
| Record | Primary job | Control key |
|---|---|---|
| General-public receipt | Describe one sale | Consecutive transaction number |
| Named CFDI | Invoice an identified customer | Customer RFC and fiscal data |
| Global CFDI | Aggregate remaining public sales | Period and included receipt population |
| Settlement report | Explain collection timing and fees | Terminal batch or platform ID |
The generic RFC is not a substitute for bad customer master data
If a known Mexican customer requests an invoice, validate and use that customer's fiscal information. Do not force the sale into XAXX010101000 merely because the legal-name or postal-code validation was inconvenient.
The under-MXN 100 rule has a narrow effect
When the buyer does not request a general-public receipt, Rule 2.7.1.21 removes the obligation to issue that receipt for a general-public transaction below MXN 100. It does not remove the sale from the global CFDI or the books. The POS still needs a reliable event record so the aggregate can be rebuilt.
A repeatable daily workflow
- Lock the POS sequence and investigate missing or duplicated numbers.
- Tag every transaction that has a valid named CFDI.
- Separate genuine voids, refunds, and discounts with approval evidence.
- Aggregate the remaining general-public tickets by tax treatment.
- Reconcile cash, terminal batches, delivery platforms, and receivables.
- Generate and archive the global XML with its transaction-detail report.
Worked close: one restaurant day
| Population | Gross amount | Treatment |
|---|---|---|
| All closed checks | MXN 92,400 | Sales universe |
| Named customer CFDI | MXN 18,750 | Exclude from global |
| Approved voids before sale completion | MXN 1,150 | Not a completed sale |
| General-public population | MXN 72,500 | Reconcile for global CFDI |
Card processors deposit MXN 61,900 because cash, tips, commissions, and settlement timing differ. Issuing the global CFDI for the bank deposit would understate or misclassify the day's sale. Reconcile gross sales to collection channels in a separate bridge.
Late request for a named invoice
If a transaction has already been included in a global CFDI, issuing a second named CFDI without removing it creates two invoice trails for one sale. SAT's cancellation guidance identifies reason code 04 as “named transaction related to a global invoice.” The exact ticket must be removed from the reconstructed global population.
| Step | Evidence retained |
|---|---|
| Locate original transaction | Ticket, date, amount, tax, payment |
| Validate customer | RFC, legal name, postal code, regime and use |
| Issue named CFDI | Customer XML tied to the original sale |
| Correct global | Cancellation reason and new aggregate excluding the ticket |
| Reconcile | One sale, one final invoice treatment, unchanged collection |
Do not lose the original global population
Before cancelling a global CFDI, preserve its transaction report and prepare the corrected aggregate. Removing one ticket must not drop or duplicate the hundreds of other transactions in the document.
Accrual and cash-basis installment sales
Rule 2.7.1.21 addresses general-public operations settled in installments or later. An accrual taxpayer reflects the full operation in the applicable global invoice; a cash-basis taxpayer reflects amounts actually collected in each global invoice. Configure the logic by regime instead of applying one POS setting to every Mexican entity.
Multi-store architecture
- Maintain transaction sequences by store, terminal, and business date.
- Map each store to the correct issuing location and certificate workflow.
- Centralize named-CFDI tags before global invoices are generated.
- Preserve original currency and Mexican tax treatment for each sale.
- Reconcile intercompany gift cards, delivery apps, and loyalty redemptions separately.
- Monitor late named-invoice requests as a process metric.
Exception dashboard
| Exception | Risk |
|---|---|
| Ticket appears in named and global CFDI | Duplicate income and tax |
| POS sale appears in neither | Omitted invoice population |
| Global total equals net bank deposit | Fees and cash may be misstated |
| Unsupported generic sales line | Transaction population cannot be rebuilt |
| Cancelled named CFDI remains excluded | Sale may disappear from final invoice trail |
| Tax by rate differs from POS | IVA or IEPS misclassification |
Frequently asked questions
Must a Mexican retailer issue one CFDI per customer?
Not for every eligible general-public sale. Rule 2.7.1.21 permits a controlled daily, weekly, or monthly global CFDI while retaining the underlying operation records.
Can the global CFDI equal the credit-card deposit?
No reliable rule says so. Deposits can be net of fees, delayed, or combined. Build the global population from sales and use a separate settlement reconciliation.
Does the MXN 100 exception remove tax?
No. It concerns the individual general-public receipt when none is requested; the sale still enters the relevant global CFDI, accounting, and return.
Which generic RFC applies to a foreign tourist?
Rule 2.7.1.23 distinguishes domestic generic RFC XAXX010101000 from foreign-resident generic RFC XEXX010101000. Apply the correct customer and transaction facts.
Official sources
Review Articles 29 and 29-A of the Federal Tax Code, Rules 2.7.1.21 and 2.7.1.23 of the compiled 2026 RMF, and SAT's invoice cancellation guidance. Sector-specific and regime rules may modify the workflow.
