How to understand and trace pending, delayed, returned and rejected bank transfers

Why this matters

Pending, delayed, returned and rejected are distinct processing states; the fastest way to resolve ‘missing’ money is to get the correct trace token from the sender (ACH trace number for U.S. ACH, or UETR/MT103 for SWIFT) and provide exact transaction details to your bank.

What pending, delayed, returned and rejected mean

Pending / in‑flight means the originator bank has sent the instruction but final credit hasn’t occurred yet. The payment may be moving through intermediaries, waiting a cut‑off, or queued for screening or manual review.

Delayed / investigated means the payment is being held for additional checks: compliance (AML/KYC), screening, missing beneficiary details, or operational exceptions. Time to resolution depends on the rail and whether a formal trace is opened.

• Pending: instruction sent but not settled.
• Delayed: held for compliance or operational review.
• Returned: funds sent back to originator with a return reason.
• Rejected: not accepted for processing (format/routing/sanctions).

Identifiers banks need to trace a transfer

For U.S. ACH the single most useful token is the 15‑digit ACH Trace Number plus the originating routing (ODFI) and originating company ID. These are the fields the FedACH PTR references as required to match an item in the clearing system.

For cross‑border SWIFT wires the primary trace token is the UETR (36 characters) and the related payment message (MT103 or ISO 20022 pacs.008). Many banks can also trace using field 20 (transaction reference), BICs, value date and exact amount.

• ACH trace number (15 digits) — critical for FedACH traces.
• Originating routing (ODFI) and company ID — helps match files.
• UETR (36 chars) — primary token for SWIFT gpi tracking.
• MT103 / pacs.008 copy — documentary proof for recipient banks.

Who requests traces and how long it takes

The originator’s bank (sender) can run the authoritative trace; a beneficiary’s bank will generally require the sender to provide the trace token or an MT103/pacs.008 copy before completing its own investigation. For ACH in the U.S., FedACH defines a Payment Trace Request (PTR) process banks use to locate items.

Response times vary: some rails and gpi‑enabled SWIFT participants offer near‑real‑time status via UETR; ACH traces typically take business days depending on cut‑offs and investigation complexity. Do not assume funds are lost until you receive a formal returned status.

• Sender’s bank is the primary actor to verify the debit and provide trace tokens.
• FedACH PTR is the formal U.S. ACH trace mechanism.
• SWIFT gpi + UETR give much faster end‑to‑end visibility when participants support gpi.
• Investigation timelines vary by bank and corridor.

Practical steps and what to give your bank

Ask the sender first for the trace token — ACH Trace Number for U.S. ACH, or UETR/MT103 copy for SWIFT wires. Banks often refuse to start formal traces without that token because it is the quickest way to match and confirm movement through the rails.

Provide a concise evidence pack to your bank: exact amount and currency, value/initiation date and time, sender and receiver names and account numbers, any booking/confirmation receipt, and screenshots of the debit from the sender’s account statement if available.

• For ACH: beneficiary name, account, exact amount, date, ACH Trace Number, ODFI routing.
• For SWIFT: UETR or MT103/pacs.008, amount, value date, sender/beneficiary accounts and BICs.
• Include any return code or text shown on your statement (NACHA return codes for ACH).
• Use secure channels and avoid sending full credentials over insecure messages.

Practical checklist

• Ask the sender for the ACH Trace Number (15 digits) — or UETR (36 chars) / MT103 copy for SWIFT.
• Record and provide exact amount, currency and value/initiation date to your bank.
• Provide sender and beneficiary names, account numbers and BICs if available.
• If in the U.S. ACH rail, request your bank to submit a FedACH Payment Trace Request (PTR).
• Keep booking confirmations, screenshots or PDFs of the debit and any return messages.