How do you translate ISO 9362:2022 BIC and SWIFT code instructions without changing a bank identifier, confusing the beneficiary with an intermediary institution, or suggesting that a code guarantees a payment? Keep the code itself exactly as authorised, translate the surrounding financial roles with precision, and verify any operational claim separately. A business identifier code names an organisation or relevant branch for financial-service information; it is not an account number or proof that a particular transfer will succeed.
This guide addresses ISO 9362:2022 translation, BIC and SWIFT code meaning, eight-character versus eleven-character identifiers, branch codes, beneficiary bank instructions, non-connected BICs, bank-directory labels, payment forms and multilingual treasury documentation. It is written for translators, bank support teams, finance and treasury staff, software localisation teams and businesses exchanging cross-border payment instructions. The intent is to make institutional identifiers and their role labels dependable across languages, not to offer universal payment routing or investment advice.
Quick answer: preserve every supplied BIC character; keep organisation, branch and beneficiary-account fields separate; distinguish connected and non-connected identifiers; do not infer registration from format alone; confirm bank details through an authorised independent source; and test copied codes in the final multilingual document. When a payment instruction is uncertain, escalate rather than invent a valid-looking value.
- BIC identifies a business party; IBAN and local account identifiers answer different questions.
- Eight characters may be supplemented by an optional three-character branch identifier.
- Not every registered BIC is connected to the Swift messaging network.
- Payment and bank-detail changes need verified authorisation.
- Localized display must never alter identifier bytes.
The question a BIC translation must answer
A BIC is an institutional identifier, not a sentence that can be freely rewritten. ISO 9362:2022 sets out the structure of business identifier codes for financial and non-financial institutions involved in financial messaging. In practical translation, the code string stays unchanged while surrounding labels, roles, instructions and explanations may be localised. This prevents a bilingual document from pointing to a different organisation or making a payment role sound more certain than it is. A translator should ask four questions before editing: Which party does the identifier name? What role does that party play in this transaction? Is the identifier supplied by an authoritative source? Does the instruction describe a routing address, an account destination or merely a reference record?
Read the code without inventing its meaning
The familiar BIC consists of eight characters and can have an optional three-character branch identifier, giving an eleven-character form. Swift, as registration authority, describes the first four characters as a business-party prefix, the next two as an ISO 3166-1 country code, and the next two as a business-party suffix. The optional last three identify a branch or other specific location or service. That pattern is not a licence to invent a BIC for a business that has not been assigned one. Character syntax and actual registration are distinct questions. A string can look structurally correct but not identify any active registered entity. It is unsafe to claim that a code is valid solely because a regular expression accepts it.
Connected and non-connected BICs
Swift distinguishes connected BICs that can access its messaging network from non-connected BICs used as reference identifiers without that network access. Translators must preserve that distinction when localising onboarding manuals or treasury instructions. ‘Has a BIC’ is not equivalent to ‘can send Swift messages’. A bank or organisation may appear in reference data without being able to act as a network endpoint. An instruction that tells a counterparty to route a payment through a non-connected code may be operationally misleading. Check the current authoritative directory and applicable payment workflow before turning an identification statement into routing advice.
BIC is not IBAN, account number or LEI
The International Bank Account Number identifies an account in an internationally defined format where adopted; the BIC identifies a business party or relevant branch identity. An account holder can possess an IBAN and still need to provide a beneficiary-bank BIC under a particular scheme. Conversely, knowing a bank’s BIC does not identify the intended customer’s account. The Legal Entity Identifier is another distinct identifier used for legal-entity reference and regulatory purposes. Account identifiers, party identifiers, routing details, merchant identifiers and local clearing codes each answer different questions. Translation should not collapse them into one generic term such as bank code.
BIC as data and BIC as prose
If the source says ‘Enter the beneficiary bank BIC’, localise the instruction and keep the supplied BIC untouched. If the source labels a field ‘Sender BIC’, a translator should determine whether sender refers to a message-originating institution or to the customer authorising funds. These can be different. In payment screens, space is limited, but truncating ‘intermediary’ to ‘recipient’ changes the financial role. A good interface translation preserves field semantics even if it uses concise explanatory text alongside the field. When a value is unknown, show an unanswered field or controlled placeholder, not a plausible-looking bank code.
Why transaction roles matter
Banking instructions can involve an ordering customer, originating bank, intermediary or correspondent institution, beneficiary bank and beneficiary customer. The same party may perform more than one role in a simple transfer, but the labels are still not synonyms. A translator should establish who sends the message, whose account is debited, whose account is credited, which institution clears funds and which institution merely relays instructions. Do not confuse a payment’s business purpose with its messaging path. The safest workflow maps the source document’s role names to the payment system’s data model before approving human-readable translations.
Avoid the false authority of familiarity
‘SWIFT code’ is widely used by the public to mean BIC, yet precision matters in technical documents. The standard’s term is business identifier code, and not all BICs are network-connected. Similarly, a reference to head office might mean a location, a registration convention or a particular institutional function; do not assume that every code ending in XXX represents the only correct way to pay that bank. Use current directory records and the originating payment scheme’s instructions when this detail changes a payment. If you cannot verify it, retain the code and flag the claim for an authorised payment specialist.
Safe translation in cross-border payments
Payment instructions often bundle an organisation’s name, BIC, IBAN or local account number, address, country, intermediary details, amount, currency, fee option and purpose. A translation can be grammatically perfect yet send money to the wrong place if it interchanges the beneficiary and the intermediary or reformats a reference field incorrectly. For high-value, time-sensitive or compliance-sensitive transactions, financial staff should verify details through a trusted independent channel, especially after a request to change bank account information. The translator provides faithful language, not independent confirmation that the payment recipient is legitimate.
Version control, display and character safety
Treat assigned identifiers as immutable values within a translation project unless the authoritative source owner explicitly changes them. Preserve uppercase characters where presented, leading zeroes in adjacent account or reference numbers, and the difference between the Latin letter O and digit zero. Ensure line wrapping does not split a field that users must copy. In multilingual PDFs, test fonts, bidirectional text, right-to-left layouts and copied text to ensure the original sequence is preserved. For machine-readable files, keep identifiers in protected data fields rather than sending them through a string-localisation pipeline that may normalise punctuation.
A practical sign-off chain
The financial operations owner approves account and institution details. A data-governance or integration owner checks that fields map to the correct schema. A qualified language reviewer checks grammar, instructions, role distinctions and readability. A compliance reviewer may need to assess sanctions-screening or personal-data concerns. No reviewer should guess that a code has been registered, accepted by a payment rail or connected to Swift. The release packet should include the original value, source owner, relevant jurisdiction, approval version, target-market display and a note about unresolved exceptions. That evidence is more useful than an unexplained label saying ‘verified’.
26 distinct BIC and financial-message translation cases
The following cases are fictional teaching examples. Codes, where discussed, are conceptual rather than payment instructions. They illustrate the difference between faithfully translating a field and taking authority for bank routing, which belongs to the responsible financial institution and payment operator.
Case 1: Eight characters and eleven characters
Source: The supplier provides an eight-character BIC while the translated form demands exactly eleven characters. Failure mode: The translator appends XXX without consulting the authorised bank details. Controlled target meaning: Keep the supplied eight-character identifier and ask whether the receiving workflow truly requires a branch suffix.
Adding characters changes the transmitted identifier, even when a convention exists for branch references. A display interface’s validation rule is not authority to alter master data. The correct answer may be a different form configuration rather than a modified code. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Compare the trusted bank letter, current directory record and the payment platform’s exact requirements. Log the branch decision and approved value. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 2: A code that looks valid
Source: A four-plus-two-plus-two pattern matches a string typed by a customer. Failure mode: The bilingual help page declares that the institution is registered and reachable. Controlled target meaning: Explain that syntax checking is not registration or network-connectivity verification.
A plausible arrangement of letters and digits proves only that a field may have the right format. It does not prove the business exists, belongs to the intended recipient or can receive a payment. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Use current authoritative BIC reference data and an independent known contact to confirm details when necessary. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 3: Business prefix and organisation name
Source: A bank has rebranded its public-facing name, while its assigned BIC retains a historical prefix. Failure mode: The translation replaces the identifier’s first four characters to resemble the new name. Controlled target meaning: Keep the assigned BIC exactly and localise only the display name as approved.
Identifier prefixes are not editable marketing abbreviations. A historic prefix can remain valid after a merger or rebrand, subject to official records. Renaming its letters may create a different or nonexistent identity. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Check the bank’s authorised instructions and registry entry rather than deriving the code from brand spelling. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 4: Country code and place of payment
Source: The BIC contains a two-letter country code, but the customer’s transfer is in a different currency. Failure mode: The translation says the code proves the money will be settled in that country and currency. Controlled target meaning: Explain only the country component’s identity function, not settlement geography.
Currency, intermediary routing and settlement arrangements are separate parts of a payment. A two-letter component does not guarantee where all funds travel or which currency is supported. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Cross-check route and settlement claims against the payment provider, not the BIC text alone. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 5: Branch suffix and head-office assumption
Source: A document lists an eleven-character BIC ending in XXX. Failure mode: The target-language instruction calls it the head office and disallows any other branch. Controlled target meaning: Preserve the supplied code and verify the official branch description.
Common suffix conventions must not be promoted into universal operational rules. The intended payment destination comes from current verified instructions, not from a translator’s interpretation of the final letters. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Consult the registration details and the institution’s payment instruction sheet. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 6: Non-connected BIC
Source: A counterparty has a non-connected BIC for identification in reference records. Failure mode: The translated manual tells users to send a Swift message directly to that code. Controlled target meaning: Say it identifies a party but does not itself establish messaging connectivity.
Conflating reference identity and network access can cause messages to fail or lead users to route through the wrong participant. The public label ‘SWIFT code’ encourages this mistake. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Check the BIC’s connectivity attribute and the applicable payment channel before approving routing text. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 7: BIC and bank account
Source: An invoice displays a beneficiary BIC plus a separate account identifier. Failure mode: The target invoice labels the BIC as the account number. Controlled target meaning: Translate the BIC as an institutional code and account data separately.
An identifier of an institution cannot uniquely designate the recipient’s account. This distinction matters even if the two fields appear next to one another in a bank details table. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Check the invoice template field names against the finance master-data schema. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 8: BIC and IBAN
Source: An EU payment instruction lists an IBAN and a BIC. Failure mode: The translation replaces the IBAN heading with ‘bank code’. Controlled target meaning: Keep the IBAN as the account identifier and the BIC as the business-party identifier.
Different payment systems may require different combinations of these values. Translating both into one label can lead a user to omit data or enter it in the wrong field. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Confirm field-level validation, country-specific requirements and scheme instructions. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 9: BIC and LEI
Source: A counterparty registration form includes BIC and LEI in adjacent columns. Failure mode: The translation combines them under one heading ‘company identifier’. Controlled target meaning: Keep separate field labels explaining the financial messaging identity and legal-entity reference.
Both values may identify aspects of a business but serve different data ecosystems. A business can hold both, one or neither depending on context. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Trace each field to its designated registry and downstream use. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 10: BIC and local clearing code
Source: A remittance form asks for the BIC and also a local branch or routing number. Failure mode: The target says to enter either one interchangeably. Controlled target meaning: Describe the values as separate identifiers and follow the particular payment rail.
An ABA number, sort code, BSB or other national clearing code does not automatically perform the same task as a BIC. Some channels require both. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Ask the payment operations team which identifier belongs to which network and field. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 11: Beneficiary bank versus beneficiary
Source: The source distinguishes beneficiary bank BIC from beneficiary customer name. Failure mode: The translated form says the beneficiary is the bank. Controlled target meaning: Keep bank identity and the ultimate recipient of funds distinct.
An individual or company can receive funds through an institution without being that institution. Mislabelled forms confuse payers and can affect validation. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Review the complete payment-chain diagram and confirm the owner of each field. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 12: Intermediary bank
Source: A payment instruction lists an intermediary bank BIC and a receiving bank BIC. Failure mode: The target text swaps their order. Controlled target meaning: Retain the exact institutional roles and code-to-field associations.
The intermediary can relay or support the payment route; it is not necessarily the bank holding the recipient’s account. Field order alone does not define function. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Match each label to its source field and confirm with authorised routing instructions. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 13: Ordering institution versus ordering customer
Source: A transaction record includes the financial institution that sends a message and the customer who ordered payment. Failure mode: The translation uses ‘sender’ for both without qualification. Controlled target meaning: Distinguish sender institution from ordering customer where the schema does.
Ambiguous role words can mislead audit teams about who initiated instructions and who carried them over a network. A legal person and a technical endpoint are not synonymous. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Check message definitions and the payment operator’s glossary. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 14: Payment confirmation versus routing instruction
Source: A bank letter says funds have been instructed for transfer, not confirmed credited. Failure mode: The target-language email says funds have arrived. Controlled target meaning: Preserve the difference between initiation, acceptance, settlement and beneficiary credit.
A payment instruction can be accepted without completed settlement. Misrepresenting status creates disputes and may affect inventory release or contractual deadlines. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Locate the actual transaction event and approval timestamp before choosing completion verbs. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 15: Connected BIC versus active account
Source: A bank’s BIC has Swift connectivity, but the beneficiary account may be closed. Failure mode: The translation assures the customer that funds will be received. Controlled target meaning: State network connectivity as a property of the institution, without claiming account status.
A messaging endpoint does not validate any specific customer’s account or entitlement. Verification must be performed through the correct banking process. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Ask the beneficiary and banking team to check account details through trusted channels. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 16: BIC directory display name
Source: The official registry uses a legal name different from the institution’s brand. Failure mode: A localized payment page discards the legal reference and shows a translated brand only. Controlled target meaning: Keep the controlled identifier and preserve the legal identity where required.
A public brand may be useful for recognition, but it need not be the same as the registered business party. Clearing systems can compare names and identifiers. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Keep separate display name, legal name and registered identifier fields. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 17: Mixed scripts and right-to-left interfaces
Source: An Arabic screen places an eleven-character Latin BIC near right-to-left explanatory text. Failure mode: Copying the value reverses character order. Controlled target meaning: Use a protected left-to-right data span and test the copied value.
Bidirectional layout can visually reorder alphanumeric values without changing the source text. Users may send the wrong string if they transcribe from a misleading display. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Test with native speakers, screen readers and paste into a raw-text editor. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 18: Letter O and digit zero
Source: A scanned bank letter contains an ambiguous O/0 character. Failure mode: The translator substitutes the visually familiar alternative. Controlled target meaning: Do not guess; confirm the original registered code from an authorised source.
Optical recognition and typeface ambiguity can change a real identifier into a false one. Some characters may be legal in a given position and others may not, but syntax is only a first check. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Read the original digital source, compare the authoritative directory and record the verified value. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 19: Copy-and-paste line wrapping
Source: A PDF breaks the BIC across two lines in a mobile view. Failure mode: The translated PDF inserts a space inside the code. Controlled target meaning: Keep a contiguous identifier and verify text extraction.
Display typography must not corrupt data. A human reader may ignore a line break while software ingests an embedded space as part of the value. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Copy the code from rendered PDF into plain text, compare character by character and test mobile display. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 20: Currency description
Source: A transfer in USD uses a BIC whose country letters refer to a different nation. Failure mode: The translation changes the payment amount to that country’s local currency. Controlled target meaning: Preserve the explicit currency and amount separately from bank identity.
BIC geography does not determine transaction denomination. Converting a figure without instruction could cause a major payment error. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Cross-check ISO currency code, amount, account denomination and exchange instruction if provided. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 21: Bank merger
Source: A sender supplies an old bank code after an institutional merger. Failure mode: The translator substitutes a newer code mentioned on a public blog. Controlled target meaning: Do not modify the payment value without a trusted instruction from the financial owner.
Mergers can lead to transitions, redirects or temporary parallel identifiers. A translator cannot know from public branding which code applies to a specific account and scheme. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Request a current bank-issued instruction and keep a versioned record of the change. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 22: Fraudulent change request
Source: An email asks a translator to replace a beneficiary BIC and bank account at the last minute. Failure mode: The translator treats it as a harmless terminology correction. Controlled target meaning: Freeze the existing verified payment details and escalate the change to the finance approver.
Business-email compromise often relies on urgent changes that look like routine administration. Translation workflows must not bypass payment verification controls. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Use an independently verified communication channel already on file; do not reply to the suspicious email alone. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 23: Public invoice template
Source: A template includes dummy bank details for a training workbook. Failure mode: The translation presents the examples as a live destination for real payments. Controlled target meaning: Label all sample identifiers as fictional and not for actual transfers.
An illustrative string must not inadvertently become a plausible instruction to pay an unknown recipient. The training use and real-world use should be unmistakably separated. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Use unambiguously labelled placeholders, avoiding real customer data and live account numbers. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 24: Beneficiary reference field
Source: An international payment form has a beneficiary reference distinct from the BIC. Failure mode: The translation moves invoice numbers into the institution-code field. Controlled target meaning: Keep reference and identity fields independently.
Payment reconciliation needs the remittance reference while routing needs institutional identities. Swapping them can lead to rejection or a payment that cannot be matched to an invoice. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Compare the translated form with the API schema and a dummy end-to-end transaction. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 25: Swift network versus standard name
Source: An onboarding page refers to ISO 9362 but does not promise participation in any messaging network. Failure mode: The target-language heading becomes ‘Swift-connected bank’. Controlled target meaning: Use the accurate standard name and describe connectivity only when verified.
Many readers treat BIC and Swift code as synonyms, but a reference to a standard cannot establish operational network participation. Terminology should not add an implied guarantee. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Compare the exact statement against Swift’s registry information and the bank’s stated service. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Case 26: Active directory entry and outdated screenshot
Source: An archived manual shows bank details captured two years ago. Failure mode: The translation treats the screenshot as the current payment instruction. Controlled target meaning: Preserve its archival date and require a fresh source before operational use.
A historical screenshot can be a valid record of what staff were told then, while being unsafe as current guidance. Language revision should not erase the temporal distinction. The bilingual reviewer should look beyond vocabulary and ask whether the translated instruction would make the user select a different field, institution, branch or transaction state. If it could, the discrepancy is substantive, not cosmetic. Do not repair operational uncertainty by writing a more confident sentence than the source.
Verification: Record the edition, capture date, owner and retrieval date; ask finance whether the bank detail remains current. Retain the original identifier and a record of the authorised decision. Practical reader check: Read the target as someone entering details for the first time. Can that person distinguish the organisation being identified, the account receiving funds and the institution relaying the payment? A successful translation makes those distinctions without asking the customer to infer them from banking jargon.
Worked translation: a multilingual supplier onboarding pack
Imagine a manufacturing company registering an overseas supplier. The source workbook has columns for the supplier’s legal name, beneficiary name, beneficiary-bank BIC, beneficiary account, local clearing code, intermediary-bank BIC and remittance reference. A quick machine translation maps all five banking fields to the same local expression for ‘bank number’. The completed target workbook would be easy to read but dangerous to submit. The correct intervention is to establish a field dictionary first, preserve each data type and use separate visible descriptions. An optional explanatory tooltip can teach the user what belongs in each field without changing its identity.
A test record should use unmistakably fictional placeholders instead of real customer banking details. Fill each column once and compare the exported spreadsheet, web form and generated PDF. Pay special attention to leading zeroes in non-BIC reference fields, scientific notation in spreadsheets, RTL text display and autocorrection. The banking team should sign off the exact field mapping. The language reviewer signs off instructions and names. Those are separate approvals because perfect grammar cannot fix a routing-data mismatch.
Worked translation: a supplier changes banking instructions
Assume an invoice arrives with a notice that bank details have changed. A bilingual assistant receives the change request and updates the translated payment instructions because the email seems to come from the usual supplier. The actual risk is not translation accuracy; it is whether the change was authorised. A language team should preserve the received message for evidence while refusing to let it modify financial master data outside the approved workflow. The authorised accounts-payable team should verify the change through a known independent channel.
If the bank details are genuinely updated, the final bilingual invoice template must change consistently. Record the effective date, account owner, old and new versions, the person who approved the change and which open invoices use which details. Do not translate historic invoices retrospectively to show a new BIC, because that would destroy evidence of what the payer was told at the time. The correct record distinguishes the old valid instruction, the newly approved instruction and the point at which staff changed their process.
Worked translation: a bank merger and institutional identity
A company encounters a historic institution name, an old BIC in contract annexes and a new public brand after a bank merger. It is tempting to replace every occurrence of the former name and its associated identifier. That would conflate archival translation with current payment guidance. For a legal archive, preserve the historical names and identifiers in their dated context. For a live payment template, obtain current authorised instructions and verify the relevant accounts and payment rail. A single translation-memory replacement rule is not suitable for both purposes.
Where brand recognition is useful, include a controlled note approved by the bank or treasury owner, such as a current display name linked to a historic legal name. Avoid claiming that any apparent predecessor-successor relation proves one BIC can be substituted for another. The financial reference data must decide that; language editing only makes the distinction understandable.
Data dictionary for translators and implementers
Build a field specification that records data type, allowed length, source system, authoritative owner, translation policy, validation method and example user error. For the BIC itself, the translation policy is ordinarily ‘do not translate value’. For the field label, the policy is ‘translate with controlled terminology’. For legal name and address, the policy can depend on jurisdiction and official registration. For account numbers and reference data, preserve characters and leading zeroes. For payment statuses, map each verb to the source event taxonomy rather than a generic phrase such as completed.
In software, identifiers should be stored and transmitted as data values, not mixed with localised narrative text. Test the export path: web form to backend, backend to confirmation email, email to PDF and PDF back to copied text. Compare exact string values at every point. If a localisation library normalises digits or reverses display order, treat it as a defect rather than assuming that human readers will compensate.
Glossary governance and specialist escalation
Use one concept record for each distinct role: business party, beneficiary bank, ordering institution, intermediary bank, beneficiary customer, account identifier, remittance reference and network connection status. A termbase entry needs a definition, approved translation, disallowed near-synonyms, evidence source and reviewer. The reviewer should record whether a phrase is consumer-facing explanatory wording or a machine-schema label. Consumer text may be made clearer; schema labels must map exactly to the system meaning.
Escalate if a document claims that a BIC establishes account ownership, payment settlement, sanctions approval or network access. Those are not translation conclusions that can be drawn from the code alone. When a payment might be affected, obtain a decision from the appropriate bank, treasury or compliance owner. Release multilingual material only after exact identifiers, field mappings, display order and instructions pass separate checks.
Questions and answers about translating BICs
What is the difference between BIC and SWIFT code?
BIC is the identifier standardised by ISO 9362; SWIFT code is a widespread public label. Not every BIC has Swift network connectivity, so operational statements should be precise. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
Can a BIC be eight or eleven characters?
Yes. The common form has eight characters, with an optional three-character branch element. Do not invent characters merely because a form seems to expect eleven. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
Does a BIC identify a bank account?
No. It identifies an organisation or a relevant branch identity. A specific customer’s account requires separate account data. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
Does a registered BIC guarantee successful payment?
No. Registration does not validate an individual beneficiary account, sanction status, routing permission or payment acceptance. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
Can I derive a BIC from a bank’s name?
No. The business prefix is assigned, not a translator-controlled abbreviation. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
Does a country component prove settlement location?
No. Payment routing, currency and settlement arrangements cannot be inferred from those two characters alone. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
What is a non-connected BIC?
A registered identifier used for reference purposes without access to the Swift messaging network; it should not be described as a direct messaging endpoint. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
How is BIC different from LEI?
BIC is oriented toward business-party identification in financial messaging, while LEI identifies legal entities in another global reference system. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
Should an old BIC be silently replaced after a merger?
No. Ask for authorised current account and routing instructions. Keep the historic value in archival records where it documents the past. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
How do I handle a code in Arabic, Hebrew or another right-to-left layout?
Preserve the original Latin character order, protect copying and test rendered text and screen-reader behaviour. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
Who should validate the bank details?
A finance or banking operations owner using trusted records, not the translator alone. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
Do international transfers always require a BIC?
Requirements vary by scheme, country, currency and provider. Use current instructions for the actual payment rail. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
What if the recipient sends replacement details by email?
Use independent verification through trusted channels and the organisation’s change-control process before changing payment data. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
What should I translate in a payment message?
Localise labels and explanatory language while preserving protected identifiers, role mappings, exact amounts, dates and documented status. For a live transaction, the institution and relevant payment service must still confirm the actual data and routing requirements.
Official references and connected learning
See the official ISO 9362:2022 catalogue for the published fifth edition and scope; and Swift’s BIC explainer for the registration authority’s summary of structure and connectivity. The published ISO standard is copyrighted; this article is an independent educational translation guide, not a reproduction or a guarantee of conformance.
Broader method: Master Art of Translation | The Complete System for Moving Meaning Between Languages. Language support: Vocabulary Learning Hub and How English Works | Translation and Meaning Across Languages. This article remains a specialist financial-identifier guide rather than a competing translation hub.