SoftTech AI Registry
Microsoft · Dynamics 365 Business Central

Payables Agent

An autonomous agent in Dynamics 365 Business Central that monitors a designated Microsoft 365 mailbox for vendor invoices sent as PDF attachments, imports each PDF as an Inbound E-Document, extracts invoice data with Azure Document Intelligence, identifies the vendor, drafts line-level accounting details in a purchase document draft, and finalizes the draft into a purchase invoice. Microsoft documents it as running under its own Business Central agent user identity, as never posting invoices, and as treating vendor creation and conversion of a draft into a purchase invoice as high-risk actions requiring human approval.

Recorded characteristics

Function
Microsoft documents the Payables Agent as handling "end-to-end processing of vendor invoices" in Business Central, where "the Payables Agent monitors mailboxes for incoming vendor invoices, uses AI to analyze invoice content, and shows invoice drafts to agent supervisors for review". The documented process flow is: a vendor or an employee sends or forwards an email to the monitored mailbox; the agent "picks up unread email in the monitored mailbox", imports the email and "creates an entry in Inbound E-Documents for every PDF attachment"; an agent supervisor reviews the email and PDF; the agent "extracts invoice information from the PDF using Azure Document Intelligence"; the agent "identifies a vendor in Business Central based on the extracted invoice information"; if it cannot confidently identify the vendor it stops and the agent supervisor may instruct it to create the vendor, after which the agent "attempts to create the vendor and uses the available OCR extracted vendor details to fill out as many fields on the vendor card as possible" and the supervisor is asked to review the newly created vendor, which is blocked for processing until unblocked; the agent "uses AI to suggest invoice details based on the extracted invoice information"; the agent supervisor "can review, confirm, or change the suggested invoice details in a purchase document draft, depending on agent configuration settings and the agent's confidence in the suggestions"; and the agent "finalizes the purchase document draft into a purchase invoice", after which "users now see the invoice in the Purchase Invoices list". Microsoft states that the dashed review steps in that flow are intended to become optional in time but "in the public preview release, these steps aren't optional". For line-level work Microsoft states that after identifying the vendor the agent "starts line-level processing of the invoice details" and "uses different methods to draft the best possible details. For example, it might use AI, vendor invoice history, mapping text to G/L accounts, Item References, and more", recording "all draft details for the specific vendor invoice in a Purchase document draft related to the Inbound E-Document". Microsoft's FAQ adds that the agent "analyzes each line item to suggest appropriate accounting treatments" and that account classification "matches line descriptions to general ledger accounts based on your chart of accounts and transaction history", "recommends deferral templates when items should be deferred over time" and "identifies items that match your existing inventory". Architecturally, Microsoft states the agent "interacts with Business Central features like a Business Central user", receiving general natural-language instructions and using UI metadata and page data so that "starting from the designated Role Center, the agent goes through pages, selects UI actions, and enters data as a user does", and that "it can also try to automatically fix validation errors by processing displayed error messages and adjusting the input".
Data access
Microsoft documents the agent reading: unread email in the designated Microsoft 365 mailbox or configured subfolder and its PDF attachments; the resulting Inbound E-Document records and the OCR extraction result, which "is stored in the same E-Document record"; the vendor list, including government registration numbers such as VAT registration numbers and Global Location Numbers, vendor names and addresses; vendor invoice history and historical transactions; the chart of accounts; item references and existing inventory items; deferral templates; and matched purchase invoice history, from which administrators can select "more fields from matched purchase invoice history to populate automatically when the agent finalizes purchase document drafts". Microsoft states the agent's reach is bounded by its assigned permission sets: by default the agent has the PAYABLES AG. - RUN permission set, which "restricts access to only the objects, data, and UI elements (such as pages, fields, and actions) necessary for processing vendor invoices", and "the agent can only access data within these predefined boundaries and can't exceed the permissions granted to it". Microsoft states the PDF is sent to Azure Document Intelligence for OCR extraction and that the feature uses Azure OpenAI Service, which may require administrators to allow data movement across geographies.
Actions
Can take actions
External actions
Unknown
Human confirmation
Conditional
Permission basis
Mixed
Administrative control
Documented controls: the Payables Agent appears under the Generally available section of the Copilot & agent capabilities page, where administrators can turn the capability off or on for all users in the environment. Beyond that, an administrator must configure and activate the agent: "each company can have only one Payables Agent", activation is performed with the Active toggle in the Configure the Payables Agent assisted setup guide, and configuration covers the monitored Microsoft 365 mailbox and optional folder, the agent language, and the Email review behaviour with options Manage per sender (recommended), Never ("process all emails without requesting review") and Always ("request review for all incoming emails before processing"). Known senders carry Ask, Approve or Reject policies that determine whether incoming email is processed without review, skipped entirely, or held for review; Microsoft states the agent itself adds new senders to the known senders list. Administrators can select additional fields from matched purchase invoice history to be populated when drafts are finalized. Access is controlled by the agent user access list with a Can configure checkbox and by the system permissions Configure All Agents (ID 9665) and Manage Agent Tasks (ID 9670); the SECURITY permission set includes Configure All Agents and the System Execute - Basic permission set includes Manage Agent Tasks. The agent's own authority is controlled through the Agent Permission Sets section of its agent card; the default PAYABLES AG. - RUN set cannot be modified directly but can be copied and adjusted, and the agent State must be set to disabled before permission sets are added or removed. Supervisors can Stop a task or Stop all tasks, noting that "stopped tasks can't be restarted", and can give per-step natural-language instructions that "apply only to the current step" and are not saved or reused. Oversight surfaces include the Tasks pane task timeline, a data review bar on documents created or modified by an agent, Done review marking that records the reviewer's name and date, agent KPI summaries, and clear marking of AI-generated content. Administrators also control billing: agents consume Copilot Credits, and when the quota is depleted "the agent stops processing new invoices from the monitored mailbox" while remaining active, resuming automatically and processing accumulated unread email when credits return unless the agent is deactivated first. Sandbox environments additionally require the Allow HttpClient Requests toggle on the Payables Agent extension.
Default state
Disabled
Availability
Microsoft lists the Payables Agent under the Generally available section of the Copilot & agent capabilities page in Business Central, and states that "the agent is available in Business Central and is ready for you to use. To activate it, see Payables Agent Setup". The overview page simultaneously refers to review steps that "in the public preview release ... aren't optional", so Microsoft's own current pages are not consistent on release stage, and that discrepancy is recorded rather than resolved here. Prerequisites include a Business Central environment in "a country/region version supported by the Payables Agent as listed in Feature availability by country/region and language", a Microsoft 365 email account (user or shared mailbox) in the organization to be monitored, and configured consumption-based billing for the environment. Microsoft states the feature "is available in all supported Business Central countries/regions", but that it uses Azure OpenAI Service, "which is currently available for Business Central in some geographies", and that where Azure OpenAI Service is unavailable "administrators must allow data to move across geographies". Language support: "this Copilot feature is validated and supported in English only", and the setup page specifies validation "in English (EN) in the following locales: Australia (AU), United Kingdom (UK), United States (US) and New Zealand (NZ)". The documentation is written for Business Central online environments administered through the Business Central admin center; the overview page was last updated 2026-05-03 and the setup page 2026-07-28.
Licensing
Microsoft states that "the Payables Agent uses Copilot Credits for AI interactions, which can incur charges based on interaction complexity" and that a billing model must be set up for the environment before use; the setup page adds that "agents use Microsoft Copilot Studio messages when activated, which your company is charged for". A trial mode available only in production environments before activation lets an organization "process up to 50 invoices without consuming billable AI credits", after which "the trial ends automatically and the agent transitions to full mode" and billable credits begin to be consumed. On user licensing, Microsoft states that "Essential and Premium license entitlements now include the Manage Agent Tasks permission" and that "all license types include the Configure All Agents permission". Consumed credits are visible in the Cost section of the agent configuration page.
External model or provider
Microsoft states that the agent "extracts invoice information from the PDF using Azure Document Intelligence" and that the feature uses the Microsoft Azure OpenAI Service, which is available for Business Central in some geographies only. Microsoft does not name a specific language model for the Payables Agent on the pages reviewed; the Copilot and agent configuration page states generally that administrators can see and select the model used by agents in the agent design experience, which is not established for the Payables Agent specifically.
Limitations and uncertainty
Recorded boundaries and open questions: (1) Autonomous processing is not autonomous approval. Microsoft states the agent "runs autonomously in the background" and "operates independently", but also that it "never performs severe or irreversible actions. It creates drafts only and never automatically posts invoices or makes permanent changes to your financial data without explicit human approval", and that it "treats vendor creation and converting drafts to purchase invoices as high-risk actions that require mandatory human approval before proceeding". (2) Creation versus posting: Microsoft establishes that finalizing a draft creates a purchase invoice visible in the Purchase Invoices list, and that after finalization the draft "is linked to the purchase invoice and is no longer editable" and remains for as long as the invoice exists. No posting authority is established; the FAQ states the agent "never automatically posts invoices" and trial-mode documentation states "nothing is posted automatically - you review and approve all drafts before posting". No documented authority to post, create vendor ledger entries, create or release payment journal lines, generate payment files, interact with bank accounts or transmit payments was found; the phrase "end-to-end processing of vendor invoices" is not treated as establishing any of these. (3) Approval workflows: the overview states that the Payables Agent "currently doesn't support" approval flows and anomaly detection. The agent therefore does not create approval requests, submit invoices into a Business Central approval workflow, approve or reject invoices on the pages reviewed; "ready for approval" describes the state in which the invoice is left for humans. The FAQ's use of the word approval for supervisor confirmation of agent steps is confirmation of the agent's work, not financial approval. (4) Vendor creation is documented but only on supervisor instruction: the agent stops when it cannot identify a vendor, and only after the supervisor instructs it does it create the vendor card from OCR data, with the Blocked field set to All; Microsoft states "the agent itself doesn't provide any capabilities for vendor approvals". (5) Account matching means general ledger account suggestion from line descriptions using the chart of accounts and transaction history, plus deferral template recommendations and matching to existing inventory items. No documented handling of dimensions, posting groups or tax/VAT determination as agent behaviour was found on the pages reviewed. (6) Purchase order matching is not established. No documentation was found of header, line, quantity, price, receipt or tolerance matching against purchase orders, or of three-way matching; the documented source records are the email, its PDF attachments, the Inbound E-Document and vendor invoice history. (7) The documented extracted data is described by Microsoft as "text, amounts, dates, line items, and vendor details"; individual field names such as invoice number, due date, currency or tax lines are not enumerated on the pages reviewed. (8) Permission basis is recorded as mixed because two distinct runtime mechanisms are documented: inside Business Central the agent "operates with its own unique user identity", has "a user account in Business Central, similar to other users" and "works within the permissions and profile (role) the admin assigns", with the PAYABLES AG. - RUN permission set by default; while mailbox access is documented as running under a human user's context - "when a user activates the agent, it runs as a background task in the context of that user and needs access to the shared mailbox to process emails", with Read and manage (Full Access) Exchange permission required on the mailbox for users who activate and configure the agent. (9) External action capability is recorded as unknown: the agent consumes unread email from an Exchange mailbox and PDFs are sent to Azure Document Intelligence, but Microsoft does not state on these pages whether the agent changes state outside Business Central - for example whether it marks, moves or deletes mail - and the generic agent supervision page's reference to reviewing "incoming and outgoing emails" covers Business Central agents in general, including the Sales Order Agent, and is not attributed to the Payables Agent here. (10) Human confirmation is recorded as conditional: draft finalization into a purchase invoice and vendor creation require human approval, and review steps are currently non-optional per the overview, while email review can be configured to Never so that emails are processed without review, and senders with an Approve policy or emails in a monitored subfolder are processed automatically. (11) Ingestion is email-only: "the invoices must arrive via email to monitored mailboxes. Users can't upload files directly", the agent processes only emails with PDF attachments, and emails without PDF attachments "appear as agent tasks that require manual attention". Trial-mode documentation nonetheless describes uploading a PDF invoice in the setup guide to start the agent, which is a setup action rather than the ongoing ingestion path. (12) Microsoft's two current pages disagree on processing constraints: the overview states PDFs of more than 10 pages, PDFs larger than 5 MB, more than 100 emails per day and more than 500 invoices per day are not processed, while the FAQ states up to 100 emails per day, up to 50 emails in one batch and PDF attachments of 20 MB or smaller with a maximum of 10 pages. Both are recorded; the discrepancy is unresolved. (13) Accuracy limitations documented by Microsoft: account classifications and vendor matches "can be inaccurate", the system "can't understand business context", suggestion quality depends on historical transaction data, unrecognized PDFs are marked Unknown Document Type, and high-volume processing might experience delays. (14) Release stage, model identity and the precise boundary of the agent's authority over Exchange remain open questions.

Evidence