Can Extend AI keep corrected data in the downstream record?
Extend AI delivered the corrected receipt number through its API. The subtotal, tax and total due stayed at $85.00, $5.10 and $90.10.
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
We ran the service receipt through an Extend workflow and replaced the receipt number printed on the document in Human Review before approving the run. We then retrieved the same record through Extend's read API.
Delivered output "output": { "value": { "tax": "$5.10", "subtotal": "$85.00", "total_due": "$90.10", "receipt_number": "RHS-99999" }, "metadata": { } }, Initial extraction "initialOutput": { "value": { "tax": "$5.10", "subtotal": "$85.00", "total_due": "$90.10", "receipt_number": "RHS-70234" }, Reviewed output "reviewedOutput": { "value": { "tax": "$5.10", "subtotal": "$85.00", "total_due": "$90.10", "receipt_number": "RHS-99999" }, "metadata": { } Edit history "edits": { "receipt_number": { "notes": "Benchmark test: receipt_number deliberately changed from RHS-70234 to RHS-99999 to check whether the corrected value reaches the saved run record.", "fieldType": "string", "editedValue": "RHS-99999", "originalValue": "RHS-70234" } },
API response: the corrected receipt number delivered to downstream readers
Copied from Output file (JSON), lines 638–648
Open the JSON file ↗Copied from Output file (JSON), lines 649–655
Copied from Output file (JSON), lines 707–716
Copied from Output file (JSON), lines 729–736
| ✓ | Expected: A downstream system must receive the corrected receipt number through one of Extend's own delivery paths.Found: The API's main output and reviewed output contained the corrected receipt number; the initial extraction retained the original number. |
The correction reached the output a downstream system reads, not just the review screen. That meets delivery through one of Extend's own paths; the demonstrated scope is its read API.
Processing and read-back costs. The receipt workflow used 5 credits in total. The API call that retrieved it was not billed.
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 | Extend AI → |
Global scenario definition → · Global capability definition → · Extend AI 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.