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

Can LlamaParse aggregate across documents?

LlamaParse did not produce the required combined total of 474.93 across three receipts in Extract on the Free plan. It filled the requested cross-document sum with individual receipt totals instead.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
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.

Total across every documentFailEvidence
What we sent

We uploaded three receipt PDFs—the baseline receipt, the invoice with a different total label, and the different-layout receipt—to Extract, one at a time. Each used the same schema, including a field requesting the sum of the total due across all documents in the project.

Input 1Document (PDF)
Input PDF: baseline receipt with a $90.10 total
Open the PDF ↗
Input 2Document (PDF)
Input PDF: invoice with a different total label and $227.33 due
Open the PDF ↗
Input 3Document (PDF)
Input PDF: different-layout receipt with USD 157.50 due
Open the PDF ↗
Cross-document sum definition
Sum of the total due across all of the documents uploaded in this project
What the tool returned

Copied from Output file 1 (JSON), line 14

JSON
"total_due_all_documents": "$90.10"

Copied from Output file 1 (JSON), lines 107–131

JSON
  "total_due_all_documents": {
    "citation": [
      {
        "page": 1,
        "matching_text": "$90.10",
        "bounding_boxes": [
          {
            "x": 512.6664632463455,
            "y": 304.2129379463196,
            "w": 31.964370346069337,
            "h": 10.385311059951782
          }
        ],
        "page_dimensions": {
          "width": 594.96,
          "height": 841.92
        }
      }
    ],
    "confidence": 0.9420762965080913,
    "extraction_confidence": 0.9420762965080913
  }
},
"page_metadata": null,
"row_metadata": null

Copied from Output file 2 (JSON), line 14

JSON
"total_due_all_documents": "$227.33"

Copied from Output file 3 (JSON), line 14

JSON
"total_due_all_documents": "USD 157.50"

Returned JSON: the baseline receipt’s cross-document sum points to its own total

Open the JSON file ↗

Returned JSON: the different-label invoice’s cross-document sum points to its own total

Open the JSON file ↗

Returned JSON: the different-layout receipt’s cross-document sum points to its own total

Open the JSON file ↗
Expected vs. Found
✗Expected: The correct total across every extracted document: 474.93, summed from the amounts the product returned.Found: The combined-total field returned $90.10, $227.33 and USD 157.50 in separate answers, rather than the required 474.93 sum of the extracted amounts.
Supporting proof
Proof 1Screenshot
Extract screenshot: the $90.10 receipt’s cross-document sum is $90.10
Open original ↗
Proof 2Screenshot
Extract screenshot: the $227.33 receipt’s cross-document sum is $227.33
Open original ↗
Proof 3Screenshot
Extract screenshot: the USD 157.50 receipt’s cross-document sum is USD 157.50
Open original ↗
Why this result

Extract read each receipt correctly but offered no option to query them together. Because a combined answer was required inside the product, this is a querying failure rather than an extraction error, limited to Extract on the Free plan.

Tested by Rugved Nichite · evidence dated 28 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
LlamaParse
Build or version
LlamaCloud web app (build v09046f5c); Extract, Agentic tier
Plan or tier
Free plan (20,000 credits)
Surface
Web app
Set up before the run
Three receipts with individual totals were required. The combined total had to use the amounts returned by the product, rather than amounts read directly from the PDFs.
Extraction configuration
one JSON schema with the receipt identifier, subtotal, tax, total due and total due across all documents
Tested
28 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
CapabilityQuerying →
ScenarioAggregate across documents →
ToolLlamaParse →

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
17 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/llamaparse/aggregate-across-documents · 0 pass · 1 fail · coverage 1/1 · graded 2026-11-16

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 1 · Document (PDF) ↗application/pdf · 7 KB
Input 2 · Document (PDF) ↗application/pdf · 8 KB
Input 3 · Document (PDF) ↗application/pdf · 7 KB
Proof 1 · Screenshot ↗image/png · 102 KB
Proof 2 · Screenshot ↗image/png · 118 KB
Proof 3 · Screenshot ↗image/png · 115 KB
Output file 1 (JSON) ↗text/plain; charset=utf-8 · 4 KB
Output file 2 (JSON) ↗text/plain; charset=utf-8 · 4 KB
Output file 3 (JSON) ↗text/plain; charset=utf-8 · 4 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input 1 · Document (PDF)1f464ae863aadb1682805b8ee3fdd8b368a2ddd4e0f602e1cb194640b9253302
Input 2 · Document (PDF)4a0b1754da9f52ce35a783d58f8e8a1b5e1353b5b992d5553122886f1cd4a638
Input 3 · Document (PDF)0276d246d69482340b53797f4eaa21831977cede22c8c8f14fc48dbf84757660
Proof 1 · Screenshot1a6c6cd646dd37aa6ff097be8f9d4eb417fd27fe914b7e46888238a88454c9af
Proof 2 · Screenshotd3a4b613012c6529f6c50376d42c2dae3c56654b13f3a91c1f920c9a5cf3985e
Proof 3 · Screenshot83a60636c77009440ccd778e7b8fbec654b3d6991ba4a135f16564fb82bf18e1
Output file 1 (JSON)22714d95f3fd054c8d3dac1d852480197af582e15ccd57ea4c371704b820a986
Output file 2 (JSON)eb3bda3b22016fcca1ca6d962169f312f75ac0f2abbc14596a66918bfb13404d
Output file 3 (JSON)df82be54e8bd773d8f97cfa1022c1b4cf0d0a593e396cfe163853b6c0c80f768