Best OCR API for Accounts Payable: $10 vs $100 per 1,000
Two vendors quote the same job and the quotes differ by ten times, with nothing on either pricing page explaining what the extra money buys.
📜 Table of Contents
Two managed parsers do the same advertised job, read an invoice, return the fields, and one charges ten times what the other does per page. For an accounts payable team running 5,000 invoices a month at two pages each, that is $100 against $1,000 for identical volume.
Both numbers come from the vendors, not from a reseller blog. I pulled the AWS figure from the official price list feed for us-east-1 on 22 November 2026 and the Google figure from the Document AI pricing page the same day. Prices move; the ten-to-one ratio is the part worth remembering.
The price board
| route | what it returns | price per page | per 1,000 invoices (2 pages) |
|---|---|---|---|
| AWS Textract AnalyzeExpense | vendor, total, line items, dates | $0.010 first 1M pages/month, $0.008 after | $20 |
| Google Document AI, Invoice parser | invoice fields against a fixed schema | $0.10, or $0.09 and $0.08 under committed savings plans | $200 |
| Google Document AI, Expense parser | receipt fields | $0.10, same tiering | $200 |
| AWS Textract DetectDocumentText | text and words, no fields | $0.0015 first 1M pages, $0.0006 after | $3 raw OCR |
Read the fourth row as the floor. Raw text out of the same document, from the same vendor, costs a sixth of the parsed fields. The gap between row four and row one is the price of someone else having solved field extraction for you.
What the tenfold gap actually buys
Both managed routes take a PDF and return structured values. The difference that matters at invoice volume is not model quality, which you cannot compare from a price page, it is what happens when a field is missing or ambiguous. A managed parser has a fixed schema and a documented behavior, so your downstream code can assume keys exist and be wrong in a predictable way.
That predictability is what you are buying with the extra $180 per thousand. If your AP process runs through an ERP connector that expects vendor, date, currency, net, tax and total, and a human then approves exceptions, the managed parser is a smaller integration than a self-built pipeline that needs its own accuracy evaluation before anyone trusts it.
The trap is choosing on sticker price alone in either direction. Ten times cheaper is not worth much if the cheaper parser silently drops the tax line on multi-page invoices and nobody measures it. Ten times more expensive is not worth much either if the output schema does not match what your ERP wants and you rebuild the mapping anyway.
Worked example: 5,000 invoices, ten thousand pages
| route | monthly cost | what you still owe |
|---|---|---|
| Google Invoice parser | $1,000 | nothing on extraction, mapping to ERP |
| AWS AnalyzeExpense | $100 | mapping to ERP, exception review |
| Textract text plus your own LLM | $20.75 | schema, prompts, evaluation, accuracy ownership |
The third row is not a guess. Ten thousand pages of DetectDocumentText is $15.00. A two-page invoice produces roughly 1,400 tokens of OCR text, and a constrained JSON answer is about 300 output tokens. At Mistral Large list prices, $0.50 per million input tokens and $1.50 per million output, 5,000 invoices cost $3.50 in input and $2.25 in output. Total: $20.75 a month, or $4.15 per thousand invoices.
Those token figures are my assumptions, stated so you can replace them: 700 tokens of text per dense invoice page, 300 tokens of JSON out. If your invoices are scanned at low quality and the OCR text triples, the LLM line triples with it and the total lands near $30.
Where the cheap route breaks
The $20.75 path fails in five specific ways, and knowing them in advance is the difference between a working pipeline and a support ticket.
Multi-page line items. OCR returns text in reading order, and a table that continues onto page two becomes a paragraph. Detecting the continuation and re-attaching it is your code, not the vendor's.
Totals that must reconcile. A managed expense parser returns fields. Your own pipeline returns fields too, plus every arithmetic inconsistency that proves a field is wrong. Use that: sum the line items, compare against the subtotal, and reject on mismatch instead of passing bad numbers downstream.
Currency and tax formats. A comma is a thousands separator in one country and a decimal point in another. One rule table, written once, beats a prompt asking the model to be careful.
Handwriting and stamps. Detecting that a document is out of distribution is worth more than guessing. Fail closed on low confidence.
Evaluation you have to build. Fifty invoices with hand-checked fields, scored per field, is the minimum honest test. Without that number you do not know whether the cheap route is cheap or merely quiet.
Picking, by volume and tolerance
| situation | sensible route | why |
|---|---|---|
| under 500 invoices a month, one bookkeeper | managed parser, or a receipt scanner app | the integration is the cost, not the per-page fee |
| 2,000 to 20,000 a month, ERP downstream | AWS AnalyzeExpense, or Google if a committed plan is already in place | fixed schema, predictable exceptions, price at $0.01 a page |
| same volume, engineering time available | raw OCR plus your own model, with a 50-invoice eval set | 5x cheaper at this volume, and you own the failure modes |
| over 500,000 pages a month | negotiate, then re-measure | AWS drops to $0.008 a page, Google to $0.08 with a plan |
One thing that does not change with volume: whoever reads the output needs the same six fields either way. Spend the engineering time on the reconciliation checks before you spend it on prompt wording, because the checks are what catch a wrong vendor name at 3am.
What about the free tiers
Azure Document Intelligence publishes 500 free pages a month on the S0 tier, which the pricing page lists in the tier table. That is enough to run a real pilot on your own documents before committing to any vendor, and it is the cheapest way to find out whether your scanned invoices are as clean as you think.
I did not verify Azure unit prices for this piece. The Azure pricing page renders its per-page figures through script, so the numbers were not in the response I could read, and I am not going to quote a price I could not fetch. Their calculator is the place to get it. The same caution applies to any vendor whose pricing page is a JavaScript app: if you cannot read a number without running their code, treat the number you remember as unverified.
FAQ
Is the AWS price the same for the synchronous and asynchronous call? Yes, at this volume. The price list carries SyncExpensePagesProcessed and AsyncExpensePagesProcessed at the same $0.010 for the first million pages. Pick sync for single invoices and async for batches; the billing does not care.
Do prices differ by region? They can. Every number here is us-east-1 on 22 November 2026. Check the region you actually deploy into; the ratio between the two vendors will hold even if the absolute numbers shift.
Is Document AI cheaper if I only need text? Its OCR processors are priced differently from the invoice parser, but at $0.10 a page for the invoice model, the interesting comparison for text-only work is Textract at $0.0015. Same arithmetic either way: pay for parsing only where you cannot parse.
Can I skip OCR and send the PDF straight to a multimodal model? Yes, and it is a legitimate fourth route: one call per document, no separate OCR bill. The catch is that you pay image tokens instead of page fees, and the cost scales with resolution and page count in a way that is harder to forecast. Measure it on your own documents before switching.
What breaks first at scale? Not the parser. Rate limits and retries. Batch endpoints exist for this reason, and a queue that retries on 429 with backoff is cheaper to build now than to retrofit after the first month-end crunch.
Bottom line
At 5,000 invoices a month the managed parsers cost $100 and $1,000, and a self-built pipeline on the same vendor's raw OCR costs about $21. The tenfold gap between the two managed options is not a quality difference you can read off a price page, so pick on schema fit and on who owns the exceptions. If you cannot name the person who checks the extracted fields, buy the parser. If you can, and you have fifty hand-checked invoices to prove the pipeline works, the raw route pays for itself in the first month.
Related: receipt scanners priced for bookkeepers, clause maps that cut contract review tokens 83 percent, what 1,000 RAG questions cost, measured.
Written by our editorial team; tools listed here are tested or verified against public sources. Links point to official sites or GitHub repos for reference only — no paid placements.