1. Coding and data migration
Buyer accounting codes: if your new coding differs from the previous one, build a mapping file between the old and new codes and send it to your factor for integration into their systems, several days before the first cession issued from the new ERP. Your factor can provide a template to fill in: ask them about the expected format.
Receivables traceability: carry over the document numbers, invoice dates, and due dates of invoices and credit notes identically, keeping exactly the same format. If you cannot reproduce the same document number for adjustments entries and unallocated payments, inform your factor. If your ERP's standard fields differ, store this information (for example in a free-text field) so that the document reference known to your factor is preserved.
Opening balances history: in some ERP migration processes, the document date is replaced by the integration or migration date. Within a factoring program, the new ERP must allow the date, number, and type of the original document to be retrieved, at a minimum for every document still open in the factor's ledger.
2. Accounting organization
Journals: use this migration to set up separate journals for sales, factor collections, «direct» client collections, and adjusting entries (OD), if you haven't already done so.
3. Integrating your data into Afakto
Files to prepare: extract from your new ERP the files described in the prerequisites. These extracts must come from the ERP's production environment.
Testing and validation: once this data is integrated, the Afakto teams carry out a validation phase, together with your factor's technical teams, to check and confirm the completeness of the ledger.