Verified July 2026

Bank Statement OCR API Pricing: Cost Per Statement Compared

Bank statement OCR APIs run from about 2.5 cents to 75 cents per statement. Mistral is about $0.025 and Azure about $0.05 for a five-page statement (per page), Veryfi charges a flat $0.25 per document, and Google's dedicated Bank Statement parser is $0.75 per document.

Statements are multi-page, so the per-page vendors and the flat per-document parsers price the same statement very differently. Here is the honest math. Last updated July 2026.

  • Rates read off the vendor pages
  • Per-page, per-document and flat units
  • Why statement length flips the cost
  • Transaction fields, not just text
Upload a statement, no signup

PDF, JPG, PNG, BMP, HEIC, TIFF

Upload a document to extract

Before you wire up an API, drop in one of your real statements and see the account, balances, and transaction rows come back as clean fields.

SOC 2 Type II
256-bit encryption
US data handling
Transaction rows
$0.025
Mistral, a 5-page statement
$0.05
Azure prebuilt, per page
$0.25
Veryfi, flat per document
$0.75
Google dedicated parser
// The short answer

What a bank statement OCR API actually costs

A bank statement OCR API costs between about two and a half cents and seventy-five cents per statement, and the reason the range is that wide is the billing unit. Mistral Document AI bills per page at $0.005, so a typical five-page statement is about $0.025. Azure's prebuilt Bank Statement model bills per page at $0.01, about $0.05 for the same statement. Veryfi charges a flat $0.25 per document up to 15 pages, and Google's dedicated Bank Statement parser charges $0.75 per classified document no matter how many pages it holds. Because a statement is several pages, the per-page vendors stay cheap while the flat per-document parsers charge the same whether the statement is short or long. That is the opposite of receipts, where a single page makes the per-document parsers look expensive on the one page you send.

Where each option honestly wins

  • Cheapest per statement: Mistral at ~$0.025, then Azure's prebuilt model at ~$0.05.
  • Statement-native schema, less mapping: Google's parser and Azure's model return account, balances, and transaction rows directly.
  • Predictable flat fee: Veryfi at $0.25 per document up to 15 pages, cheaper than Google's dedicated $0.75.
// The statement problem

Statements are multi-page, and that flips the pricing

A bank statement is not one page. A monthly personal statement runs four to six pages, and a business or brokerage statement can run ten or more. That single fact decides your bill. A per-page vendor like Azure or Mistral charges for every page, so cost scales with statement length. A flat per-document parser charges the same whether the statement is two pages or twelve.

On a typical five-page statement the spread is stark. Mistral is about $0.025, Azure about $0.05, Veryfi a flat $0.25, and Google's dedicated Bank Statement parser a flat $0.75. Google's parser costs roughly fifteen times Azure's per-page rate for that statement. Veryfi's $0.25 per document undercuts Google's dedicated parser by three to one, but the per-page vendors still win outright: even a fifteen-page statement is $0.15 on Azure, less than Veryfi's $0.25 and far below Google's $0.75.

So the per-document parsers are not buying you a lower price. They are buying you a statement-native schema, account, period, running balance, and per-transaction rows, that already knows the shape of the document. That can be worth $0.75 if it saves engineering time. On pure cost per statement, the per-page vendors win at every realistic page count.

Ask these before you wire it up

  1. 1. How many pages is a typical statement in my pipeline, and does the vendor bill per page or per document?
  2. 2. Does a per-document cap apply, like Veryfi's 15 pages, and what happens past it?
  3. 3. Does the API return transaction rows and running balance, or only text I have to reconstruct?
  4. 4. Is there a monthly floor, like Veryfi's $500, that bites at my volume?

Rates change. Everything on this page was read from each vendor's own pricing page in July 2026, and we would rather you confirm it there than trust us.

// The rate card

Bank statement OCR API pricing, per statement

Read from each vendor's own pricing page in July 2026 and normalized to a typical five-page statement. Per-page figures scale with your real page count; per-document figures do not.

Vendor Cost per statement Billing unit Statement fields? Free allowance
Mistral Document AI About $0.025 (5-page) Per page ($5 per 1,000) Structured, generic schema No standing free tier
Azure AI Document Intelligence (Bank Statement) About $0.05 (5-page) Per page ($10 per 1,000) Yes, statement-native model 500 pages a month (F0)
DocuOCR About $0.07 to $0.10 (5-page) Per page (product) Yes, plus review and export On your own documents
Veryfi $0.25 per statement Per document, up to 15 pages Yes, statement fields 100 documents a month
Google Document AI (Bank Statement parser) $0.75 per statement Per classified document, flat Yes, statement-native model New-customer credit
AWS Textract About $0.35 (5-page), you build it Per page ($70 per 1,000, Forms+Tables+Queries) No native model, build the schema 100 pages a month, 3 months

Two rows on that card need your own numbers to pin down. AWS Textract has no dedicated bank statement model, so the figure is what it costs to build the schema from its Tables, Forms, and Queries features at $70 per 1,000 pages, and you own the transaction parsing. The DocuOCR figure is a product range that includes classification, review, and export, not a raw OCR rate. For the full per-vendor rate cards, see the OCR API pricing comparison.

// Worked example

5,000 statements a month, priced honestly

The same volume of five-page statements, 25,000 pages, run through each option so the per-page and per-document units show up in dollars.

Option Monthly cost Why
Mistral Document AI $125 25,000 pages at $0.005 each. The cheapest verified structured rate, generic schema.
Azure (Bank Statement model) $250 25,000 pages at $0.01 on the prebuilt statement model, per page.
DocuOCR $350 to $500 A product that also classifies, reviews, and exports, at a per-page product rate.
Veryfi $1,250 5,000 statements at $0.25 each, above the $500 monthly floor.
Google Bank Statement parser $3,750 5,000 statements at $0.75 each, the flat per-document dedicated parser.

Thirty times the spread, from about $125 to about $3,750, for the same 5,000 statements, decided almost entirely by whether you pay per page or per document. Mistral and Azure give you cheap pages but a generic or self-mapped schema. Google's and Veryfi's per-document rates buy a statement-native model that already knows the transaction layout. A ready-to-use product like DocuOCR sits in the middle and includes the review and export step. See the per-vendor detail on Veryfi pricing and Mistral OCR pricing.

// Frequently asked

Bank statement OCR API pricing FAQ

How much does a bank statement OCR API cost?
It ranges from about two and a half cents to seventy-five cents per statement, depending on the billing unit. Mistral Document AI runs about $0.025 for a five-page statement and Azure about $0.05, both per page. Veryfi charges a flat $0.25 per statement document, and Google's dedicated Bank Statement parser charges $0.75 per document regardless of page count.
What is the cheapest bank statement OCR API?
For structured transaction data, Mistral Document AI is the cheapest verified rate at $5 per 1,000 pages, about $0.025 for a typical five-page statement. Azure AI Document Intelligence follows with its prebuilt Bank Statement model at $10 per 1,000 pages, about $0.05. Both bill per page, so they stay cheap even on long statements, unlike the per-document parsers.
Why does Google charge $0.75 for a bank statement?
Google's Document AI Bank Statement parser bills $0.75 per classified document, a flat fee that does not change with page count. That buys a statement-native model that already knows the schema: account details, statement period, running balance, and per-transaction rows. On a five-page statement it works out to roughly 15 times Azure's per-page cost, so you pay for the ready-made schema, not for the pages.
Is bank statement OCR billed per page or per document?
Both, and the difference is larger for statements than for any other document because statements are multi-page. Azure and Mistral bill per page, so a ten-page statement costs ten pages. Veryfi bills $0.25 per document up to 15 pages, and Google's Bank Statement parser bills $0.75 per document. On statements the per-page vendors are almost always cheaper, because a statement is several pages, not one.
Does AWS Textract extract bank statements?
AWS Textract has no dedicated bank statement model. You extract statement data by combining its Tables, Forms, and Queries features at $70 per 1,000 pages, or by running plain Detect Document Text at $1.50 per 1,000 and parsing the transactions yourself. Either way you build the statement schema, the account, period, balances, and transaction rows, that Google's and Azure's prebuilt models return out of the box.
How much does bank statement extraction cost at scale?
At 5,000 statements a month of about five pages each, Mistral Document AI runs about $125, Azure's prebuilt Bank Statement model about $250, a full IDP product around $350 to $500, Veryfi about $1,250 at its per-document rate, and Google's dedicated Bank Statement parser about $3,750. The billing unit, per page versus per document, accounts for almost the entire 30x spread.
What fields does a bank statement OCR API extract?
A good bank statement API returns structured fields, not just text: account holder and account number, bank name and address, statement period, opening and closing balance, and a row for each transaction with date, description, amount, and running balance. Google's and Azure's prebuilt statement models return this schema directly. Plain OCR endpoints return only the raw text, leaving you to reconstruct the transaction table.
Is there a free bank statement OCR API?
Some vendors offer an allowance rather than a permanently free API. Veryfi processes 100 documents a month free on an ongoing basis. Azure's free tier covers 500 pages a month, enough to test its prebuilt statement model. Google offers a new-customer credit. These allowances suit testing and low volume; production statement processing quickly moves onto paid per-page or per-document rates.
Do bank statements count as multiple pages for OCR pricing?
Yes on per-page vendors, and that is the whole point. Azure and Mistral charge for every page, so a six-page statement is six pages of billing. Veryfi treats a statement of up to 15 pages as one $0.25 document, and Google's Bank Statement parser treats it as one $0.75 document. So for long statements the per-document vendors flatten the cost, while for short ones the per-page vendors are cheaper.
Which is cheaper for bank statements, Veryfi or Google?
Veryfi, on price. Veryfi charges $0.25 per statement document up to 15 pages; Google's dedicated Bank Statement parser charges $0.75 per document. For the same statement Veryfi is three times cheaper. Google's parser competes on statement-native field quality and Google Cloud integration, not on price. The per-page options, Azure and Mistral, undercut both at typical statement lengths.
How do I compare bank statement OCR API pricing fairly?
Pick a realistic page count for your statements, five is typical, then normalize every vendor to cost per statement at that length. Check whether the rate is per page or per document, whether a per-document cap like Veryfi's 15 pages applies, and whether the vendor returns statement-native fields or only text. Add the free allowance and any monthly floor, such as Veryfi's $500 minimum. Only then are the vendors comparable.

Extract your statements and see the transaction rows

A per-statement rate cannot tell you whether the balances and every transaction line come out right on your real statements, dense brokerage ones included. Upload one, look at what comes back, and then decide which billing unit you want.