Form F-6EF Files Dataset

The Form F-6EF Files Dataset is a structured corpus of every Form F-6EF submission accepted by EDGAR — the auto-effective variant of Form F-6 used by depositary banks to register American Depositary Shares (ADSs) evidenced by American Depositary Receipts (ADRs) over the deposited equity of a foreign private issuer. One record corresponds to a single EDGAR accession, materialized as a self-contained folder that bundles the F-6EF registration statement, the standard exhibit set (form of ADR, opinion of U.S. counsel, Rule 466 certification, and where applicable a standalone deposit agreement and amendments), and a metadata.json index that captures the structured filing header and the dual-entity block naming the depositary as filer and the foreign private issuer as subject. Filings are made by depositary banks — predominantly The Bank of New York Mellon, Citibank N.A., JPMorgan Chase Bank N.A., and Deutsche Bank Trust Company Americas — at the moment a new sponsored or unsponsored ADR program is established, additional ADSs are registered under an existing program, or a successor depositary takes over a program. The dataset covers EDGAR F-6EF accessions from January 2002 to present and is distributed as monthly ZIP containers.

Update Frequency
Daily
Updated at
2026-05-07
Earliest Sample Date
2002-01-01
Total Size
231.2 MB
Total Records
31,468
Container Format
ZIP
Content Types
HTML, JSON, TXT, PDF
Form Types
F-6EF

Dataset APIs

Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.

Dataset Index JSON API

Download the entire dataset as a single archive file.

Download Entire Dataset:

Download a single container file (e.g. monthly archive) from the dataset.

Download Single Container:

Dataset Files

292 files · 231.2 MB
Download All
2026-05.zip413.6 KB77 records
2026-04.zip1.3 MB252 records
2026-03.zip977.4 KB160 records
2026-02.zip860.3 KB144 records
2026-01.zip520.3 KB84 records
2025-12.zip567.7 KB88 records
2025-11.zip612.9 KB88 records
2025-10.zip648.0 KB104 records
2025-09.zip730.0 KB124 records
2025-08.zip471.1 KB60 records
2025-07.zip1.0 MB156 records
2025-06.zip1.2 MB188 records
2025-05.zip464.7 KB53 records
2025-04.zip581.5 KB96 records
2025-03.zip741.8 KB123 records
2025-02.zip582.3 KB90 records
2025-01.zip289.8 KB44 records
2024-12.zip523.8 KB72 records
2024-11.zip269.6 KB40 records
2024-10.zip272.1 KB40 records
2024-09.zip467.8 KB52 records
2024-08.zip301.1 KB52 records
2024-07.zip346.8 KB48 records
2024-06.zip324.2 KB52 records
2024-05.zip710.1 KB76 records
2024-04.zip645.1 KB87 records
2024-03.zip342.1 KB46 records
2024-02.zip282.0 KB48 records
2024-01.zip243.7 KB32 records
2023-12.zip166.2 KB20 records
2023-11.zip52.8 KB8 records
2023-10.zip424.6 KB60 records
2023-09.zip194.8 KB28 records
2023-08.zip153.3 KB16 records
2023-07.zip344.9 KB38 records
2023-06.zip358.9 KB52 records
2023-05.zip447.9 KB58 records
2023-04.zip141.0 KB20 records
2023-03.zip733.2 KB112 records
2023-02.zip264.9 KB32 records
2023-01.zip278.2 KB44 records
2022-12.zip332.2 KB28 records
2022-11.zip397.6 KB52 records
2022-10.zip285.3 KB36 records
2022-09.zip233.1 KB36 records
2022-08.zip754.9 KB77 records
2022-07.zip309.5 KB51 records
2022-06.zip436.4 KB51 records
2022-05.zip473.6 KB54 records
2022-04.zip16.4 MB70 records
2022-03.zip947.7 KB139 records
2022-02.zip528.8 KB67 records
2022-01.zip319.9 KB44 records
2021-12.zip160.8 KB28 records
2021-11.zip577.2 KB79 records
2021-10.zip568.8 KB80 records
2021-09.zip717.5 KB104 records
2021-08.zip655.1 KB96 records
2021-07.zip376.5 KB47 records
2021-06.zip882.4 KB124 records
2021-05.zip653.6 KB89 records
2021-04.zip829.3 KB120 records
2021-03.zip1.0 MB142 records
2021-02.zip557.6 KB91 records
2021-01.zip545.7 KB80 records
2020-12.zip487.0 KB56 records
2020-11.zip504.2 KB68 records
2020-10.zip639.5 KB93 records
2020-09.zip303.7 KB44 records
2020-08.zip165.5 KB23 records
2020-07.zip464.7 KB80 records
2020-06.zip66.6 KB12 records
2020-05.zip154.1 KB20 records
2020-04.zip255.2 KB44 records
2020-03.zip423.3 KB72 records
2020-02.zip638.9 KB104 records
2020-01.zip309.9 KB52 records
2019-12.zip426.5 KB63 records
2019-11.zip35.2 MB1,674 records
2019-10.zip128.3 KB20 records
2019-09.zip357.7 KB53 records
2019-08.zip391.5 KB67 records
2019-07.zip138.2 KB20 records
2019-06.zip247.0 KB33 records
2019-05.zip433.7 KB57 records
2019-04.zip542.1 KB84 records
2019-03.zip209.9 KB32 records
2019-02.zip283.3 KB48 records
2019-01.zip583.5 KB77 records
2018-12.zip318.3 KB36 records
2018-11.zip511.8 KB68 records
2018-10.zip327.2 KB52 records
2018-09.zip250.7 KB38 records
2018-08.zip479.6 KB80 records
2018-07.zip249.5 KB44 records
2018-06.zip241.2 KB36 records
2018-05.zip505.9 KB66 records
2018-04.zip380.8 KB60 records
2018-03.zip574.2 KB96 records
2018-02.zip374.6 KB64 records
2018-01.zip232.2 KB40 records
2017-12.zip455.9 KB76 records
2017-11.zip471.0 KB68 records
2017-10.zip734.5 KB128 records
2017-09.zip769.3 KB132 records
2017-08.zip888.9 KB152 records
2017-07.zip487.3 KB76 records
2017-06.zip1.4 MB225 records
2017-05.zip1.3 MB208 records
2017-04.zip357.4 KB64 records
2017-03.zip1.1 MB196 records
2017-02.zip325.9 KB48 records
2017-01.zip351.8 KB55 records
2016-12.zip606.9 KB92 records
2016-11.zip617.4 KB77 records
2016-10.zip754.6 KB116 records
2016-09.zip676.7 KB100 records
2016-08.zip935.6 KB130 records
2016-07.zip339.5 KB41 records
2016-06.zip321.9 KB41 records
2016-05.zip958.6 KB145 records
2016-04.zip1.0 MB153 records
2016-03.zip2.4 MB357 records
2016-02.zip2.4 MB376 records
2016-01.zip894.6 KB140 records
2015-12.zip1.4 MB224 records
2015-11.zip513.5 KB80 records
2015-10.zip733.7 KB112 records
2015-09.zip1.6 MB252 records
2015-08.zip415.0 KB64 records
2015-07.zip1.1 MB168 records
2015-06.zip1.7 MB254 records
2015-05.zip960.4 KB156 records
2015-04.zip890.9 KB136 records
2015-03.zip200.7 KB36 records
2015-02.zip390.0 KB60 records
2015-01.zip706.0 KB148 records
2014-12.zip2.5 MB380 records
2014-11.zip4.1 MB667 records
2014-10.zip4.1 MB676 records
2014-09.zip689.5 KB116 records
2014-08.zip312.7 KB56 records
2014-07.zip776.6 KB128 records
2014-06.zip461.4 KB76 records
2014-05.zip801.7 KB129 records
2014-04.zip1.0 MB170 records
2014-03.zip656.4 KB112 records
2014-02.zip634.0 KB116 records
2014-01.zip624.5 KB112 records
2013-12.zip421.1 KB65 records
2013-11.zip706.2 KB124 records
2013-10.zip807.5 KB124 records
2013-09.zip417.9 KB76 records
2013-08.zip531.8 KB93 records
2013-07.zip958.6 KB169 records
2013-06.zip788.3 KB140 records
2013-05.zip784.0 KB157 records
2013-04.zip1.0 MB185 records
2013-03.zip1.0 MB177 records
2013-02.zip2.7 MB472 records
2013-01.zip1.0 MB188 records
2012-12.zip758.0 KB107 records
2012-11.zip453.9 KB88 records
2012-10.zip590.1 KB101 records
2012-09.zip503.4 KB87 records
2012-08.zip956.9 KB184 records
2012-07.zip625.9 KB116 records
2012-06.zip685.1 KB148 records
2012-05.zip1.0 MB188 records
2012-04.zip792.3 KB152 records
2012-03.zip1.1 MB236 records
2012-02.zip482.6 KB74 records
2012-01.zip779.0 KB137 records
2011-12.zip1.1 MB213 records
2011-11.zip535.7 KB102 records
2011-10.zip918.3 KB178 records
2011-09.zip996.9 KB162 records
2011-08.zip873.6 KB148 records
2011-07.zip616.3 KB112 records
2011-06.zip527.1 KB71 records
2011-05.zip534.5 KB81 records
2011-04.zip765.2 KB142 records
2011-03.zip933.6 KB183 records
2011-02.zip959.3 KB166 records
2011-01.zip396.8 KB65 records
2010-12.zip679.7 KB133 records
2010-11.zip534.6 KB99 records
2010-10.zip684.5 KB140 records
2010-09.zip266.1 KB52 records
2010-08.zip512.8 KB73 records
2010-07.zip371.7 KB68 records
2010-06.zip690.6 KB118 records
2010-05.zip610.8 KB93 records
2010-04.zip994.9 KB164 records
2010-03.zip437.1 KB79 records
2010-02.zip472.4 KB81 records
2010-01.zip453.3 KB69 records
2009-12.zip433.3 KB64 records
2009-11.zip763.4 KB120 records
2009-10.zip546.0 KB72 records
2009-09.zip265.6 KB53 records
2009-08.zip603.7 KB112 records
2009-07.zip323.3 KB69 records
2009-06.zip671.2 KB143 records
2009-05.zip822.1 KB163 records
2009-04.zip2.2 MB399 records
2009-03.zip2.1 MB376 records
2009-02.zip2.0 MB377 records
2009-01.zip1.7 MB352 records
2008-12.zip3.3 MB620 records
2008-11.zip4.7 MB997 records
2008-10.zip14.7 MB3,013 records
2008-09.zip444.5 KB37 records
2008-08.zip258.1 KB30 records
2008-07.zip313.7 KB49 records
2008-06.zip916.3 KB136 records
2008-05.zip628.2 KB95 records
2008-04.zip355.6 KB72 records
2008-03.zip188.5 KB35 records
2008-02.zip164.3 KB25 records
2008-01.zip187.0 KB28 records
2007-12.zip309.3 KB52 records
2007-11.zip766.8 KB82 records
2007-10.zip364.1 KB55 records
2007-09.zip334.2 KB34 records
2007-08.zip492.9 KB74 records
2007-07.zip262.7 KB39 records
2007-06.zip421.9 KB37 records
2007-05.zip296.2 KB31 records
2007-04.zip288.5 KB33 records
2007-03.zip288.0 KB50 records
2007-02.zip359.6 KB28 records
2007-01.zip293.2 KB42 records
2006-12.zip311.7 KB48 records
2006-11.zip226.0 KB21 records
2006-10.zip255.5 KB37 records
2006-09.zip110.6 KB15 records
2006-08.zip418.0 KB67 records
2006-07.zip88.7 KB11 records
2006-06.zip340.6 KB47 records
2006-05.zip182.7 KB21 records
2006-04.zip250.6 KB34 records
2006-03.zip298.7 KB45 records
2006-02.zip217.6 KB40 records
2006-01.zip22.5 KB4 records
2005-12.zip290.1 KB31 records
2005-11.zip182.7 KB23 records
2005-10.zip124.3 KB14 records
2005-09.zip63.4 KB4 records
2005-08.zip339.8 KB41 records
2005-07.zip42.2 KB4 records
2005-06.zip172.1 KB26 records
2005-05.zip122.5 KB15 records
2005-04.zip15.1 KB6 records
2005-03.zip268.5 KB31 records
2005-02.zip25.5 KB10 records
2005-01.zip64.5 KB8 records
2004-12.zip168.4 KB20 records
2004-11.zip116.0 KB15 records
2004-10.zip76.4 KB12 records
2004-09.zip16.2 KB4 records
2004-08.zip87.3 KB12 records
2004-07.zip60.3 KB12 records
2004-06.zip293.8 KB47 records
2004-05.zip74.0 KB8 records
2004-04.zip175.7 KB26 records
2004-03.zip187.7 KB22 records
2004-02.zip50.6 KB6 records
2004-01.zip101.9 KB14 records
2003-12.zip129.9 KB27 records
2003-11.zip127.4 KB22 records
2003-10.zip49.8 KB5 records
2003-09.zip181.5 KB23 records
2003-08.zip36.1 KB8 records
2003-06.zip88.7 KB15 records
2003-05.zip101.4 KB17 records
2003-04.zip32.6 KB8 records
2003-03.zip169.4 KB17 records
2003-02.zip159.9 KB22 records
2003-01.zip146.0 KB28 records
2002-12.zip180.9 KB36 records
2002-11.zip66.7 KB16 records
2002-10.zip22 B0 records
2002-09.zip22 B0 records
2002-08.zip22 B0 records
2002-07.zip22 B0 records
2002-06.zip22 B0 records
2002-05.zip22 B0 records
2002-04.zip22 B0 records
2002-03.zip22 B0 records
2002-02.zip22 B0 records
2002-01.zip22 B0 records

What This Dataset Contains

The dataset materializes the full population of Form F-6EF registration statements filed on EDGAR from January 2002 forward. Each filing registers a discrete ADR program — one foreign issuer, one class of deposited securities, one depositary — and discloses the contractual mechanics of that program rather than financial information about the issuer or the depositary. The "EF" suffix designates filings that elect immediate effectiveness under Rule 466 of the Securities Act: the registration takes effect at the moment EDGAR accepts the submission, with no separate declaration of effectiveness by the staff, conditioned on the depositary having a previously effective F-6 with identical terms of deposit (other than the identity of the deposited securities and the ADS-to-ordinary-share ratio) and on the depositary's Rule 466 designation authority not being suspended.

The document is layered: a brief registration cover and signature page carry almost no narrative, while the exhibits carry essentially all substantive content (the form of ADR, the deposit agreement, counsel's legal opinion, and the Rule 466 certification). The dataset ships as monthly ZIP archives that materialize the textual and structured documents — HTML, JSON, TXT, and PDF — and a per-accession metadata.json index. Image attachments and the full SGML submission .txt envelope are referenced in metadata but deliberately not bundled.

Content Structure of a Single Record

1. What one record represents

One record is a single Form F-6EF submission as accepted by EDGAR, identified by its 18-digit accession number and materialized as a self-contained folder. The folder bundles the registration-statement document, the standard F-6EF exhibit set (form of American Depositary Receipt, opinion of U.S. counsel, Rule 466 certification, and where applicable a deposit agreement and amendments), and a metadata.json index that captures the structured filing header, the inventory of every document EDGAR received, and the two entities that always appear on an F-6 — the depositary bank acting as filer and the foreign private issuer named as subject company.

2. The underlying filing

Form F-6EF is the auto-effective variant of Form F-6, a Securities Act of 1933 registration statement that registers depositary shares evidenced by American Depositary Receipts (ADRs) issued against deposited equity securities of a foreign private issuer. Substantively the filing registers a discrete ADR program — one foreign issuer, one class of deposited securities, one depositary — and discloses the contractual mechanics of that program rather than financial information about the issuer or the depositary. The document is layered: a brief registration cover and signature page carry almost no narrative, while the exhibits carry essentially all substantive content.

3. Container layout and physical record structure

The dataset ships as monthly ZIP archives keyed by filing month under the path pattern <YYYY>/<YYYY-MM>.zip. Each monthly ZIP unpacks to a folder named after the month (e.g. 2025-05/); underneath that month folder there is exactly one subfolder per filing, named with the EDGAR accession number stripped of dashes (e.g. 000119380525000751). All files belonging to a filing live directly inside the accession folder with no further nesting.

Inside each accession folder the dataset materializes:

  • metadata.json — always present, exactly one per accession.
  • The Form F-6EF registration statement as an HTML document (<TYPE>F-6EF, <SEQUENCE>1).
  • One or more exhibit documents as HTML; in older or filer-idiosyncratic submissions, plain TXT or PDF.

Image attachments listed under documentFormatFiles[] with <TYPE>GRAPHIC (typically depositary logos or certificate vignettes) are deliberately not bundled — the dataset materializes only the textual/structured documents. The full SGML submission .txt is referenced through linkToTxt and as a trailing documentFormatFiles[] entry but is also not bundled.

Filenames inside an accession folder are not normalized. Filers use their own conventions such as formf6ef.htm, tm2514894d1_f6ef.htm, e664572_f6ef-reece.htm, or f-6_registration_statement.htm; exhibit filenames range from descriptive (d_opinion_white_case_llp.htm, rule466.htm, depositagreement.htm) to opaque (tm2514894d1_exa.htm, e664572_ex99-d.htm). The authoritative way to classify a document is the type field on the corresponding documentFormatFiles[] entry, not the filename.

The file-types found in the dataset are HTML, JSON, TXT, and PDF. JSON appears only as metadata.json. HTML dominates the document bodies for all modern filings; TXT and PDF appear in older or atypical submissions.

4. metadata.json — the per-accession index

metadata.json is the structured header for the record and the authoritative cross-reference between the dataset's flat folder of files and EDGAR's submission model. Top-level fields:

  • formType — fixed string "F-6EF".
  • accessionNo — EDGAR accession in dashed canonical form (e.g. "0001193805-25-000751").
  • filedAt — ISO-8601 timestamp with timezone offset capturing the EDGAR acceptance moment, which for an F-6EF is also the moment of effectiveness.
  • description — constant human-readable label "Form F-6EF - Registration of American Depository Receipt shares, immediately effective".
  • linkToFilingDetails — URL of the primary F-6EF document on EDGAR.
  • linkToHtml — URL of EDGAR's filing-index page.
  • linkToTxt — URL of the full SGML submission .txt.
  • linkToXbrl — empty for F-6EF; the form does not carry XBRL data.
  • id — internal 32-character hexadecimal identifier.
  • documentFormatFiles[] — an ordered list of every document EDGAR received. Each entry carries sequence (its position in the submission, as a string), size in bytes (as a string), documentUrl (canonical EDGAR archive URL), type (the EDGAR document-type label, e.g. F-6EF, EX-99.(A), EX-99.(D), EX-99.(E), EX-99.1, EX-1, EX-4, EX-5, GRAPHIC), and an optional description. A trailing entry with blank sequence and blank type and description "Complete submission text file" points to the full submission .txt.
  • dataFiles[] — empty for F-6EF.
  • seriesAndClassesContractsInformation[] — empty for F-6EF.
  • entities[] — the dual-entity block described next.

The dual-entity structure

Every F-6EF involves two distinct EDGAR entities, and entities[] always carries both as a fixed-length pair.

The first entity is the depositary bank, marked (Filed by) in companyName — typically Citibank N.A./ADR, Deutsche Bank Trust Company Americas/ADR Group, JPMorgan Chase Bank N.A./ADR Depositary, or The Bank of New York Mellon/ADR Division. Its record carries cik, companyName, stateOfIncorporation, irsNo, fiscalYearEnd, sic (commonly "8880 American Depositary Receipts"), and type (echoing "F-6EF").

The second entity is the foreign private issuer, marked (Subject) in companyName — the operating company whose ordinary shares back the ADRs (for example Reece Limited/ADR, James Hardie Industries plc, MARFRIG GLOBAL FOODS S.A., Techtronic Industries Co Limited/ADR). The Subject entity carries the same core demographic fields plus act ("33" for Securities Act registrations), fileNo (the 333-prefixed Securities Act registration number assigned to this ADR program, e.g. "333-287671"), filmNo, and frequently a tickers[] array listing the ADR symbol and any underlying ordinary-share symbol. stateOfIncorporation on the Subject is an EDGAR jurisdiction code (a two-letter U.S. state for U.S.-domiciled depositaries on the filer side; a non-U.S. country code such as "C3" for Australia, "L2" for Ireland, etc., on the Subject side).

This split — filer versus subject — is the structural signature of an F-6: the depositary is the legal registrant, but the regulated identity for the registration program is the foreign issuer.

5. The HTML document envelope

Every HTML document in the dataset is wrapped in EDGAR's SGML <DOCUMENT> envelope before the actual HTML body:

1 <DOCUMENT>
2 <TYPE>EX-99.(D)
3 <SEQUENCE>3
4 <FILENAME>e664572_ex99-d.htm
5 <TEXT>
6 <html>... (full HTML body) ...</html>
7 </TEXT>
8 </DOCUMENT>

The wrapper exposes <TYPE> (matching documentFormatFiles[].type), <SEQUENCE> (matching the sequence number), <FILENAME> (matching the filename inside the accession folder), and frequently a <DESCRIPTION> line such as EXHIBIT (A) or OPINION OF COUNSEL. Inside <TEXT>...</TEXT> is the document HTML — typically legacy tag-cased markup with uppercase <TABLE>, <TR>, and inline <P STYLE=...> constructs. Consumers should strip or recognize the SGML wrapper before treating the content as standalone HTML, or feed the file through an SGML-tolerant reader rather than a strict HTML parser.

6. The registration statement body

The F-6EF document itself is short — the substantive contract content is exhibitised. The cover/facing page reads FORM F-6 / REGISTRATION STATEMENT / UNDER / THE SECURITIES ACT OF 1933 FOR DEPOSITARY SHARES EVIDENCED BY / AMERICAN DEPOSITARY RECEIPTS and identifies, in tabular and inline form:

  • the exact name of the foreign issuer whose securities are being deposited, its jurisdiction of incorporation, and any translated name;
  • the depositary bank issuing the ADRs and the depositary's principal U.S. office address;
  • the address of the depositary's agent for service in the United States;
  • the title and amount of American Depositary Shares being registered, the deposited-share ratio (number of ordinary shares represented by one ADS), and the proposed maximum aggregate offering price used to compute the registration fee;
  • the calculation-of-registration-fee table.

The cover-page items are followed by a brief description-of-securities cross-reference (typically incorporating the form of ADR by reference rather than restating it), the signatures of the depositary's authorized officers and of the foreign issuer's authorized U.S. representative, and an exhibit index that enumerates each attached exhibit under the F-6 exhibit lettering scheme.

7. The standard F-6EF exhibit set

The substance of an F-6EF lives in its exhibits. Form F-6's exhibit table designates exhibits by parenthesized letter; EDGAR receives them under document types EX-99.(A), EX-99.(D), EX-99.(E), etc., or under sequential numeric labels (EX-1, EX-4, EX-5) depending on filer convention. The standard composition:

  • Exhibit (A) — Form of American Depositary Receipt (EX-99.(A) or EX-1). Almost always the largest document in the filing (commonly 60 KB to several hundred KB). It opens with the engraved-style NUMBER / AMERICAN DEPOSITARY SHARES certificate header and reproduces the full text of the ADR. Embedded inside the form of ADR, in most modern programs, is the entire deposit agreement among the depositary, the foreign issuer, and all holders and beneficial owners of ADRs from time to time, governing: deposit and withdrawal mechanics for the underlying securities; issuance and cancellation of ADSs; voting of deposited securities; dividend, distribution, and rights mechanics; charges and fees of the depositary (issuance, cancellation, distribution, and servicing fees); transfer and surrender procedures; pre-release; tax and FATCA mechanics; amendment and termination; governing law and jurisdiction; and limitations on liability of the depositary and the issuer.

  • Exhibit (B) — Underlying contracts, where applicable, reproducing any pre-existing depositary or custodian arrangements that govern the deposited securities.

  • Exhibit (C) — Documents establishing the deposited securities, where required by the form's instructions.

  • Exhibit (D) — Opinion of U.S. counsel (EX-99.(D) or EX-4). A short legal opinion (typically a few kilobytes) addressed to the depositary, opining that the ADSs, when issued against deposit of the underlying securities and against payment of the relevant fees, will be legally issued and will entitle holders to the rights specified in the form of ADR and the deposit agreement. Names the issuing law firm (e.g. Patterson Belknap Webb & Tyler LLP, White & Case LLP, Emmet, Marvin & Martin LLP) and is dated as of the filing date.

  • Exhibit (E) — Rule 466 certification (EX-99.(E) or EX-5). A short certification by the depositary required for auto-effective F-6EF treatment, asserting that the depositary has previously had an F-6 declared effective with terms of deposit identical to those in the present filing other than the identity of the foreign issuer and the deposited-share-to-ADS ratio, and that the depositary's ability to designate the registration as immediately effective under Rule 466 has not been suspended. Signed by an officer or attorney-in-fact for the depositary.

  • Optional additional exhibits. Some programs reference a master form of deposit agreement that exists separately from the form of ADR, in which case the deposit agreement and any amendments appear as standalone exhibits — frequently labeled EX-99.1 (amended and restated deposit agreement), EX-99.2 (amendment number 1), and so on — alongside the standard (A)/(D)/(E) lettered set.

8. Included content vs. excluded content

What the record includes:

  • metadata.json;
  • the registration-statement HTML;
  • every exhibit document materialized as HTML (or, for older or atypical filings, TXT or PDF).

What the record does not include:

  • image files attached to the submission (GRAPHIC entries in documentFormatFiles[]), listed in metadata but excluded from the ZIP;
  • the full SGML submission .txt envelope, referenced through linkToTxt and as a trailing documentFormatFiles[] entry but not bundled per accession;
  • XBRL data files; Form F-6EF carries no XBRL, so dataFiles[] and linkToXbrl are always empty.

The documentFormatFiles[] listing is the canonical inventory of the submission — including the excluded image and submission-text entries — so a consumer can always reconcile what was filed against what the dataset materializes.

9. Structural and format evolution since 2002

Form F-6EF's substantive disclosure model has been stable across the dataset's coverage: Rule 466's auto-effective mechanism, the (A)/(B)/(C)/(D)/(E) exhibit lettering, and the dual depositary/foreign-issuer registrant structure are unchanged in form. What has evolved is the document-format profile of the filings and the texture of the deposit agreements riding inside Exhibit (A).

  • Format mix. Early-2000s F-6EF submissions were often filed as ASCII/SGML text with monospaced certificate-style ADR forms; HTML adoption became near-universal during the mid-2000s and is the dominant body format across the modern record set. Occasional PDF exhibits appear where filers attached scanned certificates or depositary signature pages.
  • Deposit-agreement modernization. Post-2008, deposit agreements embedded in Exhibit (A) generally grew longer and more standardized as the major depositary banks rolled out updated master forms, covering expanded fee schedules, electronic ADR provisions, FATCA-related tax mechanics, and refinements to pre-release and voting. This shows up as gradual growth in Exhibit (A) byte sizes rather than as a change in record structure.
  • Filing volume. The corpus is unevenly distributed across the period, with substantial growth in unsponsored-ADR programs around 2008–2010 (after Rule 12g3-2(b) amendments) producing concentrated batches of F-6EFs from the major depositaries.

10. Interpretation notes

  • Two entities, always. Treat entities[] as a fixed-length pair: depositary bank ((Filed by)) and foreign issuer ((Subject)). The 333- registration number, film number, and ADR tickers live on the Subject entity; the SIC code 8880 and U.S. depositary identifiers live on the Filed-by entity.
  • Classify by type, not filename. Filenames such as tm2514894d1_exa.htm, e664572_ex99-d.htm, or rule466.htm are filer-chosen and not normalized; map documents to roles via documentFormatFiles[].type and the <TYPE> in the SGML wrapper.
  • Letter vs. numeric exhibit codes. Filers alternate between the parenthesized letter scheme (EX-99.(A), EX-99.(D), EX-99.(E)) and a numeric scheme (EX-1, EX-4, EX-5); both refer to the same Form F-6 exhibit roles. When a deposit agreement is filed standalone, it commonly appears as EX-99.1 with subsequent amendments as EX-99.2, EX-99.3, etc. Consumers should normalize across these conventions.
  • Substantive content is in the exhibits. The F-6EF body itself is largely cover-page and signature material; full ADR, deposit-agreement, and counsel-opinion text lives in the exhibits. Any extraction targeting fees, voting, withdrawal rights, or deposit mechanics must operate on Exhibit (A) (and any standalone deposit-agreement exhibits), not on the F-6EF document.
  • Auto-effectiveness signal. The presence of an Exhibit (E) Rule 466 certification is itself the structural marker that the filing is auto-effective; its absence in an F-6 (non-EF) filing is the principal distinction between the two variants.
  • SGML wrapper. Every HTML body sits inside an SGML <DOCUMENT> envelope; the wrapper's <TYPE>, <SEQUENCE>, and <FILENAME> are redundant with metadata.json but useful for in-stream classification when a document is processed without its companion metadata.

Who Files or Publishes This Dataset, and When

Who files the record

Each record is a Form F-6EF registration statement filed on EDGAR by a depositary bank as the registrant and statutory issuer of the ADSs. Although the underlying equity is issued by a foreign company, the ADSs are a separate security under U.S. law, and it is the depositary — not the foreign company — that registers them under Securities Act Section 5.

The foreign company whose shares are deposited is named on the cover page as the "subject company" (or "issuer of the deposited securities") and must qualify as a foreign private issuer under Rule 405 of the Securities Act and Rule 3b-4 of the Exchange Act. The subject company is described in the filing but does not sign it and is not the registrant. The depositary signs, certifies, pays the Section 6(b) fee, and assumes Section 11 liability for the registration of the ADSs.

Filings are dominated by the four banks that handle most U.S. depositary business — The Bank of New York Mellon, Citibank, N.A., JPMorgan Chase Bank, N.A., and Deutsche Bank Trust Company Americas — with a small tail of other institutions that occasionally sponsor or assume ADR programs.

Form F-6 is the dedicated registration form for ADSs evidenced by ADRs that meet the eligibility conditions in General Instruction I to Form F-6: (i) the ADR holder may withdraw the deposited securities at any time, subject only to limited exceptions; (ii) the deposited securities are issued or guaranteed by a foreign issuer; and (iii) as of the filing date, the issuer of the deposited securities is either an Exchange Act reporting company or is exempt under Rule 12g3-2(b), or the program otherwise meets the relevant program-tier standard.

Form F-6EF is not a separate form in substance. It is the auto-effective variant of Form F-6 filed in reliance on Rule 466 under the Securities Act (17 CFR 230.466). The "EF" suffix means the depositary has designated the registration statement to become effective immediately upon filing, without staff action. Disclosure, exhibit, and signature requirements remain those of Form F-6; Rule 466 governs only the mechanics of effectiveness.

Conditions for Rule 466 auto-effectiveness

Rule 466 requires all of the following:

  • The depositary has previously filed a Form F-6 covering ADRs of the same general character that the Commission has declared effective.
  • The depositary represents that the new ADRs and deposit agreement contain no material variation from those previously declared effective, except for variations expressly permitted under the rule (such as fee changes, depositary name changes, or comparable administrative items).
  • The depositary files the Rule 466(a)(2) certification as Exhibit (e) to the registration statement, signed by an authorized officer, stating that the conditions of Rule 466 are satisfied. This certification is the procedural marker that distinguishes F-6EF from a standard F-6.

Where any condition fails — typically a depositary's first F-6 or a materially novel program structure — the depositary must file standard Form F-6 and wait for the Commission to declare effectiveness under Section 8(a) of the Securities Act.

Triggering events

A Form F-6EF filing arises from one of these depositary-program events:

  • Establishment of a new sponsored ADR program over a foreign private issuer's deposited securities, where the deposit agreement and ADR form follow the depositary's existing template so Rule 466 conditions are met.
  • Registration of additional ADSs under an existing program once the previously registered amount is, or is about to be, exhausted. Rule 415 shelf registration is not available on Form F-6, so depositaries register a fixed number of ADSs and file a fresh F-6EF (with a new Section 6(b) fee) when more capacity is needed.
  • Successor or replacement depositary filings when the depositary role is transferred, requiring the incoming depositary to file its own F-6EF covering ADSs to be issued under the new deposit agreement.
  • Material amendments to the deposit agreement or ADR form where the depositary registers additional ADSs at the same time and concludes that a new registration statement, rather than a post-effective amendment, is the appropriate vehicle.

Routine administrative or fee-schedule changes that do not register additional ADSs are normally handled through a post-effective amendment (form type F-6 POS), not a new F-6EF.

Fees, signatures, and effectiveness mechanics

The depositary computes the Section 6(b) fee on the registration fee table under Rule 457(k), which for Form F-6 bases the fee on the proposed maximum aggregate offering price of the ADSs registered — commonly the number of ADSs multiplied by a nominal per-ADS amount (often $5.00), reflecting the depositary's issuance-fee economics rather than the market value of the underlying foreign shares. The fee is paid via the SEC's lockbox or Fedwire process, with wire confirmation referenced in the filing.

The registration statement is signed by the depositary as registrant, by an authorized officer of the depositary, and by directors or officers as required by the Form F-6 signature instructions. In contrast to F-1, F-3, F-4, and similar forms, the foreign private issuer does not sign Form F-6EF. Section 11 liability for the registration statement attaches to the depositary and its signing persons; the subject company is described but is not a registrant.

Under Rule 466(a), a properly designated F-6EF is effective immediately upon filing, with no Section 8(a) order. The EDGAR accession timestamp marks effectiveness, and the depositary may immediately issue ADSs against deposits of the underlying securities.

Earliest records and historical scope

Form F-6 was adopted in 1983 (Securities Act Release No. 33-6459) to consolidate ADR registration onto a dedicated form, with Rule 466 adopted shortly afterward to allow auto-effectiveness for depositaries operating from established templates. Pre-EDGAR filings exist only on paper. The dataset captures EDGAR F-6EF accessions from January 2002 forward, by which point depositary ADR registrations had become uniformly electronic. Each accession represents one auto-effective registration event by a depositary, with its deposit agreement, form of ADR, Rule 466(a)(2) Exhibit (e) certification, opinion of counsel, consents, and registration fee table.

How This Dataset Differs From Similar Datasets or Filings

Form F-6EF's narrow scope — Securities Act registration of depositary shares evidenced by ADRs, made auto-effective under Rule 466 — places it next to several adjacent filings that are easy to confuse on form-number or subject-matter grounds. The comparisons below sharpen the boundaries.

Form F-6 (non-auto-effective)

Same form, same disclosure content (description of depositary shares, form of ADR certificate, deposit agreement, fees, holder rights), filed by the same depositary bank. The only difference is procedural: a plain F-6 goes through SEC review and requires a separate declaration of effectiveness, while F-6EF invokes the Rule 466 election for same-day effectiveness (available when the depositary's prior F-6 for that issuer is already effective or other Rule 466 conditions are met). Use F-6EF for the auto-effective subset; use F-6 for filings that went through standard review. Together they cover the full population of original ADR registrations.

Form F-6/A and Form F-6 POS (amendments)

Form F-6/A is a pre-effective amendment to a pending F-6; Form F-6 POS is a post-effective amendment to an already-effective F-6 or F-6EF, typically filed to modify the deposit agreement, raise the registered cap on depositary shares, or change other ADR-program terms. Neither establishes a new program. F-6EF tells you when an ADR program was created; F-6 POS tells you how its terms evolved afterward.

Form 20-F (foreign private issuer annual report)

Filed by the foreign operating company, not the depositary. Contains audited financials, MD&A, risk factors, and governance disclosure about the underlying issuer. It references the ADR program but does not register depositary shares. Use Form 20-F for the issuer's business and financials; use F-6EF for the structure, economics, and legal mechanics of the ADR vehicle (fees, ratios, depositary identity, holder rights).

Forms F-1, F-3, F-4 (registration of underlying securities)

Securities Act registrations filed by the foreign issuer for its own equity, debt, or deal consideration: Form F-1 is the long-form IPO/initial registration, Form F-3 the seasoned-issuer shelf, Form F-4 the M&A and exchange-offer form. The decisive distinction is the security being registered. F-1/F-3/F-4 register the underlying foreign-issuer shares or notes. F-6EF registers the ADR wrapper that evidences deposits of those shares. A registered US offering of a foreign issuer's equity in ADR form typically involves both: an F-1 or F-3 for the underlying shares plus an F-6/F-6EF for the ADRs. Use F-1/F-3/F-4 for prospectus content, use of proceeds, and underwriting; use F-6EF for the depositary mechanics.

Form 24F-2 (investment company annual fee notice)

Annual notice under the Investment Company Act of 1940 filed by open-end funds and UITs to report shares sold and remit registration fees. Different statute, different filer, different subject. Listed here only because researchers occasionally confuse the form numbers; there is no substantive overlap with Form 24F-2 and F-6EF.

Rule 12g3-2(b) submissions

Exemption from Section 12(g) Exchange Act registration for foreign private issuers that post home-country disclosure electronically. Submissions under 12g3-2(b) make foreign-language or home-jurisdiction materials accessible to US investors but register no securities. A 12g3-2(b) issuer can have an unsponsored ADR program (registered on F-6 by the depositary) without ever filing 20-F, and unsponsored ADRs commonly coexist with 12g3-2(b) reliance. Use 12g3-2(b) materials for unregistered home-country disclosure; use F-6EF for the ADR registration itself.

Form CB, Form 425, Schedules 13D and 13G (cross-border deals and ownership)

Form CB notifies the SEC of cross-border tender offers, rights offers, and business combinations involving foreign issuers. Form 425 carries prospectus and written communications in registered business combinations. Schedule 13D and Schedule 13G report beneficial ownership above 5% of a registered class. All are event-driven; none register ADRs. A tender offer for a foreign issuer's ADRs will generate CB, 425, and possibly 13D filings, but the ADR program being tendered for was originally registered on F-6 or F-6EF. Use these for transactional and ownership analysis; use F-6EF for the existence and terms of the ADR vehicle.

Form 8-A and exchange listing applications

Form 8-A is the short-form Exchange Act registration used to register a class for listing on a national securities exchange. The exchange listing itself (NYSE Listed Company Manual, Nasdaq Rule 5000 series) is handled through a separate exchange application. F-6EF is the Securities Act leg, registering the depositary shares for issuance. Form 8-A is the Exchange Act leg, registering the class for listing. Level I sponsored ADRs trade OTC and are registered on F-6/F-6EF without an 8-A. Use F-6EF to identify all SEC-registered ADR programs; use 8-A plus exchange materials to identify the exchange-listed subset.

Boundary summary

F-6EF is the only filing that captures, at the moment of auto-effective registration under Rule 466, the full deposit-agreement-level architecture of an ADR program: depositary identity, underlying issuer and class, ADR-to-share ratio, fee schedule, and holder rights. It is narrower than 20-F and F-1/F-3/F-4 (which cover the underlying issuer or its primary offerings), distinct from F-6 POS and F-6/A (which amend rather than originate), and entirely separate from event-driven cross-border deal filings, ownership schedules, and exchange listing materials. For questions about ADR program terms at inception under Rule 466, F-6EF is not substitutable by any neighboring dataset.

Who Uses This Dataset

The dataset serves a narrow set of professional users, each keyed to specific parts of the record.

ADR program counsel

Capital markets associates and partners advising depositaries, foreign private issuers, and underwriters use the dataset as a precedent bank for new and amended deposit agreements. They diff fee schedules (issuance, cancellation, cash-distribution, ADS-services), pre-release limits, voting-instruction mechanics, governing law, and tax pass-through language across peer programs. Most-referenced fields: the deposit agreement fee schedule, the form of ADR, and the ADR-to-deposited-security ratio. Output: redlines, precedent libraries, and negotiation memos.

Depositary bank product and operations teams

Depositary-bank product, operations, and legal groups monitor competitors' filings to track fee-schedule drift, template revisions, and program wins, losses, and depositary transfers. Operations focuses on ratio changes, cash-handling, and pre-release language; product tracks fees over time and by jurisdiction (via EDGAR jurisdiction codes); legal flags novel sanctions, tax, and corporate-action provisions. Workflow: pricing models, issuer RFP responses, and migration analyses.

Foreign private issuer in-house counsel and corporate secretaries

Securities counsel at non-US issuers considering a US listing or restructuring an existing program use the dataset to see what the depositary will file on their behalf, what the standard fee schedule looks like for jurisdiction and industry peers, and where atypical provisions (rights offerings, non-cash distributions, mandatory exchanges) have been negotiated. They read the deposit agreement, the form of receipt, and cover-page metadata to identify peer depositary choices.

Cross-border IPO and capital markets bankers

Bankers and underwriters' counsel structuring ADR-backed offerings coordinate F-6EF with the F-1 or F-3 and the exchange listing application. They confirm the ADR ratio and underlying-share denomination support the intended offer size, that the deposit agreement supports the distribution mechanics, and that the Exhibit (E) Rule 466 certification and signatures properly invoke the auto-effective path.

Outside counsel writing Exhibit (D) opinions

Counsel issuing the validity opinion on the depositary shares pull the dataset for precedent opinions on analogous structures and for the form currently accepted by staff. The Exhibit (D) opinion, the deposit agreement governing-law clause, and the form of ADR are the central inputs. Output: the closing validity opinion.

Reference-data vendors and academic researchers

Data engineering teams at securities reference-data vendors and academic researchers studying cross-listings and ADR economics build structured universes of sponsored ADRs from the corpus. They parse metadata.json for filer CIK, filing date, and accession number; extract depositary name, ADR ratio, and deposited-security identifier from the registration statement; and mine the fee schedule for cost-of-cross-listing studies.

Index providers and ADR-focused portfolio managers

Index research teams maintaining ADR indices and managers running ADR strategies or ETFs use the dataset to identify newly registered sponsored ADRs, separate sponsored from unsponsored programs, and detect terminations or restructurings affecting index membership. Cover-page metadata, the deposited-security list, and the ratio drive eligibility, free-float adjustments, and basket construction.

Broker-dealer product, compliance, and AML teams

Product-onboarding and compliance teams confirming an ADR is registered under the Securities Act and eligible for unrestricted US retail sale verify the existence of an effective F-6EF. They key on metadata.json (filer, accession, filing date) and the Exhibit (E) Rule 466 certification as evidence of effectiveness, supporting product-eligibility decisions and sponsored-versus-unsponsored surveillance.

EDGAR filing agents and financial printers

Filing agents and paralegals preparing F-6EF submissions reuse recent filings as templates, focusing on cover-page formatting, exhibit indexing, signature blocks, EDGAR header tagging, jurisdiction codes, and each depositary's most current standard deposit-agreement language. The dataset cuts preparation time and reduces formatting rejections.

Event-driven and special-situations analysts

Merger-arbitrage and special-situations desks tracking going-private transactions, schemes of arrangement, mandatory exchanges, and dual-listing changes affecting foreign private issuers read deposit-agreement provisions that govern how such events flow through to ADR holders: conversion mechanics, cash-out terms, and notice requirements. This drives trade structuring on ADR-listed targets.

In aggregate, drafting counsel, depositary banks, and issuers work the deposit agreement and fee schedule; deal teams and opinion counsel work Exhibit (D), Exhibit (E), and signatures; index, asset-management, and brokerage teams work metadata and the ADR ratio; vendors, researchers, and filing agents work the full structured corpus. Each group reads a different slice of the same record.

Specific Use Cases

Concrete workflows that researchers, counsel, depositary teams, deal teams, index providers, and compliance groups run against the F-6EF corpus. Each use case names the question being answered, the parts of the record it draws on, and how the workflow proceeds.

1. Building a precedent bank of ADR fee schedules

ADR program counsel and depositary product teams compare issuance, cancellation, cash-distribution, and ADS-services fees across peer programs to support fee benchmarking and new-program negotiation. The workflow extracts the fee table from inside Exhibit (A) (form of ADR / embedded deposit agreement), or from the standalone deposit agreement when filed as EX-99.1, and pivots fees by depositary (entities[0].companyName on the Filed-by side), Subject jurisdiction (stateOfIncorporation on the Subject), and filedAt year. Output: redline-ready fee comparables and a depositary-by-depositary fee-drift time series.

2. Constructing a structured universe of sponsored ADR programs

Reference-data vendors, ADR-focused portfolio managers, and academic researchers studying cross-listings build a master list of every Rule 466 auto-effective ADR program. The pipeline reads metadata.json for accessionNo, filedAt, the depositary CIK on entities[] (Filed by), the foreign-issuer CIK and fileNo (333- number) on (Subject), and the ADR / underlying tickers on tickers[], then parses the F-6EF cover page for the ADR-to-ordinary-share ratio and the registered ADS amount. Output: a clean issuer-depositary-ratio-fee-number panel keyed on accession.

3. Index eligibility and ADR basket construction

Index research teams maintaining ADR indices and ETF managers detect newly registered sponsored programs and separate sponsored from unsponsored. The job pulls month-level ZIPs as they land, filters on formType == "F-6EF" and the presence of an Exhibit (E) Rule 466 certification, joins the cover-page ADR ratio and registered-ADS amount, and emits add/drop candidates plus float-adjustment factors. Combined with later F-6 POS amendments it also surfaces ratio changes that trigger basket rebalances.

4. Broker-dealer product onboarding and US-retail eligibility checks

Broker-dealer product and compliance teams confirming that an ADR is Securities Act-registered and eligible for unrestricted US retail distribution verify the existence of an effective F-6EF for that depositary-issuer pair. The check keys on metadata.json (accessionNo, filedAt, Subject fileNo, depositary CIK) and the presence of EX-99.(E) / EX-5 Rule 466 certification signed by the depositary, with filedAt taken as the effectiveness moment. Output: a positive or negative eligibility flag attached to the ADR security master.

5. Cross-border M&A and special-situations deal structuring

Merger-arbitrage and special-situations analysts tracking going-private offers, schemes of arrangement, and mandatory exchanges affecting foreign private issuers read the ADR-holder mechanics directly out of Exhibit (A). They locate the deposit-agreement sections governing tender offers procedures, cash-out treatment, voting instructions, distribution-of-rights, and notice periods, then map them onto the deal timeline. Output: deal-flow models for ADR-listed targets and trade-structuring memos that account for the depositary's intermediary role.

6. Drafting and template generation by filing agents and outside counsel

EDGAR filing agents, financial printers, and capital-markets associates preparing a new F-6EF reuse recent filings by the same depositary as templates. They pull the latest accession for the chosen depositary, copy cover-page formatting, exhibit indexing, EDGAR header tags (<TYPE>, <SEQUENCE>, <FILENAME>), jurisdiction codes, and the depositary's current standard deposit-agreement text from Exhibit (A), and use the prior Exhibit (D) opinion and Exhibit (E) certification as form starting points. Output: a drafting-ready submission package and a reduced rate of EDGAR formatting rejections.

7. Validity-opinion precedent search for outside counsel

Outside counsel writing the Exhibit (D) validity opinion on a new ADR program search the corpus for precedent opinions on analogous structures (same depositary, same governing law, similar deposited-security class). The query targets documentFormatFiles[].type == "EX-99.(D)" or EX-4, joined to the form-of-ADR governing-law clause inside Exhibit (A) and to the issuing firm's name on the opinion. Output: a curated set of precedent opinions feeding the closing validity opinion.

8. Tracking depositary market share and program migration

Depositary product strategy and competitive-intelligence teams measure new-program wins, losses, and depositary-of-record changes. The analysis groups records by Filed-by depositary and Subject CIK, joins with subsequent F-6 POS amendments to detect changes in fees or registered amount, and joins with later F-6/F-6EF filings naming a different depositary for the same Subject as evidence of program migration. Output: quarterly market-share dashboards and a migration log keyed on Subject CIK.

9. Academic research on the cost and adoption of cross-listing

Researchers studying ADR economics, unsponsored-program waves, and the post-Rule 12g3-2(b) 2008 cohort assemble panels of ADR programs with their economic terms. They join the dataset against the Subject's 20-F filings (where one exists) and against home-market price data, using F-6EF fields for the registration date, ratio, registered ADS amount, and depositary identity, and the Exhibit (A) fee schedule for cross-listing-cost regressions. Output: papers on cross-listing premia, fee competition, and home-bias effects.

10. Compliance surveillance for sponsored-versus-unsponsored ADRs

Broker-dealer AML and surveillance teams distinguishing sponsored from unsponsored ADR programs use the dual-entity structure plus the deposit agreement's signatory block. Sponsored programs carry the foreign issuer as a counter-signatory inside Exhibit (A) and on the F-6EF signature page; unsponsored programs are signed by the depositary and its agent only. Output: a sponsored/unsponsored flag attached to each ADR symbol and feeding suitability and supervisory routines.

Dataset Access

The Form F-6EF Files Dataset covers filings from January 2002 to present, packaged as monthly ZIP containers. Each container holds the original EDGAR submission documents (HTML, TXT, PDF) and a JSON metadata file per accession number. There are three ways to access the data.

Dataset Index JSON API: https://api.sec-api.io/datasets/form-f6ef-files.json

Returns dataset-level metadata (name, description, last updated timestamp, earliest sample date, total records, total size, form types, container format, file types), the full dataset download URL, and the list of all monthly container files with per-container size, record count, updated timestamp, and download URL. Poll this endpoint to detect which containers changed in the most recent refresh and download only the affected slices. This endpoint does not require an API key.

Example response:

Example
1 {
2 "datasetId": "1f13365b-9ae0-6925-9a73-55cfbb82028a",
3 "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-f6ef-files.zip",
4 "name": "Form F-6EF Files Dataset",
5 "updatedAt": "2026-04-25T03:02:47.848Z",
6 "earliestSampleDate": "2002-01-01",
7 "totalRecords": 31361,
8 "totalSize": 230612573,
9 "formTypes": ["F-6EF"],
10 "containerFormat": "ZIP",
11 "fileTypes": ["HTML", "JSON", "TXT", "PDF"],
12 "containers": [
13 {
14 "downloadUrl": "https://api.sec-api.io/datasets/form-f6ef-files/2026/2026-04.zip",
15 "key": "2026/2026-04.zip",
16 "size": 1843221,
17 "records": 47,
18 "updatedAt": "2026-04-25T03:02:47.848Z"
19 }
20 ]
21 }

Download Entire Dataset: https://api.sec-api.io/datasets/form-f6ef-files.zip?token=YOUR_API_KEY

Downloads every monthly container as one ZIP archive covering the full date range from January 2002 to present. Use this for a one-shot bulk load of the complete corpus. This endpoint requires an API key.

Download Single Container: https://api.sec-api.io/datasets/form-f6ef-files/2026/2026-04.zip?token=YOUR_API_KEY

Downloads one monthly ZIP container, which is the most efficient option when only a specific month or date slice is needed, or when incrementally syncing newly updated months identified via the index API. Replace the year and month path segments to target a different period. This endpoint requires an API key.

Frequently Asked Questions

What does one record in the Form F-6EF Files Dataset represent?

One record represents a single Form F-6EF submission accepted by EDGAR, identified by its 18-digit accession number and materialized as a self-contained folder containing the F-6EF registration-statement HTML, the standard exhibit set (form of ADR, opinion of U.S. counsel, Rule 466 certification, and where applicable a standalone deposit agreement and amendments), and a metadata.json index. Each record corresponds to one auto-effective ADR program registration event — one foreign issuer, one class of deposited securities, one depositary.

Who files Form F-6EF, and does the foreign issuer sign it?

Form F-6EF is filed by a depositary bank — predominantly The Bank of New York Mellon, Citibank N.A., JPMorgan Chase Bank N.A., or Deutsche Bank Trust Company Americas — as the registrant and statutory issuer of the ADSs. The foreign private issuer whose shares are deposited is named on the cover page as the "subject company" but does not sign the registration statement and is not the registrant; Section 11 liability attaches to the depositary and its signing persons.

What is the difference between Form F-6 and Form F-6EF?

Both forms have identical disclosure, exhibit, and signature requirements, and both are Securities Act registration statements for ADSs evidenced by ADRs. The difference is procedural: Form F-6 goes through SEC staff review and requires a separate declaration of effectiveness under Section 8(a), while Form F-6EF invokes Rule 466 to take effect immediately upon EDGAR acceptance — conditioned on the depositary having a previously effective F-6 with no material variation other than the identity of the deposited securities and the ADS-to-share ratio. The presence of an Exhibit (E) Rule 466 certification is the structural marker that distinguishes F-6EF from a standard F-6.

Where does the substantive ADR-program content live inside a record?

Almost all substantive content lives in the exhibits, not in the F-6EF document itself. Exhibit (A) — the form of American Depositary Receipt (EX-99.(A) or EX-1) — is typically the largest document in the filing and embeds the full deposit agreement governing deposit/withdrawal mechanics, ADS issuance and cancellation, voting, dividends and rights, depositary fees, pre-release, FATCA tax mechanics, and amendment and termination. Any extraction targeting fees, voting rights, withdrawal rights, or deposit mechanics must operate on Exhibit (A) (and any standalone deposit-agreement exhibits filed as EX-99.1/EX-99.2), not on the F-6EF cover document.

What time period does the dataset cover, and in what format is it distributed?

The dataset covers EDGAR F-6EF accessions from January 2002 forward and is distributed as monthly ZIP containers under the path pattern <YYYY>/<YYYY-MM>.zip. Each accession unpacks to a folder named with the accession number stripped of dashes, containing a metadata.json index plus the registration-statement and exhibit documents in HTML, TXT, or PDF. JSON appears only as metadata.json; HTML dominates the document bodies for modern filings, with TXT and PDF appearing in older or atypical submissions.

Why are there always two entities in the entities[] block?

Every F-6EF involves two distinct EDGAR entities, and entities[] always carries both as a fixed-length pair. The first entity is the depositary bank, marked (Filed by) in companyName and carrying SIC code 8880. The second entity is the foreign private issuer, marked (Subject), which carries the 333-prefixed Securities Act file number, the film number, the non-U.S. jurisdiction code, and frequently a tickers[] array with the ADR symbol and any underlying ordinary-share symbol. This split — filer versus subject — is the structural signature of an F-6: the depositary is the legal registrant, but the regulated identity for the registration program is the foreign issuer.

Does the dataset include image files and the full SGML submission text?

No. Image attachments listed under documentFormatFiles[] with <TYPE>GRAPHIC (typically depositary logos or certificate vignettes) are referenced in metadata.json but are not bundled in the ZIP. The full SGML submission .txt envelope is referenced through linkToTxt and as a trailing documentFormatFiles[] entry but is also not bundled per accession. The documentFormatFiles[] listing remains the canonical inventory of the submission, so a consumer can reconcile what was filed against what the dataset materializes.

How does Form F-6EF differ from Form 20-F or Form F-1?

Form 20-F is the foreign private issuer's annual report, filed by the operating company and containing audited financials, MD&A, risk factors, and governance disclosure about the underlying issuer. Forms F-1, F-3, and F-4 are Securities Act registrations filed by the foreign issuer to register the underlying foreign-issuer shares or notes. Form F-6EF, by contrast, registers the ADR wrapper that evidences deposits of those shares — capturing depositary identity, the ADR-to-share ratio, fee schedule, and holder rights at the moment of auto-effective registration. A registered U.S. offering of a foreign issuer's equity in ADR form typically involves both an F-1 or F-3 for the underlying shares and an F-6/F-6EF for the ADR program.