Payment Received Under Legacy Customer Code Email Template

Use this page when funds arrive under a legacy customer code, old account code, or retired buyer identifier that no longer maps cleanly to your current receivables setup. This is different from an old vendor number in remittance. Here, the mismatch sits on the customer-side identity used to tag the payment itself, which makes it harder to connect incoming cash to the right open balances. That is why the page deserves its own scenario. The email should ask the payer to confirm what current account the legacy code now belongs to, which invoices the payment was intended to settle, and whether their treasury or AP master data still needs to be updated to prevent repeated misposting. The outcome you want is not just to identify today’s payment, but to stop future cash from arriving under obsolete customer identifiers that no longer help your team reconcile anything. It is commercially strong because the visitor is already dealing with real cash that could remain stuck purely because the payer is still using a retired code in their outbound payment process.