parsr.

Use case · Lending & underwriting

Income verification from bank statements, with balance-chain integrity built in.

Consumer credit, BNPL, and SMB lending platforms verify income by parsing 3-6 months of borrower bank statements. The parsing layer needs to handle every EU and US bank format, return clean transaction-level data, and flag statements where the balance chain doesn't add up — that's a fraud signal underwriters care about. parsr is built for exactly this. Each parsed statement comes with a `validation.balance_chain` block that tells you whether opening + Σtransactions = closing within tolerance. Combined with per-field confidence scores, your underwriting agent can decide on its own when a statement needs human review (low confidence on key fields like closing_balance) versus when it's safe to auto-approve. Region-bound API keys mean a borrower in Germany has their statement parsed in Germany — no cross-border data flow that triggers BaFin scrutiny.

Workflow

How agents wire this up

  1. 01

    Parse the statement

    POST /v1/parse with doc_type='bank_statement'. Returns structured transactions, opening + closing balance, currency, account holder.

  2. 02

    Read the integrity verdict

    Inspect `validation.balance_chain.valid`. False = chain is broken (sign error, missing transaction, or fabricated statement). Diff is published alongside.

  3. 03

    Score income signals

    Group recurring credits by description fingerprint. Stable monthly recurring credits are salary signals; lump-sum quarterly credits flag self-employment.

  4. 04

    Flag low-confidence fields

    If field_metadata['closing_balance.amount'].confidence < 0.85, queue for review. Most legit statements score 0.95+.

Why parsr fits this

Operator concerns, addressed

EU residency = BaFin / DORA-friendly

Region-bound API keys mean borrower data parsed in EU stays in EU. DORA-aligned ICT third-party clauses available in the DPA.

60-second sync mode

?wait=60 returns the structured result inline if processing finishes in time — perfect for a real-time underwriting decision flow.

Idempotency on retries

If your underwriting service retries a parse on a network error, Idempotency-Key returns the same job — no double-billed pages.

Ship a prototype on the free tier in an afternoon.

Start free