Pass EDGAR Validation: SEC Filing Translation for U.S. Compliance
SEC filings and required exhibits must be in English. When a foreign-language document is part of a submission, the filer must provide a fair and accurate English translation unless a specific form rule permits an English summary instead. Verify the applicable form instructions, get issuer and counsel signoff on the reporting basis, and build translation checks directly into your EDGAR production process before submission.
Table of Contents
What SEC filing translation covers and who owns what
SEC filing translation refers to converting foreign-language source documents, or portions of them, into English so they meet the requirements of a Commission submission. The documents that most often require translation include annual reports, audited financial statements and their notes, auditor’s reports, legal opinions, prospectuses, and press releases sent to securityholders. Any exhibit attached to a filing that originates in a language other than English is a candidate for translation review under 17 CFR § 232.306.
Translators are not positioned to make accounting or legal judgment calls. Whether a company reports under U.S. GAAP or IFRS, and how any reconciliation is presented, is a decision for the issuer’s finance team and outside counsel, not the language vendor. The SEC Financial Reporting Manual guidance on foreign private issuer reporting makes clear that these determinations sit with the filer, and a translation workflow should require written confirmation of the reporting basis before financial statements or notes go into production.
A short classification checklist helps compliance teams scope the work before it starts:
Identify every foreign-language document attached to or referenced in the filing.
Confirm whether the applicable form permits an English summary or requires full translation.
Confirm the reporting basis (U.S. GAAP or IFRS) and reconciliation approach with finance and counsel.
Flag documents distributed to securityholders, since these typically require full translation regardless of form.
Log the original-language source alongside the English version for the controlled filing record.
Our related guide on foreign entity legal document translation covers issuer and counsel responsibility in more depth, including where certification limitations apply.
Which SEC forms require translation and how scope changes by form
The translation deliverable depends on which form is carrying the foreign-language content. Foreign private issuers file under a different set of forms than domestic filers, and each has its own translation posture.
Form 20-F: registration statements and annual reports filed by foreign private issuers generally require full English translation of financial statements and material exhibits; Item 17 and Item 18 reconciliation requirements determine how much U.S. GAAP reconciliation detail must accompany IFRS-based statements.
Form 6-K: used for periodic furnished reports, Form 6-K instructions permit an English summary for some attachments, but press releases and documents distributed to securityholders, including audited financial information, generally require full translation rather than a summary.
F-series registration statements: prospectus attachments and exhibits filed alongside F-1, F-3, and related forms follow the same default rule as other Securities Act filings: full translation unless a narrow exception applies, with each exhibit type evaluated separately rather than assumed to inherit the treatment of the main document.
The practical takeaway is that form type does not automatically tell you the translation scope. Each attachment within a single filing can carry a different translation obligation, so compliance teams should evaluate exhibits individually rather than applying a blanket rule to the whole submission.
The regulatory rules that decide translation versus summary
Two provisions govern this decision. 17 CFR § 230.403 requires a fair and accurate English translation for foreign-language exhibits in Securities Act filings, lists the exhibit types that normally require translation, and sets out the narrow conditions under which an English summary may substitute. Regulation S-T Rule 306, codified at 17 CFR § 232.306, extends the English-language default to electronic filings and submissions generally: foreign-language documents must carry a fair and accurate English translation unless an applicable rule permits a summary.
All electronic filings and submissions generally must be in English; if a filing includes a foreign-language document, the filer must submit a fair and accurate English translation unless an applicable rule permits an English summary.
Both provisions carry an identification requirement. The submitter must label the document as either an English translation or an English summary, and the unabridged foreign-language original must remain available on request. The “fair and accurate” standard covers more than grammar: it extends to preserved materiality, defined terms, negation, numbers, and cross-references, based on the translation standard set out in Rule 306. A translation that reads smoothly but drops a negation or restates a defined term inconsistently fails that standard even if no word is technically mistranslated.
The EDGAR Filer Manual, Volume II governs how the translated document must be formatted for submission once the language question is settled. Document construction rules, exhibit handling, and Inline XBRL requirements apply to translated exhibits the same way they apply to English-original ones, which means a linguistically correct translation can still fail EDGAR validation if production steps are skipped.
The production workflow and quality controls this requires
A defensible SEC filing translation process treats language conversion as one stage in a longer filing-production pipeline, not a standalone task handed off and returned. The sequence that holds up under audit review looks like this:
Asset integration: ingest the client’s existing Translation Memory and Term Base so prior filings anchor terminology consistency.
Constrained generation: produce the target-language draft under the client’s terminology and style guidance rather than free-form rendering.
Subject-matter expert review: a reviewer with relevant financial, legal, or accounting background checks technical accuracy, regulatory compliance, and contextual nuance.
ISO-aligned quality assurance: run QA gates consistent with ISO 17100 and ISO 18587, since these standards address translation service delivery and machine-output post-editing respectively.
EDGAR production checks: validate the translated document against Filer Manual formatting rules before it enters the submission package.
Terminology governance sits underneath every step. A term base with change control and glossary signoff prevents the same source term from being rendered two different ways across an annual report and its exhibits, a common source of investor confusion and disclosure inconsistency. Version control on both the source and target documents gives compliance teams an audit trail showing which term base version and which reviewer touched each draft.
Data security and auditability controls matter just as much as linguistic accuracy for filings that often contain material nonpublic information before public release. Access controls limiting who can view draft filings, encrypted transport between systems, and a record of reviewer identity and qualifications all belong in the acceptance criteria for any vendor statement of work. Our translation quality checklist for regulated sectors outlines QA gate structures that map onto this same logic.
Pro Tip: Require your vendor to retain the source-language file and the term base version used for each filing so a Commission staff request for the underlying document can be answered without reconstructing the translation history.
A complete SOW should specify source retention, a signed attestation where the engagement calls for one, clear labeling of translation versus summary, and delivery of an EDGAR-ready file package rather than a plain document handoff.
EDGAR formatting and pre-submission validation for translated exhibits
Translation accuracy does not guarantee a clean EDGAR submission. The EDGAR Filer Manual sets specific rules for accepted file types, PDF construction, exhibit tagging, and Inline XBRL obligations for financial statements, and a translated document has to satisfy the same rules as an English-original one.
Confirm the translated file matches accepted EDGAR file types and PDF construction rules before conversion into the submission package.
Preserve cross-references, pagination, and exhibit numbering so translated exhibits still map correctly to the body of the filing.
Coordinate translation and localization of dates, currency formats, and numeric conventions with the XBRL preparer so tagging is not broken during the language change.
Run EDGARLink validation, and a test submission where the filing calendar allows it, before the final filing goes out.
Check point | What to verify | Who signs off |
Document format | File type and PDF construction meet EDGAR Filer Manual rules | Filing agent |
Exhibit mapping | Cross-references and numbering match the main filing | Compliance/legal |
Inline XBRL | Numeric tags remain intact after translation and localization | XBRL preparer |
Translation label | Document identified as translation or summary per 17 CFR 230.403 | Issuer/counsel |
Our financial document translation guide walks through these iXBRL and exhibit checks in more detail for teams building an internal checklist.
Common translation failure modes and how to prevent them
The errors that create the most disclosure risk are rarely obvious mistranslations. They tend to be quieter problems that survive a surface read.
Terminology drift: the same source term rendered differently across the filing and its exhibits, confusing readers about whether two concepts are the same or different.
Silent accounting changes: a translator’s word choice that implies a different reporting treatment than the one counsel and finance approved.
Lost negation: a dropped “not” or “except” that reverses a sentence’s meaning without changing its length.
Mismatched defined terms: a capitalized term defined once in English losing its defined status in translation.
Broken exhibits or XBRL tags: formatting or numeric changes made during localization that detach a tag from its intended data point.
Mitigation starts with side-by-side redlines between source and target text, numeric reconciliation on every translated financial table, and a signed SME attestation confirming technical review. Set a clear signoff threshold: any unresolved question about accounting-framework treatment or reconciliation methodology stops the submission and escalates to securities counsel rather than getting resolved by the translation team alone.
Pro Tip: Build a one-page escalation runbook naming who at the issuer and which outside counsel contact gets pulled in when a translator flags an accounting-framework ambiguity, so the filing clock doesn’t stall while people figure out who owns the decision.
Where AD VERBUM fits in an audit-ready translation program
SEC filing translations can be managed through an AI+HUMAN hybrid workflow: integrating client Translation Memories and Term Bases first, generating a draft constrained by that terminology via a proprietary system, followed by a subject-matter expert review for technical accuracy, and quality assurance aligned to relevant ISO standards. Such a system may be hosted on EU servers without reliance on outsourced public cloud tooling for core processing, and can draw on networks of subject-matter expert linguists across finance, legal, and technical fields.
This setup fits compliance teams facing a specific combination of conditions: regulated content where a translation error carries disclosure consequences, a need for an audit trail tying each translated passage to a named reviewer, terminology that must stay consistent across years of filings, and sensitive financial data that has not yet been publicly disclosed. Relevant certifications for information security and translation standards may be independently audited by recognized bodies.
When scoping a statement of work for SEC filing translation, ask for:
Term Base and Translation Memory onboarding before the first draft is produced.
Named reviewer qualifications tied to financial or legal subject matter experience.
QA gate definitions referencing ISO 17100 and ISO 18587.
EDGAR-ready package delivery rather than a plain document handoff.
Written data-handling commitments covering access control and storage location.
AD VERBUM’s translation services page outlines these capabilities for compliance and legal teams evaluating a vendor for regulated filing work, and a project quote reflects the scope of the specific filing package.
A compliance policy worth adopting
Translation for SEC filings should sit inside your controlled filing program, not outside it as a vendor task nobody owns internally. Require counsel and finance signoff on the reporting basis before a single page gets translated, and treat that signoff as a gate the filing cannot pass without. Demand traceable evidence: which Term Base version was used, who the subject-matter reviewer was and what their qualifications were, what the QA log shows, and confirmation that EDGAR pre-submission validation ran clean.
Default to full translation. Reach for an English summary only when the specific form rule expressly permits it and counsel has approved that path in writing. That default costs a little more upfront and saves considerably more the day a regulator or a shareholder asks why a disclosure reads differently in two languages.
— Eric Brown
Sources
FAQ
Who can certify a translation in the US?
There is no single government-recognized “certified translator” credential required for SEC filings; the requirement is a fair and accurate English translation under 17 CFR § 232.306. Filers typically use a qualified vendor or subject-matter expert reviewer and, where the engagement calls for it, a signed attestation confirming the translation’s accuracy.
What is a US SEC filing?
A U.S. SEC filing is a document a company submits to the Securities and Exchange Commission to meet registration, reporting, or disclosure obligations under federal securities law. Filings range from registration statements like Form 20-F to periodic reports like Form 6-K, and all must generally be submitted in English under Regulation S-T Rule 306.
What are the US GAAP rules for translating foreign currencies?
Deciding how to translate foreign currency amounts and reconcile them to U.S. GAAP is an accounting determination made by the issuer’s finance team and auditors, not a language translation task. The SEC Financial Reporting Manual addresses reporting basis and reconciliation for foreign private issuers, and that guidance should be confirmed in writing before any linguistic translation of financial statements begins.
What translations are accepted by USCIS?
USCIS is a separate federal agency from the SEC with its own certified translation requirements for immigration filings, and its standards do not govern SEC submissions. For SEC filings specifically, the controlling standard is the fair and accurate English translation requirement under 17 CFR § 230.403, which differs from USCIS certification rules.
Recommended
