CFDI 4.0 Stamping Errors: Stop Rejections Before They Happen
Most CFDI rejections aren't about the format—they're about mismatched data. Here's how to catch and fix the five mistakes that cost you time and credibility every month.
Why Your CFDIs Keep Getting Rejected
I've watched invoices bounce back from the SAT more times than I can count. A receiver's name that doesn't match their tax certificate. A ZIP code that's off by one digit. A CFDI use that doesn't fit the customer's tax regime. Each one feels like a small thing until you're fixing the same mistakes for the same customers month after month.
The pattern is always the same: someone manually enters customer data once, assumes it's correct, and then stamps invoices against bad information for months. The SAT catches it. The invoice gets rejected. You're scrambling to reissue and re-stamp. Your customer is confused. Your accounting is a mess.
Let me walk you through the five most common stamping errors I see, and how to stop them before they happen.
Mismatched Receiver Data: The Name, Tax Regime, and Address Problem
This is the biggest culprit. Your customer's legal name on their tax certificate doesn't match what you have in your system. Or their tax regime code changed, but you're still stamping with the old one. Or the ZIP code in your database is outdated.
The SAT validates every CFDI against the receiver's tax certificate. If even one field is wrong, the stamp fails.
- The fix: Before you stamp a CFDI, validate the receiver's tax data against the SAT's public registry. Ask for their RFC and let the system pull their current legal name, tax regime, and registered address. Don't assume last month's data is still good.
- Make it a rule: If a customer's data hasn't been verified in the last 90 days, verify it again before stamping. It takes 30 seconds and saves you hours of corrections.
CFDI Use Doesn't Match the Customer's Tax Regime
You're stamping a CFDI with use code 'G02' (General expenses) but the customer is registered as a physical person (Persona Física) who can't receive that use. Or you're using 'P01' (Payroll) for someone who isn't set up to receive payroll invoices.
The SAT rejects it because the use code doesn't fit the regime.
- The fix: Know your customer's tax regime before you stamp. Different regimes have different allowed CFDI uses. Physical persons have a narrower list than corporations. If you're unsure, ask the customer which CFDI uses they accept, or stick with the most common ones (like 'G03' for general expenses).
PUE vs PPD: Timing and Payment Receipt Confusion
PUE (Pago en Una Exhibición) means paid in full upfront. PPD (Pago en Parcialidades o Diferido) means payment in installments or deferred. If you stamp a PPD invoice, you must issue a payment receipt (Recibo de Pago) when the customer actually pays. If you don't, the SAT sees an unpaid invoice forever.
Many small businesses stamp PUE by default, then when payment is delayed, they either re-stamp as PPD (wrong—you can't change a stamped invoice) or forget to issue the payment receipt altogether.
- The fix: Stamp PUE only if the customer pays on the same day. If there's any delay expected, stamp PPD and set a reminder to issue the payment receipt when money actually arrives. Track this in your invoicing system so you don't forget.
Cancellations Without a Reason Code
You need to cancel an invoice. The SAT requires a reason code—but you don't provide one, or you provide the wrong one. The cancellation fails or gets flagged.
- The fix: Use the correct reason codes. The most common: '01' (Comprobante emitido con errores con relación) for errors with the invoice itself, or '02' (Comprobante emitido con errores con relación al destinatario) for receiver data errors. Always provide a reason.
The Validation Habit: Fix It Once, Not Every Month
Here's the real problem I see: businesses validate customer tax data one time, when they first sign them up. Then they stamp invoices against that data for months or years without checking again. Tax regimes change. Addresses update. Legal names get corrected. And your invoices start bouncing.
The solution is to make validation part of your stamping workflow, not a one-time event. Every time you prepare to stamp, check that the receiver's data is current.
The Answer: Validate Before You Stamp
The cleanest way to avoid all of this is to build validation into your invoicing system itself. When you enter a customer's RFC or tax ID, pull their current data from the SAT registry. Show the operator what the system found. Let them confirm it matches what the customer expects. Only then stamp.
That's exactly what I built into Hailan—the system I created where CFDI 4.0 invoicing comes out of the sale itself, with the customer tax data validated before stamping. No rejected invoices. No monthly corrections. No guessing about receiver names or tax regimes. The invoice is right the first time because the data was right before you ever hit stamp.
Start today: pull your last five rejected CFDIs and trace the error. I bet four of them are data mismatches that a validation step would have caught.
Invoices that come out right the first time
The CFDI 4.0 invoice comes straight from the sale, with customer tax data validated before stamping and the payment receipt when needed.
See invoicing →