Skip to content
Blogguide

GUIDE

How to export invoice data to JSON: fields, rows and review status

Use structured invoice data in your own scripts without guessing where each value came from. Download JSON after checking the proposed fields against the original.

By Kaliits · Reviewed · Editorial standards

Download the example ↓

The JSON export is an array of document records

Each document record contains an invoice object when an invoice is available, plus processing and review metadata. Do not assume every record contains a complete invoice. Inspect status, error information and confirmed before using a record.

Dates serialize in ISO form, such as 2026-10-03. Amounts and quantities are decimal strings so downstream code can choose decimal arithmetic without binary floating-point surprises. Unavailable scalar fields are null; missing values are not zero.

{
  "invoice": {
    "invoice_number": "DEMO-000042",
    "invoice_date": "2026-10-03",
    "currency": "EUR",
    "subtotal": "100.00",
    "tax": "20.00",
    "total": "120.00",
    "line_items": [
      {"description": "Demo supplies", "quantity": "2",
       "unit_price": "50.00", "amount": "100.00"}
    ]
  },
  "confirmed": true
}

Download first, validate before importing

The example above is an abbreviated document record using invented data. The downloadable sample shows the export envelope more fully. This is a downloadable file workflow; a public developer API, webhooks and automatic ERP connectors are not offered in the current pilot.

For a script, check the top-level array, then validate each invoice object. Parse money with a decimal library, retain identifiers as strings, and handle null explicitly. Keep the document ID in any downstream record so a correction can be traced back to its source.

  1. Upload a permitted invoice and review its fields and lines.
  2. Choose JSON in the document export actions.
  3. Validate status and confirmation, then read record.invoice.
  4. Map your downstream fields explicitly instead of importing every property.
  5. Recheck totals and preserve the original document in your own archive.

A short review that protects the spreadsheet

Check the supplier and customer separately, then the invoice reference, date and currency. Compare each line with the original. A correct total does not prove that the descriptions or quantities are right.

Keep invoice IDs as text, including leading zeros. Check decimal separators and date conventions before combining files from different countries. Missing values need attention; a blank field is more useful than an invented value.

  • Compare row count and continuation pages.
  • Check quantities, unit prices and line amounts.
  • Check subtotal, discounts, charges, tax and total.
  • Export a copy and retain your source in your own archive.

Current invoice pilot availability

Preview your first invoice result without an account. Verify your email to export. The free pilot includes 30 pages per month and a seven-day account history. Uploads accept PDF, JPG and PNG, up to 10 MB per file. PDFs can contain up to 30 pages, with a maximum of 10 pages per invoice.

English and French typed invoices are the supported focus. Handwriting and Arabic are not reliable supported cases. Review is part of the workflow. Read the privacy and availability page before uploading: the current free AI-assisted pilot accepts only invented or appropriately redacted, non-sensitive documents and is unavailable in the EEA, UK and Switzerland. The browser text extractors included in these guides do not send your files for AI processing.