Form S-BMEF Files Dataset

The Form S-BMEF Files Dataset packages every Form S-BMEF registration statement submitted to EDGAR from March 2004 to the present, organized as one accession folder per filing. Form S-BMEF is the abbreviated Rule 462(b) "matching effective filing" companion to Form S-B, the Schedule B registration statement used by foreign governments and political subdivisions thereof to register securities offerings under the Securities Act of 1933. A single record represents one Rule 462(b) abbreviated registration filed against a previously effective Form S-B to register up to an additional 20 percent of the prior aggregate offering price, becoming effective automatically and immediately upon filing. Each accession folder contains the documents the sovereign registrant transmitted to EDGAR — primary HTML body, exhibits, and the synthesized full-submission text bundle where present — together with a metadata.json describing the EDGAR header, the parties, and the document inventory.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures the complete EDGAR submission corpus for Form S-BMEF, the abbreviated Rule 462(b) companion to Form S-B. Form S-B is the Schedule B registration statement used by foreign governments and political subdivisions thereof to register securities offerings under the Securities Act of 1933. "Schedule B" refers to the schedule of disclosures that Section 7 of the Securities Act prescribes for sovereign issuers, distinct from Schedule A used by corporate registrants. Form S-BMEF is filed when the issuer wishes to register up to an additional 20 percent of the aggregate offering price covered by the prior, already-effective Form S-B and to have that additional registration take effect immediately upon filing.

The "MEF" suffix denotes the Rule 462(b) "matching effective filing" mechanic. Under Rule 462(b), a registration statement filed solely to register additional securities of the same class as those covered by an effective registration statement of the same registrant becomes effective upon filing, provided the new registration covers no more than 20 percent of the maximum aggregate offering price set forth for each class of securities in the prior fee table. The S-BMEF therefore piggybacks on the parent registration: it incorporates the parent's substantive disclosures by reference and supplies only the incremental information required, which is in practice the additional fee calculation, any Rule 430A pricing-related information that was previously omitted, fresh consents and legal opinions where applicable, and signatures.

The dataset covers every Form S-BMEF filed on EDGAR from March 2004 forward, distributed as monthly ZIP containers under a top-level ZIP archive, with HTML, JSON, and TXT file types inside each accession folder.

Who Files or Publishes This Dataset, and When

Who files

Form S-BMEF is filed by foreign sovereigns and their political subdivisions — the only issuer classes the Securities Act of 1933 routes through Schedule B. In practice that means:

• foreign governments (e.g., the United Mexican States, the Republic of Italy, the Republic of Korea, the State of Israel, the Republic of the Philippines, the Republic of Colombia), and
• political subdivisions of foreign governments (provinces, states, cantons, autonomous regions, and similar sub-sovereign public bodies issuing debt in their own name).

The legal registrant is the sovereign or sub-sovereign issuer itself, signing through its authorized financial officials (typically the finance ministry, treasury, or central debt management office) and through the U.S. authorized representative whose signature is required on foreign-sovereign filings. Underwriters and counsel appear in supporting roles but are not registrants.

S-BMEF is the Rule 462(b) companion to Form S-B, so eligibility tracks Form S-B eligibility exactly: only Schedule B issuers can file it.

When the filing is triggered

Form S-BMEF is event-driven, not periodic. It exists for one situation: a Schedule B issuer with an already-effective Form S-B shelf decides at pricing that demand exceeds remaining shelf capacity and elects to upsize the offering using Rule 462(b).

Rule 462(b) permits a registrant with an effective registration statement to file a follow-on registration that becomes effective automatically and immediately upon filing, provided:

• the new registration covers securities of the same class as those on the earlier, currently effective registration;
• the additional dollar amount registered does not exceed 20 percent of the maximum aggregate offering price of that same class on the earlier registration statement;
• the additional Section 6(b) filing fee for the incremental securities is paid at the time of filing; and
• the filing occurs no later than the time of confirmation of sales of the additional securities (Rule 462(b)(2)).

There is no SEC acceleration, declaration of effectiveness, or staff review cycle — effectiveness attaches at the moment of filing, and the upsized portion can be sold and confirmed in the same pricing event. Pricing-related information omitted from the underlying Form S-B in reliance on Rule 430A is typically supplied through the S-BMEF or the related prospectus mechanics.

Regulatory layering

Four authorities stack to produce an S-BMEF:

• Securities Act of 1933 — the governing registration statute.
• Schedule B — the disclosure schedule embedded in the Act itself, prescribing the content for foreign-government and foreign-political-subdivision registrations. Form S-B is the form on which Schedule B disclosure is delivered.
• Rule 462(b) — the mechanism allowing a same-class, up-to-20% supplemental registration to take effect immediately on filing.
• Section 6(b) — the fee provision under which the additional registration fee is paid concurrently with the S-BMEF.

Form S-BMEF itself is a short, mechanical filing that incorporates the underlying Form S-B by reference.

Important distinctions

• Form S-B vs. Form S-BMEF. Form S-B is the full Schedule B shelf registration and may be subject to staff review. Form S-BMEF is the abbreviated, automatic-effectiveness 462(b) companion used solely for the at-pricing 20% upsize.
• Foreign sovereigns vs. foreign corporates. Only foreign governments and political subdivisions register on Schedule B / Form S-B, so only they can file S-BMEF. Foreign private commercial issuers use Form F-1/F-3/F-4, with F-1MEF/F-3MEF/F-4MEF as their Rule 462(b) companions.
• Domestic issuers. U.S. domestic registrants use S-1/S-3/S-4 with S-1MEF/S-3MEF/S-4MEF — never S-BMEF.
• Multilateral and supranational issuers. The IBRD (World Bank), IADB, ADB, and similar multilaterals register under their own enabling legislation and SEC schedules, not Schedule B, and do not file S-BMEF.
• Deadline ceiling. "No later than time of confirmation of sales" is a hard cutoff under Rule 462(b)(2); a late S-BMEF cannot retroactively register securities already sold.
• Cap mechanics. The 20% ceiling is measured against the maximum aggregate offering price of the same class on the prior effective Form S-B. A second S-BMEF on the same shelf is possible only if same-class headroom remains within that 20% cap.
• Frequency. No recurring schedule applies. A sovereign issuer may go years between S-BMEF filings or never file one, since most Schedule B shelves are sized to absorb upsizes without needing 462(b) relief.

Content Structure of a Single Record

What one record represents

One record in the Form S-BMEF Files Dataset is a single EDGAR submission of Form S-BMEF, identified by its 18-digit accession number and materialized on disk as one accession folder. Each folder bundles the documents the foreign-sovereign registrant transmitted to EDGAR for that submission (image attachments excluded) together with a metadata.json file that captures the parsed EDGAR header, the party identifiers, and the document inventory in a structured form. Functionally, a record is the complete, machine-readable representation of one Rule 462(b) abbreviated registration statement filed against a previously effective Form S-B (Schedule B) registration.

Container and folder organization

The dataset is distributed as a top-level ZIP archive that decomposes into per-month ZIP containers under a <year>/<year>-<month>.zip path convention. Decompressing a monthly ZIP yields a flat list of accession folders, one per S-BMEF submission filed in that month. Folder names use the 18-digit EDGAR accession number with hyphens removed (for example, 000119312507136629 for accession 0001193125-07-136629), matching the directory convention used inside sec.gov/Archives/edgar/data/<cik>/<accession-no-hyphens>/. Months containing no S-BMEF filings produce no container, so the year/month index is sparse rather than continuous.

Per-record file inventory

Inside an accession folder the file inventory is intentionally minimal. Every record contains a metadata.json describing the submission, plus the document files transmitted to EDGAR for that accession. The file types present in the dataset are HTML, JSON, and TXT; image files originally attached to the EDGAR submission (logos, scanned signature graphics, decorative imagery) are excluded from the dataset packaging. For a typical S-BMEF accession the folder reduces to two artifacts: the JSON metadata and a single primary HTML document, conventionally named dsbmef.htm by the financial-printer agents that prepare these submissions. Larger accessions may add one or more .htm exhibits (legality opinions, expert consents, pricing supplements) and, in some cases, the synthesized full-submission .txt SGML bundle as a sibling file.

The metadata.json schema

The metadata file describes the submission at the EDGAR header level and is the structured anchor for cross-referencing the document files. Its top-level fields are:

• formType — fixed at "S-BMEF".
• accessionNo — the canonical hyphenated EDGAR accession number, for example "0001193125-07-136629".
• filedAt — ISO 8601 timestamp with timezone offset, capturing the EDGAR acceptance time.
• description — a short text label describing the form's regulatory role.
• linkToFilingDetails — URL to the primary document on sec.gov/Archives/edgar/....
• linkToTxt — URL to the full-submission SGML text file (the <accession>.txt bundle on EDGAR).
• linkToHtml — URL to the EDGAR filing-index HTML page.
• linkToXbrl — empty string for this form type.
• documentFormatFiles — array of objects, one per document in the submission. Each entry carries sequence, size (bytes, encoded as a string), documentUrl, description, and type. The synthesized full-submission text bundle, when listed, appears as an entry with a blank type and a single-space sequence, matching EDGAR's convention for the auto-generated complete-submission file.
• dataFiles — empty array; there are no XBRL or structured financial-data attachments for this form type.
• entities — array of party objects describing each filer or co-filer. Each entity carries companyName (with the EDGAR role suffix in parentheses, for example "PERU REPUBLIC OF (Filer)"), cik (zero-padded to ten digits), irsNo, fileNo (the EDGAR file number assigned to the S-BMEF, distinct from the parent S-B file number), act ("33" for the Securities Act), fiscalYearEnd, type, sic (a single string combining the numeric code and label, for example "8888 Foreign Governments"), and filmNo.
• id — a hex content identifier assigned by the dataset pipeline.

A structurally important detail: the entities[].fileNo value is the new 333-series file number assigned to the S-BMEF itself, not the file number of the parent S-B. The parent registration's file number appears inside the document body on the facing page as a Registration No. reference and must be parsed from the HTML if downstream code needs to link the abbreviated filing back to its parent.

The SGML <DOCUMENT> envelope around the HTML body

Each document file inside the accession folder is not raw HTML; it is wrapped in EDGAR's SGML <DOCUMENT> tag envelope, even when the inner payload is HTML. The envelope carries four header tags before the <TEXT> payload:

• <TYPE> — the document type code, S-BMEF for the primary document and exhibit codes such as [EX-5](https://sec.gov/interps/legal/cfslb19.htm) (legality opinion) or [EX-23](https://www.law.cornell.edu/cfr/text/17/229.601) (auditor or expert consent) for exhibits.
• <SEQUENCE> — the ordinal position of the document within the submission, 1 for the primary.
• <FILENAME> — the on-disk filename inside the submission, for example dsbmef.htm.
• <DESCRIPTION> — a free-text label such as POST-EFFECTIVE AMENDMENT NO. 3 TO SCHEDULE B.

The <TEXT> block then contains the full HTML document, including <HTML>, <HEAD>, <TITLE>, and <BODY>. Closing </TEXT></DOCUMENT> tags terminate the envelope. Any extraction pipeline must strip the SGML wrapper before treating the payload as standalone HTML; conversely, the wrapper is the canonical place to read the document's filer-declared type and sequence, independent of the inventory in metadata.json.

Required content of the S-BMEF document body

Inside the HTML body, an S-BMEF registration statement follows a tightly prescribed Rule 462(b) layout. The document is short — usually a small handful of pages — because virtually all substantive disclosure is incorporated by reference from the parent S-B. The recurring components, in the order they appear, are:

• Facing page. The standard "As filed with the Securities and Exchange Commission on [date]" header, the new EDGAR file number assigned to the S-BMEF, and a Registration No. reference identifying the parent S-B that this filing tops up. The facing page also carries the form-type title block, typically phrased as "REGISTRATION STATEMENT UNDER SCHEDULE B OF THE SECURITIES ACT OF 1933" or, where the S-BMEF is structured as a post-effective amendment to the parent, "POST-EFFECTIVE AMENDMENT NO. [n] TO REGISTRATION STATEMENT UNDER SCHEDULE B".
• Registrant identification block. The sovereign issuer's name (for example, Republic of Peru) and contact details, followed by the U.S. Authorized Representative block — a U.S.-resident agent for service of process required for foreign-government filers, often a consulate general or U.S. counsel.
• Counsel "Copies to:" block. The U.S. legal counsel handling the offering, listed for service of communications from the Commission.
• Calculation of Registration Fee table. A tabular block with rows for each class of securities being registered (typically Debt Securities, Warrants, Units, and a Total row for sovereign shelf programs) and columns for Title of Each Class of Securities to be Registered, Amount to be Registered, Proposed Maximum Offering Price Per Unit, Proposed Maximum Aggregate Offering Price, and Amount of Registration Fee. Because Rule 462(b) caps the additional registration at 20 percent of the parent's aggregate offering price, the figures here represent that incremental top-up rather than a full offering.
• Footnotes to the fee table. A series of numbered footnotes (commonly (1) through (8)) explaining the fee calculation methodology, currency translation if applicable, the application of Rule 457 in the prior S-B and any fee carry-forward, and reservations of the right to issue securities in series, in different currencies, or with original-issue discount.
• Explanatory Note. A short narrative block explicitly invoking Rule 462(b) and stating that the registration statement is filed solely to register additional securities of the same class as those covered by the prior effective S-B and that it becomes effective immediately upon filing. This note is the structural marker that distinguishes an S-BMEF from a substantive post-effective amendment.
• Incorporation-by-reference statement. The body explicitly incorporates the contents of the prior Schedule B registration statement by reference, so that the underlying disclosures — the description of securities, the sovereign issuer's economic and political profile, the fiscal information schedules required under Schedule B, and any Rule 430A pricing-related information — flow through from the parent filing without restatement.
• Rule 430A pricing-related information. Where the parent S-B was filed under Rule 430A — which permits omission of pricing-related information from the prospectus at effectiveness — the S-BMEF may be the vehicle that supplies the previously omitted information for the additional 20 percent (price to the public, underwriting discounts and commissions, proceeds to the issuer, and similar terms). When present, this appears as a discrete pricing-supplement section before the signatures.
• Required opinions and consents. Where the additional securities require fresh attorney opinions on the legality of the securities (Exhibit 5) or consents from named experts (Exhibit 23), these are filed as exhibits and referenced from the body. Many S-BMEF filings rely on Rule 457 fee carry-forward and the parent S-B's existing opinions and consents and therefore omit new exhibits entirely.
• Signature page. A signature block executed by the registrant's authorized officer — for sovereign issuers typically a senior finance-ministry official such as a Director of Public Credit or Director General of Public Indebtedness — followed by a second "Signature of Authorized Representative" block signed by the U.S.-resident authorized representative (often a consul general). The dual-signature pattern is mandatory for foreign-government filers.

Included content

A record includes the SGML-wrapped HTML body of the S-BMEF primary document with all the components above, the metadata.json describing the EDGAR submission, and any additional .htm exhibits the filer transmitted (legality opinions, expert consents, pricing supplements). When the synthesized full-submission .txt SGML bundle is also packaged inside the folder, it duplicates the document content already present as separate files.

Excluded or separate content

Image files attached to the original EDGAR submission (logos, scanned signatures, decorative graphics) are excluded from the per-folder packaging. The parent Form S-B registration statement and its exhibits — which carry the substantive disclosure that the S-BMEF incorporates by reference — are not bundled into the S-BMEF record; they live in their own EDGAR submission and must be fetched separately using the parent Registration No. visible inside the S-BMEF body. There is no XBRL or Inline XBRL payload for this form type; structured-data tagging requirements have never extended to Schedule B sovereign registrations.

Interpretation and extraction notes

Several nuances matter for downstream extraction:

• The primary document's extension is .htm, but the file is not parseable as raw HTML until the <DOCUMENT>...<TEXT>...</TEXT></DOCUMENT> SGML envelope is stripped.
• The dataset functions largely as a pointer system into a parent filing: the substantive disclosures live in the prior Form S-B and must be retrieved separately, using the parent Registration No. parsed from the facing page rather than the new entities[].fileNo in the metadata, which identifies the S-BMEF itself.
• The Calculation of Registration Fee table is the principal source of structured per-record data — class of security, amount to be registered, aggregate offering price, fee paid — and is amenable to table extraction, but column headers and row labels vary modestly across sovereign filers and across years and should be normalized rather than parsed positionally.
• The Explanatory Note is the most reliable textual marker confirming Rule 462(b) status and immediate effectiveness and is a useful anchor for automated classification, particularly where the facing-page title block is phrased as a post-effective amendment rather than a fresh registration.
• The dual signature block (authorized sovereign officer plus U.S. authorized representative) is required and consistent for sovereign filers and is the cleanest location to extract the names and titles of the filing officials.
• The structural layout of records is stable across the dataset's full date range. The metadata.json shape, the SGML envelope, and the body's facing-page-through-signatures sequence have not drifted, and there is no migration to PDF, XML, or Inline XBRL within this form type.
• Gaps in the year/month index reflect the absence of qualifying filings rather than incomplete coverage: Rule 462(b) is a narrow procedural mechanism, and the filer universe is concentrated on a recurring set of foreign-government issuers, all carrying SIC code [8888 Foreign Governments](https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&SIC=8888&owner=exclude&count=100).

How This Dataset Differs From Similar Datasets or Filings

Form S-BMEF sits at a narrow intersection: the Schedule B regime for foreign-sovereign issuers and the Rule 462(b) "MEF" mechanism for last-minute upsize registrations. The most useful comparisons fall into three groups: the parent Schedule B filing, the parallel MEF upsize forms for non-sovereign issuers, and adjacent foreign-government filings that often co-occur with S-BMEF in the same issuer's EDGAR history.

Form S-B (Schedule B registration)

S-B is the parent that S-BMEF presupposes: the full registration statement filed by a foreign government or political subdivision under Schedule B of the Securities Act of 1933, containing the complete prospectus, exhibits, opinions, and consents.

S-BMEF differs on three concrete axes:

• Scope. S-BMEF can register only up to an additional 20 percent of the dollar amount already covered by the prior effective S-B.
• Effectiveness. S-BMEF auto-effects on filing under Rule 462(b); S-B becomes effective only after staff review and a declaration of effectiveness.
• Document set. S-BMEF is intentionally thin — facing page, a short statement incorporating the prior S-B by reference, fresh opinions and consents, signature page, and any Rule 430A pricing information — not a full prospectus.

The two datasets are complementary: S-B carries substantive disclosure, S-BMEF carries the upsize mechanics referencing it.

Corporate MEF forms (S-1MEF, S-3MEF, F-1MEF, F-3MEF, S-11MEF)

These are the parallel Rule 462(b) upsize registrations for non-sovereign registrants — operating companies (Form S-1MEF, Form S-3MEF), foreign private issuers (Form F-1MEF, Form F-3MEF), and real estate registrants (Form S-11MEF). All share S-BMEF's Rule 462(b) mechanic: immediate effectiveness on filing, a 20 percent dollar-amount cap, and a window tied to the pricing of the offering.

The decisive difference is the underlying statutory schedule and the filer population. Corporate MEF forms attach to Schedule A registrations by operating companies or REITs; S-BMEF attaches exclusively to Schedule B registrations by sovereign issuers. Disclosure content diverges accordingly: issuer-specific business, financial, and risk disclosure on the corporate side; sovereign disclosure on the economy, public finances, and external debt on the S-BMEF side. In volume terms, S-BMEF is by far the rarest of the family — dozens of filings versus thousands for S-1MEF and S-3MEF — so corporate MEF datasets are not a usable proxy for sovereign upsize activity.

Asset-backed MEF (SF-1MEF, SF-3MEF)

Form SF-1MEF and Form SF-3MEF are the Regulation AB analogs, riding on Forms SF-1 and SF-3. They share the Rule 462(b) auto-effectiveness mechanic and 20 percent ceiling, but the underlying regime — pool-level ABS disclosure, transaction parties, servicing, asset characteristics — has nothing in common with sovereign debt. Structurally analogous, substantively unrelated.

Rule 424(b) prospectus supplements

A 424(b) supplement delivers final pricing, terms, or supplemental disclosure for an already-effective registration. It is a disclosure document, not a registration statement, and registers no additional securities. S-BMEF, by contrast, increases the registered amount itself. In sovereign offerings the two are often filed within the same window — S-BMEF expands the registered offering, 424(b) delivers the pricing prospectus supplements to investors — but they answer different legal questions and are not interchangeable as data sources.

Form 18 and Form 18-K (foreign-government filings)

Form 18 is the historical Schedule B registration form for foreign governments and political subdivisions. Form 18-K is the annual report filed by foreign governments that have previously registered U.S. securities, refreshing economic, fiscal, and debt-stock disclosure each year. Both share S-BMEF's sovereign filer population, but 18-K is recurring and periodic while S-BMEF is event-driven and tied to a specific upsized offering. They serve different research questions: 18-K for ongoing sovereign reporting, S-B / S-BMEF for offering-specific registration.

Form F-X

Form F-X is a procedural filing — the appointment of a U.S. agent for service of process — routinely submitted by foreign sovereigns and foreign private issuers in connection with Schedule B and other foreign registrations. It contains no offering, financial, or pricing content. F-X filings often appear alongside or shortly before S-B and S-BMEF in the same issuer's history, making them useful as a cross-reference for identifying sovereign filer populations, not as a source of registration substance.

Boundary summary

S-BMEF is defined by the intersection of three narrow conditions:

1. The issuer is a foreign government or political subdivision (excludes every corporate MEF form).
2. The prior registration is a Schedule B filing (excludes every Schedule A and Regulation AB MEF).
3. The filing is a Rule 462(b) upsize that auto-effects on filing, capped at 20 percent (excludes the parent S-B itself, 424(b) pricing supplements, F-X procedural filings, and 18-K periodic reports).

That intersection makes S-BMEF the rarest member of the MEF family and the most specialized sovereign registration event captured on EDGAR. A complete picture of a sovereign offering typically requires pairing S-BMEF with the underlying S-B, related 424(b) supplements, and, where relevant, the issuer's F-X appointment and 18-K annual reports.

Who Uses This Dataset

The user base is narrow and clusters around sovereign-debt capital markets, securities law, and EDGAR engineering. Across these groups the load-bearing fields are the same: entities[] (filer name and CIK), filedAt, the referenced prior Schedule B file number, and the documentFormatFiles[] payload (facing page, incorporation-by-reference statement, opinions, consents, signatures, and any Rule 430A pricing material).

Sovereign DCM Bankers and Syndicate Desks

Sovereign and EM coverage bankers and syndicate desks read each S-BMEF as a near-real-time deal-upsize signal. They watch filedAt and the prior Schedule B file number to identify which sovereign program is being topped up, then pull the registered-amount language from documentFormatFiles[] to size the in-flight tranche. The output is book-building intelligence on competing mandates and league-table forecasting.

Sovereign Issuer's Counsel

Sovereign capital markets practice groups at international and U.S. law firms use the dataset as a precedent library. Because the form is rarely filed, drafters mine documentFormatFiles[] for facing pages, incorporation-by-reference language, validity and tax opinions, consents, and finance-ministry signature blocks. entities[] plus the prior Schedule B file number reconstruct the chain of registration documents for any one sovereign across mandates.

Underwriters' Counsel

Underwriters' counsel on sovereign syndicates use the dataset to run the Rule 430A pricing-supplement workflow. They check the additional 20 percent registered under the S-BMEF against the original Schedule B amount to confirm coverage of the priced offering, align the comfort, opinion, and consent package to the upsized shelf registration, and rely on filedAt to establish effectiveness ahead of any sale.

EM Sovereign Fixed-Income Research

Sell-side and buy-side EM sovereign credit analysts fold S-BMEF events into issuance calendars and supply models. The filer in entities[], filedAt, and the linked Schedule B let them update gross issuance forecasts, net financing estimates, and country-level supply commentary, since a top-up usually precedes or accompanies a tap or new tranche.

EM Sovereign Portfolio Managers and Trading Desks

Hard-currency EM debt PMs and sovereign bond trading desks use the dataset to anticipate same-day supply pressure on a sovereign curve. They correlate filedAt with order-book activity and price action to position hedges in CDS, benchmarks, and curve trades around the announced upsize.

Sovereign Debt Management Offices and Issuer Legal

Debt management offices, finance ministries, and central bank legal teams running SEC-registered programs use the dataset to coordinate their own EDGAR pipeline against precedent. They reference prior entities[] CIK conventions, signature blocks, and incorporation-by-reference structure, and use documentFormatFiles[] for continuity when counsel or staff rotate.

Legal Research and Forms-Precedent Editors

Editors of practice-area form libraries, treatises, and CLE materials on sovereign offerings treat each accession as canonical. They tag documentFormatFiles[] by issuing sovereign and filedAt to build form annotations and sovereign-debt practice notes around facing pages, opinions, and consent text.

International Finance and Securities Law Academics

Quantitative researchers in sovereign debt correlate filedAt against secondary-market spreads, FX, and macro variables to test whether sovereigns systematically upsize into receptive markets; the small population makes a full census tractable. Securities law scholars read the document text and signatures to study how Rule 462(b) is used by foreign governments across jurisdictions of incorporation.

EDGAR Data Engineers and Issuance-Tracker Platforms

Engineering teams building EDGAR analytics, sovereign-bond data products, and primary-market trackers ingest the dataset for full form-type coverage. They consume entities[], form type, filedAt, accession number, and prior Schedule B file number to normalize S-BMEF events into the same schema as S-B and 424B records, and parse documentFormatFiles[] to extract the additional registered amount and link each top-up to its parent shelf in an issuer-program graph.

Broker-Dealer Compliance and Primary-Market Surveillance

Broker-dealer compliance on sovereign syndicates and primary-issuance surveillance teams use the dataset to confirm that allocations fall within registered capacity after the top-up. They reconcile the prior Schedule B file number, the additional amount in documentFormatFiles[], and the filedAt effectiveness stamp against allocation records to rule out sales against unregistered amounts.

Specific Use Cases

The use cases below tie directly to specific record fields and document slices.

Real-time sovereign upsize alerting

Subscribe to filings where formType is S-BMEF and treat the filedAt timestamp as the moment a sovereign shelf is topped up under Rule 462(b). Because S-BMEF auto-effects on filing, filedAt is also the effectiveness stamp, giving DCM desks and EM trading a same-day signal that the issuer named in entities[].companyName has just expanded its registered offering capacity ahead of a tap or new tranche.

Computing the incremental registered amount

Parse the Calculation of Registration Fee table inside the SGML-wrapped primary HTML (the dsbmef.htm payload referenced from documentFormatFiles[]) to extract the additional Amount to be Registered, Proposed Maximum Aggregate Offering Price, and Amount of Registration Fee per class of securities. The result is a structured per-record measure of the 20 percent top-up size, suitable for sovereign gross-issuance models and league-table forecasts.

Linking each top-up to its parent Schedule B program

Note that entities[].fileNo identifies the S-BMEF itself, not the parent. To build an issuer-program graph, parse the parent Registration No. reference from the facing page of the HTML body and join each S-BMEF accession back to the corresponding Form S-B submission. This produces a sovereign-program ledger that connects every upsize event to the underlying shelf for any one issuer CIK.

Coverage reconciliation for underwriters' counsel and compliance

Underwriters' counsel and broker-dealer surveillance teams use filedAt as the effectiveness stamp and the fee table's aggregate offering price to confirm that allocations on a priced sovereign deal fall within registered capacity after the top-up. The reconciliation joins the parent Schedule B amount, the S-BMEF incremental amount, and the actual allocation records to rule out sales against unregistered notional.

Rule 430A pricing-supplement extraction

Where the parent S-B was filed under Rule 430A, the S-BMEF carries the previously omitted pricing-related information (price to public, underwriting discounts, proceeds to issuer) as a discrete section before the signature block. Extracting this slice from the HTML body produces a structured pricing record per upsized tranche, useful for downstream offering-economics analysis and for aligning the comfort, opinion, and consent package to the priced deal.

Sovereign drafting precedent library

Mine documentFormatFiles[] for facing pages, incorporation-by-reference paragraphs, Explanatory Notes invoking Rule 462(b), Exhibit 5 legality opinions, Exhibit 23 consents, and the dual signature block (sovereign authorized officer plus U.S. authorized representative). Indexed by entities[].cik and filedAt, this becomes a precedent library for sovereign capital markets counsel preparing the next S-BMEF for the same or a comparable issuer.

Training a sovereign-debt event extractor

The consistent SGML <DOCUMENT> envelope (<TYPE>S-BMEF, <SEQUENCE>, <FILENAME>, <DESCRIPTION>) wrapping a stable facing-page-through-signatures body provides a clean labeled corpus for training extractors that pull issuer name, parent registration number, incremental registered amount, fee paid, and signing officials. The structural stability across the dataset's full date range, with all filers carrying SIC 8888 Foreign Governments, makes the population a tractable full census rather than a sample.

Dataset Access

Dataset Index JSON API: [https://api.sec-api.io/datasets/form-sbmef-files.json](https://sec-api.io/datasets/form-sbmef-files)

This endpoint returns metadata describing the Form S-BMEF Files Dataset, including the dataset name, description, last updated timestamp, earliest sample date, total record and byte counts, covered form types (S-BMEF), container format (ZIP), and file types (HTML, JSON, TXT). It also returns the full dataset download URL and the complete list of container files, with each entry exposing its key, size, record count, last updated timestamp, and per-container download URL. Use this index to monitor which containers were refreshed in the most recent run and to decide which containers to download incrementally on a day-by-day basis.

This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a65-a76e-e63e90b32b9e",
        

          3
            "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-sbmef-files.zip",
        

          4
            "name": "Form S-BMEF Files Dataset",
        

          5
            "description": "Form S-BMEF is a registration statement filed under Rule 462(b) of the Securities Act of 1933 to register up to an additional 20 percent of securities covered by a prior effective Form S-B (Schedule B) registration statement. Form S-B is used by foreign governments and political subdivisions thereof to register securities offerings in the United States, and the S-BMEF becomes effective immediately upon filing.",
        

          6
            "updatedAt": "2026-04-16T08:50:26.128Z",
        

          7
            "earliestSampleDate": "2004-03-01",
        

          8
            "totalRecords": 39,
        

          9
            "totalSize": 194718,
        

          10
            "formTypes": ["S-BMEF"],
        

          11
            "containerFormat": "ZIP",
        

          12
            "fileTypes": ["HTML", "JSON", "TXT"],
        

          13
            "containers": [
        

          14
              {
        

          15
                "downloadUrl": "https://api.sec-api.io/datasets/form-sbmef-files/2026/2026-03.zip",
        

          16
                "key": "2026/2026-03.zip",
        

          17
                "size": 13818,
        

          18
                "records": 2,
        

          19
                "updatedAt": "2026-04-16T08:50:26.128Z"
        

          20
              }
        

          21
            ]
        

          22
          }
        

Download Entire Dataset: [https://api.sec-api.io/datasets/form-sbmef-files.zip](https://sec-api.io/datasets/form-sbmef-files)?token=YOUR_API_KEY

Downloads the complete Form S-BMEF Files Dataset as a single ZIP archive containing every container file. This endpoint requires an API key.

Download Single Container: [https://api.sec-api.io/datasets/form-sbmef-files/2026/2026-03.zip](https://sec-api.io/datasets/form-sbmef-files)?token=YOUR_API_KEY

Downloads one individual monthly container instead of the full dataset, which is useful for incremental updates based on the updatedAt timestamps returned by the index JSON. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form S-BMEF, the abbreviated Rule 462(b) "matching effective filing" companion to Form S-B. It is filed solely to register up to an additional 20 percent of the aggregate offering price covered by a prior, already-effective Form S-B (Schedule B) registration statement, and it becomes effective automatically and immediately upon filing.

What does one record in this dataset represent?

One record is a single EDGAR submission of Form S-BMEF, identified by its 18-digit accession number and materialized on disk as one accession folder. Each folder contains a metadata.json describing the EDGAR header, parties, and document inventory, plus the document files transmitted to EDGAR — typically a single primary HTML document such as dsbmef.htm, optional .htm exhibits (legality opinions, expert consents, pricing supplements), and sometimes the synthesized full-submission .txt SGML bundle.

Who is required to file Form S-BMEF?

Only foreign governments and their political subdivisions — the issuer classes the Securities Act of 1933 routes through Schedule B — can file Form S-BMEF. The legal registrant is the sovereign or sub-sovereign issuer itself, signing through its authorized financial officials (typically the finance ministry, treasury, or central debt management office) and through the U.S. authorized representative whose signature is required on foreign-sovereign filings. Domestic and foreign corporate issuers use parallel MEF forms (S-1MEF, S-3MEF, F-1MEF, F-3MEF) and never file S-BMEF.

When is a Form S-BMEF filing triggered?

Filing is event-driven, not periodic. A Schedule B issuer files an S-BMEF when, at pricing, demand for an offering exceeds the remaining capacity of an effective Form S-B shelf and the issuer elects to upsize using Rule 462(b). The filing must occur no later than the time of confirmation of sales of the additional securities, with the additional Section 6(b) filing fee paid concurrently.

How does this dataset differ from the Form S-B dataset?

Form S-B is the full Schedule B shelf registration containing the complete prospectus, exhibits, opinions, and consents, and becomes effective only after staff review and a declaration of effectiveness. Form S-BMEF is intentionally thin — facing page, fee table, Explanatory Note invoking Rule 462(b), incorporation-by-reference statement, signatures, and any Rule 430A pricing supplement — and auto-effects on filing. The two datasets are complementary: S-B carries the substantive disclosure that the S-BMEF incorporates by reference.

What time period does the dataset cover, and how is it organized?

The dataset includes every Form S-BMEF filed on EDGAR from March 2004 to the present. It is distributed as a top-level ZIP archive that decomposes into per-month ZIP containers under a <year>/<year>-<month>.zip path convention, with one accession folder per submission inside each monthly container. Months containing no S-BMEF filings produce no container, so the year/month index is sparse rather than continuous.

Does the dataset include XBRL or structured financial data?

No. The linkToXbrl field in metadata.json is an empty string and the dataFiles array is empty for every record. Structured-data tagging requirements have never extended to Schedule B sovereign registrations, so the principal source of structured per-record data is the Calculation of Registration Fee table parsed from the HTML body.

How do I link an S-BMEF record back to its parent Form S-B?

The entities[].fileNo value in metadata.json is the new 333-series file number assigned to the S-BMEF itself, not the parent. The parent registration's file number appears inside the document body on the facing page as a Registration No. reference and must be parsed from the HTML to join each S-BMEF accession back to the corresponding Form S-B submission.