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

Can Extend AI handle a document fact that is not in the schema?

Extend AI offered no way to ask about a document fact outside the extraction schema. The extraction returned the invoice reference and total due, without an answer about the printed due date.

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.

Answer outside the schema, attributedFailEvidence
What we sent

We loaded the invoice into Extend AI’s Extract Playground, ran an extraction for the invoice reference and total due, and looked for a way to ask about its printed due date.

Input 1Document (PDF)
Input PDF: the two-page invoice
Open the PDF ↗
Input 2File (JSON)
Extraction schema: invoice reference and total due, with no due date
JSON
{
  "type": "object",
  "properties": {
    "invoice_reference": {
      "type": ["string", "null"],
      "description": "The invoice reference number"
    },
    "total_due": {
      "type": ["number", "null"],
      "description": "The total amount due on the invoice"
    }
  },
  "required": ["invoice_reference", "total_due"],
  "additionalProperties": false
}
Open the JSON file ↗
What the tool returned
JSON
{
  "total_due": 6591.24,
  "invoice_reference": "MRG-INV-20481"
}

Extraction result: the invoice reference and total due

Copied from Output file (JSON)

Open the JSON file ↗
Expected vs. Found
✗Expected: State that the requested fact is absent from the extracted data, or answer it while making clear it comes from the document.Found: No document question-answering option was available; the due-date question could not be asked.
Supporting proof
Proof 1Screenshot
Playground screenshot: the printed due date, extracted result and absence of a document question box
Open original ↗
Why this result

The printed due date was outside the schema. Extend AI offered no way to ask about it and documented no alternative. This is a failure, not a question left untried: the requirement counts an inability to query as a failure.

Also observed in this test case

No invented values. The invoice extraction result contained no invented values.

Tested by Rugved Nichite · evidence dated 17 November 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
Extend AI
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
The invoice’s printed due date of 06 Jul 2020 had to be outside the schema for the invoice reference and total due. The product was checked for a way to ask about that date.
Tested
17 November 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 →
ScenarioThe answer was never in the schema →
ToolExtend AI →

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/extend-ai/the-answer-was-never-in-the-schema · 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 · 82 KB
Input 2 · File (JSON) ↗application/json · 0 KB
Output file (JSON) ↗application/json · 0 KB
Proof 1 · Screenshot ↗image/png · 98 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input 1 · Document (PDF)d1f3282702260730267278b1071ee30cf79918fa8489d9411c98d8f6e5209f18
Input 2 · File (JSON)1025fb0a4ed945567ca62e2999a4357378b48676a2863fd44269421ca9b06590
Output file (JSON)2fab99ad3efa1a01dfc128eac8213327042ee79e0120faa4ebae106885d94b55
Proof 1 · Screenshot51074735701518a05a1f15c8b27bcdc24bb1551e3d28f70f0058a6daa2ced88b