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

Can FutureSmart Document Intelligence keep one array when a set continues across a page break?

FutureSmart Document Intelligence kept one array across the page break. The invoice splits across two pages, and the output keeps ten entries in order with item 6 followed by item 7 and no missing or repeated member.

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.

Set continues past a page boundaryPassEvidence
What we sent
InputDocument (PDF)
Invoice PDF: both pages of the table
Open the PDF ↗
What the tool returned
JSON
{
  "summary": "This invoice from Meridian Retail Group to Blackwood Distribution LLC details the supply of various retail fixtures and store equipment. The document lists ten line items including shelving, checkout counters, and scanning equipment, totaling £6,591.24 including VAT.",
  "document_type": "invoice",
  "line_items": [
    {
      "amount": 1008,
      "quantity": 12,
      "unit_price": 84,
      "description": "Retail Shelving Unit - Steel, 5-Tier"
    },
    {
      "amount": 930,
      "quantity": 3,
      "unit_price": 310,
      "description": "Checkout Counter - Laminate Top"
    },
    {
      "amount": 273,
      "quantity": 6,
      "unit_price": 45.5,
      "description": "Security Tag Deactivator - Handheld"
    },
    {
      "amount": 648,
      "quantity": 4,
      "unit_price": 162,
      "description": "Price Label Printer - Thermal"
    },
    {
      "amount": 304,
      "quantity": 8,
      "unit_price": 38,
      "description": "Shopping Basket - 20L, Set of 10"
    },
    {
      "amount": 1080,
      "quantity": 2,
      "unit_price": 540,
      "description": "Storeroom Pallet Racking - 4-Bay"
    },
    {
      "amount": 580,
      "quantity": 10,
      "unit_price": 58,
      "description": "Barcode Scanner - Wireless"
    },
    {
      "amount": 330,
      "quantity": 15,
      "unit_price": 22,
      "description": "Receipt Paper Roll - Case of 50"
    },
    {
      "amount": 570,
      "quantity": 6,
      "unit_price": 95,
      "description": "Mannequin - Adjustable, Full Body"
    },
    {
      "amount": 380,
      "quantity": 5,
      "unit_price": 76,
      "description": "Display Signage Kit - Window Set"
    }
  ]
}

Output JSON: ten extracted rows in order

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

Open the JSON file ↗
Expected vs. Found
✓Expected: One array with all members and no duplicate at the page break.Found: It returned one array of ten entries in order, with no member missing or repeated at the page break.
Supporting proof
Proof 1Screenshot
Document overview: items 1-4
Open original ↗
Proof 2Screenshot
Overview scrolled: items 5-10
Open original ↗
Why this result

It is a Pass because the invoice spans two pages, and the product returned one array of ten entries in order with no missing or repeated member at the break.

Also observed in this test case

Numeric prices. Unit prices are numeric, and amounts are returned without currency.

Tested by Rugved Nichite · evidence dated 17 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
FutureSmart Document Intelligence
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
The product was set to extract a line_items array with description, quantity, unit_price, and amount from a two-page invoice whose 10-row table breaks after row 6 and repeats the header on page 2.
Field setup route
Fields were set up in the product's web app (Settings → Extracted fields), not supplied as JSON.
Extracted fields
line_items array with description, quantity, unit_price, amount
Tested
17 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.

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
3 October 2026First publishedStructured Document Extraction v1
21 October 2026Taken down
The page left the site; nothing was deleted.
26 October 2026Republished
27 October 2026Updated — the page was revised
The result is unchanged: 1 pass · 0 fail. The earlier result stays readable. Read the earlier result →

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/futuresmart-document-intelligence/the-set-continues-across-a-page-break · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-26

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.

Proof 1 · Screenshot ↗image/png · 95 KB
Proof 2 · Screenshot ↗image/png · 74 KB
Input · Document (PDF) ↗application/pdf · 82 KB
Output file (JSON) ↗application/json · 2 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshota24e5b5ad25721835ff5f16c985c0f3a4711f17a14fd53e7be5f42f07130d32a
Proof 2 · Screenshot8cb3e31f416022bff0b03f29771114abe153abd308e3cbd63a9983bf4a2ff17d
Input · Document (PDF)d1f3282702260730267278b1071ee30cf79918fa8489d9411c98d8f6e5209f18
Output file (JSON)af4aa8fd1a94aeee97b0a09e5264af3338a82c1120f1fc172b820b387c1a7bdc