Use case / Accounts payable

Invoice images into reviewable JSON.

Replace repeated data entry with a schema that names the invoice fields your accounts-payable workflow actually needs.

Start free See a real request and response

Example schema

Ask for the fields that move work forward.

Field names, types, and descriptions travel with every extraction request, so the response matches the object your code already expects.

Schema fields5 fields

invoice_numbervendor_nameinvoice_datepurchase_ordertotal_due

Response

What your integration receives.

The terminal result for the schema above. Validate it against your own types before writing to a system of record.

extract.tsTypeScript client

const { result } = await client.extractFile({
  file,
  idempotencyKey,
  input: { fileName, mediaType, sizeBytes },
  schema: {
    version: "1",
    fields: [
      { name: "invoice_number", type: "string" },
      { name: "vendor_name", type: "string" },
      { name: "invoice_date", type: "string" },
      { name: "purchase_order", type: "string" },
      { name: "total_due", type: "number" }
    ]
  }
});

terminal resultcompleted

{
  "invoice_number": "INV-2048",
  "vendor_name": "Northwind Office Supply",
  "invoice_date": "2026-06-18",
  "purchase_order": "PO-7781",
  "total_due": 1248.5
}

Production path

From document to validated workflow input.

Define required and optional invoice fields.
Upload a supported image directly to regional storage.
Create an authenticated extraction job with an idempotency key.
Validate the terminal result before posting downstream.

FAQ

Frequently asked questions

Can the invoice schema match my ERP fields?

Yes. Routeser requests carry user-defined field names, types, descriptions, and required flags.

How should uncertain fields be handled?

Treat warnings and review outcomes as workflow signals and validate the result before automatic posting.

Can Routeser read multi-page invoices?

Yes. A PDF is rendered and metered per page, and the schema you submit applies across the document.

Next step

Run this schema on your own documents

Open the console to define these fields in a workspace and evaluate them against real documents.

Open console