Put CBPR+ corporate payment — full MX lifecycle back in order

THE DRILL AS TEXT

1. In CBPR+ corporate payment — full MX lifecycle, what happens first, and what follows?
   • Treasury sends the payment instruction — Asha Traders asks Bank Alfa to pay one supplier. The pain.001 is a customer instruction, not an interbank payment and not proof that funds moved.
   • Bank Alfa validates the instruction — The bank checks authority, account and address data, duplicate references, available funds, cut-off time, and sanctions-screening results before accepting the instruction.
   • Treasury receives an accepted status — A pain.002 says the instruction passed the reported checks and was accepted for processing. It does not say the supplier has been credited; banks choose which lifecycle statuses their service reports.
   • Bank Alfa debits the corporate account — Bank Alfa books the customer debit. The debit and the interbank settlement are separate ledger events and can occur at different times under the account agreement.
   • Treasury receives an entry notification — Where the service provides it, a camt.054 reports the booked debit promptly and carries structured references for cash application. It reports an account entry; it does not create the entry.
   • Bank Alfa sends the interbank payment — Bank Alfa turns the accepted customer instruction into a pacs.008. The UETR, end-to-end reference, parties, agents, amounts, and remittance data identify the same business payment on the interbank leg.