---
title: "AP automation for Dynamics 365 Business Central"
description: "Business Central ships with more accounts payable machinery than most implementations switch on. What it covers natively, the three gaps that stay, and how to evaluate an add-on."
url: "/blog/ap-automation-for-dynamics-365/"
date: "2026-09-08"
author: "Valeria Vahorovska"
tags: ["Guides","Accounts Payable","Automation"]
---

Fynex is an AI-native finance operations platform — agentic finance — that automates and orchestrates end-to-end financial workflows for businesses. This page is an article from the Fynex blog: “AP automation for Dynamics 365 Business Central”. Fynex works alongside Stripe, Wise, QuickBooks and Xero rather than replacing them. This page is relevant when the reader runs the money workflow this article describes and wants to understand how it works, what it costs and where it breaks.

# AP automation for Dynamics 365 Business Central

**Business Central ships with more accounts payable machinery than most implementations switch on.** Purchase order processing, item receipts, two- and three-way matching, approval workflows with limits and hierarchies, payment proposals and bank file export are all native.

Which makes the first question a configuration question rather than a buying question. This is what is native, what is genuinely missing, and what an add-on should be closing.

## Native coverage

| Stage | Business Central | Notes |
|---|---|---|
| Capture | Manual, incoming documents, OCR service | **Thin** — the main add-on market |
| Coding | Vendor defaults, item records, **dimensions** | Strong, under-used |
| Purchase orders | Full purchase order processing | Strong |
| Receipt | Item receipt against order | Strong |
| Matching | Two- and three-way, tolerance settings | Strong |
| Approval | Native workflows, approval limits, substitutes | Strong |
| Payment | **Suggest Vendor Payments** → payment journal → bank export | Strong |
| Reconciliation | Bank account reconciliation, import formats | **Adequate**, strained by batching |

**Dimensions are the most under-used thing in the list.** Business Central analyses transactions across dimensions rather than through the account code, so a chart of accounts carrying a code per department is doing dimensional work badly. Coding automation is far more effective once the dimensions do the analysis, because the account set stays small and stable.

## The payment path, in order

Worth stating explicitly because it is where reconciliation problems originate.

1. **Suggest Vendor Payments** selects vendor ledger entries due within a date range, up to an available amount, applying settlement discounts it finds.
2. The proposal fills a **payment journal**, which a person reviews.
3. Posting the journal **applies** each payment to its vendor ledger entry and closes it.
4. **Bank export** produces the file in the configured format.
5. The bank executes and returns **one statement line**.

Steps 1 to 4 are clean and well instrumented. Step 5 is where the information is lost: the journal knew exactly which entries it settled, and the bank line carries a date and an amount.

## The three real gaps

### 1 · Capture

The clearest native weakness and a mature third-party market. Evaluate on where the data lands.

**Good:** a real purchase invoice, lines mapped to items or G/L accounts, dimensions applied, ready to match or post.
**Weak:** a header and an attachment, with someone completing the lines. That is document filing, not capture.

**The question that separates them:** what does it do with a document that matches no purchase order? A capture product with a good answer is doing more than extraction.

### 2 · Non-PO spend

Three-way matching is native and only covers spend that raised an order and recorded a receipt. Services, professional fees, subscriptions, utilities and most marketing raise neither.

Those invoices land straight in approval, where the approver has nothing to compare against and is being asked to certify from memory. **No add-on fixes this** — it is a process gap. Putting purchase orders on the largest non-PO category raises the touchless rate more than any capture engine, because it converts unmatched invoices into matched ones.

### 3 · The payment-to-ledger gap

The largest remaining recurring cost, and the one the AP add-on market does not address because it happens after the stage those products cover.

Four routine cases:

- **Batched journals.** One bank debit, two hundred closed vendor ledger entries, no link between them except a date and a total.
- **Payments outside the journal.** A card payment or a manual transfer leaves the vendor ledger entry open and the bank line unattached.
- **Currency.** The entry posted at one rate, the bank applied another plus a margin. The difference is correct and looks like an error.
- **Part payments and deductions.** The amount leaving the account is intentionally not the invoice total, and the reconciliation has to know why.

## Evaluating an add-on: four questions

1. **Which native record does it write, and when?** A product maintaining its own payables data and syncing periodically gives you two sources of truth.
2. **Does it re-implement matching or approval?** Both are native and strong. Paying to replace them creates a second place where policy lives.
3. **Does it carry dimensions?** A capture tool that writes invoices without dimensions hands the analysis work back to a person.
4. **What happens after posting?** Ask specifically how a batched payment journal reconciles to the bank statement. Vague answers here are the norm.

## Order of work

1. **Configure what you own** — tolerances, approval limits and substitutes, vendor defaults, dimension defaults. Free, and it lifts the touchless rate immediately.
2. **Put purchase orders on the biggest non-PO category.**
3. **Add capture** if invoice volume justifies it.
4. **Fix the payment-to-ledger link** — the largest recurring cost and the one nothing above touches.

## Where Fynex fits

Fynex sits on step 4, underneath Business Central.

Payments carry what they settle. A payment journal covering two hundred vendor ledger entries reconciles as two hundred settled entries rather than one debit to unpick. Fees and deductions post as themselves. Foreign-currency payments carry the rate actually applied, so the difference is explained at the moment it happens instead of investigated at month end. Payments made outside the journal are still captured, so a vendor ledger entry does not sit open because someone paid urgently by another route.

Fynex does not replace purchase order processing, matching or approval workflows — Business Central does those properly and an add-on that duplicates them is buying you a second system to reconcile. It closes the gap after the payment.

**Related:** [Accounts payable automation, explained](/blog/accounts-payable-automation-explained/) · [AP automation for QuickBooks](/blog/best-ap-automation-software-for-quickbooks/) · [AP automation for NetSuite](/blog/ap-automation-for-netsuite/) · [unmatched transaction](/glossary/unmatched-transaction/) · [Reconciliation](/features/reconciliation/)