Business Central Payables Agent is Microsoft's AI-assisted invoice intake feature for Dynamics 365 Business Central. It monitors a mailbox for PDF vendor invoices, or takes invoice PDFs a user uploads, extracts the invoice data, identifies the vendor, suggests invoice lines, and proposes matches to purchase order lines. The result is a draft that a supervisor reviews and finalizes into an unposted purchase invoice. The agent does not post it. That makes it useful for reducing manual keying at the point where vendor invoices first enter the system.
The important qualification comes immediately after the definition. The agent reads PDFs only, and Microsoft documents hard limits on attachments, file size, page count, and daily volume. It is validated and supported in English only, it has no approval flow or anomaly detection of its own, and every invoice it processes is billed in Copilot Credits. If you are evaluating Business Central Payables Agent as part of a broader Business Central vendor invoice automation plan, those boundaries matter more than the headline feature description.
That is why it helps to think of Payables Agent as a capture and draft-creation layer inside Microsoft Dynamics 365 Business Central rather than a full accounts payable automation stack. It can help move invoice data from inbox to draft purchase invoice faster, but your team still owns review, exception handling, and the rest of the payables process.
For most teams, the real decision is not "Does Business Central have invoice AI?" It is "Does the native path fit the way our suppliers actually send invoices, and does it reduce cleanup enough to help the next step?" The rest of this guide answers that question from an operational point of view rather than repeating product copy.
How Invoices Move from Mailbox to Draft Purchase Invoice
The native flow starts before anyone opens the purchase invoice screen. A supplier sends a vendor invoice to the mailbox your team has designated for intake, or someone forwards one there. As Microsoft's Payables Agent overview describes it, the agent picks up unread email in that mailbox and creates one entry in Inbound E-Documents for each PDF attachment. It extracts the invoice data with Azure Document Intelligence, then identifies the vendor from registration numbers such as a VAT number, from name and address similarity, or by searching your vendor list and past transactions. When it cannot, it stops and asks a supervisor, who can instruct it to create the vendor. A vendor the agent creates is set to Blocked until someone reviews and unblocks it.
With the vendor known, the agent suggests invoice lines from vendor invoice history, G/L account mappings, Item References, and deferral templates. Where the invoice references a purchase order, it proposes order-line matches, and Business Central checks that each order line is compatible before allocating the invoice quantity to it. Everything lands in a purchase document draft, the agent's draft purchase invoice, rather than a posted transaction.
Since 2026 release wave 1 there is a second way in. Any user can start a free trial from the agent setup card or the Purchase Invoices page by uploading invoice PDFs, with no email setup and no administrator role. A company gets 50 free invoices that way, and continued use after that needs Copilot Credits.
That draft status is a practical detail, not a footnote. Business Central email invoice intake reduces how much data your team needs to retype, but it does not remove the review step. Someone still needs to confirm that the right vendor was identified, that the extracted values and order-line matches make sense, and that the draft is ready to finalize. Confirming that review is not a Business Central approval workflow: the agent finalizes the draft into an unposted purchase invoice, which then goes through whatever approval and posting your process requires. If your team uses the phrase invoice registration in Business Central, this is the handoff to define before approval and posting.
This is also where Inbound E-Documents matters. Every PDF the agent picks up gets an entry there, including files that are not invoices at all: those are marked as an unknown document type, and someone has to find them in the Unknown Document Type view and remove them. Invoice capture is not only about reading a file. It is about how incoming documents are brought under control inside the system, linked to the right vendor and purchase order, and handed to a person who can decide whether the draft is accurate enough to continue. If your team wants to scan vendor invoices in Business Central with less manual entry, this is the part of the workflow that actually changes.
The outcome is best understood as purchase invoice draft automation, not touchless AP. The system can move supplier emails into a usable draft much faster than manual entry, but AP still does the judgment-heavy work around validation, exception handling, and release readiness.
Prerequisites That Determine Whether Native OCR Works Well
Before you rely on Business Central invoice OCR in production, check the prerequisites that determine whether the workflow is available and whether it will behave predictably. In practice, that means confirming the agent is activated for the company, the monitored mailbox is configured correctly, a billing model for Copilot Credits is in place, and the right users have the permissions needed to supervise and review the resulting drafts.
Availability is broad, but language support is not. According to Microsoft's Payables Agent FAQ, the agent is available in all supported Business Central countries and regions, but it runs on Azure OpenAI, so where that service is not available for your environment's geography an administrator must allow data to move across geographies. The agent is validated and supported in English only. Microsoft says it can be used in other languages but might not work as intended, so if a meaningful share of your vendor invoices arrives in French, German, or Spanish, test it on those before planning around it.
The mailbox needs more thought than a forwarding address. Microsoft recommends a shared Microsoft 365 mailbox kept internal rather than given to vendors, so your own staff see invoices first and can spot fraud, and attended only from within Business Central. The agent picks up unread email, so an invoice someone opens or deletes in Outlook may never reach it, and a mailbox shared with the Sales Order Agent causes conflicts over which agent owns incoming email.
Suggestion quality depends on your data. Account suggestions improve with transaction history, and a company with little purchase history gets fewer of them. Vendor matching and order-line matching are only as good as the vendor, item, purchase order, and chart of accounts records they are checked against.
Teams usually get better results when they treat setup as an operations decision rather than a toggle. Mailbox ownership, supplier sending habits, review responsibility, master data, and credit capacity all affect whether the feature saves time or just moves cleanup to a different screen.
What Business Central Payables Agent Costs
The agent is billed per use in Copilot Credits, Microsoft's billing unit for agents, at rates set out on Microsoft's consumption billing page for Business Central. Processing an invoice costs 50 Copilot Credits, covering the ten agent actions that turn it into a purchase document draft, and each invoice line adds 5. Emails without a valid invoice attachment cost nothing. Microsoft's own example: 100 invoices a month with three lines each comes to (50 + 5 × 3) × 100 = 6,500 Copilot Credits a month. Line count drives the bill as much as invoice count does: a 20-line invoice costs 150 credits, against 55 for a one-line invoice.
Credits come from prepaid Copilot Credit packs, bought through the Microsoft 365 admin center, or from pay-as-you-go through an Azure subscription linked to the Power Platform environment. Where both exist, prepaid capacity is used first, and that capacity is shared with other Microsoft services on the tenant. When the quota runs out, the agent is unavailable until more capacity is added, which is worth knowing before month-end close. Microsoft publishes the price per credit on its Copilot Studio pay-as-you-go pricing page, and the 50 free invoices of the upload trial let you see the agent on your own invoices before any of it applies.
The Limits That Still Create AP Cleanup Work
The most useful way to assess Payables Agent is to separate what it automates from what it still leaves with your AP team. The current documented limits are narrow enough that they should shape your rollout decision from the start.
Microsoft documents these limits:
- PDF only. An email with no PDF attachment is not processed for invoice creation and becomes a task that needs a person.
- An email with more than 10 attachments is skipped entirely.
- A PDF of more than 10 pages is not processed.
- A PDF larger than 5 MB is not processed.
- At most 100 emails and 500 invoices a day.
- Validated and supported in English only.
- No approval flows.
- No anomaly detection, and no vendor approval: a vendor the agent creates stays blocked until a person approves and unblocks it.
- Purchase order matching does not cover Charge (Item) lines or order lines with prepayments, and its warnings are Business Central's quantity, receipt, unit-of-measure, and price validations, not AI confidence.
Those details explain why some teams still experience heavy cleanup work even when the first extraction step is automated. If suppliers send image files, large packets, multi-document bundles, or invoices that need more pre-processing before they are usable, the native path can stop short of what the operation needs. Order matching is now part of the draft, within its restrictions, but approval routing and anomaly signals still sit outside the agent, so a process that depends on them before anyone moves forward has to provide them elsewhere.
This is also where the real constraint becomes visible: it is not just about OCR recognition quality. It is about the scope of the entire capture workflow. Business Central purchase invoice OCR can help with eligible PDF intake, but it does not replace the wider controls many AP teams associate with full invoice processing automation.
When Native Payables Agent Is Enough and When Upstream Extraction Helps
Native Payables Agent is often enough when your intake profile is narrow and predictable. If most supplier invoices arrive as standard English-language PDFs by email, volumes sit well within 500 invoices a day, and your team mainly wants faster draft creation with human review inside Business Central, the native route can be a sensible fit. In that situation, the main goal is to reduce rekeying, not to redesign the whole intake stack.
The trade-off changes when the intake profile becomes messier. Scans saved as JPG or PNG images, PDFs over 10 pages such as an invoice with pages of line items or a scanned batch in one file, invoices in languages other than English, custom field rules, a backlog that would run past the daily caps, and document packets that need filtering before they reach ERP review all push the problem upstream. A large one-off load raises a cost question too, since every invoice and every line is billed in credits. That is where an additional extraction layer can help. A workflow built around AI invoice extraction for Business Central workflows gives teams more control before the invoice ever becomes a draft purchase invoice.
This is also the point where workflow quality matters more than feature count. If you need cleaner outputs for downstream review, import, or posting, the upstream step has to normalize data before Business Central sees it. For example, Invoice Data Extraction takes PDFs of up to 5,000 pages as well as JPG and PNG images, in any language, up to 6,000 files in one batch, and extracts header fields and line items by rules you write in plain words: tell it what to ignore, email cover sheets or remittance advice for instance, and it will. It returns Excel, CSV or JSON with the same columns and formats for every document, and a value or a row the panel of AI agents cannot agree on is flagged as Review Needed, with what to check. Those capabilities are useful when your next step may involve one of several invoice import methods in Dynamics 365 Business Central, or when your team wants tighter control over what reaches reviewers.
Finance teams are already investing in this kind of operational control. Dynamics 365 itself reflects how much ERP-driven automation demand is growing: Microsoft's FY2026 Q2 earnings report showed Dynamics 365 revenue grew 19%, with growth across all workloads, a signal that finance teams are actively investing in platform-native automation. The takeaway here is not that every AP team needs another tool. It is that native Business Central payables automation works best when its document boundaries match your real intake conditions. When they do not, upstream extraction can reduce the cleanup that otherwise gets pushed into the ERP.
How to Design the Next Steps After Capture
Once a draft exists, the hard part of the workflow is not over. A workable Business Central AP automation workflow still needs clear ownership for review, correction, approval, and posting. If the intake step produces drafts that regularly need manual fixes, the bottleneck simply moves downstream.
Design capture and post-capture steps together. At minimum, decide:
- Who owns the monitored mailbox and the exceptions that never fit the native intake rules.
- Who validates draft quality before an invoice moves forward.
- Who checks the agent's order-line matches in the draft, and where approvals and posting happen after it.
- What route out-of-bounds documents follow when they exceed native limits or arrive in the wrong format.
If your next concern is routing and control inside Business Central, this is where Business Central purchase invoice approval workflows become the more relevant topic than Payables Agent itself.
Keep ecosystem comparisons separate from capture decisions. Some organizations evaluating Microsoft finance tools are really comparing product families, responsibilities, and workflow depth, not just OCR behavior. In those cases, a broader view of how Dynamics 365 Finance automates vendor invoices can clarify whether the issue is invoice intake, ERP design, or the division of work between upstream extraction and the system of record. Teams running F&O at higher volumes often pair this evaluation with a look at batch vendor invoice import through the Data Management Framework, since the staging-table and workflow handoff there shapes how upstream extraction output should be structured.
The decision lens is straightforward. Keep the native path if your invoice sources are stable, the documented limits are acceptable, the credit cost fits your volume, and draft review remains lightweight. Add more upstream control when document variety, formatting rules, or cleanup effort start slowing the people who should be approving and posting rather than fixing intake issues.