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

Can Docsumo trace a value to its location?

Docsumo traced the extracted subtotal to its location on page 2 of 2. It returned 6103 for the printed £6,103.00 and highlighted that amount with a box on the Subtotal line.

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.

Pointer to where the value sitsPassEvidence
What we sent

We uploaded the two-page invoice to Docsumo, exported the extraction as JSON, and opened the subtotal’s source in the review screen.

InputDocument (PDF)
Input PDF: the two-page invoice with the subtotal on page 2
Open the PDF ↗
What the tool returned
JSON1 uncited part folded (…) · the whole file · copied lines 17–31 marked
[
  {
    "meta_data": { … },
    "data": {
      "Invoice Details": {
        "subtotal": {
          "value": 6103.0,
          "position": [1438, 2939, 1530, 2968],
          "confidence": 0.94,
          "review_required": false
        }
      }
    }
  }
]

JSON export: the extracted subtotal and its location box

Copied from Output file (JSON), lines 17–31

Open the JSON file ↗
ConfigurationScreenshot
Field setup: the numeric subtotal field and extraction prompt
Open original ↗
Expected vs. Found
✓Expected: A pointer to the returned subtotal’s actual location—£6,103.00 on page 2—at the precision Docsumo offers.Found: Docsumo returned 6103 for the printed £6,103.00 and highlighted that amount on the Subtotal line, on page 2 of 2.
Supporting proof
Proof 1Screenshot
Review screen: the subtotal highlighted on page 2 of 2
Open original ↗
Why this result

A location pointer had to identify the returned value, not just its document. The subtotal appears once, on page 2, and Docsumo’s own source highlight identifies that amount at bounding-box precision.

Also observed in this test case

Exported location format. The subtotal’s location in the JSON export uses coordinates spanning the whole document, rather than naming a page.

Tested by Rugved Nichite · evidence dated 5 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
Docsumo
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
The two-page invoice had to contain the subtotal exactly once, on page 2. The task was to extract that one value and locate its source.
Tested
5 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
CapabilitySource Grounding →
ScenarioTrace a value to its location →
ToolDocsumo →

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
20 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/docsumo/trace-a-value-to-its-location · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-19

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

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)d1f3282702260730267278b1071ee30cf79918fa8489d9411c98d8f6e5209f18
Output file (JSON)9168557c4c5c662e319c0c3e52491e94a0bea3a645d8095b3ac68e2a95e54171
Proof 1 · Screenshot5f648ccdf0dde9753516603c2539719af6a052476291297580359b8d04537e10
Configuration · Screenshot8ea7b2a9da4e3818ad4d7dce9bba61005ffebe939bca79bbf023cef70af361bd