Bank statement to JSON

Convert a bank statement PDF to JSON

Your app needs transactions, and your users' banks send PDFs. Drop one here to see the JSON, then call the API to get the same JSON from your own code: no templates per bank, no webhooks to host.

Goes in

A bank or credit-card statement PDF, digital or scanned, up to 20 MB, from the web or the API

Comes out

statement.json: account details, a transactions array and a balance check

{
  "date": "2026-10-02",
  "description": "Acme Payroll",
  "credit": 3200,
  "debit": null,
  "balance": 5450,
  "reference": "PPD 1002",
  "classification": "ACME PAYROLL"
}

What the JSON looks like

This is the structure the worker stores and you download, filled with a four-line sample statement. Amounts are numbers, missing values are null, dates are YYYY-MM-DD strings.

{
  "bank_name": "Example Bank",
  "account_holder": "Jordan Lee",
  "account_number": "XXXX4821",
  "currency": "USD",
  "statement_period": {
    "from": "2026-10-01",
    "to": "2026-10-31"
  },
  "opening_balance": 5450,
  "closing_balance": 4766.61,
  "transactions": [
    {
      "date": "2026-10-02",
      "description": "Acme Payroll",
      "credit": 3200,
      "debit": null,
      "balance": 5450,
      "reference": "PPD 1002",
      "classification": "ACME PAYROLL"
    },
    {
      "date": "2026-10-03",
      "description": "Amazon",
      "credit": null,
      "debit": 64.99,
      "balance": 5385.01,
      "reference": null,
      "classification": "AMAZON"
    },
    {
      "date": "2026-10-05",
      "description": "City Electric Co",
      "credit": null,
      "debit": 118.4,
      "balance": 5266.61,
      "reference": "ACH 88213",
      "classification": "CITY ELECTRIC CO"
    },
    {
      "date": "2026-10-07",
      "description": "Rent - Oak Street",
      "credit": null,
      "debit": 500,
      "balance": 4766.61,
      "reference": "CHK 1043",
      "classification": "OAK STREET RENTALS"
    }
  ],
  "balance_check": {
    "is_valid": true,
    "opening_balance": 5450,
    "closing_balance": 4766.61,
    "expected_closing": 4766.61,
    "discrepancy": 0,
    "total_credits": 0,
    "total_debits": 683.39,
    "rows_verified": 3,
    "rows_failed": 0,
    "failed_rows": [],
    "warnings": [
      "All balances verified successfully"
    ]
  }
}

Sample data from a made-up statement, not a real account.

Who this is for

  • Developers building lending, accounting, budgeting or KYC features that start from a statement PDF.
  • Teams running scripts or AI agents that need statement rows as data, not as a spreadsheet.

How it works

  1. Step 1

    Try it here

    Upload a PDF on this page and open the JSON tab of the preview.

  2. Step 2

    Create an API key

    Sign in and name a key in the developer console. The secret is shown once.

  3. Step 3

    Upload, poll, fetch

    POST the PDF, poll the upload until it is done, then fetch the result.

Getting the JSON from the API

Processing is asynchronous. Upload returns an id; poll that id every few seconds until its status is done; the result holds the statement as JSON and as CSV.

1. Upload

POST /api/v1/developer/uploads with the PDF as the multipart field "file" and the header Authorization: Bearer <your key>. Returns 202 with an upload id.

2. Poll

GET /api/v1/developer/uploads/:id until status is done or failed. Every two or three seconds is enough; most single statements finish in seconds.

3. Fetch

GET /api/v1/developer/uploads/:id/result returns outputJson (the structure above), outputCsv and rowsDetected.

curl -X POST https://parsemystatement.com/api/v1/developer/uploads \
  -H "Authorization: Bearer $PSM_API_KEY" \
  -F "[email protected]"

curl https://parsemystatement.com/api/v1/developer/uploads/$UPLOAD_ID/result \
  -H "Authorization: Bearer $PSM_API_KEY"

Keys are created in the developer console; every endpoint is in the API and MCP docs.

Accuracy and limits

  • Keys see only their own uploads. The secret is shown once; store it server-side, never in a browser.
  • There are no webhooks. Poll for status; results are kept for a limited window, so store them when they arrive.
  • The API returns JSON and CSV. Excel is only a download from the web app.
  • Fields the statement does not show, such as account holder or statement period, come back as null rather than guessed.
  • PDF only, up to 20 MB per file. Photos and screenshots (JPG, PNG) are not accepted; save them as a PDF first. If the PDF is password-protected, save an unlocked copy.
  • Without an account you can convert one PDF of up to 3 pages a day. A free account converts up to 5 pages a day; Pro 400 at $15 / month (up to 400 pages per month) or Scale 1000 at $30 / month (up to 1000 pages per month).
  • On our ground-truth benchmark the current engine scores 93% transaction F1 and 99% date accuracy. That benchmark is three hand-checked statements (Canara, HSBC, ICICI), so treat it as a sign, not a guarantee for your bank. Check the preview before you download.
  • The running balance of every row is recomputed from the one before it. A row that does not add up is flagged in the JSON (balance_check), not silently fixed.

Questions

What fields does the JSON contain?

bank_name, account_holder, account_number, currency, statement_period (from, to), opening_balance, closing_balance, a transactions array (date, description, credit, debit, balance, reference, classification) and balance_check.

Is there a bank statement to JSON API?

Yes. Create a key at /developers, POST the PDF to /api/v1/developer/uploads, poll /api/v1/developer/uploads/:id, then GET its /result for the JSON and CSV. The full reference is at /docs/api.

Are amounts strings or numbers?

Numbers. Credit and debit are positive floats, balance can be negative, and any value the statement does not show is null.

What does balance_check tell me?

Whether each running balance equals the previous balance plus credits minus debits. rows_failed and failed_rows point at the rows that do not add up, which is where to look first.

Can an AI agent call it?

Yes. Besides the REST API there is an MCP server, documented with the API at /docs/api.

Do I need different code for each bank?

No. The parser is not template-based; every bank's statement comes back in the same JSON shape.

Related