Skip to content
Document
Invoices and bills
Typical fields
vendor · tax_id · line_items · total
Output
JSON · Excel · CSV
Plans
$0 · $9.90 · $100 · Custom

Invoices in.
Validated fields out.

An invoice parser for accounts payable: invoices and bills arrive by upload, e-mail or API, and the fields you define are extracted and checked against your validation rules before they reach your system.

30 minutes · no commitment

SampleRESULT · invoice.pdfJSON
{  "extracted_data": [    {      "vendor": "Acme Supplies Inc.",      "tax_id": "12-3456789",      "invoice_number": "INV-2417",      "reference_key": "R-3187",      "issue_date": "2026-03-04",      "due_date": "2026-04-03",      "line_items": [        { "item": "Pens", "qty": 4, "amount": 248.00 },        { "item": "Ink", "qty": 6, "amount": 711.00 },        { "item": "Lamp", "qty": 7, "amount": 763.00 }      ],      "taxes": 137.76,      "total": 1859.76,      "payment_reference": "PAY-4413"    }  ]}

Fictional invoice; values are illustrative. Only the extracted_data of a result is shown.

What changes in accounts payable.

01
Process
How the work changes

Done by hand

  • Each invoice is opened, read and typed into the ERP by a person.
  • Totals, tax IDs and due dates are checked by eye.
  • The last entries are keyed and re-checked before month-end close.

With Parser

  • Invoices arrive by upload, e-mail or API. The fields in your template are read from each one.
  • Validation rules you define check the values before they enter your system: a total against its line items, for example.
  • The result reaches your system by webhook or API, or as JSON, Excel or CSV.
02
Fields
Typical fields and a sample

Fields come from your extraction template.

These are the fields invoices usually carry. Add, rename or drop any of them in the template.

  • vendor
  • tax_id
  • invoice_number
  • reference_key
  • issue_date
  • due_date
  • line_items
  • taxes
  • total
  • payment_reference

Field names are set in the template and come back as the keys of the result. Define your own fields in the API guide.

03
Solutions
Where to look next

Related solutions.

  • 3.1

    Contract extraction

    Parties, dates, amounts and the clauses you name, read at intake.

    Fields parties effective_date term contract_value

    Contract extraction, see use case
  • 3.2

    Receipts & expenses

    Merchant, tax ID, total, taxes and expense category from receipts and proofs of payment.

    Fields merchant tax_id total taxes

    Receipts & expenses, see use case
  • 3.3

    Bank statements

    Account, period, opening and closing balances and one row per transaction from bank statements.

    Fields account_holder account_number period_end closing_balance

    Bank statements, see use case
  • 3.4

    Bills of lading

    Shipper, consignee, ports, vessel and cargo lines from each bill of lading, to JSON or Excel.

    Fields bl_number shipper shipped_on_board_date cargo_lines

    Bills of lading, see use case
  • 3.5

    Logistics & freight

    Bills of lading, freight invoices, rate confirmations and delivery receipts, read into shipment fields.

    Fields bol_number shipper consignee gross_weight_lb

    Logistics & freight, see industry
  • 3.6

    Insurance

    Claim forms, policy schedules, certificates of insurance and repair estimates, read into claim and coverage fields.

    Fields claim_number policy_number loss_date claimed_amount

    Insurance, see industry

Your documents are different? Book a demo.

Bring a real invoice.

In the demo we process your documents live — no slides, no fluff.

30 minutes · no commitment

  • Self-serve

    Free, Starter ($9.90/month) and Pro ($100/month) start when you sign up. No card required for Free.

  • Enterprise

    By contract · your own model key · an engineer for your team · setup done for you if you want it · POC on your documents.