Can FutureSmart Document Intelligence correct a field value?
FutureSmart Document Intelligence did not let the corrected value reach the stored record. The overview and document view showed plain-text fields with no edit control, and the stored receipt number stayed RHS-70234 while RHS-99999 never appeared.
1 of 1 test case failed
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 counts this row.
Corrected value reaches the stored recordFailEvidence
In the document view, we double-clicked the Receipt Number field, which read RHS-70234, and typed RHS-99999.
{ … "receipt_number": "RHS-70234", … }
Text export: the receipt number stayed unchanged.
Copied from Output file (JSON), line 70
Open the JSON file ↗| ✗ | Expected: The stored record should keep the corrected value and leave everything else unchanged.Found: The document view had no edit control; the receipt number stayed RHS-70234, and RHS-99999 did not appear in the view or the stored JSON. |
The case required the corrected value to be stored with nothing else changed. The evidence shows no edit control, no changed field in the view, and the stored record still kept RHS-70234 instead of RHS-99999, so the correction did not reach storage.
Per-field magnifier. The only field-level control is a magnifier that highlights the extracted value.
The attempt itself is not shown; the captures show only the states before and after it.
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 row says which 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 row 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 | Correct a field value → | |
| Tool | FutureSmart Document Intelligence → |
Global scenario definition → · Global capability definition →
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.