The Payables Agent Is What AP Automation Was Supposed to Be 10 Years Ago 

A reality check for mid-market manufacturing and distribution finance teams. 

Business Central AP automation has been a focus for finance teams for more than a decade. For many manufacturing and distribution organizations, traditional automation tools never fully delivered. Invoice processing remained manual, exceptions piled up, and AP teams continued to carry the operational burden.

The Payables Agent that went live in the Microsoft 2025 Wave 2 release, and that expands in the 2026 Wave 1 release landing now, is the first version of AP automation that is structurally different. It is not better OCR. It is an AI agent that works your AP inbox the way a clerk would, with confidence scoring, human-in-the-loop exceptions, and a native audit trail. For mid-market finance teams, especially in manufacturing and distribution where invoice volume and vendor variance are high, this is the moment to reopen the AP roadmap conversation. 

Why the last wave of AP automation stalled 

The pitch in 2015 was the same as the pitch in 2025: capture invoices automatically, extract the data, eliminate typing. 

What actually happened in most shops is a story your controller can probably tell in one breath: 

• OCR accuracy was good for the top 20 vendors and bad for the long tail. 
• Exception handling was a separate queue that AP clerks still worked manually. 
• The invoice capture vendor, the AP automation platform, and the ERP each used a different data model. Somebody had to reconcile them. 
• When a vendor changed their invoice layout, the OCR template broke. AP staff absorbed the rework. 

For a distributor running 1,500 invoices a month across 400 vendors, the math never quite worked. The savings from automating the top 20 vendors did not cover the implementation and the ongoing cost of managing the long tail. Many manufacturers abandoned or never fully deployed the automation they paid for. That is the context the 2026 Payables Agent is landing into. Your CFO is not starting from zero. She is starting from scar tissue. 

What’s Structurally Different About Business Central AP Automation 

An agent is not a workflow. It is a worker. 

The Payables Agent runs in the background on a dedicated AP mailbox. When an invoice PDF arrives, it does six things in sequence: 

1. Extracts data using Azure Document Intelligence. 
2. Identifies the vendor against your existing vendor master. 
3. Proposes a draft purchase invoice with line items and GL coding. 
4. Assigns a confidence score. 
5. Surfaces low-confidence cases to a human supervisor. 
6. Flags unknown document types separately for review. 

The shift is in steps 4 and 5. The agent knows what it does not know. When confidence is high, it creates the draft and routes for approval. When confidence is low, it hands the email to a supervisor and waits. It does not guess and hope. It does not silently miscategorize. It works until it cannot, then it asks. 

This is the governance model that prior OCR-based automation could not offer. The agent runs inside the ERP with the same permissions and profile as a user. Its actions are logged. Its drafts are reviewed before posting. The audit trail stays intact because the work happens in the ERP, not in an adjacent system that someone has to reconcile later. 

For a walkthrough of how this looks in practice, watch the Payables Agent demo here:

Business Central AP Automation in a Real AP Workflow

Here is what this looks like in a real AP queue. This is where Business Central AP automation starts to show measurable impact at scale.

A regional distributor processing 1,500 vendor invoices a month currently has three AP clerks. Two of them spend most of their week keying invoices from freight carriers, packaging suppliers, and product vendors. The third manages approvals and exceptions. Monthly cost per invoice is in the $12 to $18 range, consistent with APQC benchmarks for this volume. 

With the Payables Agent running, the inbound pattern changes. Invoices land in a dedicated mailbox. The agent drafts most of them automatically. The AP team reviews drafts in batch, works exceptions, and handles the vendors the agent flagged. The work does not disappear. It concentrates on judgment and exception handling, which is the work AP clerks were always best at and had the least time for. 

What does not change: vendor relationships, PO matching discipline, approval authority thresholds, the controller’s sign-off on new vendor creation. The agent enforces these. It does not replace them. 

What it costs, what it saves, and what the tradeoffs are 

Nothing in here is free. A few things CFOs should know going in. 

The agent uses consumption-based Copilot Credits. Cost scales with invoice volume and complexity. A pilot quantifies this before you scale, and billing is set up at the environment level. You should know your monthly AP volume and complexity mix before you model the cost. 

Setup is not trivial. It requires a dedicated AP mailbox with ownership assigned to the ERP, Inbound E-Documents enabled, vendor approval workflows configured, and supervisor roles assigned. Governance effort is front-loaded, not eliminated. 

Real limitations apply today. The agent processes PDFs only, up to 10 pages, up to 5 MB, up to 10 attachments per email, up to 100 emails per day. For most mid-market shops these are non-issues. For the few shops still receiving scanned paper invoices, XML EDI feeds, or very high volume, additional plumbing is needed before the agent carries its share of the load. 

This is not set and forget. Organizations that commit to measuring cycle time, cost per invoice, error rate, exception volume, and early payment discount capture before and after deployment are the ones that see real ROI. Organizations that turn it on and walk away get the same mediocre result the last generation of AP automation produced. 

Where to Start with Business Central AP Automation

Before implementing Business Central AP automation, finance teams need a clear view of where friction exists today. The honest starting point is not a platform decision, it is a diagnostic. 

Before you evaluate the Payables Agent, evaluate your current AP friction. What percentage of your invoices come from your top 20 vendors? What is your current cost per invoice? Where are your exceptions actually concentrated? How many early payment discounts did you leave on the table last quarter? 

These numbers tell you whether agent-based AP automation is a year-one ROI move, a year-two nice-to-have, or a year-three infrastructure bet. They also tell you what to pilot first. A shop with high volume and a clean vendor master is a different pilot than a shop with lower volume and a messy vendor master. 

This diagnostic work is the first thing we do in a Crestwood Business Optimization Assessment. No platform recommendation until the friction is mapped. 

Why Crestwood 

Crestwood Associates has delivered more than 5,000 ERP implementations in 27 years, with deep bench strength across Microsoft Dynamics 365 Business Central and Acumatica. The Payables Agent is one of the new Copilot and AI agent capabilities inside Business Central, and our team is already configuring and deploying it for manufacturing and distribution clients in production. 

For a deeper walkthrough of how AI agents in Business Central actually work, including a live Payables Agent demo, watch our webinar with Stephanie McColly and Jason McColly here: https://youtu.be/PBonuyndHiI. 

If AP is one of your operational friction points, we help you see it clearly before we help you solve it. 

Get Your Free ERP Assessment | Explore Our Services | Learn More About Crestwood

Connect With Us: X | LinkedIn | Contact Us
More Resources: Acumatica ERP | Business Central | Blog Home 

© 2025 Crestwood Associates. All rights reserved.