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

Can Landing AI process scanned pages inside a mixed digital PDF?

Landing AI failed this mixed digital-and-scanned PDF case. All four fields came back, and the scanned-page values were exact, but the total due returned as "#1,246.80" even though the page text and rendering show "£1,246.80"; the run also carried both parse and extract ids.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
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 pagesFailEvidence
What we sent
InputDocument (PDF)
Input PDF: mixed digital and scanned pages, page 3 totals
Open the PDF ↗
What the tool returned
JSONthe whole file · copied lines 2–7
{
  "data": {
    "total_due": "#1,246.80",
    "received_by": "J. Whitlock",
    "vehicle_registration": "LR19 KVM",
    "line_item_description": "Dosing pump, 240V, Chemical feed tubing, 10m coil, Inline flow sensor"
  },
  "extractionMetadata": {
    "total_due": {
      "value": "#1,246.80",
      "ranges": [ { "start": 1815, "end": 1824 }, { "start": 761, "end": 788 } ]
    },
    "received_by": { "value": "J. Whitlock", "ranges": [ { "start": 969, "end": 986 } ] },
    "vehicle_registration": { "value": "LR19 KVM", "ranges": [ { "start": 839, "end": 869 } ] },
    "line_item_description": {
      "value": "Dosing pump, 240V, Chemical feed tubing, 10m coil, Inline flow sensor",
      "ranges": [
        { "start": 1331, "end": 1348 },
        { "start": 1425, "end": 1455 },
        { "start": 1531, "end": 1549 },
        { "start": 885, "end": 918 }
      ]
    }
  },
  "extract_id": "extract-01m4an9njhahxsteszb434cx21",
  "parse_run_id": "parse-01m4an8yxeaj98q65443v587vd",
  "created_at": "2026-10-07T07:47:32.265Z"
}

Output JSON: all four fields and parse/extract ids

Copied from Output file (JSON), lines 2–7

Open the JSON file ↗
Expected vs. Found
✗Expected: Return all requested values from both page types.Found: All four values were returned. The scanned-page values were exact, but the total due came back with "#" instead of "£", and no uncertainty was reported.
Supporting proof
Proof 1Screenshot
Screenshot: extracted values and schema on page 3
The tool’s response is printed above, under What the tool returned. Show this screenshotOpen original ↗
Why this result

The case required values from both page types. The scanned-page values were exact, but the total due came back as "#1,246.80" even though the page shows "£1,246.80", so the mixed-page extraction fails.

Also observed in this test case

Merged descriptions. The three goods-table descriptions were merged into one string in the description field.

Tested by Rugved Nichite · evidence dated 7 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
Landing AI
Build or version
DPT-3 Pro (parse model; app version not exposed)
Surface
Web app
Set up before the run
A document had to have a digital page first and a scanned image-only page second, with one requested value only on the scanned page and one only on the digital page; the task asked for values from both page types.
Extraction schema
JSON schema with 4 string fields
Tested
7 October 2026 · Rugved Nichite

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 →
ToolLanding AI →

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
9 October 2026First publishedStructured Document Extraction v1
30 October 2026Updated — retested
The result is unchanged: 0 pass · 1 fail. The earlier result stays readable. Read the earlier result →

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/landing-ai/a-document-mixing-digital-and-scanned-pages · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-11

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
Proof 1 · Screenshot ↗image/png · 127 KB
Output file (JSON) ↗text/plain; charset=utf-8 · 1 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)89fb14d7c0897bbfef47ffa3aa3930ee7eccf62c8a9430710d1906598c9bdfec
Proof 1 · Screenshot3f68d3a226b35481d4dd721cf9e465eaf34a90c90afb36202ff7539a01cc82ab
Output file (JSON)ca871ffdd0ac592969be5f182cb496e56fe0fcde9fea47d84f658f0a1fc2fac1