AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 7 November 2026

Can Reducto extract values from a document that mixes digital and scanned pages?

Reducto extracted all five requested values in one call from an invoice mixing digital and scanned pages. The two values exclusive to the scanned page were returned accurately, and the digital-page values were preserved.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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.

Values on both digital and scanned pagesPassEvidence
What we sent

In Reducto Studio, we used the three-page invoice PDF as the extraction input.

InputDocument (PDF)
Input PDF: three-page invoice with digital pages surrounding a scanned delivery note
Open the PDF ↗
What the tool returned

Copied from Output file (JSON), result

FieldValueCited page
invoice_referenceHIS-44021
order_referenceFWT-PO-22911
vehicle_registrationLR19 KVM2
received_byJ. Whitlock2
total_due£1,246.803

Extraction response: five returned values with citations to their source pages

Open the whole JSON file ↗
Expected vs. Found
✓Expected: Return every requested value from the digital and scanned pages without omissions, invention or altered values.Found: All five values were returned without omissions, invention or degradation. The returned total and invoice total were both £1,246.80, including the pound sign.
Supporting proof
Proof 1Screenshot
Studio screenshot: page 1 invoice and order references highlighted beside the extracted results
Open original ↗
Proof 2Screenshot
Studio screenshot: page 2 scanned vehicle registration and delivery recipient highlighted beside the results
Open original ↗
Proof 3Screenshot
Studio screenshot: page 3 total highlighted beside the extracted results
Open original ↗
Cited values2 values from this file
job_id
363d23b8-3208-4e90-8808-e1a461606056
duration
2.257169
Why this result

Values had to be read from both page types in one extraction. The scanned page had no text layer, yet its two exclusive values were returned with citations to page 2. The delivery recipient came from the recipient line, not the nearby driver line.

Also observed in this test case

No separate OCR charge. The extraction’s usage report counted 0 OCR pages and billed no separate OCR step for the scanned delivery note on page 2.

Tested by Shivohum Pandita · evidence dated 29 October 2026

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.

Software that produced the output
Reducto
Build or version
Not exposed by the hosted product
Plan or tier
Standard
Model
Extract v4 (the default extract model) and parse model r-1 (Preview)
Surface
Web app
Set up before the run
The invoice had to contain a digital first page, an image-only delivery note second, and a digital third page holding the total due. Requested values spanned these pages; extraction used the standard path with citations enabled.
Schema
citations enabled · five required text fields, each with a description: invoice_reference, order_reference, vehicle_registration, received_by, total_due
Tested
29 October 2026 · Shivohum Pandita

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

LevelNameScope
BenchmarkStructured Document Extraction →19 scenarios · 10 tools
CapabilityOCR →
ScenarioA document mixing digital and scanned pages →
ToolReducto →

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.

from the publication record
21 November 2026First publishedStructured Document Extraction v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/structured-document-extraction/results/reducto/a-document-mixing-digital-and-scanned-pages · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-07

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.

Input · Document (PDF) ↗application/pdf · 176 KB
Output file (JSON) ↗application/json · 8 KB
Proof 1 · Screenshot ↗image/png · 205 KB
Proof 2 · Screenshot ↗image/png · 382 KB
Proof 3 · Screenshot ↗image/png · 209 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)89fb14d7c0897bbfef47ffa3aa3930ee7eccf62c8a9430710d1906598c9bdfec
Output file (JSON)57a89a519d2d4366059bf7fdb57a3b51b54879731254d6ddaeb922f2f3125dfd
Proof 1 · Screenshota3b34e891332c941bc61d1e60b66c8abaea66f5ea7fbb119f9f048c4911640ba
Proof 2 · Screenshot7fcce0ff7716543646439e9541d68b2284a0760a6bfb80d3693a76cbe4bc69a4
Proof 3 · Screenshota906d420dad191ba531dc022f7f38c8dc8c29e3f1b34cd7ace93ec18b5a1a36e