Finance Index
Microsoft Business Central Integration in Accounts Payable
Complete guide to Microsoft Business Central ERP integration for AP workflows, covering data sync, invoice export, payment processing, and configuration.
Microsoft Business Central integration synchronizes invoice coding, payment data, and master records between the ERP system and accounts payable workflows. The integration imports vendor records, chart of accounts, dimensions, purchase orders, and tax codes while exporting approved invoices, credit memos, and payments back to Business Central. This bidirectional data flow maintains coding consistency with the ERP chart of accounts and creates a unified audit trail across both systems.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Data Flow | Imports master data, exports approved transactions | Maintains ERP alignment and eliminates duplicate data entry |
| Deployment Support | Both cloud (SaaS) and on-premises versions | Accommodates different IT infrastructure preferences |
| Tax Handling | US tax areas/groups or global VAT posting groups | Ensures compliance with local tax regulations |
| Document Types | Invoices, credit memos, payments, purchase orders | Covers complete procure-to-pay lifecycle |
| Multi-Company | Single tenant, multiple companies supported | Scales with organizational structure |
What Microsoft Business Central Integration Covers
Microsoft Business Central integration encompasses the complete data exchange between AP workflows and the Business Central ERP system. The integration operates through extensions installed in Business Central that provide the connectivity layer for data import and export operations.
The integration supports both cloud-hosted Business Central (SaaS) and on-premises deployments. For on-premises installations, the connection uses a secure bridge connector installed in the organization's environment to maintain data security and network isolation.
Master Data Synchronization
Master data synchronization imports foundational records from Business Central that support invoice coding and payment processing. The synchronization includes vendor records with payment terms, addresses, and default coding values, along with the complete chart of accounts structure with posting configurations and business posting groups.
Dimension values and default dimension assignments flow into the AP system to support multi-dimensional coding requirements. Tax codes import differently based on locale configuration, with US implementations receiving tax area and tax group combinations, while global implementations receive VAT business posting groups and VAT product posting groups.
Purchase orders and receipt information synchronize to support procurement matching workflows. The system imports open and partially received purchase orders with line details, enabling three-way matching between purchase orders, receipts, and invoices.
Invoice and Credit Memo Export
Invoice export creates purchase invoice documents in Business Central based on approved AP transactions. Non-purchase-order invoices can export as either draft documents requiring manual posting or as fully posted transactions, depending on configuration settings.
Purchase-order-based invoices must export as posted documents due to Business Central limitations. The system validates that invoice coding aligns with the imported chart of accounts and dimension structure before export. Credit memos follow the same export patterns as invoices, supporting both draft and posted creation.
The export process includes complete transaction details: vendor information, dates, amounts, account coding, dimensions, tax codes, and any configured custom fields. Each exported document includes a reference link back to the original AP record for audit trail purposes.
Payment Processing
Payment processing exports payment journal entries that apply to one or more posted invoices in Business Central. The system supports partial payments, credit memo applications, and payment reversals for voided transactions.
Payment export requires that target invoices already exist as posted documents in Business Central. The system validates this requirement before creating payment records and provides clear error messages when invoices need to be posted first.
Payment receipts combine invoice creation and payment application in a single workflow. When configured to export invoices as drafts, the invoice portion requires manual posting in Business Central before the payment can be applied.
Tax Code Management
Tax code management varies by locale configuration to accommodate different regulatory requirements. US-locale integrations import tax areas, tax groups, tax area lines, and tax details from Business Central, building available tax code combinations from these foundational tables.
During invoice export, the system sets tax area codes on invoice headers and both tax area codes and tax group codes on individual lines. Manual tax adjustments are fully supported for US tax locales, allowing AP staff to override calculated tax amounts when necessary.
Global and VAT locales use VAT business posting groups and VAT product posting groups from the VAT posting setup. Only combinations with standard VAT calculation types are imported, and manual tax adjustment support is limited compared to US implementations.
Dimension and Custom Field Support
Dimension support enables multi-dimensional coding aligned with Business Central's dimension structure. Header dimensions support up to two shortcut dimensions at the invoice level, while line dimensions use dimension set entries to support broader dimensional coding requirements.
Payment dimensions follow the same shortcut and table dimension structure, ensuring consistent dimensional reporting across all transaction types. Multi-company configurations map dimensions appropriately when different companies use different dimension assignments.
Custom field support extends standard invoice data with additional header-level or line-level information from third-party Business Central extensions. Supported field types include text, date, number, checkbox, and list values that import from Business Central and export back with transaction data.
Common Misconceptions
Integration is not real-time mirroring
Master data refreshes on scheduled intervals rather than reflecting every Business Central change immediately. Organizations should plan for sync timing when making critical master data updates.
Purchase order matching has specific limitations
An invoice can match multiple receipts but only one purchase order due to Business Central constraints. Invoices cannot mix purchase order lines and receipt lines on the same document.
Draft export is not available for all invoice types
Purchase-order-based invoices must export as posted documents. Only non-purchase-order invoices support draft export options.
Custom fields require additional implementation
Custom field support needs wrapper extensions in Business Central to expose third-party fields, requiring coordination between implementation teams and Business Central administrators.
Where This Fits in the P2P Workflow
Microsoft Business Central integration serves as the bridge between AP processing workflows and the organization's financial system of record. The integration receives master data from Business Central at the beginning of the invoice lifecycle, ensuring that coding options, vendor information, and purchase order details are current and accurate for invoice processing.
During invoice approval workflows, the integration validates coding against imported chart of accounts and dimension structures, preventing coding errors before they reach the ERP system. After approval, the integration exports completed transactions back to Business Central, where they become part of the official financial record and feed into financial reporting, cash management, and audit processes.
Frequently Asked Questions
US tax handling uses tax area codes and tax group codes with full manual adjustment support, while global implementations use VAT business posting groups and VAT product posting groups with limited manual adjustment options. The locale setting determines which tax model applies to your integration.
Multi-company support connects to multiple companies within a single Business Central tenant, with a company code field appearing on invoices to filter data appropriately. Each company maintains separate vendor lists, charts of accounts, and dimension configurations while sharing the same integration connection.
No, purchase-order-based invoices must be exported as posted documents due to Business Central limitations. Only non-purchase-order invoices support the draft export option, which creates documents requiring manual posting in Business Central.
When master data sync fails, imported lists become stale until connectivity is restored. The system includes volume safeguards that skip imports returning significantly fewer records than previous runs to prevent data loss from potential sync issues.
Custom fields require wrapper extensions in Business Central to expose third-party fields to the integration. Supported field types include text, date, number, checkbox, and list values that import for coding and export back with transaction data.
The system validates account coding against the imported chart of accounts, checks dimension assignments, verifies tax code configurations, and ensures invoice number series are properly configured. Purchase-order-based invoices undergo additional validation for line matching requirements.
Payment processing supports partial payments applied to multiple invoices and credit memo applications within the same payment record. All target invoices and credit memos must be posted in Business Central before payment export can proceed.
On-premises integration requires a bridge connector installed in the organization's environment with network access to the Business Central instance. The connector must maintain compatible versions with both the Business Central installation and the installed integration extension.