Extract the folio fiscal UUID, issuer and recipient RFC, tax regime, uso CFDI, conceptos, and taxes from a Mexican CFDI 4.0 revenue invoice PDF.
The full guide: Folio Fiscal, RFC, and IVA on a Mexican CFDI 4.0
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
It is the SAT revenue invoice used in Mexico (Comprobante Fiscal Digital por Internet, document type "I" for ingreso). The extractor reads the fiscal folio UUID (the 36-character Folio Fiscal assigned when the SAT-authorized provider stamps the invoice), the stamp timestamp, the certification provider RFC (the PAC, or Proveedor Autorizado de Certificacion), the CFDI version (4.0), and the internal folio and serie.
The issuer (supplier) name and RFC and tax regime (catalog c_RegimenFiscal, such as 601 for the General Regime), and the recipient (buyer) name, RFC, tax-domicile postal code (new in CFDI 4.0), tax regime, and CFDI use (catalog c_UsoCFDI, such as G01 for acquisition of merchandise). The export indicator (catalog c_Exportacion, new in CFDI 4.0) is captured for international revenue.
Yes. The conceptos table returns each line with its clave_prod_serv (SAT product/service code), SKU, quantity, unit code, description, unit price, line amount, and tax object, and the impuestos table returns each tax with its impuesto code (002 = IVA, 001 = ISR, 003 = IEPS), tipo_factor, tasa_o_cuota (rate or fixed quota), and importe.
The subtotal, document-level discount, transferred (output) tax amount, withheld tax amount, and grand total, the currency and the exchange rate to MXN when the currency is not the peso, and the payment form (catalog c_FormaPago) and payment method (PUE for a single exhibition or PPD for deferred/installments).
The field set is modeled on the SAT CFDI 4.0 standard (Anexo 20, schema cfdv40.xsd with the Timbre Fiscal Digital complement). PDF only, up to 10MB and 100 pages, and the invoice is not retained after extraction.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See document data extraction if you run this for risk and compliance teams, or the extraction API if you are building it in.