The Form 10-D Files Dataset is the full corpus of asset-backed issuer distribution reports submitted to EDGAR since the form's inception. One record is a single Form 10-D or Form 10-D/A accession — a periodic distribution report filed by the issuing entity of a registered asset-backed securities (ABS) trust under Rule 13a-17 or Rule 15d-17 of the Securities Exchange Act of 1934 — bundled as the accession folder into a monthly ZIP archive. The filer is always a bankruptcy-remote issuing entity (typically a Delaware statutory trusts, common law trust, or LLC), and the filing reports, for a single distribution period, the cash distributions paid to certificateholders or noteholders and the performance of the underlying asset pool. Coverage runs from June 2005, when EDGAR first accepted 10-D submissions under the new Regulation AB regime, through the present, and includes both original 10-D filings and 10-D/A amendments. Each record is distributed as an accession-number folder containing a pipeline-generated metadata.json plus every document in the original EDGAR submission except image files.
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:
The dataset bundles every Form 10-D and Form 10-D/A submission made to EDGAR under one unique accession number, packaged as the accession folder inside a monthly ZIP archive keyed as YYYY/YYYY-MM.zip. The folder name is the 18-digit, zero-padded EDGAR accession number with dashes stripped, and each folder is self-contained — it carries its own metadata.json, the primary 10-D or 10-D/A HTML cover document, and every exhibit attached to the original submission. Folders sit flat beneath a single top-level YYYY-MM/ directory; there is no cross-record index, no CIK-level grouping, and no issuer-level grouping inside the container.
Form 10-D itself is the recurring disclosure vehicle that asset-backed issuers use to report on the performance of a securitized asset pool over a single distribution period. It was introduced by the December 2004 Regulation AB adopting release and took effect for distribution reports required on or after June 1, 2005, replacing the prior practice of disclosing distribution data on Form 8-K. Filings are made on a distribution-period cadence — monthly for most auto, credit-card, student-loan, and equipment-backed trusts, monthly or quarterly for mortgage-backed and CMBS trusts — and are due within fifteen days of the related distribution date. The form's function is to give holders of the certificates or notes recurring, structured information on the cash flows paid to each tranche, the composition and condition of the collateral pool, and any credit-enhancement balances or trigger events that affect the capital structure.
The body of the form itself is short. It is essentially an EDGAR cover page plus a set of Items that largely incorporate by reference the detailed servicer and trustee reports attached as exhibits. The substantive disclosure lives in those exhibits. The form's Items are: Item 1 — Distribution and Pool Performance Information, broken into Item 1(a) (distribution/performance narrative, in practice a pointer to EX-99.1) and Item 1(b) (Asset-Level Information, grounding EX-102 / EX-103 for covered asset classes); Item 2 — Legal Proceedings; Item 3 — Sales of Securities and Use of Proceeds; Item 4 — Defaults Upon Senior Securities; Item 5 — Submission of Matters to a Vote of Security Holders (essentially always "Not applicable" for pass-through trust issuers); Item 6 — Significant Obligors of Pool Assets; Item 7 — Significant Enhancement Provider Information; Item 8 — Other Information; and Item 9 — Exhibits. Item 9 is in practice the center of the filing, because it is where the monthly Statement to Noteholders and, for CMBS and similar collateral, the Regulation AB II asset-level data files are attached.
The dataset is distributed as ZIP containers, and the file types found inside a record are HTML, JSON, TXT, PDF, and XML.
A single record layers three kinds of material:
metadata.json that describes the submission and its header entities;Depending on asset class, the exhibit set may consist only of a single EX-99.1 Statement to Noteholders (typical for auto, credit-card, student-loan, and equipment trusts) or additionally include the Regulation AB II EX-102 and EX-103 asset-level data XML pair (typical for CMBS and certain other real-estate-backed and debt-backed deals). Some filers submit the EX-99.1 as a PDF in addition to, or in place of, an HTML rendition.
The primary 10-D HTML is usually still wrapped in the EDGAR SGML <DOCUMENT> / <TYPE> / <SEQUENCE> / <FILENAME> / <TEXT> envelope as it was transmitted to EDGAR. The exhibits, by contrast, have been split out of the combined .txt submission into unwrapped standalone HTML, XML, or PDF files. The concatenated SGML submission .txt is not written to the folder — only its URL is recorded in metadata.json under linkToTxt. Image files referenced inside the HTML exhibits (logos, chart renderings, scanned signatures) are likewise not downloaded.
metadata.jsonAlways present and always exactly one per accession folder. It is the dataset's structured view of the EDGAR submission header and document manifest. Primary fields include:
formType — "10-D" or "10-D/A".accessionNo — the dashed EDGAR accession (e.g. "0001628297-25-000931"); the folder name is the undashed version of the same number.description — the EDGAR form description, typically "Form 10-D - Asset-Backed Issuer Distribution Report [Section 13 or 15(d) of the Securities Exchange Act of 1934]"; amendments append ": [Amend]".filedAt — ISO-8601 filing timestamp with timezone offset.periodOfReport — the distribution/reporting period end date in YYYY-MM-DD form.linkToFilingDetails — URL to the primary 10-D document on EDGAR.linkToTxt — URL to the complete SGML submission file (not stored locally).linkToHtml — URL to the EDGAR -index.htm page for the accession.linkToXbrl — empty string for 10-D filings.dataFiles — empty array for 10-D filings.seriesAndClassesContractsInformation — empty array.id — opaque 32-character hex record identifier assigned by the pipeline.documentFormatFiles — ordered array describing every document present in the submission. Each entry carries sequence (numeric, or a single space for the synthetic "complete submission text file" row), size (byte count as a string), documentUrl (absolute EDGAR URL whose basename matches the local filename inside the folder), type (EDGAR document type tag such as "10-D", "EX-99.1", "EX-99.1 CHARTER", "EX-102", "EX-103"), and an optional free-form description.entities — array of EDGAR header entities, usually one filer per 10-D. Each entity carries cik, companyName (with a role annotation such as "(Filer)"), type (form type), act ("34" for Exchange Act filings), fileNo (the EDGAR file number, typically of the form 333-<shelf>-<NN> reflecting the issuer's ABS shelf registration), filmNo, sic (uniformly "6189 Asset-Backed Securities" across the dataset), stateOfIncorporation, fiscalYearEnd, and an optional irsNo.Listed as sequence: "1" with type: "10-D" (or "10-D/A") in documentFormatFiles. This is the EDGAR cover and skeleton of the report. It contains the report title, the Securities Exchange Act caption, the identification of the issuing entity (the trust), the depositor, the sponsor(s), the trustee or indenture trustee, their respective Central Index Keys, the commission file number of the underlying shelf, the principal executive office address, telephone number, registrant CIK, any check boxes for accelerated-filer or shell-company status (typically unchecked for trust issuers), and the distribution period and monthly distribution date fields. Below the cover, the document walks through each required Item in order, usually in highly compressed form — the filer will write "See Exhibit 99.1" under Item 1(a), "None" or "Not applicable" under Items 2 through 8, and list the attached exhibits under Item 9. The document closes with the signature block of the depositor or servicer signing on behalf of the issuing entity. In most submissions the primary HTML is still wrapped in the SGML <DOCUMENT>...<TEXT>...</TEXT></DOCUMENT> envelope as received by EDGAR.
Listed with type: "EX-99.1" (or "EX-99.1 CHARTER" when the filer uses the CHARTER exhibit-type tag, common among certain auto-trust filers). This is the substantive heart of the filing and is produced by the trustee or servicer rather than by counsel. Its content is dominated by dense HTML tables in a template that varies by asset class and by administrator but almost always covers:
For CMBS deals the EX-99.1 additionally carries top-ten-loan schedules, watchlist and specially serviced loan details, appraisal-reduction amounts, and loan-level modification narratives. It is the largest component of most records — typically several hundred kilobytes of HTML, and for large CMBS deals often more than a megabyte.
Present for CMBS and for other asset classes covered by Regulation AB II's asset-level data regime (residential mortgage-backed, debt-securities-backed resecuritizations, certain auto-loan and auto-lease deals, and debt securities collateralized by securities). Listed with type: "EX-102" and named ex102.xml, exh_102.xml, or a filer-specific variant. It is a Schedule AL XML instance that conforms to EDGAR's asset-data namespace for the relevant asset class (for CMBS, the namespace is rooted at http://www.sec.gov/edgar/document/absee/cmbs/assetdata).
The document is structured as a root <assetData> element containing one <assets> element per loan, each with nested <property> elements for the collateral properties backing that loan. The field set is large and highly coded. Representative loan-level fields include assetNumber, originatorName, originationDate, originalLoanAmount, scheduledPrincipalBalanceSecuritizationAmount, interestRateSecuritizationPercentage, maturityDate, paymentTypeCode, loanStructureCode, amortizationTypeCode, and defeasedStatusCode. Representative property-level fields include propertyName, propertyAddress, propertyCity, propertyState, propertyZip, propertyTypeCode, netRentableSquareFeetNumber, unitsBedsRoomsNumber, yearBuiltNumber, valuationSecuritizationAmount, valuationSecuritizationDate, and physicalOccupancySecuritizationPercentage, together with numerous appraisal and NOI/DSCR time-series fields. A typical CMBS EX-102 contains tens to low hundreds of <assets> blocks. The schema corresponds to the loan-level data required under Item 1(b) of Form 10-D as amended by the 2014 Reg AB II rules.
Always paired with EX-102 when EX-102 is present. Listed with type: "EX-103" and typically named ex103.xml or exh_103.xml. It carries field-level footnotes that explain or qualify specific values in EX-102. The root element contains repeated <commentData> blocks, each keyed by itemNumber (a reference into the Reg AB II Schedule AL item taxonomy such as "Item 2(c)(15)") and fieldName, with a human-readable comment string. Typical comments describe manual adjustments to occupancy figures, explain why a DSCR is unavailable, clarify tenant lease-expiry assumptions, or document why a valuation date predates the cutoff date.
Occasional, concentrated among certain auto-trust filers (notably several Mercedes-Benz auto-lease trusts routinely file the EX-99.1 in both HTML and PDF form). When present, the PDF is listed in documentFormatFiles with type: "EX-99.1" or "EX-99.1 CHARTER" and is typically a byte-for-byte equivalent of the HTML investor report, but with the servicer's native formatting preserved.
Less common exhibits that may appear with their own sequence and type tags include EX-99.2 or EX-99.3 (additional servicer or sub-servicer reports), and in rare special circumstances the Reg AB servicing-compliance triad EX-33 (assessment of compliance with servicing criteria), EX-34 (attestation of servicer assertion), and EX-35 (servicer compliance statement). The annual Reg AB servicing-compliance package ordinarily lives on the companion Form 10-K rather than on the Form 10-D, so these exhibits are uncommon on 10-D records.
Each record includes the pipeline-generated metadata.json with the parsed EDGAR header, entity list, and document manifest; the primary 10-D or 10-D/A HTML document as submitted (typically with its EDGAR SGML envelope preserved); every exhibit document attached to the original submission as its own standalone file; and the Reg AB II EX-102 asset-level XML and EX-103 asset-data-comment XML pair where applicable.
In practice, a modern record is overwhelmingly HTML documents plus the JSON manifest, with XML for the Schedule AL XML pair and occasional PDF renditions. File naming inside the folder follows the filer's agent conventions rather than any dataset normalization: Davis Polk / Paul Weiss-style filings use readable camel-case names (Form10DBMOC25C13.htm, ex99_1.htm, ex102.xml); Broadridge filings use deal tickers with YYYYMM suffixes (jpc14c25_10d-202511.htm, jpc14c25_ex991-202511.htm); Donnelley filings use opaque d<id> tokens (d77407d10da.htm); auto-trust filers use readable deal slugs (bmwlt2025-1_form10d.htm, mbalt2023a_10d_112025.htm).
Three kinds of content are not written to the accession folder:
.txt SGML submission file — its URL is recorded in metadata.json as linkToTxt but the file itself is not downloaded; andThe exhibit set scales with the disclosure regime that governs the asset class rather than with the issuer's identity.
<assets> block per loan and nested property detail; and EX-103 asset-data-comment XML keyed by item number and field name. EX-99.1 on CMBS routinely exceeds a megabyte.documentFormatFiles as a second "EX-99.1 CHARTER" entry.type: "10-D/A" and usually one EX-99.1 attachment carrying the corrected Statement to Noteholders. The amendment's metadata.json description is suffixed with ": [Amend]"; the periodOfReport matches the original filing; and the issuing-entity CIK is typically unchanged. The accessionNo is new, so the amendment lives in its own folder.Form 10-D has passed through two substantive content regimes since its inception.
Item numbering has been stable across the form's history. Item 1(b) (the Asset-Level Information item that grounds EX-102 / EX-103) was added as part of the 2014 amendments rather than by renumbering prior Items. Item 5 (Submission of Matters to a Vote of Security Holders) has existed since inception but is essentially always marked "Not applicable" for pass-through trust issuers and rarely contains substantive content.
Form 10-D has been filed through EDGAR from day one and — unlike older form types — never had a meaningful ASCII/plain-text era. By June 2005 EDGAR had long since adopted HTML as the standard presentation for narrative filings, and the format evolution of 10-D records is therefore narrower than for older forms.
<DOCUMENT> envelope; EX-99.1 is filed as HTML, sometimes with a PDF rendition alongside. Exhibit types outside the EX-99 family are rare. No structured data accompanies the filing.http://www.sec.gov/edgar/document/absee/cmbs/assetdata) rather than iXBRL-tagged HTML, and they sit as peers to the EX-99.1 rather than being embedded inside it..txt submission into its component documents. PDF renditions of the EX-99.1 appear intermittently across the whole history and are most common among auto-lease filers.accessionNo in metadata.json is dashed; the folder name is the same number with dashes removed, zero-padded to 18 digits.documentFormatFiles[i].documentUrl, take only the URL's path basename. The URLs point to EDGAR but the bytes live in the local accession folder.sic is uniformly "6189 Asset-Backed Securities" for every record, so issuer differentiation must come from companyName, cik, and the shelf-level fileNo (typically of the form 333-<shelf>-<NN>).itemNumber and fieldName; the pair should be read together when interpreting asset-level values.periodOfReport and ordering by filedAt.Form 10-D is filed exclusively by asset-backed issuers as defined in Item 1101 of Regulation AB. Operating companies, bank holding companies, REITs, BDCs, and registered funds do not use this form.
The EDGAR filer is the issuing entity — the bankruptcy-remote SPV that holds the pool assets and has issued the ABS. Issuing entities are almost always Delaware statutory trusts, common law trusts, or LLCs (occasionally limited partnerships), have no employees, and exist only to hold the pool and service the securities. Each securitization transaction has its own issuing entity and its own CIK, which is why a single sponsor program generates dozens or hundreds of distinct 10-D filers.
Three other parties appear inside every 10-D but are not the Exchange Act filer:
The filing population spans RMBS, CMBS (conduit, single-borrower, agency CMBS), auto loan and auto lease trusts (including titling trusts), auto floorplan master trusts, credit card master trusts and related note issuance trusts, equipment loan and lease trusts, FFELP and private student loan trusts, marketplace and consumer installment loan trusts, and esoteric ABS (timeshare, franchise, whole-business, solar loan, container lease) — provided the offering is SEC-registered.
Legal trigger. The filing obligation arises under the Exchange Act of 1934:
Upstream registration. The Section 15(d) obligation flows from a Securities Act registration statement — today a shelf registration on Form SF-3 under Regulation AB II (effective for takedowns from November 2016 forward), previously Form S-3 or S-1/S-11 with ABS-specific schedules — followed by a series-specific prospectus supplement. Unregistered 144A / Rule 506 ABS are outside this regime and are not represented in the dataset.
Cadence. Form 10-D is a distribution-period periodic report, not annual, quarterly, or event-driven. The cadence is set by the transaction documents (indenture or pooling and servicing agreement) — typically monthly for consumer ABS and RMBS, monthly or quarterly for CMBS and some esoteric deals.
Due date. Under Rule 13a-17(b) and Rule 15d-17(b), Form 10-D is due within 15 days after each distribution date specified in the governing transaction documents. The 15-day deadline is uniform across all asset-backed issuers; there is no accelerated-filer or large-accelerated-filer acceleration like the 10-K / 10-Q regime. A 10-D is still generally filed for a period in which no distribution is made, provided the transaction remains outstanding, to report pool performance.
Core content. The 10-D reports, for the covered distribution period, the cash distributions paid to certificateholders or noteholders, pool performance (delinquency, default, prepayment, loss, collateral statistics), identification of the issuing entity and depositor, the distribution date and record date, and required exhibits — principally the monthly servicer report or distribution date statement, and, where applicable, a contemporaneous Form ABS-EE asset-level data filing referenced as an exhibit. The substantive disclosure is governed by Item 1121 of Regulation AB (distribution and pool performance).
Suspension. Reporting continues until Exchange Act obligations are suspended under Rule 15d-22 — generally when the ABS are paid in full, the pool is wound down, or the conditions for automatic suspension under the rule are met. After that, no further 10-Ds are filed for the series.
Amendments (10-D/A). A Form 10-D/A is filed to correct or supplement a previously filed 10-D — for example, to restate distribution figures, reissue a corrected servicer report, refile a missing exhibit, or respond to SEC staff comments. It is filed under the same issuing entity CIK and references the original period; it does not reset the 15-day clock for subsequent distribution periods.
Form 10-D sits inside the asset-backed securities reporting regime of Regulation AB and Regulation AB II. The most useful comparisons are other ABS-specific forms, the general periodic forms that 10-D displaces or complements, and the registration and termination forms that bracket an ABS trust's reporting life.
Filed under Rule 13a-1 / 15d-1, the ABS Form 10-K is the annual companion to Form 10-D. Its payload is servicing-compliance, not pool cash flow: the Item 1122 assessment of compliance with servicing criteria, the Item 1123 servicer's annual statement of compliance, the registered public accounting firm's attestation, and, where applicable, Item 1119 transaction-party updates. Form 10-D is distribution-cycle (typically monthly or quarterly) under Rule 13a-17 / 15d-17 and centered on pool performance and distributions. The operating-company 10-K (MD&A, audited financials, risk factors) shares only the form number.
Required alongside Form 10-D for the asset classes covered by Item 1111(a) of Regulation AB (residential and commercial mortgages, auto loans and leases, debt securities, and resecuritizations), Form ABS-EE carries asset-level data in EX-102 (XML asset-data file) and EX-103 (asset-related document). Form 10-D reports pool-level distributions, aggregate delinquency and loss statistics, and narrative servicer information; ABS-EE delivers structured, loan-by-loan data across hundreds of fields per asset. The two are complementary and filed together, not substitutes: pool totals and waterfalls come from 10-D, line-level loan performance from ABS-EE.
10-D/A (included in this dataset) corrects a specific distribution period, for example revising delinquency totals, a distribution breakdown, or pool factors. Form 10-K/A corrects an annual servicing-compliance cycle, typically a reissued Item 1122 assessment, attestation, or Item 1123 statement. The distinction mirrors the base forms: period-tied in both cases, but one period is a distribution cycle and the other is a fiscal year.
Form 8-K is event-driven and governed for ABS by a dedicated item set: 6.01 (ABS informational and computational material), 6.02 (change of servicer or trustee), 6.03 (change in credit enhancement or other external support), 6.04 (failure to make a required distribution), and 6.05 (Securities Act updating disclosure). Form 10-D is calendar-driven by the distribution date. A missed distribution, replaced servicer, or enhancement breach surfaces first in 8-K within the item's deadline; its impact on pool arithmetic then appears in the next 10-D.
Form SF-1 (initial registration) and SF-3 (shelf registration) are the Securities Act registration statements that replaced S-1 and S-3 for ABS offerings under Regulation AB II. They register the securities, describe the transaction structure, identify cutoff-date pool assets, and attach the prospectus and pooling-and-servicing or indenture agreement. Form 10-D is the Exchange Act periodic report filed after the securities are outstanding. SF-1/SF-3 are pre-offering and one-time or shelf-wide; 10-D is recurring and post-offering. Continued SF-3 shelf eligibility depends on timely and accurate 10-D filings.
Form ABS-15G carries two disclosures that never appear in 10-D: the Rule 15Ga-1 quarterly representations-and-warranties repurchase history, aggregated across a securitizer's outstanding trusts, and the Rule 15Ga-2 third-party due-diligence report, filed at least five business days before the first sale of ABS in an offering. ABS-15G is silent on distributions, record dates, pool factors, and delinquency pools. For rep-and-warranty enforcement across a securitizer, use ABS-15G; for a single trust's cash performance in a period, use 10-D.
Filed under Rule 12g-4, 12h-3, or 15d-6, Form 15 suspends or terminates reporting obligations. For an ABS trust it ends the 10-D stream, usually when the securities are paid in full, the trust terminates, or the holder-of-record threshold is crossed. It carries no performance content; it is a boundary marker explaining the absence of further 10-Ds for a given CIK.
Rule 13a-13 / 15d-13 requires quarterly reporting from operating-company registrants but explicitly excepts asset-backed issuers, whose periodic regime is Form 10-D plus the ABS Form 10-K. No 10-Q exists for an ABS trust. The quarterly cadence of many ABS distributions can resemble 10-Q cadence, but the legal basis and content regime are unrelated.
Form 10-D is the only SEC filing that delivers recurring, distribution-period pool performance and cash-distribution reporting for registered ABS trusts, grounded in Rule 13a-17 / 15d-17 and Items 1121 and the 1100 series of Regulation AB. It is narrower in filer population than the operating-company periodic forms, narrower in content than the ABS 10-K or 8-K, and more frequent than SF-1/SF-3 or the annual 10-K. It is complementary to ABS-EE (same period, asset level) and bracketed by SF-1/SF-3 at registration and Form 15 at termination. For event narrative use 8-K; for annual servicing compliance use the ABS 10-K; for rep-and-warranty or diligence disclosures use ABS-15G; for the recurring trustee-style distribution report filed with the SEC, Form 10-D is the only source.
Form 10-D is the recurring distribution report for asset-backed trusts, and its readers are structured-finance specialists rather than generalist equity users. Each filing pairs a waterfall snapshot with pool performance, servicer narrative, and, post-Regulation AB II, loan-level EX-102 data. The roles below read different slices of that record.
Sell-side and buy-side analysts covering auto, card, student, equipment, consumer, esoteric ABS, and private-label RMBS use 10-D as the monthly pulse on every deal in coverage. They pull distribution date, record date, collection period, beginning/ending pool balance, pool factor, prepayment speeds (CPR, SMM, ABS, PSA), gross and net loss rates, 30/60/90+ delinquency buckets, cumulative net losses, OC target vs. actual, reserve balance, and CE levels, then map class-level interest and principal against the indenture waterfall to confirm trigger, step-down, turbo, or rapid-amortization events. Outputs include tear sheets, relative-value notes, new-issue comparables, and surveillance rankings by shelf and vintage.
MBS, ABS, and CMBS PMs and traders use 10-D to price held, bid, offered, or new-issue bonds. They read pool factor and principal paydown to validate settlement factors, class-level interest and principal to reconcile custodian reports, and delinquency and loss trends to re-underwrite cashflow-engine assumptions. CMBS desks additionally track watchlist status, specially serviced loan counts, appraisal reduction amounts (ARA/ASER), and modification summaries to reprice bonds where losses may migrate up the stack. Supports pre-trade checks, post-trade surveillance, and hold-vs-sell calls on seasoned paper.
Surveillance teams feed each 10-D into monthly or quarterly transition, roll-rate, and loss-projection models: pool balance, delinquency strats, cumulative losses, recoveries, prepayments, servicer advances, and trigger-status flags. They also read servicer narrative, material-change notices, R&W breach references, and any servicer or trustee turnover for operational-risk scoring. Inputs surveillance committee memos and published rating actions.
ALCO and ALM groups holding ABS, MBS, and CMBS in AFS, HTM, or trading books refresh CECL and impairment models, stress tests, LCR inputs, and regulatory capital treatment from 10-D. They focus on delinquency migration, loss severity, pool factor changes, and trigger or early-amortization events that alter expected life or loss curves. Supports quarterly credit reviews and evidence files for accounting judgments.
Life and P&C carriers use 10-D to refresh NAIC designations, statutory reserves, RBC charges, and asset-adequacy testing. Analysts track pool performance, CE burndown, and loss allocations to subordinate classes; appointed actuaries lift servicer commentary on delinquency trends, modifications, and loss mitigation into cashflow-testing assumptions.
CMBS modelers consume the supplemental schedules attached to 10-D, including watchlist, delinquency, REO, specially serviced, prepayment, modification, and appraisal-reduction reports, alongside the distribution and collateral summary. Key fields: loan number, property type, property name and location, current balance, DSCR, occupancy, maturity, special-servicer transfer date, workout code, ARA, and ASER. Feeds loan-level cashflow models, CMBX and SASB analytics, single-loan credit opinions, and long/short scenario work. History back to 2005 provides pre-crisis vintages with full workout tails.
Primary servicers, master servicers, and subservicers use peer 10-Ds to benchmark remittance formats, field definitions, and reporting lag against CREFC IRP, ABS EE, or industry templates. Reporting teams reconcile data reported upstream to the trustee and track discrepancies surfaced in 10-D/A amendments. Internal audit and SSAE 18 / ISAE 3402 control teams cite the filings as reporting evidence.
Trustee, paying-agent, and certificate-administrator teams reconcile cover-page figures, distribution schedules, factor updates, class balances, and waterfall allocations against internal books. Exhibit lists are checked to confirm servicer reports, officers' certificates, ABS-EE attachments, and compliance statements are present for SOX and Regulation AB attestations.
Securities, banking, housing, and state insurance staff monitor ABS market health and regulated-entity holdings. Securities regulators review disclosure completeness, late filings, amendments, EX-102 compliance, and servicer-compliance exhibits. Bank supervisors read pool performance to gauge risk in supervised holdings and systemic exposure. Housing agencies use pool-level loss, delinquency, modification, and prepayment trends to inform policy. Long history supports retrospective work on pre-crisis pools and post-crisis disclosure reform.
Finance, accounting, law, and economics researchers treat the corpus as a long panel of securitization performance for work on deal design, originate-to-distribute moral hazard, servicer behavior, vintage loss dynamics, and disclosure quality under Regulation AB and AB II. Standardized fields (pool factor, cumulative net losses, delinquency buckets, trigger breaches, CE) are extracted across thousands of deals and merged with origination, loan-level, and rating-action data.
Litigation consultants, forensic accountants, and expert witnesses on RMBS/CMBS disputes, including R&W putback, trustee-duty, and servicer-conduct matters, cite 10-D as contemporaneous evidence of performance and disclosure. They focus on cumulative loss trajectories, realized-loss allocations by class, R&W breach and repurchase references, servicer advancing and recovery history, ARA/ASER entries, modifications, and disclosed servicer or trustee changes. 10-D/A amendments correcting prior figures often matter in damages and causation analysis.
Structured-finance data vendors, fintech analytics platforms, and quant teams ingest the full corpus to build normalized pool-performance databases, surveillance dashboards, and factor libraries. Engineers parse HTML distribution schedules, XML EX-102 asset-level files, and PDF servicer reports into deal/class/loan/period schemas that power surveillance products, API-delivered pool metrics, ML prepayment and loss models, and quant signals on ABS and CMBS. LLM and RAG teams building structured-finance copilots ground retrieval against actual servicer language, trigger definitions, and waterfall disclosures.
The use cases below describe concrete workflows that professionals run against this corpus. Each one ties to specific fields in metadata.json, specific exhibits (EX-99.1 Statement to Noteholders, EX-102 Schedule AL XML, EX-103 asset-data comments), and a tangible output artifact.
ABS and structured-credit analysts parse every new EX-99.1 in an issuer's shelf to pull beginning and ending pool balance, pool factor, 30/60/90+ delinquency aging, cumulative net losses, reserve-fund and overcollateralization balances, and pass/fail status for delinquency, cumulative-loss, and OC triggers. Joined on issuing-entity CIK and periodOfReport across consecutive YYYY-MM.zip archives, the extracted series feed a per-deal time-series table that drives monthly surveillance tear sheets, relative-value write-ups, and early-warning alerts when a trigger flips from pass to fail.
CMBS modelers consume the paired EX-102 and EX-103 XML files for every CMBS accession folder. They iterate <assets> blocks to pull assetNumber, current scheduled principal balance, DSCR and occupancy time series, maturityDate, and defeasedStatusCode, and walk nested <property> elements for property type, address, and valuation history. EX-103 <commentData> blocks keyed by itemNumber and fieldName are joined to flag manually adjusted occupancy, missing DSCR, or pre-cutoff valuations. Combined with the EX-99.1 watchlist, specially serviced, REO, and appraisal-reduction schedules, the output is a loan-level panel that feeds CMBX scenario runs, SASB credit opinions, and long/short trade memos.
Forensic accountants and rating surveillance teams identify 10-D/A records by formType and the ": [Amend]" suffix in description, then match each amendment to its original 10-D on issuing-entity CIK plus periodOfReport, ordering by filedAt. Field-by-field diffing of the two EX-99.1 documents (distribution-date waterfall amounts, delinquency bucket counts, realized-loss figures, class factors) produces a restatement log used in damages analyses, trustee-duty litigation exhibits, and rating-committee memos on reporting reliability.
Fixed-income PMs and data vendors build normalized cross-issuer benchmarks by extracting, from each EX-99.1 in auto, auto-lease, credit-card, equipment, and student-loan trusts, the monthly pool stratifications: weighted-average coupon, weighted-average remaining term, delinquency aging, charge-off rate, prepayment speed (CPR/ABS), and excess spread. Issuer and shelf are resolved through entities[].companyName, cik, and fileNo (the 333-<shelf>-<NN> shelf identifier). The artifact is a deal-by-month matrix used for peer-vintage charts, new-issue comparables, and CECL/impairment model refreshes.
Servicer operations, trustee teams, and vendors building structured-finance parsers mine the EX-99.1 corpus to catalogue template variants across administrators (Computershare/Wells Fargo, U.S. Bank, Citibank, Wilmington Trust, BNY Mellon). Grouping filings by trustee entity and inspecting filedAt minus periodOfReport measures reporting lag distributions by administrator and asset class. Outputs include a parser-configuration library keyed by template fingerprint and an internal benchmarking report used to negotiate servicing-level expectations and SSAE 18 evidence files.
Quant and ML teams ingest the full corpus to build retrieval indexes and fine-tuning sets for securitization copilots. Waterfall narratives, trigger definitions, servicer commentary, and workout descriptions come from EX-99.1 HTML; structured loan and property attributes come from EX-102; field-level caveats come from EX-103; issuer and shelf metadata come from metadata.json. The outputs are RAG-ready chunked corpora, extraction fine-tunes that map servicer statement tables to a canonical deal/class/loan/period schema, and evaluation sets that test a model's ability to compute pool factors or identify trigger breaches from raw filing text.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-10d-files.json
This endpoint returns dataset metadata (name, description, last updated timestamp, earliest sample date, total records and total size, form types covered, container format, and file types), the download URL for the full dataset archive, and the list of individual container files with per-container size, record count, updated timestamp, and download URL. It can be polled daily to monitor which containers were refreshed in the most recent run and decide which ones to re-download incrementally.
This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-68e7-841f-3e06b398e789",
3
"datasetDownloadUrl": "https:/api.sec-api.io/datasets/form-10d-files.zip",
4
"name": "Form 10-D Files Dataset",
5
"updatedAt": "2026-04-23T02:55:21.993Z",
6
"earliestSampleDate": "2005-06-01",
7
"totalRecords": 307107,
8
"totalSize": 34674841324,
9
"formTypes": ["10-D", "10-D/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "JSON", "TXT", "PDF", "XML"],
12
"containers": [
13
{
14
"downloadUrl": "https:/api.sec-api.io/datasets/form-10d-files/2026/2026-04.zip",
15
"key": "2026/2026-04.zip",
16
"size": 13818783,
17
"records": 154,
18
"updatedAt": "2026-04-23T02:55:21.993Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-10d-files.zip?token=YOUR_API_KEY
Downloads the complete Form 10-D files dataset as a single ZIP archive covering all filings from June 2005 to present. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-10d-files/2026/2026-04.zip?token=YOUR_API_KEY
Downloads one individual monthly container ZIP instead of the full dataset, useful for incremental syncing of recently updated months. This endpoint requires an API key.
The dataset covers Form 10-D (the asset-backed issuer distribution report required under Rule 13a-17 or Rule 15d-17 of the Securities Exchange Act of 1934) and Form 10-D/A (amendments to previously filed distribution reports). Both form types are bundled together in the same monthly container archives and are distinguishable by the formType field in metadata.json.
One record is a single Form 10-D or 10-D/A submitted to EDGAR under one unique accession number, physically bundled as an accession-number folder inside a monthly ZIP archive keyed as YYYY/YYYY-MM.zip. The folder contains a pipeline-generated metadata.json plus every document in the original EDGAR submission except image files, with the primary 10-D HTML and its exhibits (EX-99.1 Statement to Noteholders and, for covered asset classes, the EX-102 / EX-103 Reg AB II asset-level XML pair) as separate standalone files.
Form 10-D is filed exclusively by asset-backed issuers as defined in Item 1101 of Regulation AB — that is, the bankruptcy-remote issuing entity (typically a Delaware statutory trust, common law trust, or LLC) of an SEC-registered ABS. Operating companies, bank holding companies, REITs, BDCs, and registered funds do not use this form, and 144A / Rule 506 private ABS and most agency securities issued by Fannie Mae, Freddie Mac, or Ginnie Mae fall outside the Form 10-D regime.
Form 10-D is a distribution-period periodic report with cadence set by the transaction's indenture or pooling and servicing agreement — typically monthly for consumer ABS and RMBS, monthly or quarterly for CMBS and some esoteric deals. Each 10-D is due within 15 days after the related distribution date under Rule 13a-17(b) / Rule 15d-17(b); the monthly containers refresh as new filings arrive, and the dataset index JSON can be polled to detect which YYYY-MM.zip archives have been updated.
Coverage begins with the earliest 10-D filings on EDGAR in June 2005 — reflecting the introduction of Form 10-D by the December 2004 Regulation AB adopting release — and runs through the present. There is no pre-EDGAR paper analogue; pre-2005 ABS distribution disclosure was made on Form 8-K, 10-K, or 10-Q exhibits and is not part of the 10-D population.
Form 10-D reports pool-level distributions, aggregate delinquency and loss statistics, and narrative servicer information; Form ABS-EE (a separate form type, filed as a sibling on EDGAR) delivers structured loan-by-loan data across hundreds of fields per asset under Regulation AB II. The two are complementary, not substitutes. Within this dataset, the EX-102 and EX-103 XML files that appear inside 10-D accession folders for CMBS and other covered asset classes are the Schedule AL asset-level data referenced by the contemporaneous ABS-EE.
The dataset is distributed as ZIP container archives, one per calendar month, organized as YYYY/YYYY-MM.zip. Inside each container, records sit as accession-number folders containing files in HTML, JSON, TXT, PDF, and XML formats — principally the metadata.json manifest, the primary 10-D HTML (often still wrapped in its EDGAR SGML envelope), the EX-99.1 HTML (or PDF) Statement to Noteholders, and, where applicable, the EX-102 and EX-103 XML asset-level data files.