In Mexico, every business sale — no matter how small — must be accompanied by a legally valid receipt called a CFDI (Comprobante Fiscal Digital por Internet). Issued by the SAT (Servicio de Administración Tributaria), Mexico's tax authority, a CFDI is a digitally signed XML document that serves as the only legally recognised proof of a transaction. It is not equivalent to a printed receipt or a regular invoice generated inside your POS. A CFDI must be certified by a PAC (Proveedor Autorizado de Certificación) — an SAT-authorised third party — before it has any legal standing.

iVendNext Mexico Localization solves this by embedding CFDI generation directly into the POS checkout flow. There is no separate portal, no secondary tool, and no extra step for the cashier.
When a cashier submits a POS Invoice in iVendNext, the system immediately triggers a call to FacturaAPI — the SAT-authorised PAC that iVendNext integrates with. FacturaAPI assembles the CFDI XML from the transaction data, signs it using the business's digital certificate, and submits it to SAT for stamping. The entire process completes in seconds.
Once SAT confirms the stamp, FacturaAPI returns a unique SAT UUID — a document identifier that is permanently stored on the POS Invoice record. From this point, the invoice is a valid fiscal document. The cashier sees no delay and takes no additional action. The compliance work happens entirely in the background.This automatic trigger applies to every POS Invoice submitted in iVendNext — standard sales, returns, and deferred payment entries — ensuring that no transaction is missed and no manual intervention is required.
Mexican tax law defines different CFDI types for different transaction scenarios. iVendNext handles all three automatically, selecting the correct type based on the nature of the transaction.
CFDI Ingreso (Type I — Standard Sales)
Every standard POS sale generates a CFDI Ingreso document. This is the most common CFDI type and covers the bulk of retail transactions. When a customer pays for goods at the counter, the Ingreso CFDI is stamped and attached to that invoice record automatically. The SAT UUID returned after stamping links this document permanently to the sale in SAT's records.
CFDI Egreso (Type E — Returns and Credit Notes)
When a customer returns goods and a Return POS Invoice is created in iVendNext, the system automatically generates a CFDI Egreso — a credit note. Critically, the Egreso CFDI is linked to the original sale's UUID using SAT relationship code 01. This traceability is a SAT requirement: a return cannot be recognised as valid without a clear reference back to the original transaction. iVendNext applies this linking automatically, so finance teams never need to manually cross-reference UUIDs when processing returns.
CFDI Tipo P (Type P — Payment Complements)
Some retail scenarios involve deferred payments — where a customer takes goods but settles in installments. In these cases, SAT requires a separate CFDI for each payment received, known as a CFDI tipo P or payment complement. When a Payment Entry is submitted in iVendNext against an outstanding deferred balance, the system automatically triggers generation of the corresponding CFDI tipo P. Each instalment is therefore legally stamped the moment payment is recorded, keeping the business compliant across the full payment lifecycle.
A CFDI must declare the payment method used in the transaction. SAT recognises two categories:
PUE (Pago en una sola exhibición) — payment made in full at the time of sale
PPD (Pago en parcialidades o diferido) — deferred or instalment payment

After every CFDI is successfully stamped, iVendNext generates a SAT verification QR code directly on the POS Invoice. Store managers and customers can scan this QR code to access the SAT portal and independently verify that the CFDI is genuine, valid, and registered in SAT's records. This is particularly useful for enterprise customers who need to verify invoices before processing them in their own accounting systems.
Finance and operations teams frequently need to retrieve signed CFDI documents — for customer requests, audits, or reconciliation. iVendNext provides a Download Signed Invoice button directly on the POS Invoice form. Clicking it downloads a ZIP file containing both the signed XML CFDI and the corresponding PDF invoice. There is no need to log into FacturaAPI's portal or the SAT portal to retrieve documents.
In any live retail environment, network outages or API interruptions can occasionally prevent a CFDI from being stamped at the time of sale. iVendNext provides two recovery mechanisms.
For a single invoice, a Submit E-Invoice button appears on any POS Invoice that is missing a CFDI stamp. One click re-triggers the generation process without requiring the manager to navigate back to a list view.
For multiple invoices — such as a batch that failed during a connectivity outage — iVendNext supports bulk CFDI re-generation. Finance teams can select multiple invoices from the POS Invoice list and queue re-generation in a single action. The system processes them as background jobs, so the recovery operation does not interfere with live POS activity.
The practical effect of automatic CFDI generation is that Mexican retail compliance becomes invisible to the cashier. Sales staff complete transactions as they always have. They do not need to understand SAT requirements, select CFDI types, enter product keys, or verify UUIDs. All of that is handled by iVendNext and FacturaAPI working together in the background.
