What Open AP Records Include
Open AP migration focuses on transactions that have not been fully settled before the new ERP goes live. Each record should retain the information needed to identify the obligation, validate its amount, and manage the payment after migration.
- Supplier details: Supplier ID, legal name, payment terms, and relevant vendor account references.
- Invoice information: Invoice number, invoice date, posting date, due date, currency, and original amount.
- Outstanding balances: Remaining payable after posted payments, credit notes, and approved adjustments.
- Purchase references: Purchase order, receipt, department, location, or project associated with the invoice.
- Accounting information: General ledger account, tax treatment, business entity, and applicable cost center.
- Payment status: Approval state, payment hold, dispute status, and any scheduled payment information supported by the destination system.
These details help maintain continuity between procurement activity, supplier invoices, and the liability recorded in the general ledger.
How the Migration Process Works
A controlled migration begins by defining a cutover date and agreeing on which transactions qualify as open. Finance teams extract supplier invoices and related adjustments from the legacy system, then compare the records with supplier subledger reports and general ledger control accounts.
Next, the team maps legacy fields to the new ERP structure. Supplier identifiers, currencies, payment terms, tax codes, and entity codes must align with the destination system. Where the old and new systems use different identifiers, approved mapping tables connect the original records to the correct destination accounts.
During validation, teams check for duplicate invoice numbers, missing supplier references, incorrect due dates, and balances that do not match the legacy records. invoice processing rules can help standardize invoice data, while AP Invoice Matching Approval describes the authorization checkpoint used to confirm that invoice details align with the relevant purchase order and receipt evidence where applicable.
After validation, approved open items are imported and reconciled. The migration team compares record counts, invoice-level balances, supplier totals, and the overall AP control account before authorizing the new system for live operations.
Calculating and Reconciling Open Payables
The key reconciliation is the outstanding balance for each invoice. A practical calculation is:
Open invoice balance = Original invoice amount − Applied payments − Applied credits
For example, a dealer has a supplier invoice for $12,500. Before migration, $4,000 has been paid and a credit note of $500 has been applied.
$12,500 − $4,000 − $500 = $8,000 outstanding
The migration should carry forward the $8,000 balance, along with the original invoice reference and due date. If the legacy system reports $8,500 instead, the difference must be investigated before import. The team should determine whether the credit note was unapplied, the payment was posted to another invoice, or the source report reflects a different cutover position.
At the overall level, the sum of migrated open invoices, less relevant credits and adjustments according to the agreed accounting treatment, must reconcile to the AP balance being transferred. This control supports accurate financial reporting and prevents liabilities from being omitted or counted twice.
Controls for Accurate Migration
Dealers should establish clear ownership across accounting, purchasing, and the migration team. vendor management records must align with supplier master data so that invoices are assigned to the correct supplier and payment destination. A documented Payment Approval process helps ensure that migration activity does not bypass the company's existing authorization rules for releasing funds.
Useful migration controls include:
- Freeze or carefully track legacy transactions at cutover so that new payments and credits are captured consistently.
- Preserve invoice numbers and source-system references for audit trails and supplier inquiries.
- Separate disputed, blocked, and unapproved invoices from items ready for payment, while retaining their correct accounting status.
- Use duplicate checks to prevent an invoice from being loaded twice or recreated as a new liability.
- Reconcile supplier-level totals to the AP control account and obtain finance sign-off before go-live.
Teams can use AP Automation Software to support invoice validation and payment planning after migration. Related payments workflows should use the verified due dates, approved amounts, and supplier details from the new system.
ERP Readiness and Post-Migration Operations
Open AP migration should be coordinated with the wider ERP transition, including supplier master data, purchasing records, general ledger balances, and approval workflows. A documented Digital Purchase Order System Migration approach can help align purchase order references and receiving information with the destination ERP. Teams comparing procurement platforms may also review Open Source PO System: Options, Use Cases & Deployment when evaluating how purchase order records are managed.
Once the new ERP is live, finance teams should review the first payment run, aged payable report, and supplier statements against the migration baseline. Confirm that invoice balances remain open until properly settled, that payments clear the intended invoices, and that credit notes are reflected correctly. The Vendor Invoice Processing 2025: AI Supplier Workflow Guide can provide additional context for the invoice capture, validation, and posting stages that continue after go-live.
Effective accounts payable reporting also depends on accurate due dates and aging buckets. These records influence short-term cash planning, supplier communication, and forecasts of upcoming cash requirements. When invoices remain unresolved, teams should trace the original source record and correction history rather than making unsupported balance adjustments.
Summary
Open AP Migration Dealers is the transfer of unpaid supplier obligations into a new dealer ERP while preserving invoice-level details, balances, payment status, and accounting references. A successful migration combines clear cutover rules, field mapping, invoice-level validation, and reconciliation to the AP control account. By confirming every open item before go-live and monitoring the first payment cycles afterward, dealers can protect financial reporting accuracy, maintain supplier relationships, and plan cash flow with confidence.