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

Can Docsumo derive a value that is not printed on the page?

Docsumo calculated a fuel cost that was not printed on the invoice. It returned £81.00 from 450 miles at £0.18 per mile and preserved the decimal fuel rate.

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.

Derived value from two present valuesPassEvidence
What we sent

We configured the extraction fields in the agent's Field setup and ran the Calderwood Freight invoice through the agent.

InputDocument (PDF)
Input PDF: the three-page freight invoice with distance and fuel rate
Open the PDF ↗
Extraction schemaJSON
{
  "section": "Invoice Details",
  "fields": [
    {
      "name": "distance_miles",
      "type": "String"
    },
    {
      "name": "fuel_rate_per_mile",
      "type": "String"
    },
    {
      "name": "total_fuel_cost",
      "type": "String"
    }
  ]
}

fuel_rate_per_mile: The fuel rate per mile, labelled 'FUEL RATE' on the document, including currency. The value may be a whole number or a decimal number — if the number in the document is in decimal form, the extraction should give the value in decimal, exactly as mentioned in the document.

total_fuel_cost: The total fuel cost — calculated as the distance in miles multiplied by the fuel rate per mile. This value does NOT appear anywhere in the document; you must compute it from distance_miles × fuel_rate_per_mile.

What the tool returned
JSONthe whole file · copied lines 2–34
{
  "Invoice Details": {
    "distance_miles": {
      "value": "450",
      "position": [1416, 524, 1453, 554],
      "confidence": 1,
      "review_required": false
    },
    "fuel_rate_per_mile": {
      "value": "£0.18",
      "position": [142, 620, 196, 650],
      "confidence": 1,
      "review_required": false
    },
    "total_fuel_cost": {
      "value": "£81.00",
      "position": [0, 0, 0, 0],
      "confidence": 0.57,
      "review_required": false
    }
  }
}

Returned JSON: the calculated fuel cost, source values and confidence scores

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

Open the JSON file ↗
Expected vs. Found
✓Expected: The fuel cost calculated from 450 miles multiplied by £0.18 per mile: £81.00.Found: It returned the required £81.00 (450 × £0.18), not either source value, and extracted the distance and fuel rate with the decimal preserved.
Supporting proof
Proof 1Screenshot
Results screenshot: the calculated fuel cost beside the invoice preview
Open original ↗
Why this result

The requirement was to calculate an unprinted value. The field definition supplied the operation, not the answer, and Docsumo returned the arithmetic result rather than either input value.

Also observed in this test case

Lower confidence for calculation. The calculated fuel cost received confidence 0.57, compared with 1 for both the distance and fuel rate.

No review flag. Despite its 0.57 confidence, the calculated fuel cost was returned with its review flag turned off.

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 Calderwood Freight invoice was used to request fuel cost by multiplying its labelled distance and fuel rate; the result had to be absent from the document.
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
CapabilityField Extraction →
ScenarioThe value must be derived →
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
13 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/the-value-must-be-derived · 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 · 118 KB
Output file (JSON) ↗text/plain; charset=utf-8 · 1 KB
Proof 1 · Screenshot ↗image/png · 136 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)1bcc6c7b945956c5b6f5a87d223ed3d578a62aa2c56c5fc1e3abedb4cc4de72e
Output file (JSON)27390a1f7d52fbc2b9f014b8e6a1b36da30d28872642a6355c3f3613b4607598
Proof 1 · Screenshot26dd59ee78d7679feb63a70fb917e09a5de9a3b892cb8374d333e27e3c249eb8