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.
Example schema
Ask for the fields that move work forward.
Field names, types, and descriptions travel with every extraction request.
Schema fields5 fields
invoice_numbervendor_nameinvoice_datepurchase_ordertotal_dueProduction path
From image 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.
Questions, answered plainly
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.
Is the public invoice demo a live extraction?
No. It is a fixed synthetic sample paired with a stored result and makes no network request.
Next step
Inspect the output shape
Start with a fixed, no-upload sample before evaluating your own documents in an authenticated workspace.