How AI-powered automation is transforming accounts payable from email inbox to posted invoice.
For most finance teams, processing vendor invoices is one of those tasks that is always there steady, demanding, and relentless. An invoice arrives in the inbox, someone opens the PDF, reads through the line items, figures out which vendor it belongs to, keys the data into the accounting system, maps it to the right GL accounts, and then routes it for approval. Multiply this by dozens or hundreds of invoices per day and you quickly have a bottleneck that no amount of overtime can permanently solve.
The challenge is not just about volume. It is about the cognitive load involved. Correctly registering an invoice requires accounting knowledge, familiarity with vendor history, an understanding of business rules, and the ability to make judgement calls when data is ambiguous. This is exactly why automation has historically struggled to crack this problem until now.
Microsoft’s Payables Agent, built into Business Central as part of the Dynamics 365 Copilot suite, takes a fundamentally different approach. Rather than following rigid rules, the agent uses AI to reason about invoice content the way a skilled accountant would identifying vendors, mapping costs, and drafting invoice details with accuracy that improves over time. And it does all of this autonomously, in the background, while keeping your team informed and in control at every critical step.
The Problem: Accounts Payable as a Bottleneck
Accounts payable has long been a source of operational friction. Invoices arrive via email in varying formats from hundreds of different vendors. Someone has to open each email, review the PDF, identify the vendor, manually key in invoice details, verify line items, and push the document through an approval chain. Even a well-organised team can only process so many invoices per day before quality begins to slip.
The downstream effects are real and compounding: delayed payments, strained vendor relationships, missed early-payment discounts, duplicate entries, GL coding errors, and an AP team stretched thin. Industry estimates suggest that manually processing a single invoice can take between 5 and 15 minutes depending on its complexity. For a business handling 150 invoices per day, that represents up to 37 hours of manual labour every single day just on data entry and verification.
Beyond the time cost, manual processing introduces variability. Different team members may interpret the same invoice differently, assign different GL codes, or handle ambiguous vendor names inconsistently. Over time, this creates data quality issues that affect financial reporting, audit readiness, and supplier payment accuracy.
Microsoft designed the Payables Agent with one clear goal: get accounting skills into the system and help register invoices correctly ideally removing bottlenecks in accounts payable so finance support does not slow company growth.
What Is the Payables Agent?
The Payables Agent is an AI-powered automation agent built natively into Microsoft Business Central. It is part of the broader Copilot for Dynamics 365 initiative and is designed to handle the full end-to-end processing of vendor invoices received via email as PDF documents with minimal human intervention required.
Unlike traditional robotic process automation tools that follow fixed scripts and break whenever a page layout changes, the Payables Agent operates more like a Business Central user with deep accounting knowledge. It reads the UI captions, tooltips, page structure and uses AI to decide what action to take at each step based on context. This makes it flexible and adaptable, capable of handling the natural variation that exists across different vendor invoice formats.
Once activated, the agent runs continuously as a background task. It monitors a designated mailbox, imports PDF invoices, extracts data using Microsoft’s Azure Document Intelligence OCR service, identifies the correct vendor, drafts a purchase invoice using multiple intelligence sources, and presents the draft to a human supervisor for a final confirmation before the invoice is posted. The entire process requires almost no manual setup to maintain.
Key Capabilities
- Continuous email monitoring: Watches a dedicated shared mailbox 24/7 for incoming vendor invoices without any manual triggering.
- OCR-powered data extraction: Uses Azure Document Intelligence to extract structured invoice data from any PDF, regardless of vendor format.
- AI-driven vendor identification: Cross-references extracted data against Business Central vendor records to find the correct match with confidence scoring.
- Intelligent invoice drafting: Combines AI suggestions, vendor purchase history, GL account mapping, and Item References to produce highly accurate draft invoices.
- Supervisor review workflow: Presents every draft to a human reviewer with full transparency into the agent’s field-level reasoning.
- Automatic vendor creation: Can create new vendor cards from OCR data when a vendor is not yet registered in Business Central.
- Audit-ready by design: New vendors are blocked by default; all agent actions are logged, traceable, and linked back to the original source document.
Functional Process Flow: End-to-End
The Payables Agent follows a clearly defined, end-to-end process from the moment a vendor invoice lands in the monitored mailbox to the moment a purchase invoice is ready for approval in Business Central. Three participants are involved throughout: the Vendor or Employee who sends the invoice, the Payables Agent itself running autonomously in the background, and the Agent Supervisor a designated Business Central user who reviews and confirms key steps.
The table below provides a detailed, step-by-step breakdown of every stage in the process, who performs it, what happens, and what the downstream effect is on the invoice journey:
| Step | Actor | Action | Description |
|---|---|---|---|
| 01 | Vendor / Employee | Send Invoice Email | Vendor sends an email with a PDF invoice to the dedicated monitored mailbox. Alternatively, an AP team member forwards the vendor’s invoice from their own inbox to the shared mailbox. |
| 02 | Payables Agent | Pick Up & Import Email | The agent’s background dispatcher continuously monitors the mailbox. It picks up unread emails, imports each one, and creates a separate Inbound E-Document entry for every PDF attachment found (maximum 10 per email). |
| 03 | Agent Supervisor | Review Incoming Email | The supervisor reviews the email and attached PDF before processing begins. This step confirms the document is a legitimate invoice and is currently required in the public preview release. |
| 04 | Payables Agent | Extract Data via Azure OCR | The PDF is sent to Azure Document Intelligence for OCR processing. Structured invoice data is extracted vendor name, address, VAT number, invoice number, date, line items, quantities, prices, and totals. |
| 05 | Payables Agent | Identify Vendor in BC | Using the extracted data, the agent searches Business Central vendor records to find a confident match, cross-referencing name, address, VAT numbers, and other identifiers. |
| 06 | Agent Supervisor | Assist with Vendor ID | If the agent cannot confidently identify the vendor, it pauses and asks the supervisor. The supervisor can select the correct vendor or instruct the agent to create a new one from the OCR data. |
| 07 | Payables Agent | Create New Vendor | If instructed, the agent creates a new vendor card using all available OCR-extracted details. The vendor is automatically set to Blocked to prevent premature invoice posting. |
| 08 | Agent Supervisor | Review & Unblock Vendor | The supervisor reviews the new vendor card, fills in any missing information, verifies bank details, and unblocks the vendor once satisfied. This step supports audit and fraud-prevention requirements. |
| 09 | Payables Agent | Draft Purchase Invoice | The agent uses AI reasoning, vendor purchase history, GL account mapping rules, and Item References to generate a purchase document draft. It records its reasoning for every suggested field value. |
| 10 | Agent Supervisor | Review Purchase Draft | The supervisor reviews the draft in Business Central. Each field shows the agent’s reasoning. The supervisor confirms, adjusts, or overrides values as needed before finalising. |
| 11 | Payables Agent | Finalise Purchase Invoice | Once confirmed, the agent converts the draft into a purchase invoice in Business Central. The invoice appears in the Purchase Invoices list ready for approval workflow and posting. |
NOTE: Steps 03, 06, 07, and 08 involve human review. In the current public preview release these steps are required. Microsoft has indicated they will become configurable in future releases allowing high-confidence, low-risk invoices to flow through with minimal or no supervisor intervention.
How the Agent Monitors Email
The agent runs an internal email dispatcher as a continuous background task. This dispatcher checks the monitored mailbox at regular intervals for any unread emails and triggers processing for each one that contains a PDF attachment. Every PDF becomes its own entry in the Inbound E-Documents list and is assigned an independent agent task meaning multiple invoices from the same email are processed in parallel rather than sequentially.
Emails without PDF attachments are not processed for invoice creation and are flagged in the task list for manual attention. Emails with more than 10 attachments are skipped entirely a practical consideration for vendors who bundle many files into a single message. Microsoft strongly recommends using a dedicated shared mailbox that is not exposed directly to vendors, and that team members access only through Business Central rather than Outlook, to keep the mailbox clean and under the agent’s full control.
How the Agent Drafts Invoices
The drafting step is where the agent’s intelligence is most visible. After identifying the vendor, the agent draws on four complementary sources to produce the most accurate purchase document draft possible:
- AI field suggestions: The agent analyses the full invoice content and applies AI reasoning to suggest the correct value for every field line descriptions, quantities, unit costs, tax codes, and more.
- Vendor purchase history: For recurring vendors, the agent reviews previous purchase invoices to identify patterns and pre-populate matching fields particularly useful for subscription or service invoices with consistent line items.
- Text-to-GL account mapping: Invoice line descriptions are mapped to the appropriate General Ledger accounts using Business Central’s existing mapping rules, supplemented by the agent’s own AI reasoning.
- Item References: Where available, vendor-specific item codes or descriptions are matched to the corresponding items in Business Central’s item catalogue using Item References.
For every field it suggests, the agent records a plain-language explanation of its reasoning. When the supervisor opens the draft, they can see not just what was filled in, but why making it straightforward to spot and correct any cases where the agent’s logic was off.
Keeping Humans in the Loop
The Payables Agent is not designed to operate as a fully autonomous, unmonitored process. It is built around a human-in-the-loop model that keeps designated supervisors informed, involved at critical decision points, and always in a position to override or redirect the agent’s work.
Agent supervisors interact with the Payables Agent through the Tasks tab in Business Central’s Copilot pane. Tasks requiring attention are surfaced at the top of the list. Each task includes a full timeline of every step the agent has taken, giving supervisors complete visibility into the processing history for any given invoice. Supervisors can review content in the main Business Central display area, make changes directly, and then confirm to let the agent continue or stop the task entirely if needed.
The two most important escalation scenarios are vendor identification and new vendor review. If the agent cannot confidently match a vendor, it pauses and asks for guidance before proceeding preventing invoices from being drafted against the wrong supplier. When a new vendor is created, the automatic ‘Blocked’ status ensures that no invoice can be posted until a human has verified the vendor record, supporting the fraud-prevention and audit requirements that most finance functions operate under.
Supervisors can also give freeform instructions to the agent in plain English through the Tasks tab for example, to create a specific vendor, look up an item, or try a different approach. These instructions are scoped to the current task only and do not affect the agent’s behaviour for other invoices.
Setting Up the Payables Agent
One of the more compelling aspects of the Payables Agent is how lightweight the setup process is. There is no lengthy implementation project, no complex integration work, and no need for specialist consultants. For organisations already running Business Central, activation is largely a matter of configuration through a guided wizard.
Prerequisites
- Supported region: The agent is available in Business Central environments for Australia, Canada, Germany, Denmark, Spain, France, the UK, Italy, New Zealand, and the United States.
- Dedicated mailbox: A Microsoft 365 mailbox ideally a shared mailbox must be set up solely to receive vendor invoice emails.
- Mailbox permissions: The activating user must have Read and Manage (Full Access) permission on the mailbox, delegated by an Exchange administrator.
- Billing setup: The agent uses Copilot Credits billed on a consumption basis. Consumption-based billing must be enabled in the Business Central Admin Centre before activation.
Activation Steps
- Select the Payables Agent icon from the Business Central navigation bar and choose Activate.
- In the configuration wizard, enable the Monitor incoming information toggle and set the designated mailbox.
- Configure review preferences whether supervisors must review incoming emails before drafting, and which additional fields from purchase history should be auto-populated on finalisation.
- Add agent supervisors by selecting Manage user access and assigning users.
- Turn on the Active toggle and select Update to complete setup.
Once active, the agent begins monitoring the mailbox immediately. The Payables Agent icon in the navigation bar updates to show the agent is live, and a red notification badge appears whenever tasks require supervisor attention.
Understanding the Limitations
As with any AI-powered tool, it is important to be clear about what the Payables Agent currently does and does not support, so you can design your AP process around its actual capabilities.
Feature Gaps in Current Release
- Purchase order matching: The agent creates standalone purchase invoices. It cannot automatically match incoming invoices against existing purchase orders this remains a manual step.
- Approval workflow automation: The agent queues invoices for approval, but it does not drive or manage the approval workflow itself.
- Anomaly and fraud detection: The agent does not flag duplicate invoices, unusually large amounts, or suspicious new vendor details. These checks remain the responsibility of the human supervisor.
Document and Volume Constraints
- File type: Only PDF attachments are processed. Emails without PDFs, or PDFs that are not recognised as invoices, are flagged for manual attention.
- Attachment limit per email: Emails with more than 10 attachments are skipped entirely.
- PDF page limit: PDFs with more than 10 pages are not processed.
- PDF file size limit: PDFs larger than 5 MB are not processed.
- Daily email limit: The agent processes a maximum of 100 emails per day.
- Daily invoice limit: The agent processes a maximum of 500 invoices per day.
For most small and mid-sized businesses these limits will rarely be reached. For higher-volume environments, it is worth planning your mailbox and vendor communication strategy accordingly.
The Business Case: What This Means for Your Finance Team
The productivity gains from automating invoice processing are tangible and measurable. At even 5 minutes saved per invoice, a team processing 100 invoices daily reclaims over 8 hours of capacity equivalent to a full-time team member every single working day. That time can be redirected toward cash flow forecasting, vendor relationship management, financial analysis, and the higher-value work that actually moves the business forward.
Beyond raw time savings, the Payables Agent addresses three other important dimensions of AP performance:
- Accuracy: By extracting data directly from the source document and applying consistent GL mapping rules, the agent eliminates the variability and human error that accumulates in a manual process. Every invoice is handled the same way, every time.
- Auditability: The agent creates a complete, traceable record for every invoice linking the original email and PDF to the draft, the draft to the final invoice, and recording the reasoning behind every field suggestion. This makes AP far more auditable than a purely manual workflow.
- Scalability: With manual processing, every increase in invoice volume requires proportional headcount growth. With the Payables Agent, your existing team handles significantly more volume and the system scales automatically as your business grows.
For businesses experiencing rapid growth, seasonal volume spikes, or simply looking to reduce operational risk in their financial processes, the Payables Agent represents a genuinely high-return investment of activation effort.
Best Practices for Getting the Most Out of the Agent
- Keep the monitored mailbox clean and dedicated: Use it strictly for vendor invoices. Do not share it with general AP correspondence or other communications the cleaner the mailbox, the more reliably the agent performs.
- Do not expose the mailbox directly to vendors: Have your team forward invoices rather than giving vendors the mailbox address directly. This adds a human review layer that helps catch fraudulent or incorrectly formatted invoices before they reach the agent.
- Start with well-known, high-volume vendors: In the first weeks, focus the agent on vendors with consistent invoice formats and a strong purchase history in Business Central. This builds team confidence in the agent’s output and helps calibrate the review process.
- Encourage supervisors to read field-level reasoning: The agent’s tips and explanations are there to build trust, not just inform. Supervisors who engage with the reasoning will catch systematic issues earlier and become much more comfortable with the agent over time.
- Keep vendor master data current: The agent’s vendor identification accuracy depends on the quality of your Business Central vendor records. Ensure names, addresses, and VAT numbers are accurate and deduplicated.
- Brief vendors on PDF formatting: Digital PDFs process significantly better than scanned images. Invoices should ideally be under 10 pages and under 5 MB. It is worth communicating these expectations to your key suppliers.
Final Thoughts
Microsoft’s Payables Agent is not a promise of future AI capability it is a production-ready tool available today in Business Central, designed to solve a problem that has frustrated finance teams for decades. By automating the most labour-intensive parts of invoice processing and doing so with the transparency and auditability that finance functions demand, it represents a genuinely meaningful step forward.
The agent will not replace your AP team. It will not make judgement calls about vendor approval, resolve payment disputes, or manage supplier relationships. What it will do is take the relentless grind of manual invoice keying off your team’s plate and free them to focus on the work that actually requires human insight, expertise, and judgement.
For organisations running Business Central who are dealing with growing invoice volumes, stretched AP teams, or simply looking to build a more scalable, accurate, and auditable financial process, the Payables Agent is worth serious consideration. Setup is lightweight, the return is measurable from day one, and as Microsoft continues to add capabilities including configurable review steps, expanded language support, and eventual anomaly detection the value will only grow.