Issuing invoices from one system already has its rules. Issuing them when the sale starts in a point of sale, the customer lives in a CRM and accounting sits in the ERP is a different story, because each system has its own idea of what the customer is called and how much they were charged. At Zygnus we issue Mexican e-invoices (CFDI 4.0) from Nori and Recaudo, and we connect client systems to their ERP. These are the errors we see most in those integrations.
The recipient does not match the tax registry
With CFDI 4.0, Mexico's tax authority (SAT) checks that the recipient's name, tax ID (RFC), tax-address postal code and tax regime match what it has on record. The problem in an integration is that this data is entered in one system and stamped in another.
The classic case: the CRM stores the company name with "S.A. de C.V." because that is how the salesperson typed it, and CFDI 4.0 expects the name without the corporate suffix. Or the stored postal code is the delivery address, not the tax address. The certified provider (PAC) rejects the invoice and someone fixes it by hand.
The way to avoid it is to keep a single place for the customer's tax data, with separate fields for tax and operational details, and have the other systems read from there.
Invoice use that does not fit the regime
The SAT catalog says which CFDI uses apply to each tax regime. If your system offers a fixed list of uses without filtering by the customer's regime, sooner or later someone picks a combination that does not exist. Filtering the list on screen by regime saves a lot of rejections.
New fields nobody filled in
CFDI 4.0 added fields that older integrations leave at default values. Two of the most common:
- ObjetoImp on each line item, which says whether the item is subject to tax. An exempt service and a taxed one do not carry the same value, and always copying "02" produces invoices with misdeclared taxes.
- Exportacion, which is almost always "01" for domestic sales but still has to be there.
A badly built global invoice
Sales to the general public use the generic tax ID XAXX010101000, the name PUBLICO EN GENERAL, regime 616, use S01, and the postal code of the place of issue. The global invoice also carries the global information node with period, month and year. A point of sale that groups the day's tickets and sends them to the ERP has to build this carefully, especially around month changes.
Zero amounts and errors nobody sees
One of our most expensive lessons did not come from the SAT. In one integration, the app sent extra line items with a $0 total and the server accepted them. In another, a child document in SAP was not created when the amount was $0.00, and the error was lost without warning. Neither case failed visibly. Both were found by reviewing data.
Since then we validate amounts on the server before stamping an invoice or sending it to the ERP, and every rejection goes into a log with the document and the reason. An integration error nobody reads is the same as having no integration.
Cancelling without planning the replacement
Since 2022 every cancellation needs a reason code. If you cancel with reason 01, because the invoice had errors, you must reference the UUID of the invoice that replaces it. That means stamping the new one first and cancelling the old one second. When your system's flow runs the other way, the user gets stuck halfway.
Installment payments
If an invoice is issued with the PPD method because it will be paid later or in parts, every payment received needs its payment complement. This is where the integration with collections matters: the payment arrives by bank transfer or a payment link, it is recorded in one system, and the complement has to be stamped in another. If those systems do not talk, complements fall behind and the customer cannot claim their VAT.
If your company invoices from more than one system and someone fixes rejections by hand every month, tell me which of these errors sounds most familiar. There is usually one that explains most of them.