The delayed supplier payment

Start where every investigation starts: what exactly did the customer ask for?

The instruction Asha Traders submitted (SYNTHETIC — TRAINING ONLY): Pay EUR 18,500.00 from our current account to Kestrel Fittings s.r.o., IBAN at Nordbank, for invoice KF-2214, value as soon as possible. Charges: shared.

Question: What has Asha Traders actually asked Bank Alfa to do?

Answer: Deliver EUR 18,500.00 in value to the supplier's account at Nordbank — by whatever route Bank Alfa chooses

Why: An instruction states an outcome — who gets how much, by when, who bears charges. Everything else (route, messages, correspondents) is the bank's execution of that outcome. Keeping the instruction separate from the execution is what lets you diagnose the execution without doubting the instruction.

Debrief: The instruction is the contract between customer and bank. Note the two facts you will reuse: charges are shared, and the customer asked for speed — both will matter when you explain the delay.

Name the role each party plays before you follow any money.

Question: Match each party to its role in this payment.

Answer: Owes the invoice and instructs the payment → Asha Traders; Debits the payer and originates the interbank leg → Bank Alfa; Carries the euro leg between the two banks as correspondent → Meridian Bank; Will credit the supplier once funds and details arrive → Nordbank; Waits for the invoice to be paid → Kestrel Fittings s.r.o.

Why: Five parties, five roles, and the two that customers never see — the agents' correspondent — is exactly where this payment will stall. Precise role names are not pedantry: they tell you whose books to look at for every question that follows.

Debrief: You now have the map. When anyone asks 'where is the money?', the answer is always 'on one of these parties' books' — there is nowhere else it can be.

Why does this payment travel through Meridian Bank at all?

Question: Bank Alfa sends the payment serially through Meridian Bank. Why?

Answer: Bank Alfa holds no euro account relationship with Nordbank, so it routes through a correspondent that connects them both

Why: Serial routing means the payment instruction and the funds move together, hop by hop, through the correspondent. Each hop is a real settlement across real accounts — which also means each hop is a place the payment can pause.

Debrief: One consequence of serial routing to hold on to: Meridian is not a bystander relaying mail. It processes the payment on its own books, under its own obligations — including its own sanctions screening.

Bank Alfa originated a pacs.008. Read the fields that matter for this case.

<CdtTrfTxInf>
  <IntrBkSttlmAmt Ccy="EUR">18500.00</IntrBkSttlmAmt>
  <ChrgBr>SHAR</ChrgBr>
  <Dbtr><Nm>Asha Traders</Nm></Dbtr>
  <Cdtr><Nm>Kestrel Fittings s.r.o.</Nm></Cdtr>
  <RmtInf><Ustrd>Invoice KF-2214</Ustrd></RmtInf>
</CdtTrfTxInf>

Question: Which statement correctly reads this fragment?

Answer: The banks settle EUR 18,500.00 between themselves, and each side's charges are borne by its own customer

Why: Two fields carry this case: the settlement amount tells you what to look for on every intermediate account, and the charge-bearer code tells you what the supplier should expect to receive. Both are facts you can quote, not opinions.

Debrief: Note what the message does NOT contain: money. It is the instruction travelling bank to bank. The value moves on the books — which is exactly where you look next.

Monday, 10:02: Bank Alfa executed. What happened on its books?

Bank Alfa's books, Monday 10:02 (simplified — SYNTHETIC — TRAINING ONLY): Dr Asha Traders — current account EUR 18500.00; Cr Nostro at Meridian Bank (our account, mirror) EUR 18500.00. Two-entry teaching view. A real bank also posts charges, control, and position entries, and account names vary by institution.

Question: Why is the nostro mirror CREDITED when Bank Alfa pays away?

Answer: The nostro is Bank Alfa's asset — money it holds at Meridian. Paying out of it reduces the asset, and an asset reduces by a credit

Why: The pair says: the customer has paid (their balance fell), and the bank expects to fund it from its money at Meridian (its asset fell). From Asha Traders' perspective the payment is 'gone' — but you can see precisely where it went: into the correspondent leg.

Debrief: You have now traced the money as far as Bank Alfa's sight extends: it sits with Meridian. Whether it moved onward is a question about Meridian's books — and Meridian's behaviour.

Wednesday: the tracker shows the payment reached Meridian on Monday and has not moved since. Precisely which legs have settled?

Payment tracker view, Wednesday 09:00 (SYNTHETIC — TRAINING ONLY): Mon 10:02 — Bank Alfa: pacs.008 sent to Meridian Bank; customer debited · Mon 10:03 — Meridian Bank: Payment received — status: pending processing · Wed 09:00 — —: No onward leg to Nordbank recorded

Question: Which statement is exactly right?

Answer: The Bank Alfa → Meridian leg is funded (the money sits on Bank Alfa's account at Meridian); the Meridian → Nordbank leg has neither cleared nor settled

Why: A serial payment is a chain of legs, each with its own clearing (agreeing the instruction) and settlement (moving the value). Diagnosis means naming the exact leg that stopped — here, inside Meridian, between receipt and onward processing.

Debrief: The money is not lost; it is parked, visibly, one leg short of the supplier's bank. Now the question changes from WHERE to WHY — what stops a correspondent from processing a clean-looking payment?

Meridian's status changes to 'compliance review'. Inside Meridian, an alert sits in Kabir's queue.

Kabir's alert, as the screening engine raised it (SYNTHETIC — TRAINING ONLY): Match candidate: beneficiary name 'Kestrel Fittings s.r.o.' scored 91% against list entry 'KESTRAL FITTING TRADING CO' (fictional training list). Fields differ: country, legal form, address. Engine action: payment held, alert routed to analyst.

Question: What is actually happening to this payment?

Answer: A name-similarity screening alert: the engine could not rule out a match, so it held the payment for a human investigator to decide

Why: Screening controls are built to pause on doubt. That pause is the system working, not failing: most alerts of this shape end as false positives, released with a documented reason. What decides the outcome is information — which is why the next move belongs to both banks.

Debrief: Kabir needs to distinguish 'Kestrel Fittings s.r.o.' from 'KESTRAL FITTING TRADING CO'. He can see the message; what he may lack is corroborating detail about the real beneficiary. Expect a request for information.

Meridian sends Bank Alfa a request for information (RFI): full beneficiary details, nature of business, invoice reference. Maya picks it up.

Question: What is Maya's correct reading of the situation?

Answer: The correspondent's screening held the payment on a name similarity; a complete, prompt RFI response is the fastest route to release

Why: Good operations work is matching the response to the actual failure mode. The evidence chain — held at correspondent, compliance status, name-similarity alert, RFI — points to one cause and therefore one fix: answer the RFI completely, through the proper channel, now.

Debrief: Notice what Maya did NOT need: access to Meridian's systems. The evidence visible from Bank Alfa — tracker states plus the RFI — was enough to name the cause with confidence.

Asha Traders is anxious and suggests: 'Just cancel it and send it again — maybe it will go through this time.'

Question: What should Bank Alfa actually do?

Answer: Answer the RFI immediately with complete beneficiary and purpose information, keep the original payment in flight, and set expectations with the customer

Why: The professional move is almost boring: give the control what it needs. Complete originator and beneficiary information is what payment-transparency practice exists for — the RFI answer lets Kabir document why the real supplier is not the listed entity, and release.

Debrief: Thursday 11:15: Kabir documents the mismatch — different country, legal form, address, and business — dispositions the alert as a false positive, and releases the payment. The onward leg settles; Nordbank credits Kestrel Fittings.

Write it twice: once for Asha Traders, once for the operations log. Different audiences, same facts.

Task: Draft (1) two or three sentences for Asha Traders explaining what happened and where their money was, and (2) two or three sentences for the internal log that another analyst could act on. Write both before revealing the model answer.

Model answer: To the customer: "Your payment was never lost — it was held for a routine compliance check at an intermediary bank because your supplier's name resembles an unrelated listed company. We supplied the confirming details, the check closed in your supplier's favour, and Nordbank credited them on Thursday. Nothing about your instruction was wrong, and no extra charge results." — To the log: "EUR 18,500.00 pacs.008, ref KF-2214, held at Meridian Mon–Thu: name-similarity alert on beneficiary vs fictional list entry; RFI received Wed, answered same day with full beneficiary details and invoice; false-positive disposition and release Thu 11:15; onward settlement and beneficiary credit confirmed. No duplicate initiated; customer informed."

Self-review checklist: Did the customer version avoid jargon (no 'pacs.008', no 'RFI') while staying truthful? · Did it say plainly that the money was safe and where it sat? · Did it protect the supplier's reputation — a similarity to someone else's name, not an accusation? · Did the log version carry the facts a colleague needs: amount, reference, leg, cause, dates, actions, outcome? · Did both versions avoid blaming any party for a control that worked as designed?

Self-review is reflective practice, not independently graded mastery.

Debrief: Self-review is reflective practice, not graded mastery — but the discipline is real: if you cannot explain the case in both registers, you have not finished working it.

A colleague challenges the file: 'How did you KNOW the funds were safe on Wednesday?' Point at the evidence, not at confidence.

Question: Which evidence chain actually proved the funds were safe mid-investigation?

Answer: Bank Alfa's posting into its nostro, the tracker showing receipt at Meridian with no onward leg, and Meridian's hold status — together they place the value on one known account under a documented control

Why: Auditable operations work rests on reconstructable chains: postings, message statuses, and control records that a third party could follow without you in the room. That is also exactly the record regulators expect a screening hold to leave behind.

Debrief: Every claim in your customer explanation traces to an artifact: ledger entries, tracker events, the RFI, the disposition record. That is what 'cite the evidence' means in a payments shop.

Close the file by testing your judgement against the paths not taken.

Task: In a few sentences, compare the chosen resolution (answer the RFI, keep the payment in flight) against the two rejected paths: cancel-and-resend, and wait-in-silence. For each, name the concrete risk it would have created in THIS case.

Model answer: Answering the RFI attacked the actual blocker — the investigator's information gap — so it was the shortest path to release, and it kept a single payment in flight with a clean audit trail. Cancel-and-resend would have re-entered the same screening control with the same name (no faster), created a window with two live payments worth EUR 37,000 between cancellation confirmation and re-initiation (duplicate risk), and complicated recall of funds already sitting under a compliance hold. Waiting in silence had the lowest effort and the highest cost: the alert could not close without the information, the supplier's invoice would age further, and the customer would reasonably conclude their bank had no idea where the money was. The general rule the case teaches: resolve the control, do not race it.

Self-review checklist: Did you name duplicate-payment risk (two payments in flight) for cancel-and-resend? · Did you note that a resent payment meets the same screening control again? · Did you identify that silence leaves the alert unresolvable by design? · Did you state the general principle — resolve the control rather than trying to route around it?

Self-review is reflective practice, not independently graded mastery.

Debrief: Done. You read an instruction, mapped five parties, traced value across three sets of books, separated clearing from settlement, recognised a screening control doing its job, chose the professional action, and explained it all with evidence. That is the whole craft in one payment.