Dynamics 365 Business Central AP Automation: Native AP, the Payables Agent, and the Gap

Dynamics 365 Business Central AP automation starts with a system that already does a lot. Business Central runs vendor records, purchase invoices, and the payment journal natively, posts to the GL against financial dimensions, and reconciles bank activity through the payment reconciliation journal. As of the 2025 release waves, it also ships an AI Payables Agent that reads emailed invoices and preps them for approval. So why do most Business Central shops still bolt something on? Because native BC plus the Payables Agent stops at structured invoices and BC-internal posting. It doesn't run managed supplier payments, configurable line-level matching, or virtual-card rebate income written back to the BC general ledger.

If you're running Business Central, the question isn't whether it does AP. It clearly does. The real question, once the Payables Agent shipped, is narrower and sharper. The Agent handles capture and prep, so where exactly does native BC stop, and what do you still have to add? That line is what this covers, along with how the pieces fit back into your BC dimensions without re-keying.

Key Takeaways

• Business Central handles core AP natively, covering vendor cards, purchase invoices, payment journals, the payment reconciliation journal, and GL posting against financial dimensions. Most BC shops are automating an edge, not building AP from scratch.

• The native Payables Agent (2025 release waves) captures emailed invoices, runs OCR through Azure Document Intelligence, categorizes from purchase history, and preps purchase invoices for human-reviewed approval; it stops at structured, email-captured documents and BC-internal posting.

• The gaps that justify a third-party layer are specific: long-tail exception capture at scale, configurable line-level three-way matching, managed supplier-payment execution, and virtual-card rebate income posted back to the BC GL.

• A Built-for-Business-Central integration syncs vendor master, POs, and financial dimensions outbound and writes approved invoices, payments, and virtual-card settlements back inbound, so dimension-aware coding survives without re-entry.

• Routing eligible supplier payments through virtual card turns a slice of AP spend into rebate income that posts to a BC GL account as a dimensional line, which is the difference between AP as a cost center and AP as a funded operation.

What does Business Central do for accounts payable natively?

Business Central handles the accounting core of accounts payable on its own, and it does it well. You set up a vendor card for each supplier, record purchase invoices against it, run the payment journal to pay them, and post everything to the general ledger against your financial dimensions and, where you use it, the project accounting module. For a smaller company with clean, PO-backed spend and a disciplined AP clerk, that's frequently enough to run payables without any add-on at all.

The strength is structured data that originates inside BC. A purchase order created in Business Central, received against a warehouse document in Business Central, and invoiced against a vendor already on file moves through the native flow with little friction. The native workflow covers the parts of AP an ERP was built for:

• Vendor cards holding remit-to details, payment terms, and the default dimensions that drive coding.

• Purchase invoices and purchase orders, with posting that respects your dimension and G/L account structure.

• Approval workflows routed by amount, vendor, or dimension through the built-in approval engine.

• The payment journal for suggesting and posting vendor payments across bank, check, and electronic methods.

• The payment reconciliation journal for matching bank statement lines back to open entries.

Where the native module strains is the same place every ERP strains: the moment an invoice arrives as a PDF in someone's inbox, as a scanned paper document, or from a vendor whose banking details changed last quarter. None of those originate as structured BC data, and someone has to key them. That is the edge the Payables Agent and, past it, a third-party layer are built to handle.

How do the Business Central payment journal and payment reconciliation journal work?

The payment journal is where Business Central proposes and posts what you owe, and the payment reconciliation journal is where you tie the resulting bank activity back to open entries. In the payment journal, you run Suggest Vendor Payments to pull open purchase invoices due within a date range and under whatever priority and available-balance rules you set, then post the batch to generate check, ACH, or electronic payments. Applied entries close against the vendor ledger so the aging is accurate the moment the batch posts.

The payment reconciliation journal is the other half of the loop. You import a bank statement feed, and BC attempts to match each statement line to an open customer or vendor entry using amount, document number, and text-matching rules you can tune. Lines it can't match automatically get handled by hand, and once everything reconciles, posting the journal updates both the bank ledger and the general ledger in one step. It's a genuinely useful native tool for a modest volume of clean bank activity. At higher volume, or when remittance detail is thin, the manual-match residue grows, which is one of the practical reasons teams start looking past the native payment flow.

What is the accounts payable process step by step in Business Central?

The native BC accounts payable process runs in a predictable sequence. You receive the invoice and record it against a vendor and PO, route it for approval, then post, pay, and reconcile. Concretely, an invoice comes in, an AP clerk creates or opens the matching purchase invoice, codes it to the right G/L account and dimensions (or lets the vendor card defaults carry), sends it through the approval workflow, posts it once approved, and later pays it through the payment journal. The accounts payable process, laid out step by step, is the same discipline regardless of which system runs it, and Business Central enforces it against your chart of accounts and dimension structure.

The part BC doesn't do in that sequence is the front of it. Getting the invoice off the page and into a purchase invoice, which means reading the vendor and amounts along with the line detail and PO reference, is manual in vanilla Business Central. That's the specific step the Payables Agent was built to remove, and it's worth understanding exactly how far it goes.

What is the Payables Agent in Business Central, and where does it stop?

The Payables Agent is Microsoft's native AI agent in Business Central that captures vendor invoices from email, extracts their data with OCR, categorizes them from your purchase history, and prepares purchase invoices for human-reviewed approval. It shipped through the Dynamics 365 Business Central 2025 release waves and runs on Copilot, so it's first-party, with no third-party app and no external connector. For a BC shop that has been keying invoices by hand, it's a real step forward on the capture-and-prep stage of AP.

According to Microsoft Learn's Dynamics 365 Business Central 2025 release wave plans, the Agent captures vendor invoices from Microsoft 365 email, extracts data via OCR through Azure Document Intelligence, categorizes expenses from purchase history and accounting policies, and prepares purchase invoices for human-reviewed approval, with each document creating an entry in the Inbound E-Documents table for a full audit trail. That audit-trail detail matters, because every captured document is traceable, which is exactly what a controller wants before letting AI touch the ledger.

What can the native Payables Agent automate today?

The Agent automates the capture-through-prep stretch of AP, and the 2025 wave 2 update sharpened how it prioritizes work. Today it handles:

1. Email capture: it reads vendor invoices arriving in a monitored Microsoft 365 mailbox.

2. OCR extraction: it pulls header and line data using Azure Document Intelligence.

3. History-based categorization: it suggests coding from your purchase history and accounting policies.

4. Approval preparation: it assembles a draft purchase invoice for a human to review and approve.

5. Confidence-based prioritization: per Microsoft Learn's 2025 release wave 2 plan, it attaches a confidence score and a reason to each AI suggestion so reviewers work the low-confidence items first.

6. Audit logging: each document lands in the Inbound E-Documents table for traceability.

The 2025 wave 2 plan also expanded the Agent's availability to Canada, Denmark, Germany, and Spain, alongside its earlier markets, which tells you Microsoft is investing in it as a durable part of the product rather than a one-off preview. If your invoice mix is mostly clean PDFs hitting an inbox, the Agent removes a lot of keystrokes.

Where does native Business Central plus the Payables Agent fall short?

Native BC plus the Payables Agent stops at structured, email-captured invoices and BC-internal posting. It doesn't execute managed supplier payments, match at the line level across tolerances, or generate rebate income. The gaps line up in a consistent order once volume and vendor variety climb:

1. Long-tail capture at scale. The Agent is built around email. Invoices that arrive by EDI, through a supplier portal, or as messy scanned paper, plus the exception cases where OCR confidence is low, still fall to manual handling. A G2 reviewer of one competing tool described exactly this residue as gaps in invoice OCR when PO numbers are missing. That's the long tail no email-first agent fully clears.

2. Configurable line-level three-way matching. Native BC and the Agent prepare and post invoices, but matching an invoice to its PO and receipt line by line, across quantity and price tolerances you define, isn't what they're built to do.

3. Managed supplier-payment execution. The payment journal posts payments; it doesn't enroll a check-only vendor onto electronic payment, chase remittance confirmations, or own the supplier relationship through a payment run.

4. Virtual-card payment delivery. There's no native mechanism to route eligible supplier payments through a single-use virtual card, which is the instrument that generates rebate.

5. Rebate income written back to the BC GL. Because there's no card-payment layer, there's no rebate, and nothing to post back as a dimensional GL line. This is the gap no native tool touches, and it's the one with the clearest dollar consequence.

None of these are defects in Business Central. They're last-mile tasks an ERP was never designed to own. The point of adding a layer on top is to close exactly this set without disturbing BC as the system of record underneath.

How does Corpay AP automation integrate with Business Central?

Corpay AP Automation connects to Business Central as a Built-for-BC extension with a real-time, bidirectional API, so master data flows out of BC and approved transactions flow back in without re-entry. Corpay complements Business Central rather than replacing it. BC stays the system of record, and the integration adds AI-OCR on the exceptions the Agent leaves, configurable matching, managed payment, and rebate write-back. Getting the architecture right is what separates a live integration from an overnight CSV dump, so it's worth being specific about how the sync behaves.

The design mirrors how disciplined invoice processing automation is supposed to work: capture once, code once, post once, with the data landing in the right place on the first pass. Sibling ERP shops hit the identical wall and solve it the same way, which is why the pattern looks familiar whether you're running BC, Acumatica AP through an integration, or Sage Intacct AP automation. The ERP holds the ledger; the integration closes the capture-to-payment gap.

Is Corpay built for Business Central, and how does the sync model work?

Corpay installs as a managed Business Central extension and syncs bidirectionally. Vendor master, purchase orders, and financial dimensions flow outbound; AP invoices, payments, and virtual-card settlements flow back inbound. Because it's built for BC rather than bolted alongside it, the extension is designed to survive Business Central's release cadence, so the 2026 Wave 1 and Wave 2 updates don't break the connection the way a brittle custom integration might.

On controls, the integration is meant to strengthen the segregation of duties BC already supports, not weaken it. Approvals stay governed by your workflow, payment batches get reviewed before release, and validated vendor banking guards the remit details, which is the exact seam most accounts payable fraud exploits: a changed bank account on a legitimate-looking invoice. Keeping BC as the system of record while the payment layer enforces batch review is a cleaner control posture than moving money out of an uncontrolled queue.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper

How do financial dimensions and project accounting sync?

Financial dimensions and project accounting sync so that an approved invoice posts to the correct BC dimension and project combination without anyone re-keying the coding. Business Central runs coding through dimensions (department, cost center, project, whatever structure you've built), and the integration reads that structure outbound, applies dimension-aware coding on capture, and writes the posted invoice back inbound already coded. A reviewer of one competing tool described the pain this removes as manual entry challenges due to syncing issues, leading to confusion and inefficiencies. Dimension-aware sync is the antidote, because the code the AP team would have keyed is already right when the invoice lands back in BC.

For project-driven businesses, the project accounting tie matters more than it sounds. If a supplier invoice needs to hit a specific job and task, and that allocation is wrong, it distorts job costing for the life of the project. Reading BC's dimension and project setup and honoring it on the way back in is what keeps job costing clean at volume.

How does the BC AP team experience it on day one?

On day one, the visible change is that manual entry disappears for structured invoices and coding disappears for known vendors, while exception review and over-threshold approvals stay with the team. The AP clerk who used to key every PDF now reviews drafts the system assembled, works the low-confidence exceptions first, and releases approved batches. The controller sees a payment batch to review before anything leaves the bank, not a pile of individual check runs.

What the AP team does on day one is exception handling and approval, which is the work that actually needs a human. Onboarding runs against named go-live milestones, including vendor-master validation, dimension mapping, and a first live payment run, so the team knows what "done" looks like at each step rather than waiting for a vague cutover. The managed side of the service means someone owns supplier enrollment during that window, not the AP clerk squeezing it between invoice runs.

How does BC native plus the Payables Agent compare to BC plus Corpay?

Here's the capability-by-capability comparison, because side by side is the cleanest way to see where native BC ends and the added layer begins. The left column is Business Central with the native Payables Agent; the right is Business Central with Corpay's integration on top. BC remains the system of record in both.

Sources: Microsoft Learn, Dynamics 365 Business Central 2025 release wave plans; Corpay product documentation, 2025; Ardent Partners, "The State of ePayables 2025."

The pattern the table makes obvious is that native BC plus the Agent owns capture and prep, and everything from matching through payment and rebate is where the added layer earns its place. A team happy with its current payment process and not chasing rebate may find native plus the Agent enough. A team that wants end-to-end AP, with payment economics attached, needs the layer on the right.

How do virtual-card rebates work inside a Business Central environment?

Virtual-card rebates work by routing eligible supplier payments through a single-use card, earning interchange-funded rebate on that spend, and posting the rebate back to a Business Central GL account as a dimensional line. It's the one capability absent across every native BC tool and most of the point vendors, and it's the difference between AP running as a pure cost and AP funding a slice of its own operation. The mechanics are worth walking through, because the economics only work if the supplier side is handled well.

There's a real fear here that deserves a direct answer. The rebate opportunity is genuine, but chasing it clumsily strains vendor relationships, and pushing suppliers onto card terms they didn't want is a fast way to sour a payment relationship. The way this stays healthy is supplier-friendly enablement, not coercion. Suppliers who already accept cards, or who benefit from faster payment, opt into terms that work for them. Managed supplier-payment automation means the enrollment conversation is handled with care rather than dumped on an AP clerk with a quota.

Which suppliers are eligible for virtual-card payment?

The eligible suppliers are the ones who accept card payments or stand to gain from earlier settlement, and finding them is a data exercise, not a guessing game. Against a large accepting-vendor network, a meaningful share of a typical AP file already takes card, and those are the immediate candidates. Others convert because the trade is fair, getting paid faster and more predictably in exchange for accepting card terms. The corporate appetite for this is not small. According to RPMG Research and Mastercard's 2022 Virtual Card Benchmark Survey, corporate virtual-card spending grew from $221 billion in 2019 to $314 billion in 2021, a 42% increase over two years. That's a lot of AP spend that moved onto card because the economics penciled out for both sides.

It also displaces the payment method most exposed to fraud. According to the Association for Financial Professionals' 2024 Payments Fraud and Control Survey, checks remain the payment type most targeted by fraud, affecting roughly two-thirds of organizations. Every supplier moved from check to virtual card is one fewer static account number floating through the mail.

How does the rebate post back to the Business Central GL?

The rebate posts back to Business Central as a GL entry coded to the dimensions you choose, so rebate income shows up in your ledger as real, reportable revenue rather than a statement credit you have to chase. When a virtual-card payment settles, the interchange-funded rebate is calculated on that spend, and the integration writes it inbound to a designated BC G/L account with the appropriate dimension tags. That means finance can see rebate by department, entity, or whatever dimension structure matters, and it reconciles inside BC like any other posted transaction.

This is the write-back that turns the whole exercise from a soft "you'll save on processing" pitch into a line a controller can point to at month-end. It offsets per-transaction AP cost directly, and because it's dimensional, it's attributable, so you know which part of the business generated it.

Automate AP end to end

Replace manual approvals, check runs, and reconciliation with a single automated workflow that syncs to your ERP — so your AP team spends time on strategy, not paperwork.

Explore AP Automation

How long does it take to implement AP automation in Business Central?

Most Business Central shops go live with AP automation in a matter of weeks, not the multi-quarter slog buyers brace for, because the heavy lifting is data hygiene rather than custom build. As a Built-for-BC extension, the install itself is lightweight, an AppSource-model deployment rather than a bespoke integration project. The real work is preparation: cleaning up the vendor master, validating remit-to and banking details, and confirming that your dimension structure maps cleanly.

There's a well-earned skepticism to address here. AP teams have heard "this will save you time" and then watched a tool create more work than it removed. The disillusionment shows up constantly in practitioner forums, where the complaint is that AP automation promises magic and delivers more manual exception-chasing. The honest answer is that the tools that disappoint are usually the ones with a thin integration and no managed layer, so the AP team inherits the enrollment and exception work the vendor should have owned. A faithful implementation names its milestones and owns supplier enablement, which is what keeps the timeline real. When you're testing any option, the criteria worth pressing on in an AP automation RFP, like integration depth, capture accuracy, and who owns enrollment, are the ones that predict whether go-live holds up.

The economics reward getting it right. According to Ardent Partners' "The State of ePayables 2025," the fastest AP teams process an invoice for $2.78 in 3.1 days, against $12.88 and 17.4 days for typical performers, and run at roughly 79% lower invoice-processing cost. That spread is the size of the prize for a BC shop that closes the capture-to-payment gap, and it's why the working-capital math around cash flow and AP automation tends to justify the project on its own.

Automate Business Central accounts payable with Corpay

Corpay AP Automation extends Business Central end to end. It adds AI-OCR capture on the exceptions the Payables Agent leaves, dimension-aware coding, configurable line-level matching, and a managed virtual-card, ACH, check, and wire payment service with supplier enablement and rebate income written back to your BC GL. It installs as a Built-for-Business-Central extension and syncs bidirectionally with your G/L accounts, financial dimensions, and project accounting, so approved invoices and payments post back without re-entry and BC stays the system of record.

The reason this matters to a finance leader is the shape of the outcome. You move from an AP function that costs money to run toward one that funds part of its own operation, with per-invoice cost dropping toward the low single digits and cycle time compressing to a handful of days once the full chain is automated. Corpay processes payments for more than 800,000 businesses and is the number one commercial Mastercard issuer in North America, which is the scale that makes supplier enrollment and rebate capture work at volume. See how Corpay's Microsoft Dynamics integration connects to Business Central, explore the broader Corpay AP Automation platform, or review how the full set of AP automation integrations fits the rest of your stack.

If you're running Finance & Operations rather than Business Central, the decision looks different, and our Dynamics 365 AP automation comparison walks through Business Central against Finance & Operations native limits in full.

Frequently Asked Questions

Does Business Central have AP automation built in?

Yes, partly. Business Central runs core AP natively, covering vendor cards and purchase invoices, payment journals, and GL posting, and since the 2025 release waves it includes an AI Payables Agent that captures emailed invoices, runs OCR, categorizes from history, and preps invoices for approval. It stops at structured capture and BC-internal posting, so many teams add a layer for matching, managed payment, and rebate.

What is the accounts payable agent in Business Central?

The accounts payable agent is Microsoft's native AI agent in Business Central that captures vendor invoices from Microsoft 365 email, extracts data via OCR through Azure Document Intelligence, categorizes expenses from purchase history and accounting policies, and prepares purchase invoices for human-reviewed approval. Each document creates an entry in the Inbound E-Documents table for audit purposes, and it runs on Copilot as a first-party capability.

What does native Business Central AP not do?

Native Business Central AP, even with the Payables Agent, doesn't capture long-tail exception invoices at scale, match at the line level across configurable tolerances, execute managed supplier payments with enrollment, or generate virtual-card rebate income posted back to the GL. Those are the last-mile tasks a Built-for-BC integration adds on top of the native module.

Is Corpay built for Business Central?

Yes. Corpay installs as a Built-for-Business-Central extension and connects through a real-time, bidirectional API that syncs vendor master, purchase orders, and financial dimensions outbound and writes AP invoices, payments, and virtual-card settlements back inbound. Business Central remains the system of record, and the integration is designed to survive BC's release-wave cadence.

What are three-way accounts payable, or three-way matching?

Three-way matching validates a vendor invoice against its purchase order and its receipt before payment, confirming that what was ordered, what arrived, and what was billed all agree. Business Central supports the pieces natively, and a Built-for-BC integration adds configurable line-level matching across quantity and price tolerances so exceptions surface automatically rather than through manual report checks. The mechanics of three-way matching are the same discipline whichever system enforces them.

How does the Business Central payment journal work?

The Business Central payment journal proposes and posts vendor payments. You run Suggest Vendor Payments to pull open invoices due within a date range under your priority and balance rules, then post the batch to generate check, ACH, or electronic payments. Applied entries close against the vendor ledger, and the payment reconciliation journal later matches the resulting bank statement lines back to open entries.

How much does Business Central AP automation cost?

Business Central AP automation cost has two parts. The native Payables Agent runs on consumption-based Copilot billing, while a third-party layer carries a license plus implementation. The number that reframes the question is rebate, because routing eligible supplier payments through virtual card generates interchange-funded income that posts back to your BC GL and offsets the gross cost, so the net can look very different from the sticker.

How long does Business Central AP automation take to implement?

Most Business Central shops implement AP automation in weeks, because a Built-for-BC extension installs through the AppSource model rather than a custom build. The main preparation is vendor-master cleanup and dimension validation, and naming go-live milestones such as vendor validation, dimension mapping, and a first live payment run keeps the timeline honest and the AP team clear on what's next.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

Payments Automation

AP Automation