MT422 — Advice of Fate and Request for Instructions

The advice of fate: sent by the presenting bank to the remitting bank when a collection runs into trouble — non-payment, acceptance refusal, non-conforming document. Request for instructions on next steps, under URC 522 ICC.

Purpose

MT422 is sent by the presenting bank when something does not go as planned: the drawee refuses to pay (D/P), refuses to accept the draft (D/A), or the documents received do not match the collection instructions. The message has two components: (1) advice of fate = description of the problem (field :75:), (2) request for instructions = explicit request for next-step instructions (field :76:).

URC 522 art. 26 obliges the presenting bank to issue this advice without delay as soon as the incident is observed. The remitter must respond quickly — typically via MT430 (Amendment) if it accepts a modification (late discount, partial payment, represent), or MT499 (free format) for more nuanced instructions.

Tag structure

Flat message longer than the other Cat 4 messages — typically 6 to 10 tags. The two key tags are :75: (fate description) and :76: (request for instructions), both in structured free text.

Mandatory tags

Real-world example

Advice of Fate sent by ICBC Beijing to BNP Paribas on 17 June 2026 — the Chinese importer Guangzhou Textile Exports refused to pay the USD 145,000 for lack of funds. ICBC asks BNP for instructions on next steps: represent, return documents, protest:

{1:F01ICBKCNBJAXXX0000000000}{2:I422BNPAFRPPXXXXN}{3:{108:AF20260617001}}{4:
:20:AF20260617001
:21:ACME-COL-2026-187
:32A:260516USD145000,00
:75:DRAWEE REFUSED PAYMENT
LACK OF FUNDS
REPRESENTED ON 17 JUNE 2026
:76:PLEASE ADVISE WHETHER TO
(1) REPRESENT IN 30 DAYS
(2) RETURN DOCUMENTS TO REMITTING BANK
(3) PROTEST FOR NON-PAYMENT
URGENT RESPONSE REQUIRED
:72:/REC/COLLECTION DOCUMENTS HELD
/REC/ON FILE PENDING INSTRUCTIONS
-}

• :20:AF20260617001 — ICBC's advice reference.
• :21:ACME-COL-2026-187 — collection reference.
• :32A:260516USD145000,00 — amount reminder.
• :75:DRAWEE REFUSED PAYMENT... — fate description.
• :76:PLEASE ADVISE WHETHER TO (1) REPRESENT... — structured request with numbered options.
• :72:/REC/COLLECTION DOCUMENTS HELD ON FILE... — operational note.

Common pitfalls

• Vague description in :75: — a text like «PROBLEM» does not pinpoint the refusal cause. The remitting bank needs the exact reason (lack of funds, document missing, signature mismatch, payment beyond limit) to decide next steps.
• Ambiguous request for instructions — :76: must list clear, numbered options. An open «PLEASE ADVISE» makes the remitter's response subjective and slows down resolution.
• Tolerance delay breached — URC 522 art. 26 mandates an advice «without delay». Sending an MT422 three weeks after the incident exposes the presenting bank to a remitter recourse for opportunity loss.
• Storage fees uncommunicated — when documents remain pending instructions, the presenting bank may charge document-holding fees to the remitter. The :72: must warn.
• Undocumented partial payment — if the drawee paid in part, MT422 must indicate the paid amount and the residual. Otherwise wrong reconciliation on the exporter side.
• Wrong recipient for instructions — MT422 goes to the remitting bank, which relays to its exporter client; the exporter instructs its bank, which responds in MT430 or MT499. Skipping a step (direct exporter-to-presenter instruction) breaches the URC 522 mandate.

ISO 20022 equivalent

No ISO 20022 equivalent. The collection domain stays in SWIFT FIN.

Related messages

• MT400 — Advice of Payment (positive reply if payment received later).
• MT410 — Acknowledgement (initial neutral ack).
• MT420 — Tracer (chase-up that may trigger an MT422 reply).
• MT430 — Amendment of Instructions (remitter's instructions in response to MT422).
• MT499 — Free Format Message Cat 4 (remitter free reply).