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

Can Nanonets extract the same field across documents with different layouts?

Nanonets returned the correct document number, subtotal, tax and total due from all three differently laid-out documents with one unchanged prompt: Riverside RHS-70234 ($90.10), GreenLeaf GLR-98213 ($227.33) and Sunrise SPD-2026-0714 (USD 157.50). It read the GreenLeaf number from a boxed work-order block rather than a receipt-number label.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
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.

Same field across three layoutsPassEvidence
What we sent

“Extract the following fields from this document and return the result as JSON: identifier_number (the receipt or work order number that uniquely identifies this document), subtotal____, tax____, total_due____.”

Input 1Document (PDF)
Input PDF: Riverside's baseline service receipt
Open the PDF ↗
Input 2Document (PDF)
Input PDF: GreenLeaf's invoice with a boxed work-order number
Open the PDF ↗
Input 3Document (PDF)
Input PDF: Sunrise's single-column receipt with USD-prefixed amounts
Open the PDF ↗
What the tool returned

Returned JSON: Riverside's document number, subtotal, tax and total due

Copied from Output file 1 (JSON), lines 1–6

JSON
{
  "identifier_number": "RHS-70234",
  "subtotal": "$85.00",
  "tax": "$5.10",
  "total_due": "$90.10"
}
Open the JSON file ↗

Returned JSON: Sunrise's document number, subtotal, tax and total due

Copied from Output file 2 (JSON), lines 1–6

JSON
{
  "identifier_number": "SPD-2026-0714",
  "subtotal": "USD 150.00",
  "tax": "USD 7.50",
  "total_due": "USD 157.50"
}
Open the JSON file ↗

Returned JSON: GreenLeaf's document number, subtotal, tax and total due

Copied from Output file 3 (JSON), lines 1–6

JSON
{
  "identifier_number": "GLR-98213",
  "subtotal": "$210.00",
  "tax": "$17.33",
  "total_due": "$227.33"
}
Open the JSON file ↗
Expected vs. Found
✓Expected: The correct document number, subtotal, tax and total due from each differently laid-out document.Found: Nanonets returned each document's number, subtotal, tax and total due as written; returned and source totals were Riverside $90.10, GreenLeaf $227.33 and Sunrise USD 157.50.
Supporting proof
Proof 1Screenshot
Result screen: Riverside's extracted values beside the baseline receipt
Open original ↗
Proof 2Screenshot
Result screen: GreenLeaf's extracted values beside the invoice
Open original ↗
Proof 3Screenshot
Result screen: Sunrise's extracted values beside the single-column receipt
Open original ↗
Why this result

The same prompt and fields were used for all three documents, and each output matched its own source document despite different label wording, label position, layout and currency format. That is what the scenario asks, so the test case passes.

Also observed in this test case

Currency format preserved. Sunrise's subtotal, tax and total due kept the USD prefix used in its receipt (USD 150.00, USD 7.50, USD 157.50) rather than changing to dollar signs.

Tested by Rugved Nichite · evidence dated 10 September 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
Nanonets
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
The same prompt and fields had to be used for three service documents: a Riverside receipt, a GreenLeaf invoice with a boxed work-order number, and a single-column Sunrise receipt with USD-prefixed amounts.
Tested
10 September 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
CapabilityField Extraction →
ScenarioThe same field across layouts →
ToolNanonets →

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
19 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/nanonets/the-same-field-across-layouts · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-17

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
Output file 1 (JSON) ↗text/plain; charset=utf-8 · 0 KB
Output file 3 (JSON) ↗text/plain; charset=utf-8 · 0 KB
Output file 2 (JSON) ↗text/plain; charset=utf-8 · 0 KB
Proof 1 · Screenshot ↗image/png · 138 KB
Proof 2 · Screenshot ↗image/png · 139 KB
Proof 3 · Screenshot ↗image/png · 132 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
Output file 1 (JSON)a5b15cd2502887b5668ef34c3a4a7c95537307bb2a046efb761052f548b55699
Output file 3 (JSON)4526eb6a43e0f9d33b102c338e88ed8a3f224372de014de53fc6ed6c8efc6016
Output file 2 (JSON)03362f5ae067ba209a213858373b75bc1366a5d665bfc14bc96bd56cd7ba068e
Proof 1 · Screenshot0c92c96a6297583a5e097f5b55ae67b04e0fc6c4d4b329f0c1f2457aeadd1b8f
Proof 2 · Screenshotd77197ff348a5e9e596c69ea927afc4e9efc128f1abfc6f49eac1d5235d52176
Proof 3 · Screenshotdf5248154dd002f602da7cc4202c8ad1a10b979b9446f37de13503aed1dbd060