CIR common mistakes
CIR · Understand the traps and how to avoid them.
Treating the UCP 600 documentary examination as a substance test: rejecting documents because the goods described seem wrong or the price looks odd, rather than checking whether the presented data conflicts with the credit, the other stipulated documents, or the UCP itself.
Candidates import general contract-law instincts or commercial common sense into a regime built on document autonomy and independence from the underlying sale contract. They forget that banks deal in documents, not goods, and that Article 14(d) sets the conflict standard against the credit and the data in the presentation, not against reality.
What to do instead
Before answering, recite the five-day examination window and the Article 14(d) data-conflict test, then classify each discrepancy as: conflicts with the credit, conflicts with another document, or merely unusual. Only the first two are discrepancies. Practise with presentations where the goods description is commercially implausible but the documents are compliant, and confirm you would honour them.
Applying a single sanctions list or a single ownership threshold when screening a counterparty, and clearing a payment because the named party is absent from one list, without checking the other applicable regimes (OFAC, EU consolidated, UN, UK OFSI, local lists) and the 50 percent ownership aggregation rule.
Candidates memorise one headline regime, usually OFAC, and treat screening as a name-matching exercise rather than a multi-jurisdictional, ownership-and-control analysis. They also overlook that a transaction can be lawful under one regime and prohibited under another, and that the strict-liability nature of most sanctions regimes removes the good-faith defence.
What to do instead
Build a screening checklist you can reproduce: identify every nexus (parties, currency, vessel, goods, correspondent, jurisdiction), list each regime engaged, then test both name matches and ownership/control aggregation. When a question gives a 40 percent plus 15 percent ownership structure, aggregate it. State explicitly that a hit requires escalation and blocking or rejection, not a judgement call by the front office.
Confusing the roles and liabilities of the confirming bank, the issuing bank, the nominated bank and the advising bank, for example assuming a nominated bank that has not confirmed owes the beneficiary a payment obligation, or that an advising bank guarantees the credit.
The terminology overlaps and candidates learn definitions in isolation without mapping obligations onto the document flow. They also miss that negotiation, acceptance and deferred payment undertakings differ in when and by whom payment is owed, and that a confirmation is a separate undertaking added to the issuing bank's.
What to do instead
Draw the four-party map for every question: applicant, beneficiary, issuing bank, and the bank in the beneficiary's country, then label which bank has given which undertaking. Memorise that advising carries no payment obligation, that a nominated bank without confirmation pays only if it has accepted or negotiated, and that the confirming bank is bound as if it were the issuing bank. Redo past questions by drawing the map first.
Answering FX exposure questions by naming the direction of the risk only, without converting the exposure into the reporting currency or netting offsetting positions, so the numerical answer or the hedge recommendation is wrong even though the concept is right.
Candidates understand transaction, translation and economic exposure conceptually but rush the arithmetic, mix up which currency appreciates, or forget that a payable and a receivable in the same currency offset. They also confuse the effect of a forward rate with the effect of the spot rate.
What to do instead
For every FX question, write the cash flows as signed amounts by currency and date before computing anything. State which currency you are reporting in, then translate. For hedging questions, verify the forward rate direction against interest rate parity logic. Do three arithmetic-only drills per study session so the mechanics become automatic.
Treating correspondent banking as a simple fee arrangement and missing the nostro/vostro mirror, the difference between a correspondent and a respondent, and the risk implications of nested or payable-through accounts for AML and sanctions exposure.
The nostro/vostro relationship is described from two viewpoints and candidates memorise one side only. Nested accounts are rarely taught with operational detail, so candidates cannot reason about why a respondent's downstream customers create indirect exposure for the correspondent and trigger enhanced due diligence obligations.
What to do instead
Anchor on one sentence: the nostro is our account held with you, the vostro is your account held with us, same account, different perspective. Then learn the risk chain: correspondent to respondent to nested respondent to underlying customer, and note that the correspondent cannot see the last link, which is why due diligence and transaction monitoring are heightened. Answer nested-account questions by tracing that chain explicitly.
Reading a payment message question as a general banking question and ignoring the specific message standard, field, and settlement finality rules, for example mixing up MT103 and MT202 purposes, or assuming a payment is final at the moment it is debited from the sender.
Candidates learn SWIFT message types as vocabulary rather than as instruments with distinct legal and operational roles. They also assume debit equals finality, missing that finality depends on the settlement system, the applicable law, and the point at which the receiving system accepts the transfer irrevocably.
What to do instead
Learn the message types by purpose: customer transfer versus bank-to-bank cover versus status and return messages. For finality questions, identify the settlement system named (RTGS, a deferred net system, a CLS settlement) and state the finality rule for that system. Never equate a debit entry with irrevocability unless the system's rules say so.
Performing a trade-based money laundering analysis by looking only at the goods price, without comparing quantity, quality, and shipping terms against the invoice and the credit, and without checking whether the trade route and vessel make commercial sense.
Candidates reduce TBML to over- and under-invoicing, which is the textbook example, and miss the other red flags: phantom shipments, multiple invoicing, falsely described goods, and carriage routes inconsistent with the counterparties. They also fail to connect the documentary credit data fields to each other.
What to do instead
Use a four-way cross-check on every trade scenario: price against market reference, quantity against weight and packing data, route and vessel against the parties' locations, and payment terms against the risk profile. If any pair is inconsistent, name the specific red flag rather than a generic concern. Practise identifying which document would reveal each inconsistency.
Applying home-country prudential rules to a cross-border lending question, or ignoring the host-country limits, transfer risk, and country risk overlay, and answering only on the borrower's creditworthiness.
Candidates study credit risk as a single-borrower analysis and treat regulatory capital and large-exposure rules as domestic. They miss that cross-border lending adds sovereign and transfer risk, that local regulatory limits may bind the subsidiary or branch, and that withholding tax and currency convertibility affect the expected return.
What to do instead
For each cross-border credit question, run a layered checklist: borrower credit, then country and transfer risk, then host regulatory limits, then home consolidated limits, then tax and currency effects. State which layer the question is testing. Memorise that a sovereign ceiling can cap a private borrower's rating in a weak-currency jurisdiction, and that transfer risk is distinct from default risk.
Mixing up the trade finance instrument's risk allocation, for example assuming a standby letter of credit and a documentary credit under UCP 600 are governed by the same rules, or that a bank guarantee is always payable on first demand regardless of the wording.
The instruments look similar on the surface and candidates learn names without the governing rule sets. They miss that standby credits are typically governed by ISP98 or URDG for guarantees, that demand guarantees turn on the wording of the demand condition, and that the fraud exception operates differently across these instruments.
What to do instead
Build a comparison table with columns for governing rules, payment trigger, documentary condition, and independence from the underlying contract, and fill it for commercial documentary credit, standby, demand guarantee, and surety. When a question names an instrument, first name its rule set, then apply only that rule set. Check whether the demand condition is documentary or conditional before deciding payment.
Answering market conduct questions by describing ethical good practice in general terms instead of naming the specific obligation, the timing requirement, and the record-keeping or disclosure rule that the scenario breaches.
Candidates treat conduct risk as a soft topic and revise it last, so they can recognise misconduct but cannot cite the concrete requirement, such as best execution, client order handling priority, conflicts disclosure, or the prohibition on misuse of confidential information. They also confuse internal policy with binding regulatory obligation.
What to do instead
For conduct questions, convert the scenario into a checklist: who is the client, what was disclosed and when, what record exists, and which specific rule governs. Learn the timing points, such as when an order becomes executable and when disclosure must precede the transaction. Answer by naming the breached obligation and the evidence that would prove compliance, not by describing good character.