Loading accounts-payable invoices and payments from Oracle EBS into Oracle Fusion — matched to the migrated suppliers and purchasing documents, with VAT and balances reconciled.
AP is the last domain in the load sequence for a reason: invoices and payments only make sense once the suppliers, sites, banks and purchasing documents they reference already exist in Fusion. That is why the production cutover ran Item → Supplier → Procurement → Finance.
Every invoice had to resolve to a supplier, site and (where matched) purchasing document already loaded into Fusion — validated before import so nothing dangled.
Tax and VAT lines were mapped to the Fusion tax setup so invoice totals reconciled to source.
Invoice and payment amounts were reconciled at row and column level against the source so the migrated AP position matched EBS.
As with every object, reloads were idempotent — no duplicate invoices when a batch was re-run.
Invoices and payments reference suppliers, sites, banks and purchasing documents. Loading Item → Supplier → Procurement → Finance guarantees those references already exist in Fusion when AP loads.
AP invoices and payments were reconciled row- and column-level against the source, including tax/VAT, so the migrated payables position matched Oracle EBS.
Tell us your source EBS footprint, modules and business units — we'll scope a mock-run-based transform-and-load plan on the Syntra ETL platform.