Mexico e-invoicing · for US companies
CFDI 4.0 e-invoicing for US companies doing business in Mexico
If your Mexican subsidiary, distributor or carrier needs a factura and your ERP cannot produce one, we build the piece in between: CFDI 4.0 issued from your own system, stamped by an authorized provider, stored and reconciled. Engineers who speak the SAT's rules natively, working on your US workday.
Architecture review (1 week): $2,500
A CFDI integration lets a US company issue Mexican electronic invoices (CFDI 4.0) from the ERP or platform it already runs, instead of retyping every sale into a Mexican billing portal. We map your transactions to the SAT's XML format, connect an authorized stamping provider, and handle receipts, payment complements, cancellations and the monthly archive your Mexican accountant needs.
What breaks when a US company starts invoicing in Mexico
Typical situations (not client quotes)
- Our Mexican customers will not pay until they get a valid factura, and SAP cannot produce one.
- Someone in Monterrey retypes every invoice into a billing portal. Two systems, two sets of numbers.
- Our carrier asked for a Carta Porte and nobody here knew what that was.
In Mexico an invoice is not a PDF. It is an XML document (CFDI) that has to be stamped by an authorized provider before it exists for tax purposes, with the customer's tax ID, tax regime, postal code and intended use filled in exactly as the SAT has them on file. A mismatch means the invoice is rejected and payment waits.
US ERPs do not do this out of the box. The usual workaround is a person retyping invoices into a Mexican billing portal, which means the ERP and the tax records drift apart, payment complements get forgotten, and month-end close becomes a hunt for XML files. If goods move by road inside Mexico, the Carta Porte complement adds a second layer of required data.
What we build
A CFDI layer that sits between your system of record and the SAT. Your ERP, e-commerce platform or custom software stays the source of truth; we read the transaction, build the CFDI 4.0 XML with the right catalogs and validations, send it to an authorized stamping provider (PAC), store the stamped XML and PDF, and push the result back to your system and to your customer.
We built it for ourselves first: Guiadalajara’s CFDI 4.0 stamping is built and tested with real stamps in its test environment. The service we build for you covers income invoices, payment complements, credit notes and cancellations with the reason codes the SAT requires. Related work often starts with a systems integration review.
- Mapping of your transactions to CFDI 4.0 fields and SAT catalogs
- Connection to an authorized stamping provider (PAC) with your company's digital seal
- Income invoices, payment complements, credit notes and cancellations with reason codes
- Carta Porte complement when goods move by road in Mexico
- Stamped XML and PDF delivered to your customer and stored for the retention period you set (article 30 of Mexico's Federal Tax Code says accounting records are kept for five years)
- Monthly export of XML files for your Mexican accountant
- Reconciliation report: every ERP transaction matched to its CFDI
What you get · Mexico e-invoicing (CFDI)
CFDI service connected to your ERP
Reads invoices from SAP, NetSuite, Dynamics, Odoo or your own platform through their APIs or exports.
Stamping with your seal
Your RFC, your certificate, an authorized PAC. We never invoice in your name.
Customer validation
Tax ID, regime and postal code checked before stamping, so invoices are not rejected after the fact.
Payment complements
Generated when the payment lands, not when someone remembers.
Archive and accountant export
Stamped XML and PDF stored and exported by month, in the structure your accountant asks for.
Reconciliation dashboard
One screen: issued, pending, cancelled, and anything that does not match the ERP.
How we work · Mexico e-invoicing (CFDI)
Architecture review
One week. We look at your ERP, your Mexican entity's setup, the transaction types you issue and where the data lives. You get a written report and a fixed price.
1 week, $2,500
Mapping and sandbox
We map every transaction type to CFDI fields and stamp test invoices against the PAC's sandbox until your accountant signs off.
2–3 weeks
Integration and go-live
Production connection, first live invoices under supervision, and the monthly export running.
2–4 weeks
Run
Monthly support with a response time in writing, and updates whenever the SAT changes a catalog or a rule.
ongoing
Proof · Mexico e-invoicing (CFDI)
We are a Mexican studio. The CFDI module of our own platform is built and tested with real stamps in its test environment, through the same kind of PAC connection we would build for you.
- Guiadalajara’s CFDI 4.0 stamping is built and tested with real stamps in its test environment — Source: Our own platform (Guiadalajara), test environment, checked October 16, 2026
- every Guiadalajara release backs up the database before anything changes — Source: Our own platform (Guiadalajara), in production, checked October 16, 2026
Pricing · Mexico e-invoicing (CFDI)
| Item | Price |
|---|---|
| Architecture review (1 week) | $2,500 |
| Monthly support (20 hours) | $1,800/mo |
Invoices in US dollars, net 15, by wire transfer. Full rate card on the pricing page.
What we build with
- TypeScript
- Node.js
- PostgreSQL
- CFDI 4.0 (SAT)
- PAC stamping
- SAP / NetSuite / Dynamics APIs
Questions · Mexico e-invoicing (CFDI)
What is a factura in Mexico?
A factura is a Mexican electronic invoice: an XML document in the SAT's CFDI format, stamped by an authorized provider, that proves a sale for tax purposes. A PDF alone is not a valid invoice in Mexico; the XML is the legal document and the PDF is its printed representation.
Can SAP or NetSuite issue CFDI 4.0 on their own?
Not without a localization layer. The ERP holds the sale; a CFDI service has to build the XML with SAT catalogs, validate the customer's tax data, stamp it with a PAC and store the result. That layer is what we build and connect to your ERP.
Do you invoice on our behalf?
No. Every CFDI is issued with your Mexican entity's RFC and digital seal certificate. We build and operate the software; the tax obligation and the documents stay yours.
What is a payment complement and why does it matter?
It is a CFDI that the SAT's Annex 20 calls for when a customer pays an invoice issued with deferred payment (PPD), linked to that invoice. Complements issued by hand get forgotten, so we generate them from the payment event in your system.
What is Carta Porte?
A complement to the CFDI that describes goods, route, vehicle and operator when merchandise is transported inside Mexico. If your products move by road from the border or between plants, your carrier or your own fleet needs it, and the data has to come from your shipping records.
Does our Mexican accountant need to be involved?
Yes, and we want them in the room. The accountant confirms tax regimes, usage codes and the archive format; we make the software produce exactly that. We do not give tax advice.
How long does a CFDI integration take?
Typically five to eight weeks after the one-week review: two to three weeks of mapping and sandbox stamping, then two to four weeks of integration and supervised go-live. The exact plan is in the fixed-price proposal.
Related
Sources
- Factura electrónica (CFDI) (opens in a new tab) · Servicio de Administración Tributaria (SAT) · accessed · official source
- Complemento Carta Porte (opens in a new tab) · Servicio de Administración Tributaria (SAT) · accessed · official source
Notice: General information, not legal or tax advice; check with your attorney or accountant. Verified on . If something is out of date, tell us at [email protected].
How many invoices get retyped into a Mexican portal each month?
Start with a one-week review. You get a written report and a fixed price whether or not you hire us for the build.