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

Can Docsumo ensure corrected field values are reflected in the stored record?

Docsumo kept a corrected value in the stored record: after the receipt number was changed from RHS-70234 to RHS-99999 in its review screen, confirmed and approved, the record reopened after a reload and Docsumo's own export both showed RHS-99999. The subtotal, tax and total were unchanged.

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.

Corrected value reaches the stored recordPassEvidence
What we sent

In Docsumo's review screen, we edited the Receipt Number field, which read RHS-70234, to RHS-99999, confirmed the edit and approved the document. We then reloaded the page and reopened the stored record.

InputDocument (PDF)
Input PDF: the one-page service receipt with receipt number RHS-70234
Open the PDF ↗
What the tool returned
JSON
"Service Receipt Information": {
  "receipt_number": {
    "value": "RHS-99999",
    "position": [1021, 501, 1131, 529],
    "confidence": 1.0,
    "review_required": false
  }
},
"Financial Summary": {
  "subtotal": {
    "value": 85.0,
    "position": [1451, 717, 1515, 746],
    "confidence": 1.0,
    "review_required": false
  },
  "tax": {
    "value": 5.1,
    "position": [1463, 769, 1515, 798],
    "confidence": 1.0,
    "review_required": false
  },
  "total_due": {
    "value": 90.1,
    "position": [1428, 841, 1514, 877],
    "confidence": 1.0,
    "review_required": false

Docsumo's export of the stored record: receipt number RHS-99999 and unchanged totals

Copied from Output file (JSON), lines 18–63

Open the JSON file ↗
Expected vs. Found
✓Expected: The stored record holds the corrected value, and no other field changes.Found: Before the edit: RHS-70234, subtotal 85, tax 5.1, total 90.1. After the reload, the reopened record and Docsumo's export show RHS-99999 with the same subtotal, tax and total.
Supporting proof
Proof 1Screenshot
Review screen before the edit: receipt number RHS-70234 and the totals
Open original ↗
Proof 2Screenshot
Record reopened after reload: approved, receipt number RHS-99999, totals unchanged
Open original ↗
Why this result

The corrected value had to reach the stored record with nothing else changed. We edited the receipt number from RHS-70234 to RHS-99999 in the review screen, confirmed and approved it; after a reload, the reopened record and the export both held RHS-99999 with the totals unchanged.

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 baseline service receipt was used. The receipt number Docsumo had extracted correctly, RHS-70234, had to be changed to a different valid value, RHS-99999, in Docsumo's own review screen and then read back from the stored record.
Plan
Free Plan
Setup
default review screen; the document had been processed through the saved agent
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
CapabilityReview and Correction →
ScenarioCorrect a field value →
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
16 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/correct-a-field-value · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-21

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

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)a96bbe1c5b22336e7b54169baf72b85e45eabf1312cd293a1821017b52fa85f7
Proof 1 · Screenshot5e053e1b0ca1793c6a81bec7feec236312648743e36df24780fe54cd2b6e5ad6
Proof 2 · Screenshot636fb641d512df54291177c7107566d02bba0542773bb94db1085540c4700e49
Output file (JSON)6b98f84324b16f904366381bf4ce2e98ff464bdf7727b0073412e555a5e57f09