Correctly extracts high-level statement values, including account number 42710540422 and total deposits 70986.83, rather than corrupting the header fields.
What was measured
Extraction Accuracy
Are field values correct, complete, and free of OCR or parsing errors, including numerical precision on financial fields?
decisive for this rankingtransformation
Correct field values are the core of the job; wrong or incomplete extraction means the tool failed to retrieve the structured data from the document. (3 of 3 judges)
What was given, what came back
Test input: Bank Statement PDF · pdf · group: business-document-extraction
Input — what we sent
Research media bank statement 2 jul.png
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
Output — unretouched
Loading file...
Also checked on this input — same tool, 4 other criteria
Schema Adherence✓ 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.Semantic Field Enrichment✗ FailedDoes not derive transaction_type on the bank statement at all; the report states that transaction_type is null for every extracted transaction.Table & Record Completeness✗ FailedLeaves the statement summary incomplete: total_transactions is null, and the report says the run extracted 47 transactions when the source contained 51.Table & Record Completeness✗ FailedFails to keep dense transaction rows fully distinct: the report says transaction descriptions were merged, dates were missing on 15+ transactions, and adjacent rows collapse into a single record on the highlighted statement crops.
Provenance
- Observation
- 0102a587-271f-42b7-8426-de7037082e4b
- 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: "nanonets",
scenario: "business-document-extraction"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 8 other tools
measured on Extraction Accuracy
Datalab⚠ StruggledMisplaces a bank-statement transaction across dates: a row that belongs to 18 Jun is attached to the 19 Jun record after merging, so date association is unreliable.Docsumo✗ FailedAcross the transaction grid, the tool fails to populate the Value Date and Transaction Type columns for the rows shown, leaving those fields empty instead of extracting per-row values.Extend AI✗ FailedThe summary aggregation is incorrect: `total_transactions` is 49 in the output, while the report says the expected count after exclusions is 40.Landing AI✓ WorkedPreserves statement metadata and balances with exact values, including bank_name "Standard Chartered", statement_date "16 Jul 2019", currency "INR", opening_balance 114453.65, and closing_balance 116149.46.LlamaParse⚠ StruggledThe tool leaves value_date blank on some bank transactions even though the source statement contains value dates, so transaction metadata is only partially accurate.Reducto✓ WorkedCorrectly extracts the bank statement currency as INR and attaches high-confidence citation metadata, with extract confidence shown as 0.984.Retab✓ WorkedDocsumo extracts the bank statement into structured customer, branch, and summary fields, including the account holder name, address, totals, and closing balance, and also supports QA over the document.Unstract✗ FailedUnderstates the derived bank-summary count: summary.total_transactions is reported as 43 even though the PDF contains 51 transactions, a 16% undercount.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com