OMB Cloud AES

Troubleshooting: invoice fails to stamp

When the CFDI/Facturae stamping rejects your invoice — common SAT or AEAT errors.

When the stamping authority rejects an invoice, the error message can be cryptic. Here are the common ones and their fixes.

MX SAT errors

  • CFDI40121: Receptor invalid: The client's RFC is wrong or doesn't exist in SAT records. Verify the RFC with the client.
  • CFDI40114: Regimen Fiscal: The receptor regimen doesn't match the operation type. Update the client's tax regime.
  • CFDI40103: Lugar de Expedicion: The postal code on the issuer entity doesn't match. Fix in the billing entity settings.
  • Sello digital invalid: Your CSD expired. Renew at the SAT portal and re-upload.

ES AEAT errors

  • NIF not valid: The buyer's NIF is incorrectly formatted or doesn't exist. Verify with the client.
  • Signature invalid: Your XAdES certificate expired or the keystore password is wrong. Re-upload in entity settings.
  • VAT rate disallowed: A line item uses a VAT rate that doesn't match the buyer's situation. Check exemption codes.

If the issuance succeeds but PDF generation fails

This is rare but happens when a logo or branding element fails to render. The XML is valid and stamped; the PDF can be re-generated from the invoice page → "Re-render PDF".

Last resort

If the stamping authority is down (outage), the system queues the request and auto-retries. Don't resubmit manually — duplicates cause CFDI 40109 errors that are messier to clean.

Was this article helpful?