Azure Document Intelligence Pricing Explained: Invoice Cost Per Page and a No-Code Alternative

Last updated August 2026. Microsoft updates Document Intelligence pricing over time, so treat the figures here as the current published US pricing and confirm the latest numbers on the Azure Document Intelligence pricing page before you build.

Azure Document Intelligence pricing vs InvoiceExtractor, side by side

Document Intelligence prices a raw OCR API per page, while InvoiceExtractor prices a finished, no-code product per month. The headline rates measure different things: one is the cost of a single model call, the other is the cost of a working invoice-to-spreadsheet workflow with nothing to build. Here is an honest comparison on the things that actually decide your total cost.

What the prebuilt Invoice model really costs per invoice

On the pricing page the prebuilt Invoice model looks almost free: $10 per 1,000 pages, about a penny a page. Unlike some cloud APIs, Azure does not round each document up to a block, so a one-page invoice really is about $0.01. Run 2,500 invoice pages a month and the base API charge is roughly $25, and 10,000 pages is about $100. The numbers that do not show on the headline are the free-tier limits and the add-ons. The free F0 tier reads only the first 2 pages of any file and stops at 500 pages a month, so any real AP volume runs on the paid S0 tier. And if you switch on Query Fields to pull values the model does not return by default, that adds $10 per 1,000 pages, while high-resolution, formula, and barcode add-ons add $6 per 1,000 each. With a couple of those enabled your effective rate is well above $0.01 a page.

That number is still only the API charge. The Invoice model returns structured JSON with fields such as vendor, invoice number, date, totals, and line items, each with a confidence score. To get that into your accounting system, a developer has to set up an Azure subscription, deploy a Document Intelligence resource, manage keys and endpoints, call the SDK, map every field to your columns, reassemble line items into clean rows, and keep it working as vendor layouts change. If a layout needs a custom model you also pay $30 per 1,000 pages plus $3-an-hour training. Add the engineering hours and the all-in cost for an invoice-only team is usually far above the sticker rate.

Now put it next to a flat plan. InvoiceExtractor Starter is $49 a month and includes 2,500 pages, and the Plus plan is $149 a month for 10,000 pages, both in US dollars, with full line items, multi-page and multi-invoice handling, a review screen, and Excel or CSV output, and no code to write or maintain. At a few thousand invoices a month with the fields you actually need, the no-code plan is competitive with Document Intelligence before you even count the build. If you have engineers and an Azure pipeline already, Document Intelligence can still fit. If you do not, the flat tool is almost always cheaper once you count the add-ons and the engineering. That is the honest trade-off, and it is worth doing the math on your own invoice volume.

Where Azure Document Intelligence is the better choice

Document Intelligence earns its place for the job it was built for. If you have developers working inside Azure, its strong OCR, broad library of prebuilt and custom models beyond invoices, batch processing, and the ability to keep documents inside your own Azure tenant for compliance are real advantages. At very high volume across many document types, the per-page rate is hard to beat, and teams that need fine control over the JSON response and how each field flows into their systems get a well-documented, capable primitive. For raw document OCR beyond invoices, an enterprise platform such as document data extraction software covers broader document types, and Document Intelligence sits comfortably in that build-your-own world.

Where a no-code invoice tool wins

For a US team whose whole job is turning vendor invoices into clean data, wrapping a raw model in custom code adds cost and fragility you do not need, and the add-on fees and free-tier limits work against a simple invoice workflow. InvoiceExtractor reads any invoice layout with no template and no code, captures every line item, splits batches that contain multiple invoices, and exports straight to Excel or CSV. The invoice data extraction software overview covers exactly what gets captured, and the invoice OCR software page shows how the AI reads PDFs, scans, and photos. If you do want a programmatic option, the invoice data extraction API returns the same structured data on a flat plan, without per-page OCR charges. Comparing the wider field on cost? The best invoice data extraction software roundup, the Azure Document Intelligence alternative and AWS Textract pricing breakdowns, and the Google Document AI pricing and Nanonets pricing pages cover the other cloud-API, platform, and developer sides of the market.

Extraction is usually the first step in a larger workflow. Once invoice data is structured, many teams route it straight into approvals and payment, so pricing the whole accounts payable stack is worth doing alongside the extraction tool. A dedicated accounts payable automation platform handles the approval and payment side once the data is clean. Getting the extraction step right first keeps everything downstream fed with reliable data.

You may already be paying for Document Intelligence inside another product

This is the part of the pricing question most buyers miss. Azure Document Intelligence is the OCR engine embedded in other Microsoft products, so a finance team can be consuming it without ever opening the Azure portal. The clearest example is the Payables Agent in Dynamics 365 Business Central: Microsoft documents that the agent sends each PDF invoice attachment to Azure Document Intelligence for extraction and stores the result in the Inbound E-Document record. You never see a per-page line item for it, because Business Central bills the agent through Copilot Credits on consumption-based billing rather than the published Azure page rate.

That matters for a cost comparison in two ways. First, the effective per-invoice cost inside Business Central is not the $10 per 1,000 pages on the Azure pricing page, it is whatever the Copilot Credit consumption works out to, and Microsoft notes charges vary with interaction complexity. Second, the embedded route carries limits the raw API does not: the agent will not process PDFs over 10 pages or over 5 MB, skips emails with more than 10 attachments, and caps at 100 emails and 500 invoices per day. If you are running the numbers for a Business Central shop, our Business Central AP automation page lays out those documented constraints against a flat-rate capture layer, and the guide to importing invoices into Business Central covers the bulk routes the agent does not handle.

The practical takeaway: before you price a Document Intelligence build, check whether the workload is already covered by a product you license, and whether that product's limits fit your invoice volume. Paying twice for the same OCR engine, or building on a raw API when an embedded one would do, are both easy mistakes at this stage.

Is Azure Form Recognizer the same as Azure AI Document Intelligence?

Yes. Microsoft renamed Azure Form Recognizer to Azure AI Document Intelligence, and the service, the models and the pricing are the same thing under a newer name. Older tutorials, SDK package names and Stack Overflow answers still say Form Recognizer, so if you are comparing a quote or an old cost estimate against current rates, you are comparing the same product.

This matters when you search for pricing, because the three names return different pages. "Azure Form Recognizer pricing", "Azure AI Document Intelligence pricing" and "Azure Document Intelligence pricing" all describe the same rate card: $10 per 1,000 pages for the prebuilt Invoice model, $1.50 per 1,000 for Read OCR, $30 per 1,000 for custom extraction, and an F0 free tier capped at 500 pages a month and the first 2 pages of any file. The naming change did not alter what you pay per page, only what the docs call it.

One practical consequence: if your team built an integration against the Form Recognizer SDK, the client libraries were renamed too, and the API version you pin determines which model set you can call. Older API versions do not expose newer add-ons such as Query Fields, so an integration that has not been touched in a couple of years may be missing capabilities you are budgeting for. Confirm the API version before you cost out a rebuild.