Does Microsoft Dynamics 365 have OCR? A simple guide

Microsoft Dynamics 365 has optical character recognition (OCR), but it depends on the stock keeping unit (SKU).

Dynamics 365 Finance includes OCR-based invoice capture through Microsoft's Invoice capture solution. Business Central doesn't run its own OCR engine and instead sends documents to a Dynamics 365 OCR service from a third-party provider. Dynamics GP has no native capture and relies on independent software vendor (ISV) add-ons.

Each SKU extracts different data and gets purchase order (PO) matching and approvals from different places. The price also changes once you add up licenses, transactions, and admin time.

Dynamics 365 OCR by SKU at a glance

In Dynamics, OCR means vendor invoice capture in accounts payable (AP). It reads a PDF or image of a vendor invoice and turns it into a draft invoice in the enterprise resource planning (ERP) system. None of the three SKUs offers a general-purpose text extraction tool for other documents.

• Dynamics 365 Finance: Native. Invoice capture is a Microsoft solution built on Power Platform and AI Builder.
• Business Central: Third-party. Business Central OCR runs through an external OCR service you connect to the Incoming Documents page.
• Dynamics GP: Third-party only. You need an ISV add-on for any OCR invoice capture.

Start by confirming which SKU you run, because that single fact decides whether OCR is something you configure or something you buy.

Dynamics 365 Finance: Invoice capture

Invoice capture is Microsoft's solution for creating vendor invoices in Finance from invoice images. It runs on Power Platform, using AI Builder to read the document, Power Automate to move files in from email or SharePoint, and Dataverse to store them before data transfers to Finance.

Finance also has an older path: vendor invoice automation with Intelligent OCR. That approach needs a connection to an external OCR provider, which hands extracted data to Finance's vendor invoice automation framework. Invoice capture is Microsoft's current tool for OCR invoice capture, so most new implementations start there.

Invoice data capture reads header and line-level data, then checks it against Finance master data:

• Header fields: Vendor, invoice number, invoice date, due date, currency, and totals
• Line items: Descriptions, quantities, unit prices, charges, and tax
• Mapping and validation: Matches the vendor, legal entity, and items to Finance master data and checks totals before transfer

Setup is an implementation project. You'll need a Power Platform admin, an environment maker, an AP admin, and AP clerks. Anyone reviewing invoices without a full Finance license needs the InvoiceCaptureOperator role.

The Finance license covers part of your Dynamics 365 AP automation, and you pick up the rest:

• Included: A monthly allotment of Invoice capture transactions as part of the Finance license
• You license: Power Apps seats for reviewers who don't hold full Finance licenses
• You may add: Dataverse storage if invoice files outgrow your default capacity
• You configure: Channels such as email, SharePoint, or OneDrive that feed invoices in
• You maintain: Vendor, legal entity, and item mappings so invoices land in the right place

Budget for the setup work as well as the license, because the mappings and roles decide how many invoices pass through without a clerk touching them.

What Invoice capture costs on Finance

Finance customers are entitled to 100 Invoice capture transactions per tenant per month, according to Microsoft Learn. Beyond that, you buy extra Electronic Invoicing SKUs at $300 per 1,000 transactions per tenant per month. Those blocks are use-it-or-lose-it, and Microsoft says you must buy for peak capacity.

Finance Premium licenses include 200 invoice capture transactions per tenant per month, according to Microsoft's licensing guidance.

The transaction fee is only one line in the bill.

If your volume spikes at quarter-end, size your capacity to that month, since unused transactions don't carry over.

Business Central: OCR through an external service

Business Central has no OCR engine of its own, so you pay a provider for it. Microsoft's documentation states the OCR feature comes from external providers, which you find on Microsoft Marketplace.

Capture runs through the Incoming Documents page and a job queue in five steps:

1. Create an incoming document: Upload a PDF or image on the Incoming Documents page, or have vendors email it to a monitored inbox.
2. Send it to the OCR service: A job queue sends the file to your provider.
3. Receive an electronic document: The service returns structured data, which the job queue brings back into Business Central.
4. Review and correct: You fix errors and send OCR feedback so the service learns each vendor's layout.
5. Create the document: Business Central turns the result into a purchase invoice, credit memo, or journal line.

Text-to-account mapping and item references fill in lines when the service returns text that doesn't match a G/L account or item number. Line-item capture depends on the provider's plan, and some entry plans capture only header and footer fields.

Check line-item support and current pricing on the provider's Marketplace listing before you commit. Scanning invoices using OCR at the header level still leaves your team keying every line.

Business Central and multiple entities

Business Central runs separate companies within one environment and supports intercompany postings and consolidation. OCR setup doesn't carry across companies, so if you run several entities, you configure each company on its own:

• OCR service setup: Connection and job queue entries per company
• Incoming documents: Each company has its own Incoming Documents list.
• Vendor and text-to-account mappings: Built and maintained in each company

With five entities, you maintain five sets of mappings, so factor that admin time in when you choose a provider.

Dynamics GP: No native OCR

If you want OCR on Dynamics GP, you'll need an ISV add-on.

GP's lifecycle shapes that decision. Microsoft stopped selling new GP subscription licenses on Apr 1, 2026. Per Microsoft's Dynamics GP lifecycle policy, product support and updates end Dec 31, 2029, and security updates end Apr 30, 2031.

Weigh any capture investment on GP against a migration to Business Central or another system.

What native capture doesn't cover

Capture gets invoice data into the ERP. Matching, approvals, posting, and payment are separate steps in Microsoft Dynamics AP automation, and each one needs its own setup.

Finance handles matching and workflow natively, but someone on your team still configures workflows, match tolerances, and vendor invoice automation. In Business Central, approvals and PO matching depend on approval workflows and sometimes on partner extensions.

Volume exposes the gaps in Dynamics accounts payable:

• Transaction caps: Finance charges for capacity in 1,000-transaction blocks, sized to your peak month.
• OCR corrections: Business Central providers need per-vendor training and OCR feedback.
• Non-PO invoices: Without a PO to match, someone still codes the GL account by hand.
• Exceptions: Mismatches and unreadable invoices land back with AP clerks.

Payment execution and vendor onboarding sit outside capture on every SKU. Plan for capture to solve data entry and nothing past it.

The total cost of the native path

Native capture costs show up in five places:

• Licenses: Finance seats, plus Power Apps for reviewers
• Capture volume: Invoice capture transactions on Finance, or provider plans on Business Central
• Storage: Dataverse capacity if invoice files exceed the default
• Implementation: Partner time to set up environments, channels, and mappings
• Ongoing admin: Hours spent training models, maintaining mappings, and handling exceptions

Native capture fits low-to-moderate volume, mostly PO-backed invoices, and an in-house Power Platform admin. A third-party AP tool fits better when volume swings month to month or most invoices are non-PO. It also makes sense if you want approvals and payments in one place.

Pick the path that matches your current invoice mix and admin bandwidth, because those two factors drive what you'll spend.

Automate invoice capture through payment with Ramp Bill Pay

Native capture gets invoice data into Dynamics, but coding, approvals, and payments still sit with your AP team. That gap widens as non-PO invoices and exceptions grow.

Ramp Bill Pay is an AP solution that runs alongside your ERP and handles invoices from intake to payment. AP Agent codes invoices from your own coding history and recommends approvals, then Ramp syncs bills to Business Central as purchase invoices or to Dynamics 365 Finance and Operations.

Here's what Dynamics invoice processing looks like with Ramp Bill Pay:

• Capture headers and line items: OCR reads invoice headers and line items with 99% accuracy.
• Code from your history: AP Agent learns from your past coding and improves as you correct it.
• Route approvals your way: Custom routing rules send each invoice to the right approver, with AP Agent recommendations.
• Pay how vendors want: Send ACH, check, card, or wire from the same place.
• Sync to Dynamics: Native integrations with Business Central and Dynamics 365 Finance and Operations keep your ledger current.

Try an interactive demo to see how Ramp handles invoices from intake to payment.