Dynamics 365 AP Automation: Business Central vs. Finance & Operations Native Limits

Dynamics 365 AP automation isn't one decision. It's two, because Microsoft Dynamics 365 is two architecturally distinct ERPs that share a brand. Business Central is the SMB-tilted accounting and ERP successor to NAV and GP, and it now ships with a native AI-powered Payables Agent introduced in the 2025 Wave 1 release, billed on consumption-based Copilot Credits. Finance & Operations is the enterprise ERP built for multi-legal-entity, multi-currency consolidation and deep requisition management. Neither flavor delivers AI-OCR invoice capture from unstructured PDFs at enterprise scale, line-level three-way matching across legal entities, or virtual-card rebate write-back to the general ledger out of the box. The first question any Dynamics AP buyer should ask is which Dynamics they're running, because the native AP capabilities, the gaps, and the third-party SuiteApp that closes them all differ by flavor.

That distinction is where the decision splits. A buyer on Business Central is comparing the new Payables Agent against a third-party SuiteApp. A buyer on Finance & Operations is comparing Built-for-F&O extensions against file-based integrations and weighing multi-entity AP queues. Treating "Dynamics" as one product answers neither buyer cleanly, so the two tracks are worth working through separately.

Key Takeaways

• Dynamics 365 is two ERPs, not one: Business Central for SMB and lower mid-market, Finance & Operations for the enterprise, and the AP automation path differs by which you run.

• Business Central now ships a native Payables Agent that reads invoices, matches vendors and accounts, and prepares invoices for approval, billed on consumption-based Copilot Credits.

• Finance & Operations handles multi-legal-entity AP, requisition management, and multi-currency consolidation natively, but not enterprise-scale AI capture, cross-entity matching, or rebate write-back.

• A third-party SuiteApp adds AI-OCR capture, configurable cross-entity matching, multi-rail payment with managed supplier enablement, and virtual-card rebate write-back that neither flavor delivers out of the box.

• For Business Central, Corpay connects through the AppSource SuiteApp model; for Finance & Operations, Corpay delivers F&O-native automation through its May 2026 partnership with Dooap.

• Top-performing AP teams process an invoice for $2.78 against $12.88 for typical performers, according to Ardent Partners' 2025 State of ePayables, so the economics of closing the gap are well documented.

What is the difference between Dynamics 365 Business Central and Finance & Operations for AP?

The difference is that they're two separate ERPs aimed at different company sizes, and the AP automation path follows from which one you run. Business Central is the smaller-company product, subscription-priced per user and built on an AppSource SuiteApp model, with lineage tracing back to Dynamics NAV and GP. Finance & Operations is the enterprise product, deployed at tenant scale with multi-legal-entity consolidation, advanced cost accounting, and sophisticated multi-currency posting. Both handle the general ledger, AP, AR, and bank reconciliation natively. They diverge sharply on depth, and that divergence is the whole reason the AP automation decision is different for each. If you need to ground the conversation in what an ERP does and doesn't handle before deciding what to bolt onto it, our explainer on what an ERP is frames the boundary.

This split matters because cost pressure on finance is real and current. More than half of surveyed CFOs say their CEOs have asked them to focus on managing and reducing costs, according to Deloitte's CFO Signals 1Q26. AP is one of the most visible places that pressure lands, and the answer depends entirely on which Dynamics the team is sitting on.

What is Business Central's native AP module and the new Payables Agent?

Business Central handles core AP natively, and in its 2025 Wave 1 release Microsoft added a Payables Agent that automates much of the front end with AI. Out of the box, Business Central manages vendor records, manual invoice entry, basic approval workflow, and GL posting. The Payables Agent extends that by reading invoices, matching them to vendors and accounts, and preparing them for approval with human oversight, learning from each invoice posted, according to Microsoft Learn's 2025 Wave 1 release plan for the Payables Agent. It is generally available across the US, UK, Canada, and Australia, and billed on consumption-based Copilot Credits rather than a flat seat fee.

For a smaller AP team, the agent is a genuine step forward. It removes a meaningful chunk of keying and coding on the structured invoice path. What it does not do is execute multi-rail payments, enable suppliers for card acceptance, or write virtual-card rebate income back to the ledger. It also stays scoped to Business Central, which means it doesn't reach the multi-entity or managed-payment problems that push larger teams toward a third-party layer. The agent is a capture-and-prepare tool, not an end-to-end AP operation, and that boundary is the one buyers most often misread.

What does Finance & Operations native AP cover?

Finance & Operations covers enterprise AP natively, and it goes deep. The native module handles a set of capabilities that a Business Central shop simply doesn't get out of the box:

• Full requisition management and a vendor collaboration portal

• Multi-legal-entity AP with intercompany handling

• Advanced approval workflows built on Power Automate

• Posting against multi-dimensional analytical accounting with sophisticated multi-currency support

This is genuinely strong on the accounting and control side, which is exactly why large organizations standardize on it. The native AP in F&O is closer to a complete enterprise ledger discipline than Business Central's, and a buyer evaluating it should not underrate what Microsoft ships.

Where F&O stops is on the capture and payment edges rather than the core ledger. It doesn't do AI-OCR capture from unstructured PDF and email invoices at scale, it doesn't run configurable line-level three-way matching across legal entities with tolerance rules, and it doesn't manage supplier enablement for card payments or post rebate income back to the GL. Those are the gaps a Built-for-F&O SuiteApp exists to fill. Understanding the accounts payable process end to end makes it clear why the gap sits where it does. The ledger is solved, but the messy middle between an invoice arriving and a payment clearing is not.

Where do Business Central native, the Payables Agent, and F&O native all stop?

Both flavors stop at the same five places, even with the Payables Agent running in Business Central. These are the gaps a third-party SuiteApp closes, and they hold whether you're on the SMB product or the enterprise one.

• Unstructured PDF capture at scale. Both flavors handle the structured invoice path well. Long-tail PDF, EDI, and email invoices with non-standard layouts remain manual exceptions, and exceptions are where AP teams lose their hours.

• Automated GL coding from supplier-specific historical patterns. The Payables Agent learns vendor and account combinations within Business Central. F&O native coding rules require manual configuration and don't learn from supplier-specific history the same way.

• Line-level three-way matching across legal entities. F&O can match within a single entity. Cross-entity matching and configurable tolerance rules are a SuiteApp concern, and getting three-way matching right at line level is what keeps overpayments and duplicate invoices out of the run.

• Managed virtual-card payment delivery with supplier enablement. Both flavors execute check, ACH, and wire natively. Onboarding suppliers to accept virtual card is a managed-service problem, not an ERP feature, and it's the part that determines how much card spend a program can capture.

• Rebate-revenue write-back to the Dynamics GL. Neither flavor posts virtual-card interchange rebate income back as a separate GL line. Without that write-back, the rebate either goes uncaptured or sits outside the financial statements where finance can't see it.

That list is the same for an SMB Business Central shop and a multi-entity F&O enterprise. What changes is how a SuiteApp plugs in to close it, which is the next decision.

How does Corpay automate AP on Business Central?

Corpay integrates with Business Central through the AppSource SuiteApp model, adding AI-OCR capture and configurable approvals on top of the native module and the Payables Agent, then layering on multi-rail payment and rebate write-back. The integration is built to match how Business Central is delivered and updated, which is the difference between a managed extension and a brittle file drop. A Business Central buyer who already has the Payables Agent isn't replacing it; they're extending past where it stops.

Is Corpay built for Business Central as an AppSource SuiteApp?

Corpay connects to Business Central as a SuiteApp installed through Microsoft AppSource, which means it runs as a managed Business Central extension rather than a side-channel integration. That posture has a practical payoff. The extension is built to survive Business Central's release cadence, including the 2026 Wave 1 and Wave 2 updates, so an upgrade to the base ERP doesn't break the AP layer. The sync is bidirectional. Vendor master records, purchase orders, and financial dimensions flow outbound from Business Central, and approved AP invoices, payment records, and virtual-card settlements flow back inbound. For a buyer who lived through a file-based integration that broke on every ERP patch, the AppSource-certified path is the part that reduces the ongoing maintenance tax.

How does Corpay compare with the native Payables Agent in Business Central?

The Payables Agent and a Corpay SuiteApp solve different stretches of the same workflow, and the honest comparison is capability by capability. The agent reads invoices, matches vendors, and prepares them for approval inside Business Central, billed on consumption. Corpay layers on deeper AI-OCR for unstructured invoices, automated GL coding tied to the multi-dimensional Business Central structure, and a managed-payment service that handles supplier enablement and posts virtual-card rebate income back to the ledger. The deciding question is scope. If the goal is faster invoice prep on the structured path, the agent may be enough on its own.

The moment the goal becomes end-to-end AP, including multi-rail payment, supplier enablement, and rebate revenue, that's the line where a third-party SuiteApp earns its place. Our AP automation RFP guide lays out the criteria to test either way before committing.

How does the Business Central AP team experience the integration on day one?

On day one, the routine work changes more than the team's role does. Manual invoice entry disappears for structured invoices. Manual coding disappears for vendors the system has already seen and learned. What stays with the AP team is the judgment work, which means vendor management, exception review on the invoices that don't match cleanly, and approvals on transactions over the configured thresholds. That division addresses a complaint that comes up constantly among AP teams evaluating automation, that "AP automation gives us more work not less." It only gives more work when the tool automates the easy invoices and dumps the hard exceptions back without structure. A managed layer is built so the exceptions arrive triaged, not raw.

Pairing the SuiteApp with disciplined invoice processing automation is what turns the native module into an actual end-to-end workflow rather than a faster front end with the same back-end pile.

How does Corpay automate AP on Dynamics 365 Finance & Operations?

For Finance & Operations, Corpay delivers AP automation through its May 2026 partnership with Dooap, pairing F&O-native invoice automation with Corpay's managed-payment and rebate layer. This is the load-bearing answer for enterprise Dynamics buyers, because F&O's depth means a generic, single-integration tool tends to fight the ERP rather than extend it. The partnership is structured so each side does what it's built for. Dooap handles capture, approval, and processing inside the F&O user experience, while Corpay handles supplier enablement, payment execution, and rebate write-back.

What is the Corpay and Dooap partnership for Finance & Operations?

Corpay and Dooap announced a partnership in May 2026 to deliver integrated AP automation and vendor payments for Microsoft Dynamics 365 Finance & Operations, according to the Corpay and Dooap partnership announcement. Dooap builds AI-powered AP automation purpose-built for F&O, so invoice capture, approval, and processing all happen natively inside the F&O UX rather than in a bolted-on portal. Corpay contributes the managed-payment service: supplier enablement, virtual-card and multi-rail payment execution, and rebate income posted back to the F&O ledger. The combined solution lives in AppSource as an F&O-native managed extension, which is the same certification posture as the Business Central path, applied to the enterprise product. AvidXchange, by contrast, supports F&O through a file-based integration rather than a native extension, and that architectural difference is exactly what an enterprise buyer should probe during evaluation.

What syncs from F&O to Corpay and Dooap, and what syncs back?

The sync is bidirectional and dimension-aware, which is what keeps a multi-entity ledger clean. What moves outbound from F&O is the context the AP layer needs to code and match against the right entity instead of guessing:

• Vendor master records with their multi-legal-entity mapping

• Purchase orders and item receipts

• Financial dimensions and multi-currency context

What comes back inbound to F&O is the posted result, with nothing re-keyed:

• Approved AP invoices, posted to the correct legal entity and dimension with no re-entry

• Payment records and virtual-card settlements, posted to the correct GL account

• Rebate income, posted as a separate dimensional line visible in F&O financial reports

The absence of re-entry is the part finance teams feel most, because duplicate keying between an AP tool and the ERP is precisely the failure mode that makes people distrust automation. As one AP practitioner put it about an ERP-synced tool, syncing directly with the ERP "means no duplicate data entry," and at multi-entity scale that isn't a convenience, it's a control.

How does multi-legal-entity AP work in F&O with Corpay and Dooap?

Multi-legal-entity AP runs as entity-specific queues, not a single shared pile. Each legal entity gets its own AP queue with its own approval workflow, GL mappings, and payment execution, mapped cleanly to the F&O multi-legal-entity architecture. This directly answers a pain that surfaces among technical evaluators looking for "OCR/AP automation that supports subsidiary-level queues." A shared queue forces an AP team to manually sort invoices by entity before anything routes, which is exactly the manual exception work automation is supposed to remove. Entity-specific queues mean an invoice for one subsidiary routes through that subsidiary's approvers and posts to that subsidiary's books without a human deciding which entity it belongs to. The cross-ERP pattern holds across Corpay's enterprise integrations, the same way our NetSuite AP automation approach handles subsidiary structure, and it's the single capability F&O buyers should weight most heavily.

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 does virtual-card payment write-back hit the F&O GL?

When a supplier payment executes by virtual card through Corpay's managed payment service, the settlement posts back to F&O as a vendor payment record against the correct legal entity and dimension. The rebate income from that card transaction posts as a separate dimensional GL line, visible in F&O financial reports. That separation is what makes the rebate real to finance, because it lands as a line item in the ledger, attributed to the right entity, rather than as an opaque quarterly credit that someone has to reconcile by hand. The mechanism is the same one that pairs F&O with deep ERP integration in Corpay's other enterprise guides, including Acumatica AP automation and Sage Intacct AP automation, adapted to F&O's dimensional accounting.

How do BC native, BC plus Corpay, F&O native, and F&O plus Corpay and Dooap compare?

Side by side is the cleanest way to see where each path lands, because the four configurations a Dynamics buyer is realistically choosing among don't line up on a single axis. The table below holds both Dynamics flavors and the third-party comparison in one view. Benchmarks come from Microsoft Learn's 2025 Wave 1 release plan, the Corpay and Dooap partnership announcement, Corpay product documentation, and Ardent Partners' 2025 State of ePayables.

Sources: Microsoft Learn, 2025 Wave 1 release plan for the Payables Agent; Corpay newsroom, Corpay and Dooap partnership, May 2026; Corpay product documentation, 2025; Ardent Partners, State of ePayables 2025.

The benchmark columns are where the case gets concrete. Top-performing organizations process invoices in 3.1 days against 17.4 days for laggards, and they hit a 49.2% touchless processing rate, according to Ardent Partners' 2025 State of ePayables. That spread between a manual-heavy F&O run at 17-plus days and an automated path at 3 to 5 days isn't a marketing claim; it's the documented distance between the top and bottom of the category. The direction of travel is set too. Some 75% of AP departments now use some form of AI or automation tooling, according to Ardent Partners' AP Metrics That Matter in 2025, which means the manual-heavy column is increasingly the exception rather than the baseline.

How do virtual-card rebates work inside a Dynamics 365 environment?

Virtual-card rebates work by routing eligible supplier payments through a card rail, where the interchange on those transactions returns a portion to the buyer as rebate income. No Microsoft Learn page, no SuiteApp marketplace listing, and no consultancy editorial explains how that income posts back to the Dynamics GL, which is the part finance leaders care about. In Business Central, the rebate posts to the BC general ledger as a separate line. In Finance & Operations, it posts as a dimensional line mapped to the correct legal entity and financial dimension. The net effect is that a portion of every AP transaction's cost is offset by rebate income, which is what turns AP from a pure cost center into a managed program with a revenue line.

The opportunity has been growing for years. Corporate virtual-card spending rose from $221 billion in 2019 to $314 billion in 2021, according to RPMG Research's 2022 Virtual Card Benchmark Survey. That growth is supplier acceptance catching up with buyer demand, and it's why the rebate question is worth getting right.

Which suppliers are eligible for virtual-card payment?

Eligible suppliers are the ones that accept card payments, which in practice is a large and growing share of any vendor file but never all of it. Some suppliers take card readily, especially those already set up for card acceptance through other customers. Others accept it once enrolled, and a portion never will, which is why a serious program keeps ACH, check, and wire in the mix alongside card. The practical work is figuring out which of your existing vendors fall into which bucket, because the size of the card-accepting base is what determines how much rebate a program earns. The mechanics of how virtual-card rebates work get into the economics, but the eligibility question is upstream of all of it.

How does Corpay's managed supplier-enablement service work for Dynamics shops?

Corpay's managed enablement service does the supplier outreach that an AP team almost never has time to do well. Rather than handing the buyer a list of vendors to chase, the managed service contacts suppliers, walks them through card acceptance, and moves the ones who agree onto the card rail, while leaving the rest on their existing payment method. This matters because supplier enablement is the single biggest determinant of program success, and it's exactly the part that stalls when it's treated as an internal side project. A capable program treats vendor enrollment as the factor that determines virtual-card program success, because a card program with a small enrolled base earns a small rebate no matter how good the technology is.

The honest version of the advice is to ask a prospective provider for the enrolled-rate range they actually hit with customers of your size and vendor mix, not a demo-environment figure.

How does the rebate post back to the BC or F&O GL, and what does the journal entry look like?

The rebate posts as its own GL entry rather than netting silently against payment costs. In Business Central, when a card settlement clears, the system records the vendor payment and posts the associated rebate income to a designated GL account as a separate line. In Finance & Operations, the same thing happens with dimensions attached, so the rebate line carries the legal entity and financial dimension of the original spend. Kept illustrative rather than tied to a specific basis-point rate, the entry pattern is a debit to cash or a rebate-receivable account and a credit to a rebate-income account, posted in the period the card transactions settle. The point of posting it as a discrete line is auditability. A controller closing the books can see exactly how much rebate the AP program generated, attributed to the right entity, without reverse-engineering it from a card statement.

How long does implementation take across the two Dynamics flavors?

Implementation timelines differ sharply by flavor, and conflating them is how buyers end up surprised. A Business Central AppSource install runs in weeks. A Finance & Operations managed-extension implementation at full enterprise scale runs multi-quarter. Both objections that AP teams raise about automation, that setup is "quite tricky" and that automation can create "more work not less," trace back to timelines and scoping that weren't set honestly upfront. The fix is to frame both paths accurately rather than quoting the fast one and delivering the slow one.

What to expect from a Business Central AppSource implementation

A Business Central implementation is lightweight by enterprise-ERP standards. The SuiteApp installs from AppSource as a managed extension, and the real work is data hygiene. That means cleaning up the vendor master and validating financial dimensions so coding and matching land correctly. Most teams go live in weeks rather than quarters, because Business Central's single-company or simple multi-company structure doesn't carry the entity-mapping complexity that drives enterprise timelines. The constraint is rarely the software; it's how clean the vendor data was going in.

What to expect from an F&O implementation with Corpay and Dooap

A Finance & Operations implementation runs through Microsoft's Lifecycle Services alongside the AppSource managed extension, and the timeline reflects enterprise reality. The scoping work includes confirming which legal entities are in scope, mapping financial dimensions across those entities, and validating approval workflows per entity. In parallel, the managed-payment supplier-enablement outreach starts, so that card acceptance is ramping by the time go-live arrives rather than starting cold afterward. At full enterprise scale across many legal entities, this is a multi-quarter program, and any vendor quoting a few weeks for a true multi-entity F&O rollout is quoting the Business Central timeline for the wrong product. That mismatch is the source of the "set up was quite tricky" frustration that shows up repeatedly in enterprise AP reviews.

What does Corpay's managed onboarding service handle?

Corpay's managed onboarding handles the work that would otherwise fall on an already-stretched AP team. That includes the supplier-enablement outreach described above, the configuration of entity-specific queues and approval thresholds, and the validation that invoices write back to the correct entity and dimension. The managed model is the difference between an AP team that has to become integration specialists and one that keeps doing AP while a service partner handles the connective work. For teams that have been burned by self-serve implementations, the managed component is often the deciding factor, because it's the part that determines whether the project reaches steady state.

How does Corpay protect a Dynamics environment from payment fraud?

Corpay adds layered payment controls on top of the Dynamics ledger, which matters because the ledger isn't where most AP fraud happens. Misdirected payments are. Corpay is SOC 2 Type II compliant, and the controls that follow from that posture are configurable per Business Central company or per F&O legal entity, so a multi-entity enterprise can enforce different thresholds where the risk profile differs. The protections target the specific failure mode behind most accounts payable fraud: a payment that goes to the wrong place because a vendor banking detail was changed or a fraudulent invoice slipped through.

Three controls do most of the work. Dual-approval thresholds require a second sign-off on payments over a configured amount. Payment-batch review holds a batch for inspection before release rather than letting it flow straight through. And validated vendor banking, with vendor-master changes subject to segregation-of-duties controls, addresses the business-email-compromise scenario where an attacker poses as a supplier and quietly swaps in new bank details. That last one is the fear that haunts every AP director, the wire that goes out for hundreds of thousands of dollars to an account that turns out to be fraudulent. Automation that adds an immutable audit trail to every Dynamics AP invoice and payment is part of the answer, and the broader case for how virtual cards and automation mitigate fraud covers why single-use card numbers shrink the attack surface in the first place. Strong AP controls also have a working-capital payoff, since a clean, automated run is what lets a team optimize cash flow with AP automation by timing payments deliberately instead of scrambling.

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 do you evaluate a Dynamics 365 AP automation SuiteApp?

Evaluate any Dynamics AP automation SuiteApp against six criteria, weighted toward whichever Dynamics flavor you run. These are the questions that separate a managed extension that fits the architecture from a generic tool that technically connects. Run them in any vendor conversation, alongside the broader set of questions to ask an AP automation vendor, so the answers are comparable across vendors rather than collected ad hoc.

1. Dynamics flavor coverage. Does the vendor support your specific Dynamics flavor as a Built-for-BC or Built-for-F&O SuiteApp, or only as a generic file-based integration? The architectural answer drives every downstream behavior, from upgrade resilience to write-back fidelity.

2. AppSource certification status. Is the application listed on Microsoft AppSource with certification, or installed through a side channel? AppSource certification is the signal that the extension is built to Microsoft's standards and the release cadence.

3. Multi-legal-entity and multi-company support. Does the platform offer entity-specific queues, dimensional mappings, and per-entity approval workflows? For F&O buyers, this is the single load-bearing criterion, and a "yes, we support multi-company" that turns out to mean one shared queue is a failed answer.

4. Sync direction and latency. Is the sync bidirectional and near real-time, or one-way batch? Does the AP invoice write back to the ledger, or is the tool post-only and leaving someone to re-key? Re-entry is the failure mode that quietly kills automation ROI.

5. Payment delivery scope. Does the vendor handle supplier enablement and remit delivery as a managed service, or does the buyer own that project? The gap between "we provide payment rails" and "we enroll your suppliers and deliver the payments" is enormous in practice.

6. Rebate economics. Does the platform optimize the virtual-card mix and post rebate income back to the Dynamics GL, or is AP treated purely as a cost center? A SuiteApp that ignores rebate economics leaves real money on the table at exactly the moment finance is being asked to cut costs.

The Hackett Group's 2025 digital finance research finds top-performing finance organizations operate at 24% lower cost than peers, and the criteria above are a fair proxy for what separates those organizations from the rest. Vendor selection on a solid vendor-management foundation is what keeps the program clean as it scales past the initial rollout.

Modernize accounts payable in Dynamics 365 with Corpay

Corpay automates accounts payable across both Dynamics 365 flavors while keeping Microsoft's ERP as the system of record. On Business Central, Corpay extends the native module and the Payables Agent through a Built-for-Business-Central SuiteApp on AppSource, adding AI-OCR capture with line-item accuracy, automated GL coding against Business Central dimensions, configurable two-way and three-way line-level matching, and AP invoice write-back so approved invoices post without re-entry. On Finance & Operations, Corpay delivers F&O-native automation through its May 2026 partnership with Dooap, paired with Corpay's managed-payment layer and full multi-legal-entity support for enterprise deployments.

The payoff is end-to-end AP that the native tools don't provide alone. Corpay's managed payment service handles supplier onboarding, virtual-card enablement, remit delivery, and rebate write-back as a separate GL line. The combined effect on the numbers is the gap shown in the benchmark rows above. Per-invoice cost drops into the low single digits from a manual-heavy starting point, cycle time compresses from the 17-day range to a few days, and roughly 40% of AP team capacity is freed for exception handling and vendor work, per Corpay product documentation corroborated by Ardent Partners' 2025 category benchmarks.

Corpay integrates with Dynamics BC and F&O as part of 180-plus ERP integrations spanning NetSuite, Acumatica, Sage Intacct, QuickBooks, Xero, Oracle, SAP, eCMS, CMiC, and Computer Guidance, and processes payments for more than 800,000 businesses as the number-one commercial Mastercard issuer in North America. To see the integration in depth, start with the Corpay AP automation platform and the full integrations index.

Frequently Asked Questions

Does Business Central have AP automation built in?

Yes, partly. Business Central handles vendor records, manual invoice entry, basic approval workflow, and GL posting natively, and as part of Microsoft's 2025 Wave 1 release it added a Payables Agent that reads invoices, matches vendors and accounts, and prepares invoices for approval with human oversight. It's billed on consumption-based Copilot Credits. It does not execute multi-rail payments or write virtual-card rebates back to the GL, so many teams add a SuiteApp for the payment and rebate side.

What is the Microsoft Payables Agent in Business Central?

The Payables Agent is an AI agent native to Business Central that automates AP preparation by reading invoices, matching them to vendors and accounts, and readying them for approval with human oversight. It learns from each invoice posted and is generally available across the US, UK, Canada, and Australia, billed on consumption-based Copilot Credits. It covers capture and preparation rather than full payment execution or rebate write-back.

Can accounts payable be automated in Dynamics 365 Finance & Operations?

Yes, through a Built-for-F&O SuiteApp pattern. Finance & Operations covers requisition management, vendor collaboration, and multi-entity AP natively, but not AI-OCR capture at scale or rebate write-back. The Corpay and Dooap partnership delivers AI-powered AP automation native to F&O, combined with Corpay's managed-payment and rebate-revenue layer, so capture, approval, payment, and rebate posting all work inside the F&O environment.

What is Dooap?

Dooap is an AI-powered AP automation solution purpose-built for Microsoft Dynamics 365 Finance & Operations, handling invoice capture, approval, and processing inside the F&O user experience. Corpay and Dooap announced a partnership in May 2026 to deliver integrated AP automation and vendor payments for F&O, with Dooap providing F&O-native automation and Corpay providing managed payment and rebate write-back.

Does Corpay integrate with Dynamics 365 Finance & Operations?

Yes. Corpay integrates with Finance & Operations through its May 2026 partnership with Dooap, combining F&O-native AP automation with Corpay's managed vendor payments and virtual-card rebates. For Business Central, Corpay connects through the AppSource SuiteApp model. The integration approach is matched to the architecture of each Dynamics flavor rather than forced through a single generic connector.

Is AvidXchange built for Microsoft Dynamics?

AvidXchange supports several Dynamics products through different integration patterns: API-based integration for Business Central and GP, and file-based integration for AX, NAV, F&O, and SL. In February 2026 it announced enhanced integrations for Microsoft Dynamics GP, NetSuite, and Sage Intacct, adding AI-driven OCR-based PO and invoice line matching. The file-based approach for F&O differs from a native AppSource extension, which is worth weighing for enterprise F&O deployments.

How long does it take to implement AP automation in Dynamics 365?

It depends on the flavor. Business Central AppSource installs run in weeks, with most of the work being vendor-master cleanup and dimension validation. Finance & Operations managed-extension implementations run multi-quarter at full enterprise scale, because they involve confirming legal-entity scope, mapping dimensions across entities, and running supplier-enablement outreach in parallel with go-live.

Is Corpay AP automation SOC 2 compliant?

Yes. Corpay AP Automation is SOC 2 Type II compliant. For a Dynamics environment, that posture supports configurable per-company or per-legal-entity controls, including dual-approval thresholds, payment-batch review, validated vendor banking, and an immutable audit trail on every AP invoice and payment.

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.

AP Automation