What Open Payables Include
The migration scope should begin by identifying every Dynamics GP payable transaction that remains open at the agreed migration cutoff date. The exact scope depends on the organization's transition strategy and accounting requirements.
- Open vendor invoices: Unpaid invoices with outstanding balances, invoice dates, due dates, and applicable payment terms.
- Credit memos: Open credits that reduce amounts owed to suppliers.
- Partial payments: Invoices where only part of the original amount has been settled.
- Unapplied payments: Vendor payments that have not yet been fully applied to specific invoices.
- Currency information: Transaction and local currency values needed for accurate settlement and reporting.
- Accounting attributes: Vendor identifiers, posting groups, dimensions, document references, and other fields required by Business Central.
Closed transactions generally remain in the legacy system or are migrated separately for historical reporting, depending on the organization's data-retention and reporting requirements.
How the Migration Works
The process normally starts by establishing a firm migration cutoff date. Dynamics GP is then reviewed to identify open vendor balances as of that date. Each transaction is classified, cleansed, mapped to Business Central fields, and prepared for loading.
Vendor identifiers must correspond to valid Business Central vendor records. Transaction dates, document numbers, currencies, payment terms, amounts, dimensions, and posting configurations should be mapped consistently. Any partially paid document requires special attention because Business Central must receive the remaining open amount rather than the original gross invoice value.
After loading, finance teams reconcile the migrated open payable balance against Dynamics GP and the general ledger. Transaction-level testing should confirm that migrated invoices can be reviewed, applied, approved, and settled correctly in Business Central.
Invoice Processing and Matching
Open payables migration directly affects future invoice processing because migrated invoices become part of the transaction population that finance teams manage in Business Central. Supporting fields should therefore be sufficient for invoice identification, approval, payment, and reconciliation.
Where purchase orders and receipts are available, teams should preserve the information needed for invoice matching. Matching can compare supplier invoices with purchasing documents and receipt information before an invoice is approved or posted.
Related controls can include Invoice Matching Approval and Accounts Payable Matching Approval, which help establish clear authorization points within invoice and accounts payable workflows. Detailed invoice capture, extraction, validation, matching, coding, approval, and posting practices can also improve the continuity of the payable process after migration.
Reconciliation and Accounting Validation
Reconciliation is one of the most important stages because the migrated open-payables subledger should agree with the corresponding liability balances at the migration cutoff. Finance teams should compare vendor-level totals, transaction counts, currencies, and outstanding balances between the two systems.
For example, if Dynamics GP shows $4.2M of open vendor invoices at the cutoff date, the corresponding migrated payable population should reconcile to the same financial position after considering approved migration adjustments and accounting treatment. Individual vendor balances should also be reviewed where material.
Open payable migration may also intersect with accruals. Accrued expenses that have not yet become vendor invoices should be treated according to the organization's cutover accounting policy rather than being incorrectly loaded as open invoices.
Payments and Cutover Controls
Payment processing should be coordinated carefully around the migration cutoff so invoices are not paid twice or omitted from the new system. The organization should establish a clear point at which payment activity moves from Dynamics GP to Business Central.
Payment Approval provides a useful control concept for authorizing payments against migrated obligations. After migration, payments should reference the correct vendor, invoice, currency, amount, and payment method so the outstanding balance is reduced accurately when settlement occurs.
Organizations should also document how pending payments, unapplied vendor credits, and payment batches existing around the cutover date will be handled. This creates a clear audit trail between the legacy system and Business Central.
Best Practices for Migration Readiness
- Freeze or clearly define the transaction cutoff before extracting open payables.
- Reconcile Dynamics GP vendor balances to the general ledger before migration.
- Validate every migrated transaction against an active Business Central vendor.
- Preserve original invoice numbers and useful document references for traceability.
- Verify partial payments, credit memos, and unapplied amounts separately.
- Test migrated transactions through invoice approval and settlement workflows.
- Document reconciliation results and approved cutover adjustments.
Integration with procurement processes should also be tested where purchase orders, receipts, and supplier transactions originate upstream. For organizations extending Business Central finance workflows, AP Automation Software can support invoice processing and payment planning around the migrated payable population.
Summary
Dynamics GP Open Payables Migration to Business Central transfers outstanding supplier obligations into Business Central while preserving the information required for accurate accounting, invoice management, reconciliation, approval, and settlement. A successful approach combines cutoff control, transaction mapping, vendor validation, balance reconciliation, payment coordination, and post-migration testing. When open payables are accurately transferred, finance teams can continue managing supplier obligations while maintaining reliable financial reporting and cash flow visibility.