How Should a U.S. Company Translate an XBRL Financial Report Containing Regulated Data, and What Must the Language Vendor Control?
Direct answer. The SEC does not require U.S. companies to submit translated XBRL reports. Filings must be in English, and a foreign-language document must be translated into or summarized in English. Translation is still needed for foreign private issuers, foreign subsidiaries, investors and regulators abroad. Translate labels and narrative text, keep tags, concepts, contexts and units unchanged, and validate the result. Use a vendor with access control, an audit trail and subject-matter review.
Table of Contents
What does XBRL stand for, and what does an XBRL report contain?
XBRL stands for eXtensible Business Reporting Language. FASB describes it as an open international standard for digital business reporting. It delivers human-readable financial statements in a machine-readable, structured format. Preparers using GAAP for publicly traded companies must tag every number, table, accounting policy, statement and note.
An XBRL report is a set of facts. The UK Financial Reporting Council explains that each fact is linked to three things:
A concept defined in a taxonomy.
A context stating who the data relates to and for what period.
A unit, such as a currency or shares.
The report text is therefore only one layer. The tags and metadata are a second layer that software reads. A translation project must treat both layers as in scope.
What is the scope of an XBRL report translation?
An XBRL report translation converts the human-readable content of a report into another language. It also converts the human-readable labels that taxonomies attach to concepts. It does not change the technical identifiers that make the data machine-readable.
Three components fall in scope:
Narrative and tables. Management discussion, notes, accounting policies, audit-related text and financial tables.
Labels and documentation. The XBRL standard notes that labels are often included in multiple languages. This allows automated language switching and wider access to corporate data. The tag “ProfitLoss” could carry a label such as “net annual earnings.”
Tag placement. Tags attached to translated text must remain attached to the right text.
Three components stay out of translation:
Concept names and technical identifiers.
Context definitions, including period and entity.
Units and numeric values.
The IFRS Foundation states that the IFRS digital taxonomies are designed to be extensible. Labels and documentation can be translated into several languages. Concepts can be presented in any required language without altering the underlying identifiers or relationships.
Does the SEC require translated XBRL reports from U.S. companies?
No. The SEC’s final rule 33-11070, Updating EDGAR Filing Requirements, became effective on July 11, 2022. It confirms that generally all filings and submissions must be in English. Rule 306(a) of Regulation S-T prohibits the electronic filing or submission of a document in a foreign language.
When an electronic filing must include a foreign-language document, the document must be translated into or summarized in English and submitted electronically. A foreign private issuer is the typical case. The same rule also adopted Inline XBRL for financial statements and notes in Form 11-K annual reports.
A law firm summary of the amendments states that foreign-language documents formerly supplied on paper to support electronic English translations can now be filed only electronically, alongside the English translation.
Translation of an XBRL report is therefore a business decision in most U.S. cases, not an SEC filing duty. Common triggers:
A foreign parent or subsidiary needs the report in its local language.
Investors, lenders or auditors outside the U.S. need a readable version.
A regulator in another jurisdiction requires a local-language submission. Confirm the local rule with counsel in that jurisdiction [VERIFY per country].
An IFRS-based report needs labels in additional languages.
What are the steps, and who owns each control?
Each step has an owner and a named control. The owner column assigns accountability inside the reporting company or the vendor.
Step | Owner | Control |
1. Freeze the English source and its XBRL instance | Financial reporting lead | Version control, change log |
2. Classify the data (public, material nonpublic, personal) | Compliance or legal | Data classification record |
3. Load approved terminology and prior translations | Localization manager | Term base and translation memory governance |
4. Extract translatable text and labels, protect tags | Vendor project manager | Tag protection, file-integrity check |
5. Translate with AI+HUMAN hybrid workflow | Vendor linguists | Subject-matter review, QA |
6. Independent financial review | Controller or external accountant | Reviewer sign-off |
7. Reinsert, validate, and compare | Financial reporting lead | Technical validation, completeness check |
8. Archive and release | Compliance | Audit trail, access control |
Treat the reporting deliverables as a project with defined outputs. One overview of financial reporting methods and deliverables describes how deliverables are structured for smaller companies, and the same discipline applies to translated reports.
How should tags be handled during translation?
The SEC EDGAR XBRL Guide explains that an XBRL instance can be stored as xBRL-XML or embedded in HTML as Inline XBRL. The location of facts within a file has no effect on their meaning in EDGAR formats. The guide also states that taxonomy relationships are stored in linkbases and concepts are annotated with text labels.
In practice:
Lock the tag markup so linguists cannot edit it.
Translate only the visible text and label resources.
Keep one label file per language. The IFRS architecture document shows label linkbases modularized by language. The language code appears in the file name suffix, and each label uses the xml:lang attribute with an ISO 639 code.
How should tag positions be checked after translation?
Languages differ in word count, spacing and formatting. Workiva’s support center explains that you may need to adjust tag position in your translation management system after translation. The same page states that facts on text and tables, including text block tags and unlinked table cells, are not included in a translation if they were added after the translation was created. XBRL on numeric links is maintained when converting to a new live document.
The control is simple. Finish tagging before creating the translation file. Re-run the comparison if tagging changes later.
What criteria decide which translation approach and vendor to use?
Use these criteria in order. A failure on an early criterion removes the option.
Data handling. Does the report contain material nonpublic information before release? If yes, require access control, confidentiality terms, and a defined hosting location.
Security certification. ISO 27001 covers information security. ISO 42001 covers AI use and safety. Ask for the certificates and the audit body.
Translation quality standard. ISO 17100 covers translation services. ISO 18587 covers post-editing of machine output.
Financial subject-matter competence. The reviewer must read IFRS or U.S. GAAP disclosures in both languages.
Terminology governance. The vendor must apply the client’s term base and translation memory and report deviations.
Tag awareness. The vendor must handle Inline XBRL or taxonomy label files without altering identifiers.
Audit trail. Every change, reviewer and approval must be recorded.
Turnaround fit. Reporting calendars are fixed. Confirm lead time against the filing and board schedule.
Deloitte’s guidance on interactive data files states that a sustainable XBRL process builds enough preparation and review time into the external reporting calendar. It also states that reviews should be a critical component of the controls governing file creation. The same logic applies to translation.
Who should review the translation, and which terminology and disclosure risks need attention?
Three reviewers cover the main risks.
Financial reviewer. A qualified accountant fluent in the target language checks that terms match the framework in use. Examples are impairment, provisions, deferred tax, going concern and related-party transactions.
Legal or compliance reviewer. Checks forward-looking statements, risk factors and defined legal terms.
Technical reviewer. Checks tags, label files and validation output.
High-risk terminology areas:
Terms that differ between U.S. GAAP and IFRS for the same concept.
Names of standards and statutory bodies, which should follow official translations where they exist.
Numbers, decimals and date formats. Decimal and thousands separators differ by language. The numeric value in the tagged fact must stay unchanged.
Defined terms that appear many times. One concept must have one translation throughout the report.
Negative values and sign conventions in tables.
These reviewer roles are a recommended control design, not a regulatory requirement [VERIFY against the applicable regulator’s guidance].
How is a translated XBRL report validated?
Two checks apply: technical validity and content fidelity.
Technical validation. The EDGAR XBRL Guide lists the checks applied to a submission: file-format syntax, EDGAR syntax restrictions, instance consistency, fact and metadata consistency, and submission-, form- and exhibit-specific checks. Filers should validate the full submission, usually as a TEST, resolve errors and warnings, and then submit LIVE.
Content fidelity. The XBRL US GAAP Taxonomy Preparers Guide frames instance review around three tests:
Completeness: do all statements, amounts, notes and text from the source appear?
Accuracy: are all numeric values the same as in the source?
Presentation: are the relationships consistent with the source?
The same guide notes that XBRL permits labels in multiple languages. The XBRL US GAAP Taxonomy itself always uses the language English (United States), abbreviated en-US. A U.S. GAAP report with translated labels therefore uses a company extension or a separate label file, not a change to the base taxonomy [VERIFY with the filing agent].
What examples show the process?
Example 1: U.S. parent, German subsidiary reader group. A U.S. issuer files its annual report in English with Inline XBRL. The German subsidiary needs a German reading copy. The company translates the narrative and notes, leaves the EDGAR filing unchanged, and keeps the German version as a controlled convenience document. The English version remains the version of record.
Example 2: Foreign private issuer exhibit. A foreign private issuer must include a foreign-language document in a filing. Under the SEC rule above, it submits an English translation or summary electronically. It may file the original in conjunction with the English version.
Example 3: IFRS label set. A group reports under IFRS and needs Spanish labels. The IFRS taxonomy already supports a separate label file per language. The vendor translates company-specific extension labels and checks them against the standard label set.
What failure modes occur, and what mitigations apply?
Failure mode | Effect | Mitigation |
Tags edited or lost during translation | Facts no longer machine-readable | Tag protection, post-translation validation |
Late tagging after translation file creation | Facts missing from translated version | Freeze tagging first, re-extract if tagging changes |
Inconsistent term for one concept | Misleading disclosure | Term base, terminology QA report |
Numbers altered or reformatted | Mismatch with tagged facts | Numeric comparison against source |
Unreleased results exposed to vendor staff or public tools | Confidentiality breach | Access control, NDA, defined hosting, no public tools |
No record of who changed what | Weak audit evidence | Audit trail for edits and approvals |
Reporting deadline missed | Delayed distribution | Calendar planning with review time built in |
What is our perspective on translating XBRL reports?
Financial report translation fails most often at the boundary between text and data. Linguists see the sentence. Software sees the tag. Both must stay aligned. We run the work as a controlled workflow. Terminology comes from the client’s term base and translation memory. Translation runs on an AI+HUMAN hybrid process, and subject-matter experts review the financial content. Hosting stays on EU infrastructure, and the audit trail records each change. We recommend that the reporting team keep ownership of the tagged instance. The language team should own labels, narrative and terminology. A clear split of ownership prevents the two most common errors: edited tags and inconsistent terms. Eric Brown
Where does AD VERBUM fit?
AD VERBUM is a language service provider with 25+ years of experience. It operates a proprietary LangOps System hosted on EU servers and an AI+HUMAN hybrid workflow with subject-matter expert review. Its certifications include ISO 27001, ISO 42001, ISO 17100 and ISO 18587, independently audited by Bureau Veritas. It supports 150+ languages and integrates client term bases and translation memories.
Financial and regulated-sector translation is listed on the AD VERBUM services page. Pricing is by quote.
Key points
The SEC does not require translated XBRL reports from U.S. companies. Filings are in English.
Foreign-language documents inside an SEC filing need an English translation or summary.
Translate narrative text and labels. Do not alter concepts, contexts, units or values.
Finish tagging before creating the translation file.
Check tag position after translation, because text length and spacing change.
Validate technically, then check completeness, accuracy and presentation against the source.
Use financial, legal and technical reviewers, with access control and an audit trail.
FAQ
Can I translate the XBRL tags themselves?
No. Tags refer to concepts defined in a taxonomy, and their identifiers must stay unchanged. You translate the labels that describe those concepts and the visible text. The IFRS taxonomy architecture states that labels can be translated without altering underlying identifiers.
Do I need to file a translated report with the SEC?
Generally no. The SEC requires English for filings. A translation is needed when a filing must include a foreign-language document. The English translation or summary is then submitted electronically.
Why does the translated report need a second validation?
Translation changes text length and layout, so tags can shift or detach. A new validation confirms the file still meets syntax and consistency checks. A content comparison confirms that every statement, amount and note is still present.
Who signs off on a translated financial report?
The reporting company decides. A common design uses a financial reviewer, a compliance reviewer and a technical reviewer, each with recorded approval. Confirm requirements with your auditor or counsel.
Sources