Can Reducto extract text accurately from a clean scan?
Reducto read the clean scan without changing the values extracted from the digital original. Both versions returned all 20 requested values, preserving currency formatting and hire-period punctuation.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
Image-only twin, same schemaPassEvidence
{
"instructions": {
"schema": {
"type": "object",
"properties": {
"invoice_number": { "type": "string", "description": "The invoice number." },
"bill_to": { "type": "string", "description": "The customer the invoice is billed to." },
"site": { "type": "string", "description": "The site the equipment was hired for." },
"hire_period": { "type": "string", "description": "The hire period as printed." },
"currency": { "type": "string", "description": "The currency of the invoice." },
"subtotal": { "type": "string", "description": "The subtotal before tax, as printed." },
"tax": { "type": "string", "description": "The tax / VAT amount, as printed." },
"total_due": { "type": "string", "description": "The total amount due, as printed." },
"line_items": {
"type": "array",
"description": "Every hired item line on the invoice, one entry per line.",
"items": {
"type": "object",
"properties": {
"description": { "type": "string", "description": "Description of the hired item." },
"quantity": { "type": "string", "description": "Quantity hired." },
"unit_price": { "type": "string", "description": "Unit price as printed." },
"amount": { "type": "string", "description": "Line amount as printed." }
},
"required": ["description", "quantity", "unit_price", "amount"]
}
}
},
"required": ["invoice_number", "bill_to", "site", "hire_period", "currency", "subtotal", "tax", "total_due", "line_items"]
}
},
"settings": {
"citations": { "enabled": true }
}
}Copied from Output file 1 (JSON), result › invoice_number › value
TPH-3301
Copied from Output file 1 (JSON), result › bill_to › value
Oakbridge Construction Ltd
Copied from Output file 1 (JSON), result › site › value
Oakbridge Depot Extension
Copied from Output file 1 (JSON), result › hire_period › value
03 Mar - 10 Mar 2026
Copied from Output file 1 (JSON), result › currency › value
£
Copied from Output file 1 (JSON), result › subtotal › value
£1,462.00
Copied from Output file 1 (JSON), result › tax › value
£292.40
Copied from Output file 1 (JSON), result › total_due › value
£1,754.40
Copied from Output file 1 (JSON), result › line_items · an excerpt
[ { "description": "Telehandler, 4-tonne, weekly hire", "quantity": "1", "unit_price": "£850.00", "amount": "£850.00" }, { "description": "Generator, 20kVA, weekly hire", "quantity": "2", "unit_price": "£210.00", "amount": "£420.00" }, { "description": "Site fencing, per 10m panel, weekly", "quantity": "8", "unit_price": "£24.00", "amount": "£192.00" } ]
Excerpt ends here. Open the source for the complete output.
Copied from Output file 2 (JSON), result › invoice_number › value
TPH-3301
Copied from Output file 2 (JSON), result › bill_to › value
Oakbridge Construction Ltd
Copied from Output file 2 (JSON), result › site › value
Oakbridge Depot Extension
Copied from Output file 2 (JSON), result › hire_period › value
03 Mar - 10 Mar 2026
Copied from Output file 2 (JSON), result › currency › value
£
Copied from Output file 2 (JSON), result › subtotal › value
£1,462.00
Copied from Output file 2 (JSON), result › tax › value
£292.40
Copied from Output file 2 (JSON), result › total_due › value
£1,754.40
Copied from Output file 2 (JSON), result › line_items · an excerpt
[ { "description": "Telehandler, 4-tonne, weekly hire", "quantity": "1", "unit_price": "£850.00", "amount": "£850.00" }, { "description": "Generator, 20kVA, weekly hire", "quantity": "2", "unit_price": "£210.00", "amount": "£420.00" }, { "description": "Site fencing, per 10m panel, weekly", "quantity": "8", "unit_price": "£24.00", "amount": "£192.00" } ]
Excerpt ends here. Open the source for the complete output.
Extraction result: the digital invoice's values with page citations
Open the whole JSON file ↗Extraction result: the scanned invoice's values, identical to the digital extraction
Open the whole JSON file ↗| ✓ | Expected: The digital document and its image-only scan must return identical values, with both extracted for this comparison.Found: Both extractions returned the same 20 values, including a subtotal of £1,462.00 and a total due of £1,754.40 in each. |
- job_id
- 199071d2-d155-4a24-a096-e1ccd4d9706d
- duration
- 33.241049
- job_id
- cafbcc81-2e63-4577-a61a-62e48f9b095e
- duration
- 38.024216
The scan had to yield the same values as the digital invoice. With no text layer to rely on, the identical outputs demonstrate reading from page images rather than embedded text.
Extraction times. Processing the scan took about 38 seconds, versus about 33 seconds for the digital invoice. The roughly 5-second gap was too small for scanning to dominate processing time.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Structured Document Extraction → | 19 scenarios · 10 tools |
| Capability | OCR → | |
| Scenario | A cleanly scanned document → | |
| Tool | Reducto → |
Global scenario definition → · Global capability definition → · Reducto product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.