NIBAF Foreign Trade common mistakes
NIBAF Foreign Trade · Understand the traps and how to avoid them.
Counting UCP 600 deadlines in calendar days instead of banking days, and treating the examination period and the refusal-notice period as two separate clocks - e.g. answering that a bank has 'seven calendar days to examine and then three days to refuse' a presentation.
Candidates memorise isolated numbers ('5 days', '21 days', '3 days') without anchoring each to its article or to the day it runs from, and they import the pre-2007 UCP 500 'reasonable time' reasoning they may have read in older commentary.
What to do instead
Build a one-page timeline table that states, for each rule, (a) the article, (b) the number, (c) banking or calendar days, and (d) the trigger day. Drill it with questions phrased from each direction: 'day of presentation is Monday, what is the last refusal day', and 'shipment was on 1st, expiry on 30th, is a 25th presentation timely'. Note expressly that refusal must be a single notice and that silence beyond the maximum period triggers preclusion.
Using 'confirming', 'advising', 'negotiating' and 'issuing' bank interchangeably, and asserting that an advising bank is liable to pay the beneficiary if the issuing bank defaults.
In practice many banks act in several capacities on the same credit, and study notes often describe a bank by what it did on one transaction rather than by the undertaking it gave. The word 'confirm' is also loosely used in ordinary business English to mean 'acknowledge receipt'.
What to do instead
For each role write the exact undertaking in one sentence and memorise the party that carries it: advising bank = authenticates and transmits, no payment undertaking; confirming bank = adds its own independent undertaking to honour or negotiate; nominated bank = authorised to act, but not obliged unless it has accepted/negotiated/incurred a deferred payment undertaking. Then practise by drawing a four-column table (role / obligation / when it arises / recourse) and answering scenario questions by naming the obligation, not the bank.
Treating documentary collections as if banks guarantee payment, and swapping D/P for D/A when the question describes release of documents against a bill of exchange that the drawee has accepted rather than paid.
Candidates carry over letter-of-credit thinking ('the bank pays') into a non-credit product, and they read 'against acceptance' as a stronger, safer variant because acceptance sounds like a commitment by the bank rather than by the buyer.
What to do instead
State the URC 522 position as a rule you can recite: banks act on instructions, deal in documents and not in goods, and give no payment undertaking to the seller; the collecting bank releases documents only as instructed. Then contrast D/P (documents released only on payment) with D/A (released on acceptance of the bill by the drawee, creating a trade acceptance, not a bank liability). Test yourself by asking 'who bears the non-payment risk?' for each and answering 'the principal/seller', never the remitting bank.
Answering guarantee questions by applying UCP 600 to a demand guarantee or standby, or by describing an on-demand bank guarantee as payable only after proof of the underlying default.
All three instruments sit under the same 'bank comfort' heading in revision notes, and candidates default to whichever rulebook they studied most recently; the word 'guarantee' in ordinary usage also implies proof of loss.
What to do instead
Fix three anchors: a demand guarantee is an independent, documentary, pay-on-first-written-demand undertaking governed (if incorporated) by URDG 758; a standby LC is likewise independent but typically governed by UCP 600 or ISP98 when so stated; a surety/contract bond of the accessory type is the exception where the underlying default matters. When answering, first identify which rulebook the instrument text incorporates, then apply that rulebook - never assume.
Placing the point of risk transfer in CIF/CIP at the destination port/place, or treating an Incoterm as deciding when the buyer must pay - and citing an outdated Incoterms edition alongside a rule that changed (e.g. DAT for delivered at terminal).
CIF feels like 'the seller delivers it to me', so cost and risk get merged; and candidates learn Incoterms from summary tables that omit the edition year, so they repeat superseded rule names.
What to do instead
Learn Incoterms by two axes only: where risk passes (the critical point) and who contracts/pays for carriage and insurance - and repeat aloud that CIF/CIP pass risk at the point of shipment, not arrival. Attach the edition year (Incoterms 2020) to every rule you cite, and note that DPU replaced DAT. Add one line to every answer: Incoterms govern delivery, cost and risk, not title, payment method or the price itself.
On export questions, describing shipment and invoicing correctly but omitting the regulatory loop - the export declaration form, bank certification/endorsement and the requirement that proceeds be realised and repatriated within the prescribed period - or ignoring that payment came from a party other than the consignee.
Candidates study the commercial documents (invoice, packing list, bill of lading) as the whole of 'export documentation' and treat exchange-control steps as back-office routine not worth an exam sentence.
What to do instead
Build a 'documentation chain' checklist for exports that runs consignment → declaration form → bank certification → shipment → documents through the bank → realisation/repatriation → closing the loop, and answer with that chain in order even when the question only asks about one stage. Keep a separate short note that the realisation period and the permitted methods of payment are set by the regulator's foreign exchange manual rather than by the contract, and that receipts from a third party require justification and bank acceptance.
Answering regulatory questions from general banking practice rather than from the specific instrument - e.g. stating that an authorised dealer can approve any transaction so long as the customer's KYC is complete, instead of identifying whether the matter falls to the central bank, the authorised dealer under delegated limits, or another authority.
Because the answer 'sounds right' operationally, candidates never check whether approval authority is delegated, conditional or reserved; they also assume foreign exchange rules are static and quote a remembered position without checking the current circular.
What to do instead
For each topic area keep a two-column note: 'who may approve' and 'what condition attaches'. Answer questions by first naming the source (the foreign exchange manual chapter, the relevant circular/notification cited in the syllabus, or the statute) and then the authority. Where the question turns on a limit or threshold, say explicitly that the current circular governs and describe the rule's structure rather than guessing a figure.
Mixing up SWIFT message types and the nostro/vostro relationship - for example calling an MT103 a guarantee of payment, using MT202 to describe a customer transfer, or confusing MT700 (issue of a documentary credit) with MT760 (guarantee/standby).
Message numbers are learned as a list without the underlying flow of funds versus flow of information, and nostro/vostro are mirror images of the same account so candidates flip them under time pressure.
What to do instead
Group messages by function, not by number: customer payment (MT103), bank-to-bank cover/settlement (MT202), credit issuance and amendment (MT700/MT701/MT707), guarantee and standby (MT760/MT767), documentary collections (MT400/MT410). For accounts, memorise from the account holder's viewpoint: 'our account with you is nostro; your account with us is vostro' and test it from both sides. Add one sentence to every payment answer separating settlement from information.
Detecting trade-based money laundering only through customer identity checks, and missing the transaction-level anomalies - over- and under-invoicing, misdescribed or phantom goods, multiple invoicing, gratuitous consignments, third-party payers, free-trade-zone round trips, and vessel or route inconsistencies - or failing to escalate because a suspicious transaction was declined rather than completed.
KYC and CDD frameworks dominate AML study time, so the trade-specific red flags look like anecdote; and attempted transactions feel 'uncompleted' and therefore not reportable.
What to do instead
Keep a trade red-flag sheet organised by layer: customer, counterparty, goods and pricing, documents, shipping and route, and payment. Apply it as a mandatory step on every trade scenario question - name at least two flags before concluding. State explicitly that a suspicion arising from an attempted or declined transaction still triggers escalation and reporting through the bank's compliance channel, and that the obligation is to report suspicion, not to prove the crime.
Treating an irrevocable letter of credit as eliminating risk, so the risk question is answered only with 'the bank pays', with no mention of country/transfer risk, issuing-bank risk, document risk, or the fact that a confirming bank's undertaking is only as good as the confirming bank and its country.
The exam narrative stresses that an LC substitutes bank risk for buyer risk, and candidates stop at that substitution instead of decomposing residual risk; they also confuse the mitigation instrument with the risk it addresses.
What to do instead
Use a fixed four-way split on every risk question: commercial (buyer/seller), bank (issuing/confirming bank solvency), country and transfer (convertibility, moratorium, FX availability), and documentation/operational (discrepancies, fraud, legal). Then name the matching mitigant for each - confirmation, insurance or ECA cover, credit limits and country limits, and discrepancy-prevention/document checking. Close by stating one residual risk the chosen mitigant does not remove.