Can Docsumo total values across multiple documents?
Docsumo correctly totaled values across multiple documents in this case. It returned 474.93 for the three receipts and showed each document’s value separately.
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.
Total across every documentPassEvidence
“What is the total of total_due summed across all 3 documents in the Invoice 1 2 3 4 5 6 agent (TC1_TC4_TC5A_baseline_receipt.pdf, TC5B_altlabel_receipt.pdf, TC5C_altlayout_receipt.pdf)?”
Copied from Output file (text), lines 4–8
Steps shown by the product: Listing documents in Invoice agent Reading TC5C receipt data Reading TC5B receipt data Reading baseline receipt data
Copied from Output file (text), lines 11–13
157.5 + 227.33 + 90.1 = 474.93 The total of total_due across the 3 documents is 474.93.
Copied from Output file (text), lines 15–18
Document total_due TC1_TC4_TC5A_baseline_receipt.pdf 90.10 TC5B_altlabel_receipt.pdf 227.33 TC5C_altlayout_receipt.pdf 157.50
Copied from Output file (text), line 20
All three documents are still in reviewing status, so these are the extracted values as they stand now. If a reviewer corrects any of them, the total will change.
Chat transcript: question, steps, per-document totals, and the sum
Open the text file ↗| ✓ | Expected: The correct total across all three documents, with no extra values or missing document.Found: It returned 474.93 and listed each document’s value, matching all three receipts. |
The product had to total the field across all three documents, and it returned 474.93 with a per-document breakdown that matches the three receipts. That shows the full cross-document sum, not a partial one.
Two-row grid. The visible data table shows two rows, while the answer lists three documents.
Values still provisional. The answer says all three documents are still in reviewing status, so the values could change if corrected.
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 | Querying → | |
| Scenario | Aggregate across documents → | |
| 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.