Follows the requested nested bank-statement schema instead of flattening the document, populating structured objects such as metadata, account_holder, account, branch, balances, transactions, and summary.
What was measured
Schema Adherence
Does the output follow the supplied JSON schema hierarchy exactly, with correct nesting, field names, and data types?
decisive for this rankingtransformation
If the tool does not follow the supplied JSON schema exactly, the extracted data cannot be reliably used for structured querying or downstream automation. (3 of 3 judges)
What was given, what came back
Test input: Bank Statement PDF · pdf · group: business-document-extraction
Input — what we sent
Bank Statement PDF
A four-page bank statement PDF with dense transaction tables, balance-forward bridges, account metadata, rewards data, and disclaimer text. It was used to stress schema-driven extraction, multi-page continuity, row completeness, and financial numerical accuracy.
Why this input is hard
- · Table extraction across 50+ transaction rows
- · Multi-page continuity with balance-forward bridges
- · Parsing structured account metadata alongside unstructured transaction descriptions
- · Numerical accuracy for deposits, withdrawals, running balances, and summaries
- · Extraction of nested rewards and disclaimer sections
Also checked on this input — same tool, 4 other criteria
Extraction Accuracy✓ WorkedThe opening and closing balance figures are extracted accurately and match the source statement values exactly.Extraction Accuracy✗ FailedUnderstates the derived bank-summary count: summary.total_transactions is reported as 43 even though the PDF contains 51 transactions, a 16% undercount.Semantic Field Enrichment✓ WorkedCorrectly enriches bank rows with transaction_type classification, with the report stating Withdrawal/Deposit was assigned correctly on all 51 transaction rows.Table & Record Completeness✓ WorkedKeeps the bank transaction table complete across all 4 pages, with the report stating the transactions array contains all 51 entries and no rows were dropped or merged.
Provenance
- Observation
- 7723ce9b-b9fc-4a93-ba5e-6a1782b61721
- Evidence run
- a061b9e7-a9c5-443d-a171-b296aaf51b8c
- Study
- Extract and query structured data from documents using natural language
- Research task
- 86b9y25e5
- Tested at
- not recorded
- Source
- first-party
- Evidence state
- verified
- Proof shown
- input + output shown
- Cost / latency
- not captured
- Repeat run
- not captured
- Tester
- not captured
The last three rows are honest blanks, not placeholders — our capture has no field for them yet.
Query this
get_evidence({
tool: "unstract",
scenario: "business-document-extraction"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 7 other tools
measured on Schema Adherence
Datalab✓ WorkedCan emit the bank-statement extraction as nested schema-shaped JSON, with separate metadata, account_holder/account, branch, transactions, summary, rewards, and disclaimers objects instead of flat OCR text.Extend AI✓ WorkedThe tool reconstructs the bank-statement hierarchy into nested JSON with branch, account, rewards, metadata, balances, summary, and transaction-related objects present in the requested layout.Landing AI✓ WorkedReconstructs the supplied bank-statement hierarchy instead of flat OCR, with nested statement.metadata, account_holder.address, account, branch, statement_period, balances, transactions, summary, rewards, and disclaimers objects present in the extracted JSON flow.LlamaParse✓ WorkedThe bank-statement output follows the requested nested schema closely, reconstructing metadata, account_holder, account, branch, statement_period, balances, transactions, summary, rewards, and disclaimers as structured objects rather than flat OCR text.Nanonets✓ WorkedPreserves the supplied bank-statement hierarchy in structured JSON, with nested statement.metadata, account_holder, account, balances, transactions, summary, rewards, and disclaimers objects instead of flattening the document into OCR text.Reducto✓ WorkedPreserves a nested, schema-shaped JSON structure for the bank statement instead of flattening the document into raw OCR, including top-level objects like metadata, account_holder, account, branch, statement_period, transactions, and summary.Retab✓ WorkedReconstructs the supplied bank-statement schema into a nested JSON object with separate statement.metadata, account_holder, account, branch, balances, transactions, summary, rewards, and disclaimers sections instead of flattening the document into OCR text.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com