The Form SF-1MEF Files Dataset is a structured collection of EDGAR submissions of Form SF-1MEF — the abbreviated, automatically effective companion to Form SF-1 used under Rule 462(b) of the Securities Act of 1933 to register up to twenty percent of additional asset-backed securities of a class already covered by an effective Form SF-1. Each record corresponds to one filed SF-1MEF submission and is delivered as a per-accession folder containing a metadata.json descriptor plus the HTM documents that constitute the submission (the primary SF-1MEF document, an EX-5.1 legality opinion, and an EX-107 calculation-of-filing-fee exhibit).
Records are organized inside monthly ZIP containers keyed by year and year-month (for example, 2022/2022-07.zip). The dataset begins with filings made in May 2022, after Regulation AB II split asset-backed registration off from the general S-1/S-3 framework and after the SEC's October 2021 fee-table amendments made Exhibit 107 mandatory for new registration statements. Distributed file types are HTML and JSON; SF-1MEF carries no XBRL.
Because Form SF-1 is used exclusively for asset-backed securities, every SF-1MEF involves a dual-registrant pattern — a sponsor or depositor and a bankruptcy-remote issuing entity — both of which appear as separate filers in the EDGAR header with their own CIKs and Securities Act file numbers. The dataset is intentionally narrow: it captures one specific event, the Rule 462(b) twenty-percent capacity expansion of an already-effective, non-shelf ABS registration.
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:
A single record in the Form SF-1MEF Files Dataset corresponds to one EDGAR submission of Form SF-1MEF — that is, one filed abbreviated registration statement under Rule 462(b) of the Securities Act of 1933, used to register additional asset-backed securities of up to twenty percent of the maximum aggregate offering price already covered by a prior effective Form SF-1. Concretely, each record is a per-accession folder named with the eighteen-digit dash-stripped accession number, containing a metadata.json descriptor and the HTM documents that constitute the EDGAR submission. Every accession folder bundles, at minimum, the SF-1MEF facing-page document and any exhibits the registrant filed contemporaneously with that submission. It does not bundle the upstream parent SF-1 contents that the SF-1MEF incorporates by reference.
Records are organized inside monthly ZIP containers by year and year-month (e.g., 2022/2022-07.zip); each ZIP unpacks to a single year-month folder that holds one subfolder per accession. The accession folder is the indivisible record unit; everything inside it pertains to one and only one SF-1MEF filing. All shipped documents are HTML wrapped in a thin SGML <DOCUMENT> envelope, and submission metadata is JSON. Image files referenced inside the HTML (firm-letterhead logos, exhibit graphics) and the consolidated submission .txt SGML wrapper are intentionally not shipped in the dataset; only HTM and JSON files are present.
Form SF-1MEF is the abbreviated, automatically effective companion to Form SF-1, the long-form registration statement used for offerings of asset-backed securities under the SEC's Regulation AB II framework. The "MEF" suffix denotes a Rule 462(b) "money effective" filing — a filing made under Rule 462(b) of the Securities Act of 1933 for the limited purpose of registering additional securities of the same class already registered on a previously effective Form SF-1. The form is not used to introduce new disclosures, new classes of securities, or new transaction structures. It is a pure upsizing mechanism: the registrant tops up the dollar amount of an existing offering by no more than twenty percent of the maximum aggregate offering price set out in the parent SF-1's calculation-of-registration-fee table (or the Exhibit 107 fee table for parents filed after the 2022 fee-table amendments).
Two structural features of the form follow directly from Rule 462(b) and Section 8(a) of the Securities Act of 1933. First, the SF-1MEF becomes effective immediately upon filing — there is no SEC review, no acceleration request, and no waiting period; the filing is deemed effective by operation of Rule 462(b) so long as the original registration statement is itself effective and the additional fee is paid concurrently. Second, the filing does not need to repeat the prospectus, transaction summary, risk factors, structural diagrams, pool data, or other Regulation AB II disclosures already contained in the parent SF-1; instead, it incorporates the parent registration statement (and any pre-effective amendments thereto) by reference in its entirety. The SF-1MEF therefore reads less like a standalone offering document and more like a short cover-and-signature wrapper that points back at the parent and carries forward only those exhibits that must be refreshed at the moment of upsizing — typically a fresh legality opinion and a new calculation-of-filing-fee table.
Each accession folder contains two layers of content. The first is the EDGAR-level submission metadata, expressed as a single metadata.json object. The second is the document layer, expressed as one or more HTM documents that retain a thin SGML <DOCUMENT> envelope around an HTML body. The file types found in the dataset are therefore HTML and JSON.
The HTM documents in a Form SF-1MEF record fall into three predictable roles:
<TYPE>SF-1MEF, sequence 1 — containing the facing page, Rule 462(b) check-box, Explanatory Note, Part II exhibit index, and dual signature pages.<TYPE>EX-5.1 — satisfying Item 601(b)(5) of Regulation S-K.<TYPE>EX-FILING FEES (Exhibit 107) — presenting the structured fee table required by Item 601(b)(107) of Regulation S-K following the SEC's October 2021 fee-table amendments.A handful of additional exhibits (consents, secondary opinions, supplemental agreements) may appear when the registrant chooses to file them with the SF-1MEF rather than rely on the parent SF-1's exhibits, but these are uncommon. The vast majority of exhibits required by Items 601(a) and 601(b) of Regulation S-K — underwriting agreement, indenture and series supplement, organizational documents, servicing and pooling agreements, tax opinions, trustee Form T-1 statements, financing orders, powers of attorney — remain at the parent SF-1 and are picked up by reference.
metadata.json is a single JSON object describing the EDGAR filing at the submission level. It carries formType fixed to "SF-1MEF", the dashed accessionNo, an effectivenessDate that — by operation of Rule 462(b) — coincides with the filing date, a precise filedAt ISO 8601 timestamp with timezone offset, a short human-readable description, and three URL fields (linkToFilingDetails, linkToTxt, linkToHtml) pointing at the EDGAR copies of the primary document, the consolidated .txt submission, and the EDGAR filing-index page. The linkToXbrl field is empty because Form SF-1MEF does not carry XBRL data.
Two arrays do the structural work:
documentFormatFiles enumerates every document EDGAR received in the original submission, including those not shipped in the dataset (notably image files with type value "GRAPHIC" and the complete submission text wrapper with an empty type). Each entry records sequence, size, documentUrl, a human-readable description such as "SF-1MEF", "EX-5.1", or "EX-FILING FEES", and an EDGAR type code.entities enumerates the filers. For SF-1MEF asset-backed registrations this array characteristically contains two entries — the sponsor or depositor and the issuing-entity SPV — each with companyName (annotated with a role such as (Filer)), cik, fileNo (the SPV's number conventionally formed as the sponsor's file number plus a -01 suffix), irsNo, stateOfIncorporation, fiscalYearEnd, act (typically "33"), sic, filmNo, and type. An optional tickers array is populated only for the publicly listed sponsor; the SPV has no ticker.The seriesAndClassesContractsInformation and dataFiles arrays are present but empty for this form type.
This document carries the regulatory substance of the filing. Its components, in order of appearance, are:
Facing page. Begins with the "As filed with the Securities and Exchange Commission on <date>" line, blank 333- placeholders for the registration numbers to be assigned by EDGAR, and the formal banner "UNITED STATES SECURITIES AND EXCHANGE COMMISSION / WASHINGTON, D.C. 20549 / FORM SF-1 / REGISTRATION STATEMENT UNDER THE SECURITIES ACT OF 1933". The printed form caption reads "FORM SF-1"; the MEF designation is conveyed by the Rule 462 check-box rather than a different banner.
Two-column registrant block. A side-by-side identification table listing each registrant's exact legal name, state of incorporation, primary SIC code, Commission File Number, IRS Employer Identification Number, and principal executive offices. The sponsor/depositor occupies the left column; the issuing entity occupies the right column.
Agent-for-service block. Names a designated officer of the sponsor (typically the general counsel or corporate secretary) with full mailing address and telephone number.
Copies-to block. Outside counsel contact information, often two firms — one representing the sponsor, the other the issuing entity.
Approximate date of commencement of proposed sale. Boilerplate phrasing such as "As soon as practicable after the effective date of this Registration Statement".
Rule 462 check-box panel. A short list of check-boxes corresponding to Rules 462(b), 462(c), and 462(d). For SF-1MEF the 462(b) box is checked, and the file number(s) of the earlier related effective Form SF-1 (and any pre-effective amendments) are entered on the 462(b) line.
Effectiveness statement. A one-paragraph affirmation that the registration statement will become effective immediately upon filing pursuant to Rule 462(b) under the Securities Act of 1933.
Explanatory Note. A short narrative section that identifies the parent SF-1 by Securities Act file number and effective date, states the additional dollar amount being registered (which must be no more than twenty percent of the parent's maximum aggregate offering price), often restates updated per-tranche principal amounts for the upsized offering, and recites that the contents of the parent registration statement, including all exhibits and powers of attorney, are incorporated by reference into this SF-1MEF.
Part II — Information Not Required in Prospectus. Because the prospectus itself is incorporated by reference, the SF-1MEF body proper consists almost entirely of Part II. The dominant element is the Exhibit Index, a two-column table listing exhibit number and description across the standard Item 601 numbering: 1.x (underwriting agreement), 3.x (organizational documents of the issuing entity), 4.x (indenture, series supplement, form of note), 5.1 (legality opinion), 8.1 (tax opinion), 10.x (servicing agreement, administration agreement, pooling and servicing agreement, intercompany notes), 21.1 (subsidiaries), 23.x (consents of counsel and auditors), 24.x (powers of attorney), 25.1 (Form T-1 trustee eligibility), 99.x (financing orders, constitutional opinions, independent manager consents), and 107.1 (calculation of filing fee table). Exhibits are tagged with footnote symbols indicating "to be filed by amendment", "previously filed with the original SF-1", "previously filed with Pre-Effective Amendment No. _", or "filed herewith". For an SF-1MEF, the overwhelming majority carry "previously filed" tags; only EX-5.1 and EX-107.1 are typically marked "filed herewith".
Signatures (dual signature pages). One signature page for the sponsor and a second for the issuing entity. Each opens with a corporate signature executed by a duly authorized officer (often the COO or treasurer), followed by individual signature blocks for the Principal Executive Officer, Principal Financial Officer, Principal Accounting Officer, and a majority of the board of directors or LLC managers. Individual signatures appear as /s/ Name entries in tabular rows alongside title and date. Many of the individual signatures are executed by an attorney-in-fact pursuant to powers of attorney filed with the parent SF-1.
A standalone outside-counsel opinion letter delivered to the registrants in HTM form, satisfying Item 601(b)(5) of Regulation S-K. Its internal structure is conventional: law-firm letterhead (often referencing a JPG logo that is not shipped with the record), date, addressee block, "Re:" subject line identifying the SF-1MEF and the underlying securities, recitals defining the Initial Registration Statement (the parent SF-1 plus any pre-effective amendments) and the Additional Registration Statement (this SF-1MEF), an examined-documents and assumptions paragraph, numbered opinions covering due organization and good standing of the issuing entity, entity power, due authorization, and the conclusion that the bonds (or notes), when issued and authenticated against payment in accordance with the indenture, will be valid and binding obligations subject to standard bankruptcy and equitable-remedies carve-outs, jurisdictional limits, consent to filing as an exhibit, and a signature block.
The structured calculation-of-filing-fee table required by Item 601(b)(107) of Regulation S-K, introduced by the SEC's October 2021 amendments to Rule 408 of Regulation S-T and Item 601(b) of Regulation S-K. Internally this is an HTML table with a two-column registrant header naming the sponsor and issuing entity, a "Table 1: Newly Registered Securities" block, and column headings for Security Type, Security Class Title, Fee Calculation or Carry Forward Rule, Amount Registered, Proposed Maximum Offering Price Per Unit, Maximum Aggregate Offering Price, Fee Rate, and Amount of Registration Fee. Footnotes reconcile the Rule 462(b) twenty-percent cap, identify any unused fees carried forward, and offset previously paid fees against the new amount due.
Every shipped HTM document opens with the canonical EDGAR SGML envelope:
1
<DOCUMENT>
2
<TYPE>...
3
<SEQUENCE>...
4
<FILENAME>...
5
<DESCRIPTION>...
6
<TEXT>
7
<HTML>...</HTML>
8
</TEXT>
9
</DOCUMENT>
The <TYPE> value matches the EDGAR document type code (SF-1MEF, EX-5.1, EX-FILING FEES), and <SEQUENCE> orders the documents within the submission. Inside <TEXT> is full HTML, almost always heavy on <TABLE> elements because the facing page, registrant block, exhibit index, signature pages, and fee table are all tabular by convention.
A record includes everything needed to read the SF-1MEF as filed: the JSON metadata descriptor; the primary SF-1MEF HTM with facing page, dual-registrant block, Rule 462(b) check-box, effectiveness language, Explanatory Note, Part II exhibit index, and dual signature pages; the EX-5.1 legality opinion; the EX-107 calculation-of-filing-fee table; and the SGML <DOCUMENT> envelope around each HTML body. Filer identification, dual-registrant entity records, accession metadata, document URLs back to sec.gov, and the 462(b)-driven effectivenessDate are all surfaced through metadata.json.
The record deliberately omits:
.txt SGML wrapper that EDGAR also stores at the accession URL.linkToHtml in metadata).Financial_Report.xlsx, no R*.htm rendering files, and no *.xml instance documents are present, and Regulation AB II's structured asset-data requirements (Schedule AL, Items 1111 and 1125 asset-level XML under Regulation AB) attach to the parent SF-1's prospectus and pool-data filings, not to the abbreviated MEF top-up.The dual-registrant entity array makes plain that the issuing entity is a separate filer with its own CIK, but no organizational documents for that entity travel with the SF-1MEF; they sit in the parent SF-1 by reference.
Form SF-1 and its abbreviated companion SF-1MEF were created by the Commission's 2014 Regulation AB II rulemaking (Release Nos. 33-9638 / 34-72982), which split asset-backed registration off from the general S-1/S-3 framework. Before that, asset-backed offerings were registered on Form S-1 or Form S-3, and the corresponding twenty-percent top-up filings appeared on Form S-1MEF or Form S-3MEF. From the 2014 effective date forward, ABS registrants have used SF-1 and SF-3 (with SF-1MEF and SF-3MEF as their respective MEF variants). The dataset begins in May 2022, well after that transition was complete. The internal structure of the SF-1MEF — facing page, Rule 462(b) check-box, Explanatory Note, Part II exhibit index, dual-registrant signatures — has been stable across the dataset's coverage window.
The most consequential post-2014 change visible in the records is the introduction of Exhibit 107 (EX-FILING FEES), the standalone calculation-of-filing-fee table. The SEC's October 2021 fee-table amendments (Release No. 33-10997) to Item 601(b) of Regulation S-K and Rule 408 of Regulation S-T removed the fee table from the registration statement's facing page and required it instead as a separately tagged exhibit (EX-FILING FEES, exhibit 107) in a structured tagging-friendly format. Compliance for new registration statements such as SF-1 and SF-1MEF was required beginning in 2022 — effectively coinciding with the dataset's May 2022 start. Records in this dataset therefore consistently carry an EX-107 exhibit document; the older convention of a facing-page fee table does not appear.
The Rule 462(b) framework that governs the form's effectiveness — immediate effectiveness upon filing under Section 8(a) of the Securities Act, subject to the twenty-percent ceiling on additional registered amount and the requirement that the registration fee be paid concurrently — has remained in force throughout the dataset window and supplies the same structural skeleton (check-box, effectiveness paragraph, Explanatory Note tying back to the parent SF-1 file number) across every record.
Several nuances bear on machine extraction and interpretation:
Heavy incorporation by reference. Reading an SF-1MEF in isolation will not yield the offering's economic terms, transaction structure, pool composition, or risk factors. Those live in the parent SF-1 identified in the Explanatory Note and on the Rule 462(b) check-box line. The parent's Securities Act file number (and its -01 issuing-entity counterpart) is the join key that links an SF-1MEF record back to its primary registration statement.
Dual-filer pattern. The entities array in metadata.json reliably contains two filers (sponsor/depositor and issuing entity), often with different states of incorporation (the sponsor in its operating state, the SPV typically in Delaware). Both must be matched to identify the transaction; relying on only one filer will misclassify the deal. The two file numbers share a common base (333-NNNNNN and 333-NNNNNN-01), which is itself a useful pairing key.
Twenty-percent cap and fee offsets. The dollar amount registered on an SF-1MEF is capped at twenty percent of the parent SF-1's maximum aggregate offering price under Rule 462(b). The Explanatory Note typically discloses both the cap and the precise additional amount being registered, and the EX-107 exhibit reconciles the new fee against amounts already paid on the parent.
Immediate effectiveness. effectivenessDate equals the filing date because Rule 462(b) makes the SF-1MEF effective upon filing under Section 8(a) of the Securities Act. Downstream users that filter for "effective registration statements" will find every SF-1MEF effective on its filedAt date with no acceleration order intervening.
Signature attribution via powers of attorney. Most individual director and officer signatures on the SF-1MEF are executed by an attorney-in-fact pursuant to powers of attorney previously filed with the parent SF-1. The named signatory on the page is therefore not always the actual hand signer; the underlying authorization sits in an exhibit incorporated by reference and not present in this record.
Form caption versus form type. The printed banner on the facing page reads "FORM SF-1" because SF-1MEF reuses the SF-1 facing page; the MEF designation is communicated by the Rule 462(b) check-box and by the EDGAR <TYPE>SF-1MEF document tag. Distinguishing SF-1 from SF-1MEF cannot be done by scanning the banner alone — the EDGAR type code or the 462(b) check-box state is authoritative.
Image references in HTML. EX-5.1 and other exhibits commonly include <IMG SRC="...jpg"> references to firm letterhead logos. The referenced JPGs are not shipped; HTML rendering will surface a broken-image marker, but the text of the exhibit is unaffected.
Empty XBRL and series fields. linkToXbrl, dataFiles, and seriesAndClassesContractsInformation are present but empty for this form type and should not be treated as missing data.
Form SF-1MEF is filed exclusively by ABS registrants with a previously effective Form SF-1. The signatories on the facing and signature pages are typically:
The asset classes on these SF-1 / SF-1MEF pairs are those that, for structural or programmatic reasons, are not eligible for shelf registration on Form SF-3. In practice, this universe consists of utility recovery / securitization bonds (rate reduction, storm recovery, energy transition, securitized utility tariff bonds), equipment lease and loan ABS, certain auto loan / lease and dealer floorplan deals run off-shelf, occasional credit-card or revolving-pool transactions, and esoteric or first-time ABS structures that do not yet qualify for SF-3.
Foreign issuers, operating companies, and registered investment companies are outside this population; they use F-series, S-series, or N-series forms and have no occasion to file SF-1MEF.
An SF-1MEF is triggered when the registrant determines, late in the offering process, that the dollar amount registered on the earlier effective SF-1 will be insufficient to cover the actual deal size. Rule 462(b) allows registration of additional securities of up to 20% of the maximum aggregate offering price set forth in the related earlier-effective registration statement, provided that:
The form itself is intentionally minimal: a facing page identifying the registrant and the Securities Act file number of the parent SF-1, the title and amount of the additional ABS, a Rule 457 fee table for the incremental amount, the required signatures, and an express incorporation by reference of the prior SF-1. No new prospectus is created.
SF-1MEF is event-driven, not periodic. It is filed at the moment the registrant concludes that the deal will exceed the dollar amount remaining on the parent SF-1, which in practice means after final book-building when the deal has upsized, shortly before or on the same day as pricing, while the parent SF-1 remains effective, and before confirmations of sale go out. Effectiveness is immediate upon filing under Rule 462(b), so the additional 20% of capacity is registered in real time without disrupting the offering schedule.
The form is not amended in the ordinary course. If more than 20% of additional capacity is needed, the registrant must file a new SF-1; Rule 462(b) caps the top-up at 20% of the parent's maximum aggregate offering price, and a second SF-1MEF against the same parent is not available for that purpose.
The earliest filings in this dataset begin May 2022. The form did not exist before Regulation AB II; ABS top-ups previously used Form S-1MEF.
The Form SF-1MEF Files Dataset is narrow by structural design, not coverage gap:
In practice, SF-1MEF is used only when (i) a sponsor or depositor is running a non-shelf ABS deal on SF-1, (ii) the deal upsizes by no more than 20% past the registered amount, and (iii) the upsize is recognized late enough that a Rule 462(b) top-up — rather than a pre-effective amendment — is the appropriate vehicle.
Form SF-1MEF is a narrow Rule 462(b) abbreviated-registration form for asset-backed securities. It is most usefully distinguished from its parent SF-1, the shelf-side SF-3 and SF-3MEF, the corporate-issuer 462(b) analogs (S-1MEF, F-1MEF, S-3MEF), pre-effective SF-1/A amendments, Rule 424 prospectuses, and ongoing ABS disclosure (ABS-EE, ABS-15G).
SF-1 is the full ABS transactional registration statement: pool composition, transaction structure, servicing and trustee arrangements, credit enhancement, risk factors, and complete exhibits. SF-1MEF carries none of that substance; it incorporates SF-1 by reference and only adds up to twenty percent of additional registered offering price. Distinction: SF-1 holds the disclosure; SF-1MEF holds only incremental registered capacity.
SF-3 is the ABS shelf registration used by frequent, programmatic issuers (autos, credit cards, mortgages); SF-3MEF is its 462(b) twenty-percent top-up. SF-1MEF sits on the non-shelf, transactional side of the same regime. Distinction: SF-3/SF-3MEF cover shelf-eligible programmatic issuance; SF-1/SF-1MEF cover one-off ABS registrations that do not qualify for, or do not use, shelf treatment.
S-1MEF and F-1MEF are 462(b) twenty-percent top-ups to S-1 (domestic corporate) and F-1 (foreign private issuer) registrations. The 462(b) mechanic is identical, but the parent regime is corporate disclosure under Regulation S-K, not Regulation AB. Distinction: filer population and disclosure regime — SF-1MEF parents are ABS depositors and SPVs governed by Regulation AB; S-1MEF/F-1MEF parents are operating companies.
S-3MEF is the 462(b) top-up to a corporate S-3 shelf. It shares the abbreviated mechanic with SF-1MEF but differs on two axes at once. Distinction: corporate vs. ABS, and shelf vs. transactional — the most distant comparison in this cluster.
SF-1/A amends an in-progress SF-1 before effectiveness, typically to respond to staff comments or revise deal terms. SF-1MEF can only be filed after the SF-1 is already effective, does not amend the parent, and adds capacity rather than disclosure. Distinction: SF-1/A is pre-effective disclosure revision; SF-1MEF is post-effective capacity top-up.
The 424B prospectuses (most often 424B5 for ABS takedowns) are the marketing documents delivered to investors, containing final pricing, tranche structure, weighted average lives, and pool statistics. SF-1MEF is a registration filing, not a prospectus. Distinction: 424B describes the offered securities to investors; SF-1MEF only expands the registered dollar ceiling upstream of any offering.
ABS-EE supplies asset-level data on offered ABS (filed alongside prospectuses and in periodic reports); ABS-15G covers securitizer demand, repurchase, and replacement activity plus Rule 15Ga-2 third-party due diligence reports. Both are ongoing post-issuance disclosure. Distinction: ABS-EE/ABS-15G are ongoing performance and conduct disclosure; SF-1MEF is a one-time registration event.
The Form SF-1MEF Files Dataset captures one specific event: a Rule 462(b) twenty-percent capacity expansion of an already-effective, non-shelf ABS registration. It is not interchangeable with SF-1 (the substantive parent), SF-3/SF-3MEF (the shelf path), S-1MEF/F-1MEF/S-3MEF (corporate 462(b) top-ups), SF-1/A (pre-effective revisions), 424B (prospectus delivery), or ABS-EE/ABS-15G (ongoing disclosure). Use it to reconstruct final registered offering size on SF-1-based deals or to map the complete population of non-shelf ABS top-up registrations; pair it with adjacent datasets for any question about deal substance, pricing, pool performance, or securitizer conduct.
Because Form SF-1MEF is a Rule 462(b) top-up that adds up to 20% of additional ABS to an already-effective SF-1 and incorporates the prior registration by reference, a narrow set of professionals reads it field by field.
Structured finance partners and disclosure counsel at issuer- and underwriter-side firms confirm Rule 462(b) compliance on a live deal. They check the prior SF-1 file number, the incorporation-by-reference statement, the additional ABS title and amount against the 20% cap, and the dual signature blocks for the depositor (or issuing-entity SPV) and the sponsor. The dataset feeds precedent libraries for facing-page and signature conventions on abbreviated registrations.
Sponsor legal departments and underwriter compliance desks reconcile the fee table and additional amount registered against the prior SF-1 maximum aggregate offering price to confirm the 20% cap was not breached. They use the dataset to build pre-filing checklists and to document industry practice for internal audit and regulator inquiries.
Engineers building registration-accounting and EDGAR ingestion pipelines parse the EX-107 filing fee exhibit, the fee calculation table on the facing page, the prior file number used for carry-forward and offset logic, and the accession-level metadata to link each SF-1MEF to its parent SF-1. Output feeds downstream tools used by deal, compliance, and surveillance teams.
ABS origination and syndicate desks read the registrant identification, prior file number, and additional ABS title and amount to detect when peers top up a shelf rather than refile. The signal informs sizing of future SF-1 shelves, timing of follow-on transactions, and read-throughs on investor demand at the parent pricing.
Fixed-income analysts covering auto, equipment, credit card, mortgage, student loan, and utility cost-recovery ABS use the registrant and depositor identification, additional amount, and prior file number to attribute incremental supply to a specific shelf. Output feeds supply forecasts and exposure tracking on programs already in the portfolio.
Analysts at rating agencies reconcile registered amounts against rated and issued amounts using the additional ABS title and amount, registrant identification, prior file number, and fee table. The dataset keeps program-level issuance-capacity surveillance aligned with the full registered universe rather than just the original SF-1.
Diligence teams reviewing sponsor or servicer acquisitions reconstruct shelf activity from the registrant identification, dual-entity signatures revealing the SPV-and-sponsor pairing, and additional ABS titles. Output supports memos on issuance behavior, contingent liabilities tied to outstanding registrations, and program continuity post-close.
Researchers studying Reg AB II disclosure dynamics and abbreviated registrations assemble the full SF-1MEF population using filing date, registrant, additional amount, prior file number, and sponsor and depositor signatures. Output supports empirical work on top-up frequency, asset-class concentration, and shelf-utilization patterns.
The dataset therefore serves a tight circle: deal counsel and compliance officers policing the 20% cap, data engineers wiring fee and parent-file linkages, bankers and buy-side analysts reading top-ups as supply signals, rating analysts reconciling registered amounts, diligence teams mapping shelf activity, and researchers studying abbreviated registrations. The facing page, fee table, incorporation-by-reference statement, prior file number, dual-entity signatures, and additional ABS title and amount carry the load.
The Form SF-1MEF Files Dataset supports a narrow set of operational workflows tied to Rule 462(b) twenty-percent top-up registrations of asset-backed securities.
Compliance officers and ABS deal counsel pull the additional aggregate offering price from the EX-107 fee table and the prior SF-1 file number plus parent maximum aggregate offering price cited in the Explanatory Note, then compute the ratio to confirm the new amount sits at or below twenty percent. The check is run pre-filing against working drafts and post-filing across the dataset to document precedent. Output flows into pre-filing sign-off memos and internal audit trails.
Data engineers join each accession to its parent registration using the 333-NNNNNN file number on the Rule 462(b) check-box line and the -01 SPV counterpart in the entities array of metadata.json. The join produces a parent-and-top-up pair that lets downstream tools recompute total registered capacity per shelf and route fee-offset entries against the correct parent accession. This pairing key is what makes registration-accounting and EDGAR ingestion pipelines reconcile correctly.
Diligence teams and structured finance bankers extract the dual-registrant block from the facing page and the dual signature pages to capture the sponsor or depositor on the left, the bankruptcy-remote issuing entity on the right, and their respective CIKs, states of incorporation, and SIC codes. Cross-referencing the two filers in the entities array surfaces SPV naming conventions, Delaware-trust patterns, and which sponsors run which shelves. Output supports acquisition diligence memos and peer-shelf comparisons.
ABS disclosure counsel harvest the EX-5.1 opinion letters across the dataset to compare recital structure (Initial vs. Additional Registration Statement definitions), assumption paragraphs, bankruptcy and equitable-remedies carve-outs, and jurisdictional limits. Filtering by issuer counsel and by asset class produces a firm-by-firm and program-by-program precedent set that can be cited when drafting a fresh EX-5.1 for a new top-up. The "filed herewith" tag on EX-5.1 in the Part II exhibit index confirms the opinion is current to the SF-1MEF rather than carried over.
Buy-side ABS credit analysts and rating analysts use the filed-at timestamp, additional ABS title (tranche names from the Explanatory Note), and additional amount registered to attribute incremental supply to a specific program already in the portfolio or under surveillance. Aggregating across months produces top-up frequency by sponsor, asset class, and shelf — a leading indicator of follow-on issuance and an input to capacity-utilization models. Pairing this with the parent SF-1 file number lets analysts express each top-up as a percentage of original shelf size.
Filing-fee engineers parse the EX-107 HTML table — Security Type, Security Class Title, Fee Calculation Rule, Amount Registered, Maximum Aggregate Offering Price, Fee Rate, and Amount of Registration Fee — together with footnotes that reconcile the twenty-percent cap, carry-forward credits, and offsets against fees previously paid on the parent. The extracted rows feed into a registrant-level fee ledger that ties new SF-1MEF fees to the parent SF-1 accession and validates the SEC's fee-offset arithmetic.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-sf1mef-files.json
This endpoint returns dataset-level metadata and the list of all available container files. The response includes the dataset name, description, last updated timestamp, earliest sample date (2022-05-01), total record count and total size, the form types covered (SF-1MEF), the container format (ZIP), the file types contained in each container (HTML, JSON), the download URL for the full dataset archive, and an array of containers with per-container key, size, records, updatedAt, and downloadUrl fields. Use this endpoint to monitor which monthly containers have changed in the most recent refresh and to decide which containers to re-download on a day-by-day basis. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6a8a-b094-18c92f10e870",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-sf1mef-files.zip",
4
"name": "Form SF-1MEF Files Dataset",
5
"updatedAt": "2026-04-16T09:00:47.878Z",
6
"earliestSampleDate": "2022-05-01",
7
"totalRecords": 6,
8
"totalSize": 24538,
9
"formTypes": ["SF-1MEF"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-sf1mef-files/2022/2022-07.zip",
15
"key": "2022/2022-07.zip",
16
"size": 4213,
17
"records": 1,
18
"updatedAt": "2026-04-16T09:00:47.878Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-sf1mef-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing every monthly container. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-sf1mef-files/2022/2022-07.zip?token=YOUR_API_KEY
Downloads one monthly container instead of the full dataset. Container keys follow the YYYY/YYYY-MM.zip pattern and are listed in the containers array of the dataset index JSON. Each ZIP container holds one folder per accession number, and each accession folder contains a metadata.json file alongside the original EDGAR HTM documents (image files excluded). This endpoint requires an API key.
One record represents a single EDGAR submission of Form SF-1MEF — a Rule 462(b) abbreviated registration statement that adds up to twenty percent of additional asset-backed securities to a previously effective Form SF-1. Each record is a per-accession folder named with the eighteen-digit dash-stripped accession number, containing a metadata.json descriptor and the HTM documents (the primary SF-1MEF document, an EX-5.1 legality opinion, and an EX-107 fee exhibit) that EDGAR received in the original submission.
The earliest filings in the dataset begin May 2022, after the SEC's October 2021 fee-table amendments brought Exhibit 107 into force for new registration statements. Records are organized inside monthly ZIP containers keyed by year and year-month (for example, 2022/2022-07.zip), and the file types shipped inside each container are HTML and JSON.
Form SF-1MEF is filed exclusively by ABS registrants with a previously effective Form SF-1 — typically a depositor or bankruptcy-remote issuing-entity SPV, with the sponsor signing as a co-registrant where it holds Securities Act registrant status. Foreign issuers, operating companies, and registered investment companies are outside this population and use F-series, S-series, or N-series forms instead.
SF-1MEF is event-driven, not periodic. The registrant files it after final book-building when the deal has upsized — shortly before or on the same day as pricing — while the parent SF-1 remains effective and before confirmations of sale go out. Effectiveness is immediate upon filing under Rule 462(b) and Section 8(a) of the Securities Act, with no SEC review or acceleration request.
Both are Rule 462(b) abbreviated ABS registrations that add up to twenty percent of additional securities. SF-1MEF tops up an SF-1 (a transactional, non-shelf ABS registration), while SF-3MEF tops up an SF-3 ABS shelf used by frequent, programmatic issuers. SF-3MEF dominates because nearly all repeat ABS issuance runs on SF-3 shelves; SF-1MEF appears only on one-off deals such as utility recovery bond securitizations, off-shelf equipment ABS, and first-time esoteric ABS structures.
No. SF-1MEF incorporates the parent SF-1 by reference and ships only the abbreviated cover-and-signature wrapper plus the EX-5.1 legality opinion and EX-107 fee table that are filed contemporaneously. The parent SF-1's prospectus, transaction structure, risk factors, pool composition, Schedule AL data, and the bulk of the Item 601 exhibits live in the parent registration and are not duplicated in the SF-1MEF accession folder.
Form SF-1MEF carries no XBRL: there is no Financial_Report.xlsx, no R*.htm rendering files, and no *.xml instance documents. Regulation AB II's structured asset-data requirements (Schedule AL, Items 1111 and 1125 asset-level XML under Regulation AB) attach to the parent SF-1's prospectus and pool-data filings, not to the abbreviated MEF top-up. The linkToXbrl, dataFiles, and seriesAndClassesContractsInformation fields are present in metadata.json but empty for this form type.