Extract a remittance advice PDF to JSON
Everything below is the response the live API returned for a remittance advice, generated when this page was built. Not a description of what it would return — the output itself, including what it scored low on.
Who this is for
Accounts-receivable and cash-application teams reconciling a single payment against many invoices.
The job, in the words people search for: “match remittance advice to open invoices automatically”.
What makes this shape awkward
The interesting content is a table of invoice numbers and the amount paid against each — and the deductions column is frequently blank, which is a shape that makes naive header detection give up.
The measured result
| Pages read | 1 |
| Time | 15 ms (15 ms/page) |
| Labelled fields found unprompted | 4 |
| Tables | 1 (14 rows) |
| Input | remittance-advice.pdf (25 KB — synthetic, generated from a spec in the repo; real documents of this type cannot be published) |
Fields, with a schema
Ask for the fields you want by the label printed on the page. Each answer carries the text exactly as printed (raw), the value coerced to the type you asked for, a confidence, and a bounding box you can draw on the page to check it.
curl -X POST https://api.pdfcraft.dev/v1/extract \
-H "Authorization: Bearer $PDFCRAFT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"file": "<base64 of your remittance advice>",
"schema": {
"payment_reference": "string",
"payment_date": "date",
"total_paid": "currency"
}
}'What came back
| Field | raw | value | confidence |
|---|---|---|---|
payment_reference | PAY-2026-0455 | "PAY-2026-0455" | 60% |
payment_date | 2026-03-20 | "2026-03-20" | 70% |
total_paid | GBP 41,002.18 | 41002.18 GBP | 70% |
Every label it found without being asked
Send no schema and you get all of these, keyed by the label as printed. Useful for discovering what a new supplier’s layout actually contains before you write a schema against it.
Payment Reference, Payment Date, Payment Method, Total Paid
Tables
Invoice · Invoice date · Gross · Deduction · Paid · 14 rows × 5 columns · page 1
Table confidence 90%. Header confidence 100% — the first row was promoted out of the data.
| Invoice | Invoice date | Gross | Deduction | Paid |
|---|---|---|---|---|
| INV-2026-04100 | 2026-02-01 | 2,608.00 | 86.00 | 2,522.00 |
| INV-2026-04101 | 2026-02-02 | 2,868.00 | 141.00 | 2,727.00 |
| INV-2026-04102 | 2026-02-03 | 8,078.00 | — | 8,078.00 |
First 3 of 14 rows.
With options.rows_as_objects, the same row keyed by its header:
{
"Invoice": "INV-2026-04100",
"Invoice date": "2026-02-01",
"Gross": "2,608.00",
"Deduction": "86.00",
"Paid": "2,522.00"
}What this does not do
- No OCR. This reads the PDF’s text layer. A scanned or photographed remittance advice has no text layer and returns
422 extraction_failedwith the page numbers that were blank — deliberately, and quickly, so you can route it somewhere that does OCR rather than waiting on a guess. - No model. Run the same file twice and you get the same bytes back. That is the trade: it cannot infer a field that is not printed, and it cannot hallucinate one either.
- Ambiguity is reported, not resolved. A date like 03/04/2026 stays a string, and a bare
$returns a null currency, because guessing wrong on either is not something you can recover from downstream.
Try it on your own remittance advice
The playground takes a file and shows the same JSON, with every bounding box drawn over the page. No key and no signup for the first few; a free key gives you 100 pages a month.