Does Docsumo keep corrected data in the delivery path?
Docsumo kept the correction in the delivery path for this case. The spreadsheet and JSON export both show the corrected receipt number and matching money fields, while the source receipt shows the earlier number. One observation notes the spreadsheet stores total_due as a float.
1 of 1 test case passed
Every test case in this scenario has a result.
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.
Correction survives the delivery pathPassEvidence
"receipt_number": { "value": "RHS-99999", "position": [1021, 501, 1131, 529], "confidence": 1.0,
JSON export with corrected receipt number and money fields
Copied from Output file (JSON), lines 19–27
Open the JSON file ↗| ✓ | Expected: The delivery path carries the corrected value.Found: Both delivery exports show receipt_number RHS-99999, and the money fields match across the spreadsheet and JSON. |
It passes because the delivery path exists and returns the corrected value, not the original extraction. The spreadsheet and JSON both carry the corrected receipt number and the same money fields, while the source receipt shows the earlier value.
Float storage note. The spreadsheet stores total_due as a long decimal, while the JSON export and receipt show 90.1.
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.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
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.
- 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.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Structured Document Extraction → | 19 scenarios · 10 tools |
| Capability | Review and Correction → | |
| Scenario | Corrected data goes downstream → | |
| Tool | Docsumo → |
Global scenario definition → · Global capability definition → · Docsumo product page →
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.
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.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →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.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.