top of page
Search

Do FINRA Rules Require Translating Customer Communications?

1 day ago
9 min read

Bilingual reviewers compare a Spanish investment brochure

FINRA does not publish a general rule that obliges a broker-dealer to translate customer communications. When a firm does communicate in another language, the same content, supervision and recordkeeping rules apply to the translated version. Rule 2210 governs content, Rule 3110 governs supervision, and SEC Rule 17a-4 governs retention.



Table of Contents

 

 

What does this question cover?

 

This reference covers U.S. broker-dealers that are FINRA members and that send, or plan to send, communications to customers or prospects in a language other than English. It addresses three questions: whether translation is required, which rules apply once a firm translates, and which controls document compliance.

 

Document types in scope

 

  • Retail communications such as websites, brochures, social posts and advertisements.

  • Account opening documents, disclosures and customer notices.

  • Investor presentations and enrollment presentations delivered through an interpreter.

  • Correspondence and internal communications that discuss translated material.

 

Data categories in scope

 

Translated files often contain nonpublic personal information, account data and supervisory records. Translation workflows therefore need access control, encryption, a defined data location and a vendor confidentiality obligation. These controls come from the firm’s own information security program and are not specific to translation.

 

Out of scope

 

This text does not cover state law, investment adviser rules, or rules of other countries. Firms serving customers outside the United States must separately check local requirements. This text is general reference and not legal advice. Confirm firm-specific obligations with your compliance department or securities counsel.

 

Does FINRA require broker-dealers to translate disclosures?

 

No rule cited in this reference creates a general duty to translate. Rules 2210 and 3110 are written without reference to language. They attach to the communication and to the member that distributes it.

 

Two sources show how the question is treated in practice.

 

  • A FINRA interpretive letter addresses a firm that planned to provide prospectuses, advertisements and sales literature only in English, while using translators in enrollment presentations. FINRA’s guidance in that letter concerns how the translator is qualified and instructed, not whether the firm must translate.

  • A comment letter to the SEC from FIBA states that the Commission had not objected since 1991 to foreign-language documentation as a disclosure enhancement, citing the Phoenix Funds no-action letter. This is an industry statement and is not an SEC rule.

 

A firm may still face translation duties from other law. A 2021 Federal Register statement on limited-English-proficient consumers says financial institutions must comply with federal and state laws that require translated documents in particular circumstances. Where translation is not legally mandated, institutions may assess whether and to what extent to provide it. Firms that choose to translate must ensure accuracy.

 

The practical rule: translation is a business decision unless a specific federal or state law, a contract or a regulator’s instruction requires it. Once the firm translates, the full FINRA framework applies.

 

Which FINRA rules apply to translated communications?

 

Rule 2210: content standards

 

FINRA Rule 2210 requires communications with the public to be based on fair dealing and good faith. They must be fair and balanced, give a sound basis for evaluating the security or service, and present risks and benefits in balance. They must not omit material facts or make false or misleading claims.

 

The rule also prohibits false, exaggerated, unwarranted, promissory or misleading statements. A member may not distribute a communication it knows or has reason to know contains an untrue material fact or is otherwise false or misleading.

 

For translation, this has one direct consequence. A translated communication is judged on what the translated text says. A risk warning that is softened, shortened or mistranslated can make the translated version misleading even when the English original is compliant. Regulatory Notice 19-31 explains that the communications rules aim to keep communications fair and balanced so investors do not receive misleading information. Its design guidance does not create new requirements.


Rule 2210: content standards

Rule 3110: supervision

 

FINRA Rule 3110 requires each member to establish, maintain and enforce written supervisory procedures reasonably designed to achieve compliance with securities laws and FINRA rules. It also requires review of covered correspondence and internal communications by a registered principal, evidenced in writing.

 

Two supplementary provisions matter for translated material.

 

  • Rule 3110.07 requires review evidence to identify the reviewer, the communication reviewed, the review date and any action taken on significant regulatory issues. Merely opening a communication is insufficient.

  • Rule 3110.06 permits risk-based review. When procedures do not require review of all covered correspondence before use, they must provide for associated-person education and training, documentation of that training, and surveillance and follow-up.

 

SEC Rule 17a-4: retention

 

FINRA’s books and records overview states that SEC Exchange Act Rules 17a-3 and 17a-4 set minimum record creation, retention and format requirements. As FINRA describes Rule 17a-4(b)(4), broker-dealers retain originals of communications received and copies of communications sent relating to their business for at least three years, with the first two years in an easily accessible place.

 

The SEC’s adopting release explains that the content and audience of an electronic message determine whether it must be preserved, regardless of the medium. A translated message sent to a customer is therefore a business communication in its own right.

 

For electronic records, FINRA’s interpretation of Rule 17a-4 describes two preservation routes. One is a complete time-stamped audit trail that captures modifications, deletions, dates, times and the identity of the relevant user. The other is a non-rewriteable, non-erasable format.


Two record-retention routes for translated messages

What steps should a firm follow, and who owns each control?

 

The table maps a translation workflow to an owner and a control. Role names vary by firm.

 

Step

Owner

Control

1. Decide to communicate in a language

Business line head with Compliance

Written approval; scope of languages and document types recorded in written supervisory procedures

2. Approve the English source

Registered principal

Rule 2210 review of the source, with dated approval evidence

3. Select the translator

Compliance or vendor management

Qualification check; confidentiality terms; data location and access control defined

4. Instruct the translator

Project owner

Translate only firm-provided text or audience questions; no independent product information

5. Translate

Vendor

Terminology and translation memory use; documented QA

6. Review the translation

Qualified bilingual reviewer, then registered principal

Equivalence check against the approved source; reviewer identity, date and actions recorded

7. Distribute

Business line

Only the approved version is released; version identifier on the file

8. Retain

Records management

Source, translation, approvals and transmission records kept under Rule 17a-4 with audit trail

9. Monitor

Compliance

Surveillance and follow-up; findings tracked to closure

Step 4 follows the FINRA interpretive letter. The letter states that a firm using a translator for an investor presentation should use a qualified translator and ensure accuracy. It also says the translator should translate only firm-provided information or audience questions. The firm remains responsible for the translator’s qualification even when the client or plan sponsor supplies the translator.

 

How should a firm decide what to translate and how to review it?

 

Use criteria, applied in writing, so the decision is repeatable.

 

  • Legal trigger. Does a federal or state law, regulator instruction or contract require the translated document? If yes, translation is mandatory for that item.

  • Customer segment. Which languages do actual customers use? Record the basis for the answer.

  • Content risk. Documents that carry risk disclosures, fees, performance claims or suitability information need a higher review level than generic educational text.

  • Delivery channel. Websites, social posts, live presentations and email each need a defined review and retention path.

  • Data sensitivity. Files with account data or nonpublic personal information require a vendor with defined access control, hosting location and information security certification.

  • Reviewer capability. The reviewer needs both subject knowledge of securities terms and fluency in the target language. A registered principal who cannot read the translation cannot evidence a meaningful review of it.

  • Version control. Every change to the English source triggers a defined update of each translated version.

 

A firm that uses machine translation or AI+HUMAN hybrid workflows applies the same criteria. The tool does not change the firm’s responsibility under Rule 2210. Human review by a qualified linguist and a registered principal remains the control that matters. Rule 3110.07 states that review evidence must identify the reviewer and the date, so the process records who checked the translated text.

 

What do compliant and noncompliant workflows look like?

 

Example 1: translated retail brochure

 

A firm publishes a Spanish brochure for a mutual fund program. The English brochure is approved by a principal under Rule 2210. A qualified translator produces the Spanish text. A bilingual reviewer compares each risk statement against the source. The principal signs off on the Spanish version with the date. Both versions are retained with the approval record.

 

Example 2: interpreted enrollment presentation

 

A plan sponsor offers its own interpreter for an enrollment session. The firm confirms the interpreter is qualified, provides the approved presentation text, and instructs the interpreter to convey only firm-provided information and audience questions. Under the interpretive letter, responsibility for qualification stays with the firm even though the sponsor supplied the interpreter.

 

Example 3: supervisory exposure

 

An SEC application for review describes findings in an appealed decision that a supervisor did not ask how a representative communicated with Asia-based customers. The findings also state that the supervisor did not check untranslated portions of documents or ensure customers understood communications and firm documents. The appellant disputed those findings. The matter is cited here only to show the supervisory questions regulators ask, not as a final outcome.

 

What are the common failure modes and mitigations?

 

Failure mode

Mitigation

Translated version is not reviewed because the principal cannot read the language

Add a qualified bilingual reviewer before principal sign-off; record both reviews

Risk language is shortened or softened in translation

Equivalence check of every risk, fee and limitation statement against the approved source

Source is updated but translations are not

Version control that links each translation to a source version; update triggers in written procedures

Written procedures describe a review that is not performed

Draft procedures to match actual practice; test them through surveillance

Translator adds product information not in the source

Written instructions limiting scope; reviewer check for added content

Translated records are missing or not retrievable

Retain source, translation, approvals and transmission under Rule 17a-4 with audit trail

Sensitive customer data sent to unvetted tools

Access control, encryption, defined hosting location and vendor security certification

Review evidence is vague

Record reviewer, communication, date and action as Rule 3110.07 requires

FINRA’s 2019 examination report states that firms must update supervisory processes and written procedures for new or amended rules, products and services. It lists inadequate written procedures and insufficient follow-through on corrective action among examination findings. Adding a new language is a change to services and belongs in the procedures.

 

Our perspective

 

We see the same pattern in regulated translation. The legal question is rarely whether a document may be translated. The question is whether the firm can show, years later, who produced each translated version, who checked it, and which source it matched.   That is why we build the workflow around evidence. Our AI+HUMAN hybrid process places subject-matter expert linguists on every project. Client translation memories and term bases keep wording for terms such as risk, fee and suitability consistent across versions. Our LangOps System runs on EU-hosted infrastructure, and our ISO 17100, ISO 18587, ISO 27001 and ISO 42001 certifications are audited by Bureau Veritas.   A broker-dealer keeps responsibility for its communications. We design our process so the compliance team receives a reviewable record and a translation it can approve with confidence.   Eric Brown

 

Where AD VERBUM fits

 

AD VERBUM provides AI+HUMAN hybrid translation for regulated content in 150+ languages, including regional variants. Its proprietary LangOps System is hosted on EU servers. AD VERBUM states ISO 17100, ISO 18587, ISO 27001 and ISO 42001 certification, and alignment with GDPR and HIPAA. Subject-matter expert linguists review the output, and client Translation Memories and Term Bases are integrated. See the translation and localization services for scope. Pricing is by quote.


AD VERBUM

Key points

 

  • No cited FINRA rule creates a general duty to translate customer communications.

  • Other federal or state law, or a regulator instruction, may require translation of specific documents.

  • Rule 2210 applies to the translated text as its own communication.

  • Rule 3110 requires written procedures and evidenced principal review of covered communications.

  • Review evidence must show the reviewer, the item, the date and the action taken.

  • SEC Rule 17a-4 retention applies to translated communications related to the business.

  • The firm must use a qualified translator and ensure accuracy, even if a client supplies the translator.

  • Written procedures must match actual practice.

 

FAQ

 

Can a broker-dealer provide English-only documents to customers who speak another language?

 

No cited FINRA rule prohibits it. The firm should still check whether federal or state law requires translation in the specific case. The Federal Register statement notes that where translation is not mandated, institutions assess whether and to what extent to provide it. Document the decision and its basis.

 

Does a translated advertisement need principal approval?

 

Treat it as a separate communication that goes through the firm’s Rule 2210 and Rule 3110 procedures. Which category it falls into and who must approve it depends on the content and the firm’s procedures. Confirm the approval path with your compliance department.

 

How long must translated customer communications be kept?

 

FINRA describes Rule 17a-4(b)(4) as requiring copies of communications sent relating to the business for at least three years, the first two in an easily accessible place. Confirm the exact category and any longer period with compliance or counsel, using FINRA’s books and records overview.

 

Can the client or plan sponsor supply the translator?

 

Yes, according to the FINRA interpretive letter, but the broker-dealer remains responsible for ensuring the translator is qualified and the translation is accurate. The translator should translate only firm-provided information or audience questions.

 

Sources

 

 
 
bottom of page