Nexcar

Document types

Catalog of types you can assign when uploading a document. If you omit the type, Nexcar tries to detect it automatically.

Catalog#

Type (type)DescriptionTypical extracted data
facturaInvoice (PDF) or CFDI XML for the vehicleVIN, issuer/recipient RFC, total amount, date
factura_xmlCFDI 4.0 XMLUUID, RFC, totals, line items
ineMexican INE/IFE official ID of the ownerName, CURP, validity, voter key
pasaporteMexican or foreign passportName, date of birth, validity
repuveREPUVE certificateVIN, make, model, year, vehicle status
tenenciaState vehicle-tax payment receiptYear, amount, payment date, plate
placasCirculation card or plates certificatePlate, validity, owner
comprobante_domicilioUtility bill (electricity, water, phone, property)Address, holder, issue date
comprobante_pagoBank receipt / SPEIAmount, bank, date, beneficiary
pedimentoCustoms declaration (imported vehicles)Pedimento number, customs office, date
verificacionVehicle emissions inspection certificateHologram, validity, plate
multasTraffic violations clearanceOutstanding fines, issue date
acta_nacimientoOwner's birth certificateName, CURP, date and place
comprobante_ingresosBank statement or pay stubHolder, period, amount
responsivaSigned transfer-of-responsibility letterBuyer, seller, date, VIN

Rules#

  • If you upload a document with type, Nexcar respects your classification but may flag inconsistencies.
  • If you upload without type, automatic content-based classification runs. The result arrives via the document.classified webhook.
  • You can change the type at any time with POST /v1/documents/{id}/classify or /reclassify (the latter re-runs OCR).

Linked documents#

Some types accept a parent document through parent_file_id. For instance:

  • A factura_xml can be linked to its matching factura (PDF).
  • A comprobante_pago can be linked to the tenencia it pays for.

This way, lookups return coherent groups of related documents.