Can FutureSmart Document Intelligence read a cleanly scanned document accurately?
FutureSmart Document Intelligence correctly extracted the expected structured values from a cleanly scanned document. The scanned twin had no recoverable text layer, and the tool returned the invoice number, site, line items, subtotal, VAT, and total due matching the digital version.
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 counts this row.
Image-only twin, same schemaPassEvidence
{ "summary": "This invoice from Thistlewood Plant & Tool Hire details the weekly rental charges for construction equipment, including a telehandler, generators, and site fencing. The total amount due for the hire period of March 3rd to March 10th, 2026, is £1,754.40, inclusive of VAT.", "document_type": "invoice", "currency": "GBP", "invoice_number": "TPH-3301", "billed_to": "Oakbridge Construction Ltd", "site": "Oakbridge Depot Extension", "hire_period": "03 Mar - 10 Mar 2026", "line_items": [ { "amount": 850, "quantity": 1, "unit_price": 850, "description": "Telehandler, 4-tonne, weekly hire" }, { "amount": 420, "quantity": 2, "unit_price": 210, "description": "Generator, 20kVA, weekly hire" }, { "amount": 192, "quantity": 8, "unit_price": 24, "description": "Site fencing, per 10m panel, weekly" } ], "subtotal": 1462, "tax": 292.4, "total_due": 1754.4, "file_name": "SiblingA1_Thistlewood_PlantHire_-_Scanned_Twin.pdf" }
Copied from Proof 1 · Output file (text), lines 1–33
Open the text file ↗{
"summary": "This invoice from Thistlewood Plant & Tool Hire to Oakbridge Construction Ltd details the weekly hire charges for construction equipment, including a telehandler, generators, and site fencing. The total amount due for the hire period of March 3 to March 10, 2026, is £1,754.40, inclusive of VAT.",
"document_type": "invoice",
"currency": "GBP",
"invoice_number": "TPH-3301",
"billed_to": "Oakbridge Construction Ltd",
"site": "Oakbridge Depot Extension",
"hire_period": "03 Mar - 10 Mar 2026",
"line_items": [
{
"amount": 850,
"quantity": 1,
"unit_price": 850,
"description": "Telehandler, 4-tonne, weekly hire"
},
{
"amount": 420,
"quantity": 2,
"unit_price": 210,
"description": "Generator, 20kVA, weekly hire"
},
{
"amount": 192,
"quantity": 8,
"unit_price": 24,
"description": "Site fencing, per 10m panel, weekly"
}
],
"subtotal": 1462,
"tax": 292.4,
"total_due": 1754.4,
"file_name": "SiblingA1_Thistlewood_PlantHire.pdf"
}Copied from Proof 2 · Output file (text), lines 1–33
Open the text file ↗Its contents are printed above, under What the tool returned.
Open the text file ↗Its contents are printed above, under Native output.
Open the text file ↗These are scenario-level criteria. Each test case's Expected and Found are listed separately.
- Whether the visible text from the scanned page is recovered accurately.
- Whether the page is not silently skipped or treated as empty because no text layer exists.
- Whether the output stays faithful to the visible content without inventing text.
- Whether scanned pages are handled as real input, not hidden by omission.
| ✓ | Found: Both runs matched on all schema values; only file_name and summary wording differed. |
The product extracted the same invoice values from the digital PDF and the image-only twin. The twin had no recoverable text layer, and the only differences were the file name and summary wording.
Summary wording differs. The summary text uses different wording in the two runs, but the stated total is the same.
Twin is larger. The scanned twin is much larger than the digital PDF, consistent with images replacing a text layer.
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 row says which 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 row 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 | FutureSmart Document Intelligence → |
Global scenario definition → · Global capability definition →
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.