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

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

GET IN TOUCH
SEPA CREDIT TRANSFER

Not enough money to send: an SCT rejected at the first gate

Trigger: The debtor's account cannot cover the transfer when Bank Alfa validates the instruction.

Contributor Shubham Mathure

What operations sees first: The payment never appears in the outbound clearing file; the customer sees a rejected status in the initiation channel almost immediately.

WHERE IS THE MONEY?

Never left the debtor's account — no debit was ever booked.

DID SETTLEMENT HAPPEN?

No interbank clearing or settlement occurred; the pacs.008 was never created.

WHO ACTS NEXT?

Bank Alfa (debtor agent) The debtor funds the account and resubmits. Operations has nothing to repair — a clean reject at initiation is the system working as designed.

PLAY THE EXCEPTION

Trigger: The debtor's account cannot cover the transfer when Bank Alfa validates the instruction.

STEP 1 / 4MESSAGE

The debtor initiates the transfer

Debtor (payer) → Bank Alfa (debtor agent) · pain.001

The customer instructs their bank to pay. A corporate typically sends a pain.001 file; a retail customer uses a banking channel that creates the same instruction internally.

Step 1 of 4: The debtor initiates the transfer

  1. 01Message
    The debtor initiates the transferDebtor (payer) → Bank Alfa (debtor agent) · pain.001
  2. 02Processing
    Bank Alfa validates the instructionBank Alfa (debtor agent)
  3. 03 · EXCEPTION PATHProcessing
    Bank Alfa refuses the instructionBank Alfa (debtor agent)
  4. 04 · EXCEPTION PATHMessage
    The debtor receives a rejection statusBank Alfa (debtor agent) → Debtor (payer) · pain.002
  5. OUTCOME
    Funds
    Never left the debtor's account — no debit was booked.
    Settlement
    No interbank clearing or settlement occurred.
    Who acts next
    Bank Alfa (debtor agent) — The debtor funds the account or amends the instruction and resubmits.
Full step-by-step text (works without JavaScript)
  1. 01Message
    The debtor initiates the transferDebtor (payer) → Bank Alfa (debtor agent) · pain.001

    The customer instructs their bank to pay. A corporate typically sends a pain.001 file; a retail customer uses a banking channel that creates the same instruction internally.

  2. 02Processing
    Bank Alfa validates the instructionBank Alfa (debtor agent)

    The debtor agent checks the format, the IBAN, available funds, and runs compliance screening before accepting the instruction for execution.

    Screening checkpoint: Debtor-agent transaction screening — Names and remittance data are screened against sanctions lists before the payment goes interbank.

  3. 03 · EXCEPTION PATHProcessing
    Bank Alfa refuses the instructionBank Alfa (debtor agent)

    Validation fails on available funds. Because nothing has gone interbank yet, this is the cheapest possible failure point — nothing needs to be unwound.

  4. 04 · EXCEPTION PATHMessage
    The debtor receives a rejection statusBank Alfa (debtor agent) → Debtor (payer) · pain.002

    A pain.002 status report tells the customer the instruction was rejected and carries a reason code so the failure can be fixed.

  5. OUTCOME
    Funds
    Never left the debtor's account — no debit was booked.
    Settlement
    No interbank clearing or settlement occurred.
    Who acts next
    Bank Alfa (debtor agent) — The debtor funds the account or amends the instruction and resubmits.

THE TIMELINE

  1. 01Debtor
    Submits a credit transfer instruction for EUR 12,500 through the online channel.pain.001
  2. 02Bank Alfa
    Validates the instruction and finds the available balance will not cover the amount.

    The failure happens before any debit is booked and before anything goes interbank — the cheapest possible failure point.

  3. 03Bank Alfa
    Sends the debtor a rejection status report carrying reason code AM04 (insufficient funds).pain.002
  4. 04Debtor
    Funds the account, or lowers the amount, and resubmits the instruction.

Resolution: The instruction dies at validation. Nothing needs to be unwound because nothing moved: no debit, no clearing, no settlement. The reason code in the pain.002 tells the customer exactly what to fix.

MESSAGES INVOLVED

LEARN THE CONCEPTS

Sources for this scenario2
  1. Scheme-specific rule2025 version 1.1 (EPC125-05)

    2025 SEPA Credit Transfer rulebook ↗ — European Payments Council · reject provisions

    Governs the SEPA Credit Transfer scheme: participant obligations, datasets, time cycles, and r-transaction rules for euro credit transfers. · Effective 2025-10-05 · Checked 2026-07-12

    Version 1.1 replaced version 1.0 at publication on 5 October 2025 and is stated to remain in effect up to 21 November 2027. It moves the date from which the unstructured address format is no longer permitted to 15 November 2026.

  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-CSM model; 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.