GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

GET IN TOUCH
SWIFT MT CORRESPONDENT

Too late for today: an MT103 that missed the cut-off

Trigger: The MT103 reaches Meridian Bank after its USD cut-off, so execution slips to the next business day.

Contributor Shubham Mathure

What operations sees first: The expected debit is missing from Bank Alfa's nostro statement the next morning, and the beneficiary is chasing funds that were promised for today.

WHERE IS THE MONEY?

Debited from the customer on day one; sat on Bank Alfa's nostro at Meridian overnight; with the beneficiary the next business day.

DID SETTLEMENT HAPPEN?

Settlement happened normally but one day later than intended; nothing failed and nothing reversed.

WHO ACTS NEXT?

Bank Alfa (ordering bank) — releasing close to the correspondent's cut-off is the root cause Operations publishes corridor cut-off tables to the front office and adds a warning when the release time makes same-day value unlikely.

PLAY THE EXCEPTION

Trigger: The MT103 reaches Meridian after its USD processing cut-off for same-day value.

STEP 1 / 8MESSAGE

The customer orders a USD transfer abroad

Ordering customer → Bank Alfa (ordering bank)

The ordering customer instructs Bank Alfa to pay a supplier banked at Cassia Bank in another country. Bank Alfa has no direct account relationship with Cassia — that is why correspondents exist.

Step 1 of 8: The customer orders a USD transfer abroad

  1. 01Message
    The customer orders a USD transfer abroadOrdering customer → Bank Alfa (ordering bank)
  2. 02Processing
    Bank Alfa validates and screensBank Alfa (ordering bank)
  3. 03Posting
    The customer's account is debitedBank Alfa (ordering bank)
  4. 04Message
    The MT103 goes to Bank Alfa's USD correspondentBank Alfa (ordering bank) → Meridian Bank (correspondent) · MT103
  5. 05 · EXCEPTION PATHProcessing
    Meridian queues the payment for the next value dateMeridian Bank (correspondent)
  6. 06 · EXCEPTION PATHSettlement
    Settlement happens the next business dayMeridian Bank (correspondent)
  7. 07 · EXCEPTION PATHMessage
    The payment continues with next-day valueMeridian Bank (correspondent) → Cassia Bank (beneficiary bank) · MT103
  8. 08 · EXCEPTION PATHPosting
    The beneficiary is credited a day laterCassia Bank (beneficiary bank)
  9. OUTCOME
    Funds
    Debited from the customer on day one; credited to the beneficiary the next business day.
    Settlement
    Settled one value date later than instructed.
    Who acts next
    Meridian Bank (correspondent) — Operations at Bank Alfa answers the enquiry using the payment's trail and reviews cut-off schedules for this corridor.
Full step-by-step text (works without JavaScript)
  1. 01Message
    The customer orders a USD transfer abroadOrdering customer → Bank Alfa (ordering bank)

    The ordering customer instructs Bank Alfa to pay a supplier banked at Cassia Bank in another country. Bank Alfa has no direct account relationship with Cassia — that is why correspondents exist.

  2. 02Processing
    Bank Alfa validates and screensBank Alfa (ordering bank)

    Format and balance checks plus sanctions screening. Cross-border payments face stricter screening because more jurisdictions are involved.

    Screening checkpoint: Outbound cross-border screening — Ordering and beneficiary parties, banks, and remittance text are screened before the payment leaves.

  3. 03Posting
    The customer's account is debitedBank Alfa (ordering bank)

    Bank Alfa books the debit and, per the charge option, any fees.

    • DR Ordering customer's account at Bank Alfa — USD 250,000.00
  4. 04Message
    The MT103 goes to Bank Alfa's USD correspondentBank Alfa (ordering bank) → Meridian Bank (correspondent) · MT103

    In the serial method the payment instruction itself travels through the account chain. Meridian holds Bank Alfa's USD account (Bank Alfa's nostro), so Meridian can debit it.

  5. 05 · EXCEPTION PATHProcessing
    Meridian queues the payment for the next value dateMeridian Bank (correspondent)

    Nothing is wrong with the payment — it simply arrived too late for today's processing. It will be executed with the next business day's value.

  6. 06 · EXCEPTION PATHSettlement
    Settlement happens the next business dayMeridian Bank (correspondent)

    The book transfer executes in the next processing day. Cut-offs and time zones are why 'same-day' is never guaranteed across currencies.

    • DR Bank Alfa's USD account at Meridian (vostro) — USD 250,000.00
    • CR Cassia's USD account at Meridian (vostro) — USD 250,000.00
  7. 07 · EXCEPTION PATHMessage
    The payment continues with next-day valueMeridian Bank (correspondent) → Cassia Bank (beneficiary bank) · MT103

    The serial chain completes normally, one value date later than the customer expected.

  8. 08 · EXCEPTION PATHPosting
    The beneficiary is credited a day laterCassia Bank (beneficiary bank)

    The delay is visible to the beneficiary — a common source of 'where is my payment?' enquiries.

    • CR Beneficiary's account at Cassia — USD 250,000.00
  9. OUTCOME
    Funds
    Debited from the customer on day one; credited to the beneficiary the next business day.
    Settlement
    Settled one value date later than instructed.
    Who acts next
    Meridian Bank (correspondent) — Operations at Bank Alfa answers the enquiry using the payment's trail and reviews cut-off schedules for this corridor.

THE TIMELINE

  1. 01Ordering customer
    Instructs a USD payment late in the day; Bank Alfa debits the customer and releases the payment.
  2. 02Bank Alfa
    The MT103 arrives at Meridian Bank after Meridian's cut-off for same-day USD processing.MT103
  3. 03Meridian Bank
    Queues the payment for the next business day — nothing is wrong with the message, only with the clock.

    Cut-offs vary by correspondent, currency, and product; they are commercial and operational, not scheme-defined.

  4. 04Bank Alfa
    The nostro reconciliation team spots that the expected debit is absent from the statement; an investigation case is opened and a free-format query goes to Meridian.MT940
  5. 05Meridian Bank
    Executes the payment next morning with the adjusted value date and forwards the MT103 to Cassia Bank.MT103
  6. 06Cassia Bank
    Credits the beneficiary one business day later than expected.

Resolution: The payment completes a day late. The investigation confirms a cut-off miss rather than a loss. Compensation for the lost value date is possible between the banks, but it depends on bilateral practice rather than any scheme rule.

MESSAGES INVOLVED

LEARN THE CONCEPTS

Sources for this scenario2
  1. Official requirement

    Swift Standards MT (annual standards releases) ↗ — Swift

    Defines the MT message standards (including MT101, MT103, MT202/202 COV, and the MT9xx statement messages) exchanged over the Swift FIN network, maintained through annual standards releases. · Checked 2026-07-12

    Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.

  2. Simplified educational illustration

    Payments Signal editorial teaching models — Payments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: Single-correspondent chain; institution-specific handling varies.

    Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.