Evidence · first-party tested/Best AI Tools for Extracting Structured Data from PDFs and Business Documents
The invoice output is reconstructed as nested JSON sections — invoice_metadata, advertiser, station, addresses, flight_dates, line_items, and summary — instead of raw OCR.
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 output does not match the requested JSON schema exactly, the extracted data cannot be reliably consumed or queried, so this is core to the task. (3 of 3 judges)
What was given, what came back
Test input: Invoice PDF · pdf · group: financial-document-extraction
Input — what we sent
Input not captured
This run recorded no prompt or input file for the test, so we cannot show you what produced the result below. Capture gaps are tracked, not hidden.
A 2-page broadcast advertising invoice PDF with 8 line items, complex time/day fields, large dollar amounts, and compliance text, used to test hierarchical line-item extraction and financial validation.
Why this input is hard
- · Nested line-item hierarchy extraction
- · Multi-page line-item continuity across a page break
- · Large dollar amount precision and total validation
- · Parsing time slots, day patterns, and air dates
- · Extraction of alphanumeric ad IDs and reference codes
- · Structured metadata mapping for advertiser, station, billing, and remit sections
- · Political advertising and FCC compliance text recognition
Also checked on this input — same tool, 5 other criteria
Extraction Accuracy✓ WorkedIts invoice totals match the source document, including 8 aired spots, gross_total 29750, agency_commission 4462.5, and net_amount_due 25287.5.Extraction Accuracy⚠ StruggledIt sometimes carries source labels into values: `payment_terms` is returned as `Payment Terms 30 Days` rather than the bare value `30 Days`.Semantic Field Enrichment✓ WorkedIt derives non-OCR line-item fields such as `day_of_week`, `days_pattern`, `time_slot`, and `air_time`.Structural Clean Output✗ FailedIt reorders several schema sections relative to the supplied schema, so the output is not consistently in the authored field order.Table & Record Completeness✓ WorkedIt extracts all eight invoice line items as separate rows, preserving description, airtime, rate, flight period, reference number, and campaign IDs without merging records.
Provenance
- Observation
- ad656fd6-a7c6-4174-a1a5-71f32b26d964
- Evidence run
- ec4d736d-95f9-4c88-884c-e280435f7b7b
- 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
- output only
- 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: "extend-ai",
scenario: "financial-document-extraction"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 7 other tools
measured on Schema Adherence
Datalab✓ WorkedReconstructs the invoice into nested JSON objects and arrays that follow the supplied schema, including invoice_metadata and line_items rather than returning generic OCR text.Landing AI✓ WorkedReconstructs the requested invoice hierarchy in structured JSON, filling invoice_metadata, advertiser, station, line_items, and summary objects instead of returning a flat extraction.LlamaParse✓ WorkedKeeps the invoice hierarchy intact, emitting invoice_metadata, advertiser, station, line_items, and summary objects rather than flat OCR text.Nanonets✓ WorkedIt preserves the invoice hierarchy exactly as requested, filling dedicated objects for invoice_metadata, advertiser, station, account_details, billing_address, remit_address, flight_dates, line_items, and summary.Reducto✓ WorkedReconstructs the invoice into the requested nested JSON hierarchy, populating invoice_metadata, advertiser, station, account_details, billing_address, remit_address, flight_dates, line_items, and summary sections.Retab✓ WorkedBuilds the requested invoice hierarchy with separate invoice_metadata, advertiser, station, account_details, billing_address, remit_address, flight_dates, line_items, and summary objects instead of a flat OCR dump.Unstract✓ WorkedPopulates the requested invoice hierarchy into dedicated sections for invoice_metadata, advertiser, station, account_details, billing_address, remit_address, flight_dates, line_items, and summary.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com