Invoice extraction

Every invoice.Instantly structured.

Vendor, line items, taxes, totals, currency. DocParse reads invoices in any layout, any language — and returns the fields your AP system already speaks.

Start extracting See the API

100 pages free No card SOC 2 in progress

app.docparse.io / extractions / inv-20294.pdf

Live

ACME SUPPLY CO.

Invoice #INV-20294

Bill toNorthwind Logistics

Issue dateApril 14, 2026

Due dateMay 14, 2026

Subtotal$1,712.50

Tax (7.6%)$130.00

Total$1,842.50

JSONCSVWebhook98.6% confidence

{
  "vendor": "Acme Supply Co.",
  "invoice_no": "INV-20294",
  "issue_date": "2026-04-14",
  "due_date": "2026-05-14",
  "subtotal": 1712.50,
  "tax": 130.00,
  "total": 1842.50,
  "currency": "USD"
}

Extracted in 2.4s · 8 fields

Scroll

Pipe extracted data into any of these — via Zapier or signed webhooks

Zapier

Google Drive

Gmail

Slack

Sheets

Notion

Airtable

Webhook

Zapier

Google Drive

Gmail

Slack

Sheets

Notion

Airtable

Webhook

Why DocParse

Three reasons teams switch to us

Reads any layout, any language

No template setup. We process invoices from 180+ countries in 60 languages on the first run.

180+countries supported

Line items, not just headers

Every row, SKU, quantity, unit price, tax rate. Even when the invoice is rotated, low-res, or stapled to a packing slip.

47line items / sec on average

Three-way match, automated

Wires invoices to POs and goods receipts so your AP team only sees exceptions. Saves a full FTE at 20k invoices / month.

1.0 FTErecovered at 20k inv/mo

How it works

From raw invoices
to structured data, in four steps.

Drop document, paste URL, or POST file

PDFPNGJPGTIFFDOCXHEICHTMLEMLXLSX

The schema

Starter schema for invoices.
Tweakable in seconds.

The invoices template comes with a 10-field starter schema based on the most common fields teams pull from invoices. Add your own fields, mark which are required, and change types in the dashboard or via the REST API.

Invoices · default schema

vendorstringrequired99.7%

invoice_nostringrequired99.4%

issue_datestringrequired99.5%

due_datestringoptional98.9%

subtotalnumberrequired99.6%

taxnumberoptional98.4%

totalnumberrequired99.8%

currencystringrequired99.9%

line_itemsarrayrequired97.8%

po_numberstringoptional99.2%

JSON SchemaTypeScriptPython

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Invoices",
  "type": "object",
  "required": [
    "vendor",
    "invoice_no",
    "issue_date",
    "subtotal",
    "total",
    "currency",
    "line_items"
  ],
  "properties": {
    "vendor": {
      "type": "string"
    },
    "invoice_no": {
      "type": "string"
    },
    "issue_date": {
      "type": "string"
    },
    "due_date": {
      "type": "string"
    },
    "subtotal": {
      "type": "number"
    },
    "tax": {
      "type": "number"
    },
    "total": {
      "type": "number"
    },
    "currency": {
      "type": "string"
    },
    "line_items": {
      "type": "array"
    },
    "po_number": {
      "type": "string"
    }
  }
}

What to expect

Field-level accuracy per field.

Multi-modal models do the reading, and accuracy depends on document quality. The numbers below are illustrative ranges we've seen on invoices — run your own documents and compare against a small ground-truth set before you scale.

98.9%

illustrative field-level
accuracy ceiling

10starter fields

Anylanguage supported

25 MBmax file size

FieldAccuracy

vendor

99.6%

invoice_no

99.4%

total

99.8%

subtotal

99.6%

tax

98.4%

line_items

97.8%

po_number

99.2%

currency

99.9%

The API

One endpoint.
Every output you need.

# Extract with one POST
curl -X POST "https://api.docparse.io/v1/invoices" \
  -H "Authorization: Bearer $DOCPARSE_KEY" \
  -F file=@"invoice-acme-20294.pdf" \
  -F schema="invoice" \
  -F webhook="https://api.acme.co/incoming"

# Returns:
{
  "status": "complete",
  "confidence": 0.987,
  "latency_ms": 2412,
  "data": { ... }
}

Plain HTTP, no SDK lock-in

Bearer-token auth with revocable, SHA-256-hashed API keys. Call it from any language that can hit a REST endpoint — we publish docs and copy-pasteable snippets, not opinionated wrappers.

cURLPythonNode.jsGoRubyPHPJava.NET

Signed webhooks for async

Register an endpoint, set the events, and we POST signed deliveries (HMAC-SHA256, Standard Webhooks spec) as extractions finish. Every attempt is logged in the dashboard with response code, body, and timing.

Webhook delivery log · per-endpoint retries

The alternatives

Why teams switch from regex.

A look at how DocParse compares to the three things you've probably already tried.

Regex + scripts

Manual review (BPO)

Rossum / Hypatos

DocParse

Works on a layout it has never seen

partial

Handles handwriting and scans

partial

Custom fields without per-vendor setup

Multi-lingual out of the box

partial

REST API + signed webhooks + Zapier

partial

Pricing scales with pages, not seats

partial

Free tier, every month, forever

partial

Time-to-first-extraction

Days

Weeks

5 minutes

Where the data goes

Reach the tools you already run.

DocParse ships two integration surfaces directly — REST API and signed webhooks — plus a native Zapier app that opens up everything else.

Zapier

Automation

Webhooks

API

REST API

API

JSON export

Export

CSV export

Export

Google Drive

via Zapier

Google Sheets

via Zapier

Gmail

via Zapier

Outlook

via Zapier

Slack

via Zapier

Dropbox

via Zapier

Airtable

via Zapier

Notion

via Zapier

HubSpot

via Zapier

Salesforce

via Zapier

Make.com

via Webhooks

n8n

via Webhooks

Postgres

via Webhooks

REST API · Signed webhooks (HMAC-SHA256) · Zapier to 6,000+ apps · JSON / CSV export

Common patterns

How teams use DocParse for invoices.

Illustrative scenarios drawn from teams piloting DocParse — names and figures are examples, not customer quotes.

“

We were paying a BPO 11 cents per invoice. Switched to DocParse, dropped to under 4 cents, and the line-item accuracy actually went up.

Priya Shah

AP Lead · Lattice Bank

$240ksaved in year one

“

Our biggest fear was edge-case vendors with weird PDFs. DocParse handled all of them on day one. Two-week pilot, ten-minute integration.

Daniel Park

Controller · Parallax

10 minto go live

“

The webhook-to-NetSuite pipeline meant our AP team stopped touching invoices entirely except for exceptions. We hired one fewer person.

Maya Okonkwo

CFO · Tidemark

0invoices manually keyed

Frequently asked

The questions teams ask before they sign up.

Does it handle international invoices?

Yes — 60 languages, RTL scripts, all common tax regimes (VAT, GST, sales tax). Currency is auto-detected from symbol, ISO code, or context.

What about PO matching?

Push your PO and GR data via API; DocParse returns invoices marked "matched", "partial-match", or "exception" with a reason field. Most teams auto-approve matches and review only exceptions.

Can it extract individual line items?

Yes. Every row with description, SKU, quantity, unit price, line-tax, and line-total. Nested tax rates per line are supported.

How do you handle duplicate invoices?

Each extraction returns a content-hash. The dashboard flags duplicates against the prior 12 months automatically; you can also dedupe in your own DB on the hash.

Do you push to NetSuite / QuickBooks?

Yes — native integrations for both, plus generic webhook + CSV. The integration writes a vendor-bill record with line items already coded to your GL accounts.

How is pricing calculated?

Per invoice, regardless of page count. Volume discounts kick in at 10k / month. No per-field, per-vendor, or per-seat fees.

Stop keying invoices.

Live in ten minutes. Free for your first hundred invoices. NetSuite, QuickBooks, and Sage all wired in.

Start extracting Talk to sales

Free for first 100 pages 5-minute setup No credit card

Every invoice.Instantly structured.

Three reasons teams switch to us

Reads any layout, any language

Line items, not just headers

Three-way match, automated

From raw invoices
to structured data, in four steps.

Define the fields

Upload the file

Multi-modal AI reads it

Get structured data back

Starter schema for invoices.
Tweakable in seconds.

Field-level accuracy per field.

One endpoint.
Every output you need.

Plain HTTP, no SDK lock-in

Signed webhooks for async

Why teams switch from regex.

Reach the tools you already run.

How teams use DocParse for invoices.

The questions teams ask before they sign up.

Stop keying invoices.

Every invoice.Instantly structured.

Three reasons teams switch to us

Reads any layout, any language

Line items, not just headers

Three-way match, automated

From raw invoicesto structured data, in four steps.

Define the fields

Upload the file

Multi-modal AI reads it

Get structured data back

Starter schema for invoices.Tweakable in seconds.

Field-level accuracy per field.

One endpoint.Every output you need.

Plain HTTP, no SDK lock-in

Signed webhooks for async

Why teams switch from regex.

Reach the tools you already run.

How teams use DocParse for invoices.

The questions teams ask before they sign up.

Stop keying invoices.

From raw invoices
to structured data, in four steps.

Starter schema for invoices.
Tweakable in seconds.

One endpoint.
Every output you need.