Skip to content

Every document format your back office processes

Fieldiq is trained on the specific documents your team actually handles — not generic forms. Invoices from 200 vendors, jurisdiction-specific claims, non-standard PO tables, regulatory filings that change formats every cycle.

AP invoice extraction — 16 fields, no per-vendor templates

Fieldiq handles invoices from hundreds of vendor formats without per-vendor configuration: standard PDFs, scanned paper, email attachments, multi-page documents with complex line-item tables. Vendor ID is resolved against your master vendor register — not just the text string on the invoice.

vendor_id
invoice_number
invoice_date
due_date
line_items[]
unit_price
quantity
line_description
subtotal
tax_code
total_amount
payment_terms
currency_code
po_reference
remit_to_address
bank_account_ref

Amber fields = highest-volume extraction requests from AP teams

See invoice extraction demo
Invoice extraction accuracy
Vendor identification 99.4%
Total amount 99.8%
Line items (full table) 98.7%
Tax code extraction 99.1%

PO extraction — variadic line-item tables, multi-currency, no per-format setup

Enterprise procurement teams receive POs from dozens of systems — SAP Ariba, Coupa, Oracle Procurement Cloud, and custom layouts. Each has its own line-item table structure, multi-currency handling, and approval status encoding. Fieldiq handles the variance without per-format configuration or template maintenance.

po_number
buyer_entity
seller_entity
issue_date
delivery_terms
delivery_address
line_items[]
sku_code
unit_cost
total_po_value
approval_status
approver_name
currency_code
payment_terms

Variadic line-item tables and multi-currency handled without per-vendor templates

See PO extraction demo
Multi-format coverage
SAP Ariba format
Coupa PO format
Oracle Procurement Cloud
Custom enterprise PO layouts
Multi-currency (40+ currencies)
Variadic line-item table structures

Claims intake extraction — jurisdiction-aware, adjuster-queue ready

Insurance claims carry jurisdiction-specific fields, adjuster-routing requirements, and regulatory review steps that don't apply to invoices. State-specific claim forms are detected and classified before extraction begins. Fieldiq feeds your existing adjuster workflow — it doesn't replace it.

claimant_name
policy_number
insured_entity
incident_date
incident_location
claim_type
damage_description
claim_amount
adjuster_id
jurisdiction_code
coverage_type
deductible_amount
supporting_docs[]
form_version

State-specific claim forms detected and classified automatically

See claims extraction demo
Before Fieldiq
"We had a 6% error rate from our previous vendor. Fieldiq's exception flagging caught things before they hit our adjuster queue."
Marcus Adeyemi
Director of Claims Processing, Redfield Insurance Group

Regulatory filing extraction — form version detection prevents silent failures

Regulatory forms change versions without notice. An extraction model trained on a 2022 filing format fails silently on the 2025 revision — producing structured output that looks correct but isn't. Fieldiq classifies form version before field extraction runs. Unrecognized versions are flagged for review, not silently processed.

filing_type
form_version
entity_identifier
filing_period
jurisdiction_code
regulatory_agency
due_date
submission_date
signatory_name
certification_fields[]
amendment_indicator
fiscal_year

Form version detection runs before field extraction to prevent silent failures

See regulatory filing demo
Version detection — live example
form_1099-NEC_2025
version detected — extraction active
form_UNKNOWN_v7
unrecognized version — flagged for review
TX_insurance_claim_2024
version detected — extraction active

Tell us what you process — we'll show you the extraction output.

Bring a sample document from your actual operations. We'll extract it live in the demo and show you every field with confidence scores and exception routing.