Evidence · first-party tested

The invoice output follows the supplied nested schema, populating invoice_metadata, advertiser, station, account_details, billing_address, remit_address, flight_dates, line_items, and summary as separate objects/arrays.

✓ WorkedRetab
Input — the actual file we sent
Invoice PDF
A 2-page broadcast advertising invoice PDF with nested header metadata, billing/remit addresses, 8 line items, and a financial summary. Designed to test schema-driven extraction of complex tabular invoice data with page-break continuity and precise monetary fields.
Output — unretouched
tool output
Output — unretouched
tool output
Output — unretouched
tool output
The observation

The invoice output follows the supplied nested schema, populating invoice_metadata, advertiser, station, account_details, billing_address, remit_address, flight_dates, line_items, and summary as separate objects/arrays.

Criterion: Schema Adherence · Scenario: Invoice PDF (group: financial-document-extraction)
Query this
get_evidence({
  tool: "retab",
  scenario: "financial-document-extraction"
})
MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Real outputs, no retouching · every cell queryable via API & MCP · aidemos.com