Put Corporate payment — legacy MT lifecycle back in order

THE DRILL AS TEXT

1. In Corporate payment — legacy MT lifecycle, what happens first, and what follows?
   • Treasury sends a request for transfer — Asha Traders asks Bank Alfa to execute the supplier payment with an MT101. It is the legacy initiation request, not the bank-to-bank customer payment and not proof of execution.
   • Bank Alfa validates the MT101 — The bank checks the mandate, message fields, funds, cut-off, routing, and sanctions-screening results. A FIN ACK only confirms network acceptance; pain.002-style business status has no MT equivalent.
   • Bank Alfa debits Asha Traders — Once it accepts the request for execution, Bank Alfa books the customer debit under the account agreement before it releases the interbank MT103.
   • Treasury receives a debit confirmation — Where contracted, MT900 confirms one booked debit on the serviced account. It is an account-entry advice, not a beneficiary-credit confirmation and not a substitute for payment status.
   • Bank Alfa sends the customer payment — The MT103 carries the customer-payment instruction into the correspondent chain. In a serial route the instruction follows the account path used to settle the value.
   • Meridian validates and screens the MT103 — The correspondent validates FIN fields, checks Bank Alfa's account, screens the parties and narrative data, and decides whether it can book and forward the payment.