Form SB-2MEF Files Dataset

The Form SB-2MEF Files Dataset is a closed historical corpus of every Rule 462(b) "more-equity" registration statement filed on Form SB-2MEF by small business issuers under Regulation S-B. Each record represents one short-form abbreviated registration statement that incrementally registered up to twenty percent of additional securities for an offering already declared effective on a predecessor Form SB-2, becoming effective immediately upon filing without further SEC review. The filer is always the same small business issuer — a U.S. or Canadian operating company with annual revenues and non-affiliate public common equity float each below 25 million dollars — that filed the underlying SB-2. Coverage spans March 1996, when Rule 462(b) and the MEF form family were introduced, through February 4, 2008, when the SEC rescinded Regulation S-B (Securities Act Release No. 33-8876) and retired the entire SB-form family in favor of the Smaller Reporting Company framework inside Form S-1, Form S-3, Form 10-K, and Form 10-Q. The dataset is distributed as monthly ZIP containers; each accession folder bundles a normalized metadata.json header with the original EDGAR submission documents (the registration cover document, the Exhibit 5 legality opinion, and Exhibit 23 expert consents) in their EDGAR-native SGML or HTML wrappers.

Update Frequency
Daily
Updated at
2026-04-15
Earliest Sample Date
1996-03-01
Total Size
1.7 MB
Total Records
330
Container Format
ZIP
Content Types
TXT, JSON, HTML
Form Types
SB-2MEF

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

66 files · 1.7 MB
Download All
2007-11.zip28.6 KB10 records
2007-09.zip10.2 KB4 records
2007-07.zip12.7 KB4 records
2007-06.zip75.6 KB11 records
2007-04.zip11.1 KB3 records
2006-12.zip18.2 KB6 records
2006-07.zip10.0 KB3 records
2006-06.zip75.8 KB1 records
2006-02.zip7.8 KB3 records
2005-12.zip13.9 KB6 records
2005-10.zip7.9 KB3 records
2005-07.zip7.4 KB3 records
2005-05.zip20.4 KB6 records
2005-03.zip9.0 KB3 records
2005-02.zip32.6 KB16 records
2005-01.zip8.2 KB3 records
2004-12.zip11.5 KB3 records
2004-11.zip8.0 KB3 records
2004-10.zip162.1 KB6 records
2004-09.zip8.8 KB3 records
2004-08.zip6.5 KB3 records
2004-07.zip9.5 KB5 records
2004-04.zip13.9 KB6 records
2004-02.zip7.2 KB3 records
2003-12.zip16.7 KB6 records
2003-11.zip12.6 KB6 records
2003-07.zip7.9 KB3 records
2003-06.zip14.5 KB7 records
2003-01.zip13.6 KB6 records
2002-11.zip22.7 KB9 records
2002-08.zip5.1 KB3 records
2002-07.zip162.7 KB8 records
2002-06.zip28.5 KB4 records
2002-05.zip10.3 KB4 records
2002-03.zip111.2 KB3 records
2002-02.zip110.9 KB3 records
2001-12.zip109.5 KB1 records
2001-07.zip8.8 KB4 records
2001-02.zip104.8 KB4 records
2000-02.zip11.7 KB6 records
1999-12.zip7.4 KB4 records
1999-07.zip5.2 KB3 records
1999-04.zip13.4 KB10 records
1999-02.zip100.7 KB5 records
1999-01.zip5.6 KB3 records
1998-12.zip7.1 KB3 records
1998-11.zip5.1 KB3 records
1998-10.zip7.2 KB6 records
1998-08.zip14.9 KB10 records
1998-06.zip21.9 KB12 records
1998-05.zip76.6 KB5 records
1998-03.zip5.8 KB3 records
1998-02.zip7.4 KB5 records
1997-12.zip6.9 KB4 records
1997-10.zip6.1 KB3 records
1997-09.zip12.1 KB6 records
1997-08.zip5.4 KB3 records
1997-07.zip5.7 KB3 records
1997-06.zip5.6 KB3 records
1997-01.zip5.5 KB3 records
1996-12.zip9.8 KB9 records
1996-11.zip21.0 KB9 records
1996-07.zip7.7 KB4 records
1996-06.zip9.4 KB7 records
1996-05.zip11.8 KB7 records
1996-03.zip4.9 KB3 records

What This Dataset Contains

Form SB-2MEF is a short-form abbreviated registration statement filed under Rule 462(b) of the Securities Act of 1933. Its purpose is narrow and procedural: it registers up to an additional twenty percent of the dollar amount of securities for an offering already declared effective on a predecessor Form SB-2. The "MEF" suffix denotes "Money, Effective" — the filing becomes effective immediately upon filing under Rule 462(b) without further SEC review, provided the new aggregate offering does not exceed 120% of the dollar amount registered on the predecessor SB-2 and the prior registration has not yet expired. Form SB-2 itself was the long-form registration vehicle reserved for "small business issuers" under Regulation S-B — issuers with revenues and public float each below $25 million. Because SB-2MEF rides on an already-effective SB-2, its content is intentionally minimal: rather than restating the full prospectus, it incorporates the predecessor SB-2 by reference and supplies only the incremental information necessary to register the additional shares, calculate and remit the additional registration fee, and renew the legal and accounting attestations attached to a registration statement.

The entire SB form family — SB-2, SB-2MEF, Form SB-1, SB-1MEF, 10-SB, 10-KSB, 10-QSB — was discontinued by the SEC effective February 4, 2008 (Release No. 33-8876, "Smaller Reporting Company Regulatory Relief and Simplification"), when scaled disclosure for smaller reporting companies was folded into the standard Forms S-1, S-3, 10-K, and 10-Q. Coverage of this dataset therefore spans a closed historical window from March 1996 through the form's retirement in early 2008. Because the dataset is defined by form type, it captures every SB-2MEF accession filed during the form's lifetime, regardless of whether the underlying SB-2 offering closed, was withdrawn, or was superseded.

Content Structure of a Single Record

One record in this dataset is a single Form SB-2MEF registration statement as accepted by EDGAR, identified by an 18-digit SEC accession number. Physically, each record is a folder named by the zero-padded, dashless accession number (for example 000095012005000545 for accession 0000950120-05-000545), nested inside a monthly ZIP partition keyed YYYY/YYYY-MM.zip that aggregates every SB-2MEF accepted in that calendar month. Inside the accession folder are one metadata.json header file and the full set of original EDGAR submission documents — the registration cover document and its exhibits — minus image attachments. The unit of analysis is therefore the filing as a whole: the short-form abbreviated registration statement plus its accompanying legal opinion and expert consent exhibits, packaged together with structured metadata describing the filer and the document inventory.

Two-layer content structure

Each accession folder contains two structurally distinct layers.

  1. metadata.json — a normalized, machine-readable header that catalogues the filing, names the parties, and enumerates the documents.
  2. EDGAR-native submission documents — SGML-wrapped text files in the early and middle years of the form, transitioning to HTML-bearing wrappers in the later years, that together comprise the submission as accepted by EDGAR.

The "Complete submission text file" (the unsplit EDGAR .txt with every document concatenated end-to-end) is referenced by URL inside metadata.json.documentFormatFiles[] but is not redistributed inside the ZIP; the per-document files inside the folder are the dataset's primary content. Image attachments referenced by the original submission (typically GIF or JPG) are excluded by design.

The metadata.json header

metadata.json is the canonical entry point for a record. Its top-level fields are:

  • formType: always SB-2MEF for this dataset.
  • accessionNo: the SEC accession number in canonical dashed form (e.g. 0000950120-05-000545).
  • filedAt: ISO-8601 timestamp with timezone offset, recording the moment EDGAR accepted the filing.
  • description: human-readable form description, typically "Form SB-2MEF - Registration adding securities to prior Form SB-2 registration [Rule 462(b)]".
  • linkToFilingDetails, linkToTxt, linkToHtml: URLs pointing to the EDGAR primary document, the consolidated submission text file, and the EDGAR filing index page (*-index.htm) respectively.
  • linkToXbrl: an empty string for every SB-2MEF record.
  • id: an opaque internal hex identifier.
  • documentFormatFiles[]: an ordered list mirroring EDGAR's document table. Each entry carries sequence, size, documentUrl, description, and type. The trailing "Complete submission text file" entry uses single-space sentinel strings for sequence and type.
  • dataFiles[]: an empty array for SB-2MEF.
  • entities[]: one or more party records describing the filer and any other named entities. Each entity carries companyName (with the role appended inline, e.g. ACME CORP (Filer)), cik (CIK), fileNo (the SEC file number assigned to the original SB-2 registration, in 333-NNNNNN form), irsNo, stateOfIncorporation, fiscalYearEnd (MMDD), act (typically 33 for Securities Act filings), sic (SIC industry code prefixed to its label, with HTML entities preserved), filmNo, type (the form type), and tickers (an array of historical and current ticker symbols associated with the CIK).

The submission document files

All non-metadata files in an accession folder are EDGAR-flavored documents wrapped in <DOCUMENT> blocks. Each document opens with header tags — <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION> — followed by <TEXT> containing the body, and closes with </TEXT></DOCUMENT>. These four header tags map one-to-one onto the corresponding entry in metadata.json.documentFormatFiles[], which makes the metadata array authoritative for enumerating and classifying the documents in a record. Filenames are EDGAR's original filer-supplied names and are not normalized: the registration document appears variously as d######.txt, sb2mef.txt, sb2mef.htm, or some issuer-specific stem; exhibit files appear as e######_exN.txt, exN-N.txt, exhibitN.txt, and similar variants. Because filer naming conventions vary record by record, downstream consumers should treat documentFormatFiles[] as the source of truth rather than directory listings.

Component-by-component anatomy of an SB-2MEF submission

A typical SB-2MEF submission contains a small, predictable set of documents corresponding to the minimum content required by Rule 462(b) and the General Instructions to Form SB-2.

1. Short-form registration statement (sequence 1, type SB-2MEF)

The primary document is short — typically a few hundred lines of fixed-pitch text or a comparably brief HTML rendering — and is structured around the requirements of Rule 462(b). Its constituent parts, in the order they appear, are:

  • Facing page / cover page. Identifies the registrant by exact corporate name, state of incorporation, IRS Employer Identification Number, principal executive office address, and primary SIC code. The cover names the agent for service, lists the prior Form SB-2 file number being incremented (in 333-NNNNNN form), explicitly invokes Rule 462(b), and confirms that the new registration becomes effective upon filing.
  • Calculation of Registration Fee table. A tabular block (rendered with EDGAR <TABLE>, <CAPTION>, <S>, <C>, <FN> tags in the SGML era and as standard HTML tables in later filings) listing the title of each class of securities being added, the additional amount to be registered, the proposed maximum offering price per unit, the proposed maximum aggregate offering price, and the registration fee being remitted. The aggregate offering price added by the SB-2MEF cannot exceed twenty percent of the dollar amount of the predecessor SB-2.
  • Rule 462(b) statement and incorporation by reference. Explicit statutory language declaring that the filing is made pursuant to Rule 462(b), referencing the prior effective SB-2 by file number, and incorporating the contents of that registration statement (prospectus, Part II information, previously filed exhibits) by reference. The substantive prospectus disclosure lives in the predecessor SB-2 and is not restated.
  • Signatures block. Signatures of the registrant and its principal officers and directors as required by the Securities Act, with names, titles, and dates. The SB-2MEF must be signed by the issuer, its principal executive officer, principal financial officer, controller or principal accounting officer, and a majority of the board of directors (or persons performing similar functions).
  • Index to Exhibits. A short list naming each exhibit included with the filing, by exhibit number and description.

2. Exhibit 5 — Opinion on legality (sequence 2, type [EX-5](https://sec.gov/interps/legal/cfslb19.htm))

A legal opinion of counsel addressed to the registrant, opining that the additional securities being registered are duly authorized and, when issued and paid for in accordance with the terms of the offering, will be validly issued, fully paid, and non-assessable. The exhibit is a letterhead-style document that names the law firm, recites the factual and legal basis for the opinion, states the opinion itself, addresses any qualifications, and consents to being named in the registration statement.

3. Exhibit 23 — Consents of experts (sequence 3+, type [EX-23](https://www.law.cornell.edu/cfr/text/17/229.601) and sub-exhibits such as EX-23.1, EX-23.2)

Short signed consents from auditors and any other experts named in the registration statement (most commonly the independent registered public accounting firm), permitting their reports and the reference to them as experts to be incorporated into the SB-2MEF. Each consent is typically a paragraph or two on firm letterhead. When multiple experts are named, multiple sub-exhibits appear (EX-23.1, EX-23.2, etc.).

4. Optional additional exhibits

Some records carry additional supporting exhibits — for example a power of attorney (EX-24), an underwriting agreement supplement, or other instruments — but the canonical content shape across SB-2MEF records is the three-document core above plus metadata.json. The minimal nature of the form is by design: the predecessor SB-2 already contains the financial statements, MD&A, business description, risk factors, and Part II information, none of which are restated in the MEF.

What the dataset record includes

For every accession folder the dataset bundles the structured metadata.json header and every individually itemized document from the EDGAR submission as a separate file in its EDGAR-native SGML or HTML wrapper. The full filing inventory — the registration document and each exhibit — is preserved with original filer-supplied filenames, original document headers, and original body content. Document classification (<TYPE>), ordering (<SEQUENCE>), and human-readable descriptions are preserved both inside each document's SGML header and in the documentFormatFiles[] array of the metadata header.

What is excluded or structurally separate

Three categories of content sit outside the record:

  1. Image attachments. GIF and JPG files referenced by the registration statement are excluded; these are typically logos or signature graphics and are not material to the textual disclosure.
  2. The consolidated "Complete submission text file". EDGAR's single concatenation of every document into one large .txt is referenced by URL in documentFormatFiles[] but is not duplicated inside the ZIP, since the per-document files already provide the same content split by document.
  3. The predecessor Form SB-2. Because SB-2MEF incorporates the prior SB-2 by reference, the full prospectus disclosure for the offering must be retrieved separately from the EDGAR record of that earlier filing. The link is the prior file number, recorded on the SB-2MEF cover page and surfaced in entities[*].fileNo.

Format and content evolution over the coverage window

The internal anatomy of an SB-2MEF filing was governed by a stable rule (Rule 462(b)) and a stable parent form (SB-2) throughout the dataset's coverage window, so the document mix — short registration document plus EX-5 legal opinion plus EX-23 consents — remained consistent from 1996 through early 2008. Within that window, periodic adjustments to Regulation S-B disclosure thresholds and to the Securities Act registration fee schedule changed the numbers appearing in the Calculation of Registration Fee table but did not alter the structural anatomy of the filing. The form's environment changed materially only at the close of the window: the February 4, 2008 rescission of Regulation S-B retired SB-2MEF, and Rule 462(b) registrations by smaller reporting companies thereafter were filed on Form S-1MEF or Form S-3MEF instead.

The presentation format of the documents shifts over the same window. In the earliest years (1996 through roughly the early 2000s), every document is a fixed-pitch ASCII text file wrapped in EDGAR SGML tags, with tabular content rendered using the <TABLE>, <CAPTION>, <S>, <C>, <FN>, and <PAGE> markup family. As the form's lifetime progressed, an increasing share of filers submitted HTML-rendered documents inside the same <DOCUMENT> SGML envelope, producing files with .htm or .html bodies that retain the EDGAR header tags but use HTML for presentation. Both formats coexist in the dataset: earlier records are predominantly plain text, later records lean toward HTML, and some mid-period records mix the two across documents within a single submission.

Interpretation and extraction notes

  • Substantive disclosure lives in the predecessor SB-2. The prospectus, financial statements, MD&A, and risk factors are not contained in the SB-2MEF record itself. Any analysis that needs them must join the SB-2MEF to the prior SB-2 keyed by entities[*].fileNo (333-NNNNNN), which also appears on the SB-2MEF cover page.
  • documentFormatFiles[] is the authoritative document inventory. Filer-supplied filenames vary widely (d######.txt, e######_exN.txt, exN-N.txt, sb2mef.htm, and many other patterns), so the metadata array — not the directory listing — should drive enumeration and typing.
  • Filter the trailing sentinel entry. The final entry in documentFormatFiles[] is the consolidated "Complete submission text file" and uses single-space strings for sequence and type. Iteration code should skip it explicitly.
  • companyName carries the role inline. The party role (e.g., (Filer)) is appended as a parenthetical suffix to the name string rather than represented in a separate role field.
  • HTML-entity encoding is preserved in JSON. SIC labels and similar fields retain encoded entities (for example &amp; rather than &) and should be decoded at consumption time if rendered as plain text.
  • Amendments are uncommon and out of scope. Because Rule 462(b) makes the SB-2MEF effective on filing, post-effective amendments are rare; when they occur, they are filed under separate accession numbers as form type SB-2MEF/A and do not appear in this single-form-type dataset.
  • EDGAR SGML is not well-formed XML. Each document is wrapped in EDGAR-flavored SGML rather than well-formed XML or HTML, so parsers should anticipate non-XML constructs — unclosed header tags, mixed-case tag names, and embedded <PAGE> separators — within the <TEXT> body.

Who Files or Publishes This Dataset, and When

Who files

Each record in the dataset is a single short-form registration statement filed on EDGAR by a small business issuer under Securities Act Rule 462(b). The filer is always the same legal entity that filed the underlying effective Form SB-2; SB-2MEF is an issuer-only filing.

Underwriters, placement agents, and selling securityholders are never the registrant, even when proceeds or resale activity flows through them. Counsel and auditors appear inside the document as named experts providing legality opinions and consents, but they are not filers.

Filer population: small business issuers under Regulation S-B

Eligibility was restricted to entities meeting the "small business issuer" definition in Item 10(a)(1) of Regulation S-B (17 CFR 228.10):

  • a U.S. or Canadian company,
  • not an investment company,
  • with annual revenues under 25 million dollars in its most recent fiscal year, and
  • with non-affiliate public common equity float under 25 million dollars.

A majority-owned subsidiary qualified only if its parent also met those tests. An issuer lost eligibility after exceeding either threshold for two consecutive years.

The population therefore consists of domestic small-cap and micro-cap operating companies and Canadian small business issuers using SB-2 instead of MJDS forms. It excludes investment companies, business development companies, asset-backed issuers, and non-Canadian foreign private issuers, all of which were ineligible for the SB-2 family. Larger issuers used Form S-1 or S-3 (with companion S-1MEF or S-3MEF), and well-known seasoned issuers and shelf registrants generally relied on automatic effectiveness under Rule 462(e) rather than the 462(b) mechanic.

Triggering event: Rule 462(b) registration of up to 20% additional securities

The record is event-driven, not periodic. It is triggered when an issuer with an effective Form SB-2 needs to register additional securities of the same class at or near pricing because demand, sizing, or final pricing exceeds the dollar amount or share count already registered.

Securities Act Rule 462(b) (17 CFR 230.462(b)) permits this incremental registration on a short-form companion filing that becomes effective immediately upon filing, subject to two limits:

  • the additional securities must be of the same class as those in the underlying registration; and
  • their aggregate offering price may not exceed 20 percent of the maximum aggregate offering price on the cover of the original effective registration statement.

There is no calendar deadline and no periodic cadence; an issuer may file zero, one, or several SB-2MEFs during the life of one SB-2 offering, but the cumulative 462(b) cap applies across them.

Timing and effectiveness mechanics

Rule 462(b) requires the SB-2MEF to be filed before the earlier of (i) the time confirmations are sent or given for sale of any of the additional securities and (ii) the time the underlying registration statement would have lapsed. In practice, SB-2MEFs are filed on the day or evening of pricing and are accompanied by payment of the registration fee for the incremental securities.

Effectiveness is automatic on filing and does not require Commission action. Amendments take the form SB-2MEF/A and are normally used to correct fee-table or scrivener errors, not to change offering structure.

Because the disclosure burden is satisfied by the underlying SB-2 prospectus, the SB-2MEF document itself is short: identification of the additional securities and offering price, a Rule 462(b) compliance statement, a legality opinion on the additional securities, and updated auditor and expert consents.

Regulatory framework

The underlying obligation is Section 5 of the Securities Act of 1933, which prohibits offers and sales without an effective registration statement. Form SB-2 was an optional registration form for small business issuers using the scaled disclosure regime of Regulation S-B (17 CFR Part 228), adopted by the Commission in 1992.

Rule 462(b) supplies the mechanic by which a properly limited companion filing takes effect on filing rather than by staff acceleration. Form SB-2MEF is the SB-2-specific implementation; parallel forms exist for other base registrations (S-1MEF, S-2MEF, S-3MEF, S-11MEF, F-1MEF, F-2MEF, F-3MEF).

Coverage window and discontinuation

The dataset begins in 1996, when Rule 462(b) and the MEF form family were introduced, and closes with the discontinuation of the SB form regime. The Commission eliminated Form SB-2 and the rest of Regulation S-B effective February 4, 2008 (Securities Act Release No. 33-8876), replacing them with scaled disclosure for "smaller reporting companies" inside Forms S-1, S-3, 10-K, and 10-Q. After that date, the 462(b) mechanic is implemented through Form S-1MEF or S-3MEF, and no SB-2MEF filings exist.

Important distinctions

  • SB-2MEF vs. post-effective amendment to SB-2: a post-effective amendment can register more than 20 percent of additional securities and update the prospectus but generally requires Commission acceleration; SB-2MEF is capped at 20 percent and effective on filing.
  • SB-2MEF vs. Rule 424(b) prospectus: a 424(b) supplement updates pricing or other information for already-registered securities and registers nothing new; SB-2MEF actually registers incremental securities and pays the corresponding fee.
  • SB-2MEF vs. S-1MEF / S-3MEF / F-series MEFs: same Rule 462(b) mechanic, different base form and different eligible filer class. Issuers that outgrew Regulation S-B during an offering migrated to S-1MEF or S-3MEF.
  • Non-filers inside the document: underwriters, selling securityholders, counsel, and auditors may be discussed or consent to being named, but the issuer is the sole registrant.
  • Ineligible entity types: investment companies (N-series forms), business development companies, asset-backed issuers (S-3/SF-3), and non-Canadian foreign private issuers (F-series MEFs) never filed SB-2MEF.

Because the dataset is defined by form type, it captures every SB-2MEF accession filed during the form's lifetime, regardless of whether the underlying SB-2 offering closed, was withdrawn, or was superseded. Each accession represents one Rule 462(b) registration event by one small business issuer.

How This Dataset Differs From Similar Datasets or Filings

Form SB-2MEF sits at the intersection of three narrow design choices: a Rule 462(b) "MEF" registration (24-hour, 20%-cap follow-on), the small business issuer regime under Regulation S-B, and a closed filing window ending February 4, 2008. The most useful comparisons are therefore the parent SB-2, the other Rule 462(b) MEF variants, the prospectus and amendment mechanisms that achieve adjacent goals, and the post-2008 Smaller Reporting Company regime that absorbed Reg S-B.

Form SB-2 (the parent registration)

SB-2 is the long-form small business registration that an SB-2MEF references and depends on: prospectus, business description, risk factors, Reg S-B scaled financials, plan of distribution, and Part II exhibits. SB-2MEF is a stub filing whose sole purpose is to register up to 20% additional securities of the same class, on the same terms, with automatic effectiveness on filing. SB-2 is narrative-heavy and self-contained; SB-2MEF is mechanical and only interpretable when joined to a specific prior SB-2 accession. Document volume per filing differs by roughly two orders of magnitude.

Form S-1MEF and Form S-3MEF

Direct structural analogs of SB-2MEF for non-small-business issuers. All three share the Rule 462(b) 20% cap, automatic effectiveness, and minimal content set (cover, fee table, incorporation by reference, legal and accountant consents). The distinction is the parent: S-1MEF supplements an S-1 (general long-form), S-3MEF supplements an S-3 (short-form for seasoned issuers), SB-2MEF supplements an SB-2 (small business under Reg S-B). S-3MEF filings dominate by count and dollar volume because S-3 issuers are larger and use shelf takedowns; SB-2MEF filings cluster among issuers with revenues or public float below $25 million. S-1MEF and S-3MEF remain active filing types; SB-2MEF is a closed population (1996–2008).

Form F-1MEF and Form F-3MEF

Foreign private issuer counterparts to S-1MEF and S-3MEF, also Rule 462(b) 20% registrations. They apply when the parent was an F-1 or F-3 and the issuer reports on Form 20-F / 6-K. SB-2MEF is exclusively domestic small business; the populations do not overlap, and no MEF form bridges the foreign and small-business regimes.

Rule 424(b) prospectus supplements

The most easily confused neighbor: 424(b) filings appear shortly after a base registration and relate to additional sales activity, but they disclose information (final pricing, terms, material updates) about securities already registered. SB-2MEF actually expands the registered amount by up to 20%. A single follow-on offering frequently produces both filings on the same day: an SB-2MEF to register the incremental shares and a 424(b) to describe pricing. 424(b) is a continuing, high-volume dataset across all issuer types; SB-2MEF is a narrow, closed historical set.

Post-effective amendments (POS AM, POS AMI, POS EX)

Both occur after the parent registration is effective and both can change what is registered, but POS AM can substantively update the prospectus, add new classes, refresh financial statements, or carry forward unsold securities, and generally requires staff review and a new effective date. SB-2MEF is locked to a 20% size increase of the same class on the same terms with same-day effectiveness. POS AM is broader, slower, and disclosure-rich; SB-2MEF is narrower, faster, and disclosure-light. (POS AMI and POS EX are related post-effective amendment variants.)

Form SB-2MEF/A

Amendments to a previously filed SB-2MEF, used to correct errors or supply omitted exhibits (typically consents). They do not register additional securities and are derivative records that must be joined back to the original SB-2MEF accession to be meaningful.

Form SB-1 and Form SB-1MEF

SB-1 was the smaller small business registration, capped at $10 million per 12-month period and using a question-and-answer disclosure format distinct from SB-2's narrative form. SB-1MEF is its Rule 462(b) counterpart. Both were retired alongside SB-2 in February 2008. SB-1MEF populations are much smaller than SB-2MEF and address a different offering tier; they are adjacencies, not substitutes.

Smaller Reporting Company framework (post-February 4, 2008)

The SEC eliminated Regulation S-B and the SB-form family by folding scaled disclosure into Regulation S-K and the standard registration forms via the "smaller reporting company" status flag. The functional successor to SB-2MEF is an S-1MEF (or S-3MEF, where eligible) filed by an SRC-flagged issuer. There is no one-to-one form-level replacement, so longitudinal research crossing 2008 must merge SB-2MEF with post-2008 S-1MEF/S-3MEF filings filtered on SRC status to maintain population continuity.

Boundary summary

SB-2MEF is the only dataset that combines all four of: Rule 462(b) automatic effectiveness with a 20% cap; Regulation S-B small business issuer scope; mandatory dependency on a named parent SB-2; and a closed filing window of March 1996 through February 2008. S-1MEF, S-3MEF, F-1MEF, and F-3MEF share the 462(b) mechanic but differ in issuer regime. SB-2 shares the issuer regime but is the long-form parent. 424(b) shares post-effective timing but registers no new securities. POS AM shares the post-effective amendment posture but is broader and not auto-effective. The SRC framework occupies the scaled-disclosure space but lives inside standard forms rather than a dedicated form family. SB-2MEF is therefore a finite, mechanical top-up tied to a specific SB-2 parent and is not substitutable by any single neighboring dataset.

Who Uses This Dataset

Because the SB-2MEF Files Dataset is a closed historical record of Rule 462(b) "more-equity" registrations filed by small-business issuers between 1996 and 2008, it is used as a reference corpus for legal precedent, regulatory history, and longitudinal small-cap research, not as a real-time feed.

Securities and capital markets counsel

Lawyers drafting modern S-1MEF, S-3MEF, and F-3MEF filings use SB-2MEF records as a precedent library for Rule 462(b) practice. They mine the cover-page registration fee table, the incorporation-by-reference language pointing to the base SB-2, the Exhibit 5 legal opinion, and the Exhibit 23 auditor consent for standard wording. Disclosure counsel handling restatement or litigation matters tied to SB-2-era issuers use the records to confirm exactly which securities were registered, when, and at what price.

Regulatory historians and rulemaking researchers

Researchers studying the pre-2008 small-business disclosure regime use the complete population of filings to characterize how Regulation S-B operated under the $25 million revenue and float thresholds. Filing counts, offering sizes, and issuer characteristics support empirical arguments about the policy effect of the transition to Item 10(f) scaled disclosure inside Forms S-1 and S-3.

Academic researchers in small-business capital formation

Finance and law academics treat a same-day MEF filing as a signal of strong demand or aggressive pricing on the base SB-2. They join the additional share count, offering price, filing date relative to base-SB-2 effectiveness, and named underwriter against secondary-market data to study dilution, post-issuance returns, and issuer survival in the small-cap segment.

Quantitative researchers running event studies

Quant teams use each filing as a discrete, machine-readable "registration capacity expansion" event for the 1996–2008 microcap universe. Accession numbers and filing dates join cleanly to price and volume histories for short-window return drift and dilution analysis on sub-$25M-revenue issuers underrepresented in standard event databases.

Small-cap and microcap market historians

Writers documenting late-1990s and 2000s small-cap activity, including the dot-com cycle and post-Sarbanes-Oxley period, use issuer name, CIK, filing date, and offering size from each accession to build cohort timelines of 462(b) top-up activity across market windows.

Forensic accountants and restatement researchers

Forensic accountants use the Exhibit 23 auditor consents to map which audit firms signed for which issuers on which dates. When an issuer later restated, was delisted, or faced enforcement, the consent chain across the SB-2MEF and its referenced SB-2 supports malpractice review, audit-firm exposure analysis, and disclosure-timeline reconstruction.

Litigation support and expert witnesses

Experts in securities class actions or fiduciary-duty matters tied to SB-2-era offerings pull the registration documents for the additional 20% tranche. Exhibit 5 legal opinions support disputes over validity of issuance; cover-page disclosures support disputes over offering size and use of proceeds. Preserved EDGAR submissions serve as primary-source authentication.

Financial data engineers and archival teams

Engineers maintaining comprehensive EDGAR archives ingest this small, complete population to close coverage gaps for a discontinued form type that commercial filing libraries often parse inconsistently. The metadata JSON normalizes issuer identifiers, filing dates, and linkage back to the parent SB-2.

Teams building retrieval systems for securities law need coverage of discontinued forms. The short, formulaic structure of SB-2MEF filings provides compact test cases for citation accuracy and indexes alongside modern MEF variants for questions about historical practice and form lineage. The filings contain no XBRL tagging.

Compliance and registration operations

Compliance staff at law firms and underwriters use the dataset for KYC, anti-fraud lookback, and successor-liability work when a current matter touches an entity that registered securities under SB-2 before 2008, recovering the exact additional share count and price.

Users cluster into four groups: counsel mining 462(b) drafting precedent for today's MEF forms; regulatory and academic researchers treating the filings as a complete population of a discontinued regime; quants and historians using each filing as a discrete capacity-expansion event; and forensic, litigation, and data engineering teams relying on it as a primary-source archive for otherwise poorly covered small-cap issuers.

Specific Use Cases

The following workflows reflect how practitioners use this closed 1996–2008 population of Rule 462(b) small-business top-up registrations.

Building a Rule 462(b) precedent library for modern MEF drafting

Securities counsel drafting current S-1MEF, S-3MEF, F-1MEF, or F-3MEF filings extract the cover-page Rule 462(b) invocation, the incorporation-by-reference paragraph pointing to a parent registration file number, the Calculation of Registration Fee table layout, and the Exhibit 5 opinion language from SB-2MEF accessions. Because the 462(b) mechanic survived the 2008 retirement of Reg S-B, the wording patterns transfer directly. The documentFormatFiles[] inventory inside metadata.json makes it straightforward to pull the EX-5 and EX-23 exhibits in bulk across the full filing population.

Reconstructing the additional-share tranche for litigation and restatement work

Forensic accountants, expert witnesses, and disclosure counsel handling matters tied to SB-2-era issuers use the cover page and fee table to recover the exact incremental share count, price per share, aggregate offering price, and registration fee for the 20% top-up tranche. The entities[*].fileNo (333-NNNNNN) on the SB-2MEF is the join key back to the predecessor SB-2 prospectus, allowing reconstruction of the full registered offering as it stood on the SB-2MEF effectiveness date.

Same-day demand-signal event studies on pre-2008 microcaps

Quantitative researchers treat the SB-2MEF filedAt timestamp as a discrete capacity-expansion event for sub-$25M-revenue issuers underrepresented in commercial event databases. Joining accessionNo, the additional aggregate offering price from the fee table, and entities[*].cik (with tickers) to CRSP-style price and volume histories supports short-window dilution and return-drift studies on the 1996–2008 microcap universe, often paired with same-day Rule 424(b) pricing supplements.

Each Exhibit 23 carries the signing audit firm, location, and consent date. Iterating across the records produces a per-CIK, per-date consent ledger that, when joined to later restatements, delistings, or enforcement actions against the same issuers, supports audit-firm risk and malpractice exposure analysis spanning both the SB-2MEF and the predecessor SB-2 it references.

Empirical characterization of the retired Reg S-B regime

Regulatory historians and rulemaking researchers use the complete closed population to compute filing-rate, offering-size, SIC-mix, and state-of-incorporation distributions for 462(b) activity under the Reg S-B small-business regime. The filedAt, entities[*].sic, entities[*].stateOfIncorporation, and the fee-table aggregate offering price together support empirical arguments about how the 2008 transition to scaled disclosure inside S-1 and S-3 changed small-issuer follow-on behavior.

Data engineering and retrieval-system teams ingest the dataset to close coverage of a discontinued form type that commercial filing libraries parse inconsistently. The normalized metadata.json header, the EDGAR-native SGML and HTML document wrappers, and the small total footprint make the corpus a clean test bed for citation-accuracy evaluation and for indexing historical 462(b) practice alongside live S-1MEF and S-3MEF feeds.

Dataset Access

The Form SB-2MEF Files Dataset is available through three access methods: a JSON metadata endpoint, a full archive download, and per-container downloads. Filings range from March 1996 through the form's discontinuation in February 2008, packaged in ZIP containers.

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

This endpoint returns dataset-level metadata along with a list of all container files and their individual download URLs. Each container entry includes its size, record count, and last updated timestamp, which makes it straightforward to detect which containers changed in the most recent refresh and download only those on a daily basis. This endpoint does not require an API key.

Example response:

Example
1 {
2 "datasetId": "1f13365b-9ae0-6a10-bf6a-741d38510479",
3 "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-sb2mef-files.zip",
4 "name": "Form SB-2MEF Files Dataset",
5 "updatedAt": "2026-04-15T18:25:34.120Z",
6 "earliestSampleDate": "1996-03-01",
7 "totalRecords": 330,
8 "totalSize": 1718834,
9 "formTypes": ["SB-2MEF"],
10 "containerFormat": "ZIP",
11 "fileTypes": ["TXT", "JSON", "HTML"],
12 "containers": [
13 {
14 "downloadUrl": "https://api.sec-api.io/datasets/form-sb2mef-files/2007/2007-12.zip",
15 "key": "2007/2007-12.zip",
16 "size": 142318,
17 "records": 12,
18 "updatedAt": "2026-04-15T18:25:34.120Z"
19 }
20 ]
21 }

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

Downloads the complete 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-sb2mef-files/2007/2007-12.zip?token=YOUR_API_KEY

Downloads one monthly container archive instead of the full dataset, which is useful for incremental syncing or for retrieving filings from a specific period. This endpoint requires an API key.

Frequently Asked Questions

What form does the Form SB-2MEF Files Dataset cover?

The dataset covers Form SB-2MEF, a short-form abbreviated registration statement filed under Securities Act Rule 462(b) that registers up to twenty percent of additional securities for an offering already declared effective on a predecessor Form SB-2. The "MEF" suffix denotes "Money, Effective" because the filing becomes effective immediately upon filing, without further SEC review.

What does one record in this dataset represent?

One record is a single Form SB-2MEF registration statement as accepted by EDGAR, identified by an 18-digit SEC accession number. Each record is a folder containing one metadata.json header file and the original EDGAR submission documents — the short-form registration cover document, the Exhibit 5 legality opinion, and one or more Exhibit 23 expert consents — wrapped in their EDGAR-native SGML or HTML envelopes.

Who was eligible to file Form SB-2MEF?

Only "small business issuers" as defined in Item 10(a)(1) of Regulation S-B (17 CFR 228.10): a U.S. or Canadian company, not an investment company, with annual revenues under 25 million dollars in its most recent fiscal year and non-affiliate public common equity float under 25 million dollars. The filer was always the same legal entity that filed the underlying effective Form SB-2; underwriters, selling securityholders, counsel, and auditors are never the registrant.

What time period does the dataset cover?

The dataset covers a closed historical window from March 1996, when Rule 462(b) and the MEF form family were introduced, through the form's discontinuation on February 4, 2008. After the SEC rescinded Regulation S-B (Securities Act Release No. 33-8876) and folded scaled disclosure into Forms S-1, S-3, 10-K, and 10-Q, no further SB-2MEF filings exist.

What file format is the dataset distributed in?

The dataset is distributed as monthly ZIP containers keyed YYYY/YYYY-MM.zip. Each container holds one folder per accession; inside each folder are a normalized metadata.json header and the EDGAR submission documents in their original SGML or HTML wrappers. Image attachments (GIF, JPG) are excluded by design, and the consolidated EDGAR "Complete submission text file" is referenced by URL but not duplicated inside the ZIP.

How does Form SB-2MEF differ from a Rule 424(b) prospectus supplement?

A Rule 424(b) supplement updates pricing or other information for securities that are already registered and registers nothing new; a Form SB-2MEF actually expands the registered amount by up to twenty percent and pays the corresponding registration fee. A single follow-on offering often produces both filings on the same day — an SB-2MEF to register the incremental shares and a 424(b) to describe final pricing.

How does Form SB-2MEF differ from Form S-1MEF and Form S-3MEF?

All three share the same Rule 462(b) mechanic — twenty percent cap, automatic effectiveness on filing, minimal disclosure set. The distinction is the parent form and the eligible filer class: S-1MEF supplements an S-1 (general long-form), S-3MEF supplements an S-3 (short-form for seasoned issuers), and SB-2MEF supplements an SB-2 (small business issuer under Regulation S-B). S-1MEF and S-3MEF remain active filing types, while SB-2MEF is a closed population that ended with the 2008 retirement of Regulation S-B.