The Form N-MFP1 Files Dataset is the complete archive of monthly money market fund portfolio reports filed on EDGAR using the interim N-MFP1 schema accepted between April 14, 2016 and October 13, 2016, together with the corresponding N-MFP1/A amendments that restate those reports. Each record is a single EDGAR submission packaged as an accession number-folder containing the curated metadata.json, the structured primary_doc.xml payload, and the EDGAR XSL-rendered XHTML view, and corresponds to one money market fund series reporting one calendar month of operational, liquidity, share-flow, and security-by-security holdings data. The underlying form is filed by registered open-end management investment companies operating in reliance on Rule 2a-7 under the Investment Company Act of 1940, pursuant to the monthly reporting obligation in Rule 30b1-7. The native filing window is narrow — original N-MFP1 reports cover reporting periods from roughly April 2016 through September 2016 — but N-MFP1/A amendments restating those months continue to arrive years later. Dataset records begin with the earliest sample date of May 1, 2016 and are distributed as ZIP containers of XML and JSON 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 captures the full population of N-MFP1 and N-MFP1/A submissions accepted by EDGAR. Form N-MFP1 is the structured monthly report required of registered money market funds under Rule 30b1-7 of the Investment Company Act of 1940. It captures the fund series' operational profile and a complete schedule of portfolio holdings as of the last business day of the calendar month being reported.
N-MFP1 is the interim version of Form N-MFP that incorporated the Commission's July 23, 2014 amendments to money-market-fund reporting and was accepted by EDGAR beginning April 14, 2016. It bridged the original N-MFP (in effect since 2010) and Form N-MFP2, which replaced N-MFP1 effective October 14, 2016. The dataset therefore covers a narrow native-filing window — roughly May 2016 through October 2016 — plus subsequent N-MFP1/A amendments that restate those months and may be filed years later. Every record describes a money market fund's portfolio under the post-2014-amendment, pre-N-MFP2 disclosure regime.
The form is organized in paper-form style: the EDGAR-rendered XHTML view groups disclosures under numbered Items (1–8 for filer/general information, Part A items A.1 through A.30 for series-level information, Part B for class-level information, and Part C for the schedule of portfolio securities), but every data point is filed natively as XML. The item numbering is purely a presentational convention applied by the XSL transform; the structured XML elements are semantically named rather than numbered. Each accession folder holds three artifacts only — metadata.json, primary_doc.xml, and the XSL-rendered xslN-MFP1_X01/primary_doc.xml — so the per-record footprint is small and uniform across the dataset, and the file types found in the dataset are limited to XML, XHTML, and JSON.
One record in the Form N-MFP1 Files Dataset is a single EDGAR submission of Form N-MFP1 or its amendment variant Form N-MFP1/A, identified by accession number and packaged as the complete folder of documents that EDGAR received for that submission. Each record corresponds to one money market fund series reporting one calendar month of operational, liquidity, share-flow, and portfolio-holdings data, together with the submission metadata, filer identification, and signature block that EDGAR required.
Inside the dataset, a record materializes as an accession-number folder (the EDGAR accession number with dashes stripped, e.g. 000114554917000915 for accession 0001145549-17-000915) that holds three artifacts: a curated metadata.json describing the EDGAR submission envelope, the canonical structured primary_doc.xml carrying the full N-MFP1 payload, and an XHTML rendering of the same filing under the subdirectory xslN-MFP1_X01/primary_doc.xml produced by EDGAR's official XSL transform.
A Form N-MFP1/A record has the same physical shape, but its submissionType and formType carry the /A suffix and the underlying form restates a previously filed monthly report. The periodOfReport of an amendment commonly precedes its filedAt date by several months because the filer is correcting an older month-end report rather than reporting fresh data.
Each accession folder contains exactly three files arranged in two levels:
metadata.json — sec-api-curated submission metadata describing the EDGAR filing envelope.primary_doc.xml — the canonical N-MFP1 XML payload, the structured machine-readable form data.xslN-MFP1_X01/primary_doc.xml — an XHTML rendering of the same filing produced by EDGAR's XSL transform, mirroring the paper-form item numbering for human reading.The XSL-rendered document is presentational and redundant with primary_doc.xml for data extraction — every disclosed value is available in the structured XML.
metadata.json — submission-level metadataThe metadata file describes the EDGAR submission envelope rather than the fund's reported figures. Its principal fields are:
formType — N-MFP1 or N-MFP1/A.accessionNo — the dashed EDGAR accession number.description — short EDGAR description, e.g. Form N-MFP1/A - [Amend].filedAt — ISO 8601 timestamp when EDGAR accepted the submission.periodOfReport — the month-end the report covers (e.g. 2016-06-30).linkToFilingDetails, linkToHtml, linkToTxt — URLs to EDGAR's XSL-rendered primary document, the filing-index page, and the complete submission text wrapper. linkToXbrl is empty because N-MFP1 is not an XBRL form.documentFormatFiles[] — submission-document inventory; each entry carries sequence, size, documentUrl, type, and (sometimes) description. For N-MFP1 this typically lists the XSL-rendered document, the raw primary_doc.xml, and the complete submission .txt wrapper.dataFiles — empty (no separate data attachments accompany N-MFP1).entities[] — filer-entity records pulled from the EDGAR header. Each entry carries cik, companyName (with role suffix such as (Filer)), fileNo, irsNo, fiscalYearEnd (MMDD), stateOfIncorporation, act (40 for the Investment Company Act of 1940), type, and filmNo.seriesAndClassesContractsInformation[] — fund-series identifiers tying the filing to the EDGAR series/class contract registry. Each item holds the EDGAR series ID (S… prefix), the series name, and a list of classesContracts each with name and classContract ID (C… prefix). For master-feeder reporting these IDs link the filing to a specific series and its share classes.id — internal record identifier.primary_doc.xml — the structured N-MFP1 payloadThe structured filing is namespaced under http://www.sec.gov/edgar/nmfp1 (with helper namespaces nmfp1common, common, and statecodes). The root element is <edgarSubmission> and contains two top-level branches: <headerData> (submission envelope) and <formData> (the actual report).
<headerData> — submission envelopeA compact metadata block used by EDGAR for routing and authentication:
submissionType — N-MFP1 or N-MFP1/A.filerInfo/filer/filerCredentials/cik — the filer CIK; the accompanying ccc (CIK confirmation code) is masked as XXXXXXXX in the public file.filerInfo/notifications — empty notification-recipient slots.<formData> — the report<formData> is organized into four sub-sections that mirror the paper-form Parts plus a closing signature block.
<generalInfo> (Items 1 through 7 on the rendered form)A short header identifying the report context: reportDate (the calendar month-end being reported), cik, seriesId, totalShareClassesInSeries, finalFilingFlag (set when this is the series' last N-MFP1 filing), and fundAcqrdOrMrgdWthAnthrFlag (set when the fund has been acquired by or merged with another fund during the period).
<seriesLevelInfo> (Part A — series-level data)The bulk of the operational profile of the fund series, including:
adviser, subAdviser, indpPubAccountant, administrator, and transferAgent, each with a name and (where applicable) SEC file number, city, and state.feederFundFlag and masterFundFlag, with a nested feederFund element carrying cik, name, fileNumber, and seriesId of the related fund when the relationship exists.seriesFundInsuCmpnySepAccntFlag (insurance-company separate-account flag), moneyMarketFundCategory (e.g. Prime, Government, Treasury, Tax-Exempt), and fundExemptRetailFlag.averagePortfolioMaturity (weighted average maturity, WAM, in days) and averageLifeMaturity (weighted average life, WAL, in days).totalValueDailyLiquidAssets, totalValueWeeklyLiquidAssets, percentageDailyLiquidAssets, and percentageWeeklyLiquidAssets, one Friday-of-week child for each Friday in the reporting month (fridayWeek1 through fridayWeek5).cash, totalValuePortfolioSecurities, amortizedCostPortfolioSecurities, totalValueOtherAssets, totalValueLiabilities, and netAssetOfSeries.numberOfSharesOutstanding, stablePricePerShare, sevenDayGrossYield, and a weekly netAssetValue series indexed by Friday.<classLevelInfo> (Part B — class-level data, repeating)This block repeats once per share class in the series. Each instance includes classesId (matching a C… ID from the EDGAR series/class registry), minInitialInvestment, netAssetsOfClass, numberOfSharesOutstanding, a weekly netAssetPerShare series, and per-week <fridayWeekN> blocks each carrying weeklyGrossSubscriptions and weeklyGrossRedemptions. A totalForTheMonthReported summary reconciles the weekly flows. Closing fields include sevenDayNetYield, personPayForFundFlag, and nameOfPersonDescExpensePay describing any expense-payer arrangement for the class.
<scheduleOfPortfolioSecuritiesInfo> (Part C — holdings, repeating)Part C is the longest section of the filing and repeats once per portfolio holding — typically dozens to several hundred times per filing. Each holding is a fully described position, not a row in a table:
nameOfIssuer, titleOfIssuer, CUSIPMember (CUSIP), and cik of the issuer when known.investmentCategory (e.g. Financial Company Commercial Paper, Treasury Debt, Government Agency Debt, Variable Rate Demand Note, Repurchase agreement, Asset Backed Commercial Paper, Certificate of Deposit, Other Note, Other Repurchase Agreement, Insurance Company Funding Agreement, Investment Company, Financial Company Note, Non-Financial Company Commercial Paper, Non-Financial Company Note, Tender Option Bond, Other Municipal Debt, Other Instrument) and securityRated (e.g. First Tier Security, Second Tier Security).designatedNrsro repeats once per credit-rating organization, each with nameOfDesignatedNRSRO and creditRatingDesignatedNRSRO.investmentMaturityDateWAM, investmentMaturityDateWAL, and finalLegalInvestmentMaturityDate.securityDemandFeatureFlag, securityGuaranteeFlag, and securityEnhancementsFlag, each accompanied by nested detail blocks (provider name, provider designation, expiration, amount) when set to Y.yieldOfTheSecurityAsOfReportingDate, includingValueOfAnySponsorSupport, excludingValueOfAnySponsorSupport, and percentageOfMoneyMarketFundNetAssets.securityCategorizedAtLevel3Flag (ASC 820 fair-value level), dailyLiquidAssetSecurityFlag, weeklyLiquidAssetSecurityFlag, and illiquidSecurityFlag.A <signature> element at the close of <formData> carries registrant, signatureDate, signature (the typed signature string), nameOfSigningOfficer, and titleOfSigningOfficer, attesting the report on behalf of the fund.
xslN-MFP1_X01/primary_doc.xml — XHTML renderingThis sibling file is the EDGAR-generated XHTML view of the same filing — declared with <!DOCTYPE html ...> and structured as a series of HTML tables that follow the paper-form item numbering: Items 1 through 8 for filer and general information, Part A items A.1 through A.30 for series-level data, Part B for class-level data, and Part C for the holdings schedule. The content is purely presentational and is fully derivable from the structured primary_doc.xml; it is included because EDGAR ships it as part of the original submission, but consumers performing data extraction can rely entirely on the XML.
The complete submission text wrapper (the SGML envelope) is referenced via the linkToTxt field in metadata.json but is not redistributed inside the record. Image files that may have accompanied the original EDGAR submission are excluded from each accession folder. The CCC (ccc — CIK confirmation code) inside <headerData> is masked as XXXXXXXX in EDGAR's public copy and therefore in the dataset.
The Form N-MFP1 record schema is essentially constant across the dataset's coverage window because N-MFP1 itself was a short-lived, fixed-version interim taxonomy. Material structural context, however, sits at the boundaries of that window:
Prime, Government, Tax-Exempt, Retail exemption flag), additional repurchase-agreement collateral disclosure, and the Level-3 / liquid-asset / illiquid flags at the security level. N-MFP1, accepted by EDGAR beginning April 14, 2016, is the EDGAR-side implementation of these amendments.Within the dataset itself, the only meaningful structural variation across records is the /A amendment marker, which leaves the XML schema identical but indicates the report restates a previously filed month.
Every record's structured payload is a single XML document under the nmfp1 namespace; there are no ASCII-era, HTML-era, or XBRL-era variants to track within the N-MFP1 window because the form was born structured, lived for roughly six months of original filings, and was retired in favor of N-MFP2 — also a structured XML form. The XSL-rendered XHTML sibling is the same document presented for human reading, never an alternate data source. CCC fields are pre-masked. CUSIPs, CIKs, file numbers, and series/class IDs are stored as plain string values and are stable across periods. Folder names use accession numbers with dashes stripped, while metadata.json carries the dashed form.
N-MFP1/A amendment is a complete restated filing, not a delta against the original; the entire <formData> payload is re-supplied. Joining originals and amendments by seriesId plus periodOfReport and ordering by filedAt is the typical way to identify the latest authoritative report for a given series-month.periodOfReport and filedAt can differ by months — and occasionally years — for amendments, so date-window queries should be specified against whichever timestamp matches the analytical intent.fridayWeek1 through fridayWeek5) are positional, not date-keyed; the actual Friday dates must be derived from reportDate. Months with only four Fridays in the reporting period leave fridayWeek5 absent or empty.<scheduleOfPortfolioSecuritiesInfo> blocks in a single filing, and repurchase-agreement holdings carry additional nested collateral subtrees that are absent from plain holdings.includingValueOfAnySponsorSupport and excludingValueOfAnySponsorSupport; the difference between them quantifies the sponsor support attributed to the security.feederFund element under <seriesLevelInfo>; correctly attributing assets requires reading feederFundFlag and masterFundFlag together, and the same master series may appear in many accession folders if multiple feeders reference it.primary_doc.xml; the XHTML file should be treated as a presentation artifact and not parsed as a data source.seriesAndClassesContractsInformation[] array in metadata.json and the seriesId / classesId values inside primary_doc.xml use the same EDGAR S… and C… identifiers, providing a direct join key between the submission envelope and the structured payload.Form N-MFP1 is filed exclusively by registered money market funds: open-end management investment companies (or individual series thereof) registered under the Investment Company Act of 1940 that hold themselves out as money market funds and operate in reliance on Rule 2a-7. The filer of record is the registered fund or trust; reports are submitted on EDGAR and signed by an officer (typically the principal executive officer) on the fund's behalf.
A trust with multiple money market series files a separate N-MFP1 for each series. All Rule 2a-7 fund categories in operation during the interim window are included: government, prime (institutional and retail), and tax-exempt funds, whether transacting at a stable share price or a floating NAV.
Outside the population:
Filing is strictly periodic, not event-driven. Rule 30b1-7 under the Investment Company Act of 1940 (17 CFR 270.30b1-7) requires every registered money market fund to file Form N-MFP for every calendar month it operates. The trigger is the close of the calendar month: the report is due no later than the fifth business day after month-end and reports portfolio and operational data as of the last business day of the prior month. There is no minimum-activity threshold and no event condition; the obligation runs every month a fund exists as a money market fund.
Funds created or terminated mid-window have a partial sequence of filings tied only to the months they operated.
N-MFP1 is the bridging schema generation of Form N-MFP. The Commission's July 23, 2014 money market fund reforms (Investment Company Act Release No. 31166) added new data items (floating NAV indicators, liquidity fees and gates, daily liquid assets and weekly liquid assets, shareholder flows, and expanded security-level fields), but the fully revised XML schema took longer to deploy than the rule. N-MFP1 was the interim EDGAR submission type used while the final schema was finished.
EDGAR accepted N-MFP1 (and amendment counterpart N-MFP1/A) starting April 14, 2016. The first dataset filings therefore appear in early May 2016, when funds submitted April 2016 reports. N-MFP1 was superseded by Form N-MFP2 effective October 14, 2016; new monthly reports filed on or after that date use N-MFP2. The dataset accordingly covers roughly a six-month operational window of original monthly reports (reporting periods April through approximately September 2016), which explains its small size.
A fund continuously operating across the reform transition has filings split across three submission-type generations: the pre-reform Form N-MFP, then N-MFP1 during the interim window, then N-MFP2 from October 14, 2016 onward. All three are governed by the same Rule 30b1-7 obligation.
N-MFP1/A is filed by the same fund that filed the original report when an error, omission, or change is identified in a previously submitted N-MFP1 (for example, a misreported CUSIP, principal amount, weekly liquid asset percentage, or NAV). Each amendment is keyed to a prior accession number and corrects a specific reporting month. Because the underlying obligation is accuracy of the monthly report, N-MFP1/A filings can appear after October 14, 2016 even though no new original N-MFP1 reports are accepted after that date.
During the N-MFP1 window, N-MFP filings were submitted to the Commission within five business days after month-end but were not released publicly on EDGAR until 60 days after the end of the reporting month. The Commission used the data internally from the moment of filing. The 60-day delay was eliminated for the successor Form N-MFP2 in later rulemaking, but during N-MFP1's lifetime the delayed-public regime applied. Distinguish the filing date from the historical public-release date when reconstructing the timeline.
Form N-MFP1 occupies an unusually narrow position in the SEC's investment-company reporting family: it is the transitional version of the money market fund (MMF) monthly portfolio report accepted by EDGAR for roughly six months, from April 14, 2016 through October 13, 2016. The most useful comparisons are with the two N-MFP generations that bracket it, the parallel non-MMF portfolio regime (N-PORT and the legacy N-Q), and the operational and registration filings (N-CEN, N-1A) that describe the same funds from different angles.
The direct predecessor. Same Rule 30b1-7 basis, same monthly cadence, same MMF filer population, and the same fund-level-plus-holdings structure. The difference is the schema: N-MFP1 implements the July 23, 2014 amendments (expanded liquidity metrics, class-level NAV, weekly liquid-asset percentages, additional security-level fields) using the interim XML taxonomy accepted starting April 14, 2016. Original N-MFP covers the older, pre-amendment field set through April 2016. Any continuous MMF time series crossing April 2016 must chain the two; neither substitutes for the other across that boundary.
The direct successor and current ongoing report. Same rule, same filers, same monthly frequency, same general structure. The substantive difference is again the schema: N-MFP2 reflects the final post-2014-amendment version with refined XML structures, additional and modified data elements, and the EDGAR validation rules that took effect on the October 2016 MMF reform compliance date. For any MMF holdings analysis from October 14, 2016 forward, N-MFP2 is the correct source. N-MFP1 covers only the brief transition window in between.
The monthly portfolio report for non-MMF registered investment companies (open-end mutual funds, ETFs, certain closed-end funds). Filer populations are mutually exclusive: MMFs file the N-MFP series, non-MMFs file N-PORT. N-PORT is broader in asset coverage (equities, derivatives, structured products) and adds portfolio-level risk metrics (interest-rate and credit-spread sensitivities) absent from N-MFP1. N-MFP1 in turn carries MMF-specific fields (weekly liquid assets, shadow NAV, repo-level detail tuned to short-term instruments) absent from N-PORT. The two are complements, not substitutes.
The discontinued quarterly holdings report for non-MMF registered funds, since replaced by N-PORT. Comparable to N-MFP1 only in reporting registered-fund holdings; it differs in filer population (non-MMF), frequency (quarterly), and format (largely tabular/narrative rather than structured XML). Useful as historical reference for pre-N-PORT non-MMF holdings, but it never overlapped N-MFP1's filer population.
The annual census report for registered investment companies (including MMFs), successor to N-SAR. Overlaps with N-MFP1 only on a small set of identifying fields (series and class identifiers, adviser, custodian, auditor). N-CEN is annual rather than monthly, operational rather than portfolio-level (board composition, service providers, securities lending, fund-type classification), and contains no security-by-security schedule. Cannot substitute for N-MFP1 on holdings; N-MFP1 cannot substitute for Form N-CEN on fund operations.
The registration statement and prospectus form for open-end funds, including MMFs. Overlap is limited to fund identity and stated investment policy. Form N-1A is narrative, legal, and forward-looking (objectives, strategies, risks, fees); N-MFP1 is structured, quantitative, and backward-looking (actual month-end holdings). N-1A defines what the fund may do; N-MFP1 records what it actually did. Pure complements, with no substitution relationship.
Form N-MFP1 Files is the only authoritative source for MMF monthly portfolio reports filed under the post-2014-amendment, pre-N-MFP2 interim XML taxonomy that EDGAR accepted between April 14, 2016 and October 13, 2016, together with the corresponding N-MFP1/A amendments. For any MMF analysis confined to that six-month window — notably studies of fund behavior immediately preceding the October 2016 MMF reform compliance date — neither original N-MFP nor N-MFP2 can substitute. Outside that window, the adjacent N-MFP and N-MFP2 datasets take over; N-PORT, N-CEN, and N-1A address distinct but adjacent needs (non-MMF holdings, annual operational census, registration disclosure).
The audience for the Form N-MFP1 Files Dataset is concentrated among professionals who need to reconstruct what money market funds held, how liquid they were, and how they repositioned in the run-up to the October 2016 rule changes.
Sell-side and in-house MMF analysts use the fund-level summary to track repositioning across the reform transition. The fields that matter most are fund category (prime, government, tax-exempt, single-state), WAM, WAL, total net assets, NAV per share, and daily and weekly liquid asset percentages. Output is peer comparison of how prime funds shed credit exposure, lifted liquidity buffers, and migrated assets to government strategies.
Credit analysts running enhanced cash, ultra-short, and short-duration strategies mine the holdings schedule for issuer-level MMF demand. Key fields are issuer name, CUSIP, security category (financial CP, ABCP, CD, repo, Treasury, agency discount notes, VRDNs), maturity date, principal amount, amortized cost, fair value, and yield. The data feeds primary-issuance demand models, relative-value screens for short paper, and issuer concentration dashboards.
Repo, agency discount note, and CP/CD desks use the holdings schedule to study MMF buying behavior across the prime-to-government conversion. Repo line items carry counterparty, collateral category, collateral CUSIPs and maturities, repo rate, and principal, supporting historical calibration of dealer funding models and retrospective analysis of repo rate dislocations during the 2016 conversion wave.
Researchers at central banks, financial-stability bodies, and regulatory research divisions treat the 2016 window as a natural experiment for the 2014 reforms. They use total net assets, liquid asset ratios, WAM/WAL distributions, and full holdings detail to measure pre-reform repositioning, asset migration between fund categories, and transmission to short-term funding markets. Outputs include reform-impact working papers, run-risk models, and post-mortems on the structural shift.
Compliance officers at fund complexes and regulatory examination staff use archived N-MFP1 filings to verify Rule 2a-7 compliance during the transition. The relevant fields are WAM, WAL, daily and weekly liquid asset percentages, illiquid security percentage, issuer diversification, and seven-day gross yield. The data supports retrospective lookbacks and responses to inquiries about historical positioning.
Corporate treasurers, sweep program managers, and fund-of-funds risk teams that allocated cash to MMFs in 2016 use the holdings schedule for look-through exposure reconstruction. They focus on issuer concentration, repo counterparty exposure, and financial-sector CP and CD exposure, validating historical risk reports and reconstructing indirect exposures through the conversion period.
Analysts at credit rating firms covering MMFs use security category, issuer, NRSRO ratings (where reported), maturity ladders, and overnight liquidity composition to validate rating model inputs against disclosed holdings, run stressed liquidity scenarios on historical portfolios, and study how reform repositioning affected rated funds.
Quant teams modeling short-term funding markets use time-stamped principal amounts by issuer and instrument type, yields, and maturity dates to reconstruct issuance and rolloff patterns. The dataset feeds short-rate models, MMF demand factors in CP pricing, and microstructure studies of the prime-to-government migration.
Vendors maintaining longitudinal MMF holdings histories ingest the full N-MFP1 and N-MFP1/A XML to fill the May to October 2016 gap between predecessor N-MFP and successor N-MFP2. Engineering work centers on normalizing CIK, series and class IDs, CUSIPs, issuer names, and category codes for continuous cross-form time series.
Teams building retrieval and reasoning systems over fund disclosures use N-MFP1 for entity extraction, table parsing, and QA fine-tuning. The consistent XML schema and the pairing of fund-level summary with security-level detail make it a clean corpus for MMF and reform-era queries.
The use cases below tie directly to the 2016 reform transition and to specific fields in primary_doc.xml and metadata.json.
Aggregate seriesLevelInfo/netAssetOfSeries and moneyMarketFundCategory (Prime, Government, Treasury, Tax-Exempt) by reportDate from May 2016 through October 2016 to quantify the run-off from prime funds and the inflows into government and Treasury funds during the conversion wave. Joining seriesId across consecutive months produces a series-level migration ledger; combining it with feederFundFlag / masterFundFlag and the feederFund cross-reference allows correct attribution at the master level rather than double-counting feeders.
Extract the Friday-indexed percentageDailyLiquidAssets and percentageWeeklyLiquidAssets series along with averagePortfolioMaturity (WAM) and averageLifeMaturity (WAL) for each filing. Plotting these per seriesId across the May to October 2016 reports shows how prime funds shortened WAM/WAL and lifted daily and weekly liquid-asset ratios above the Rule 2a-7 minima as the October 14, 2016 deadline approached, and supports peer-group benchmarking of pre-reform compliance posture.
Iterate scheduleOfPortfolioSecuritiesInfo blocks where investmentCategory is Financial Company Commercial Paper, Asset Backed Commercial Paper, Certificate of Deposit, Non-Financial Company Commercial Paper, or Financial Company Note, and aggregate includingValueOfAnySponsorSupport and percentageOfMoneyMarketFundNetAssets by nameOfIssuer and CUSIPMember. The output is a monthly issuer-demand panel covering the period when prime-fund redemption pressure forced large CP and CD issuers (notably non-US bank programs) to reprice, useful for retrospective primary-issuance analysis and for calibrating short-rate models around the 2016 dislocation.
For holdings with investmentCategory of Repurchase agreement or Other Repurchase Agreement, parse the nested collateral subtree (counterparty issuer, collateral CUSIP, principal, value, maturity) together with yieldOfTheSecurityAsOfReportingDate and finalLegalInvestmentMaturityDate. Aggregating across all N-MFP1 filings for a given reportDate produces a dealer-by-dealer view of MMF repo financing during the prime-to-government conversion, supporting analysis of GC repo rate behavior in September and October 2016 and dealer-funding model recalibration.
Walk the repeating classLevelInfo blocks and pull each fridayWeekN/weeklyGrossSubscriptions and weeklyGrossRedemptions together with netAssetsOfClass and numberOfSharesOutstanding. Reconciling against totalForTheMonthReported yields a weekly flow series per classesId that captures institutional prime-fund redemptions in the weeks immediately preceding October 14, 2016, distinguishing institutional from retail share classes via minInitialInvestment and the fundExemptRetailFlag on the parent series.
Use metadata.json (accessionNo, periodOfReport, filedAt, seriesAndClassesContractsInformation[]) and primary_doc.xml (seriesId, classesId, cik, CUSIPMember) to splice N-MFP1 records into a continuous time series with predecessor N-MFP and successor N-MFP2 reports. For each seriesId plus periodOfReport pair, retain the latest filedAt to fold in N-MFP1/A restatements, producing the authoritative monthly snapshot used by vendors and quant teams to fill the May to October 2016 gap.
For a specific fund series under regulatory inquiry, pull every N-MFP1 and N-MFP1/A filing matching its seriesId, then verify percentageDailyLiquidAssets (≥10%), percentageWeeklyLiquidAssets (≥30%), averagePortfolioMaturity (≤60 days), averageLifeMaturity (≤120 days), and the illiquidSecurityFlag count against Rule 2a-7 limits for each Friday in the reporting month. Pairing the structured values with the signature block (nameOfSigningOfficer, signatureDate) supports examination responses and internal compliance reconstructions of the 2016 transition period.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-nmfp1-files.json
Returns dataset metadata (name, description, last updated timestamp, earliest sample date, total records and size, covered form types, container format, and file types), the full dataset download URL, and the list of all container files with per-container size, record count, updated timestamp, and download URL. Use this endpoint to monitor which containers were modified in the most recent refresh run and to decide which containers to fetch on a day-by-day basis. This endpoint does not require an API key.
1
{
2
"datasetId": "1f13365b-9ae0-6969-b68c-53b5ac4d89da",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-nmfp1-files.zip",
4
"name": "Form N-MFP1 Files Dataset",
5
"updatedAt": "2026-04-15T07:57:44.758Z",
6
"earliestSampleDate": "2016-05-01",
7
"totalRecords": 7256,
8
"totalSize": 197064358,
9
"formTypes": ["N-MFP1", "N-MFP1/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["XML", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-nmfp1-files/2016/2016-10.zip",
15
"key": "2016/2016-10.zip",
16
"size": 41258374,
17
"records": 1523,
18
"updatedAt": "2026-04-15T07:57:44.758Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-nmfp1-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing every monthly container from May 2016 through October 2016. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-nmfp1-files/2016/2016-10.zip?token=YOUR_API_KEY
Downloads one individual monthly container instead of the full dataset. Use the downloadUrl values from the index JSON's containers array to retrieve specific months. This endpoint requires an API key.
The dataset covers Form N-MFP1 and its amendment variant Form N-MFP1/A, the interim version of the SEC's monthly money market fund portfolio report filed under Rule 30b1-7 of the Investment Company Act of 1940. N-MFP1 was the EDGAR-side implementation of the Commission's July 23, 2014 money market fund reforms.
One record is a single EDGAR submission of Form N-MFP1 or N-MFP1/A, identified by accession number and packaged as a folder containing metadata.json, the structured primary_doc.xml payload, and the EDGAR XSL-rendered XHTML view at xslN-MFP1_X01/primary_doc.xml. Each submission corresponds to one money market fund series reporting one calendar month of operational, liquidity, share-flow, and security-by-security holdings data.
Form N-MFP1 was filed exclusively by registered open-end management investment companies (or individual series of such companies) operating in reliance on Rule 2a-7 — that is, government, prime (institutional and retail), and tax-exempt money market funds. A trust with multiple money market series files a separate N-MFP1 for each series. Closed-end funds, ETFs, ordinary mutual funds, BDCs, UITs, private funds, and operating companies are outside the population.
EDGAR accepted N-MFP1 between April 14, 2016 and October 13, 2016, so the dataset's original filings cover reporting periods from roughly April 2016 through September 2016, with the earliest sample date of May 1, 2016. N-MFP1/A amendments restating those months continue to arrive after the cutoff and are included as they are filed.
N-MFP2 is the direct successor schema, effective October 14, 2016. It uses a new XML namespace and reorganizes feeder-fund relationships, NRSRO ratings, and repurchase-agreement collateral structures. For monthly money market fund holdings analysis from October 14, 2016 forward, N-MFP2 is the correct source; N-MFP1 is the only authoritative source for the brief interim window between the original Form N-MFP and N-MFP2.
The dataset is distributed as ZIP containers organized by month, each containing accession-number folders. The file types inside the dataset are limited to XML (the canonical primary_doc.xml payload), XHTML (the EDGAR XSL rendering), and JSON (the curated metadata.json envelope). For machine extraction, every disclosed value is available in primary_doc.xml; the XHTML sibling is presentational.
An N-MFP1/A amendment is a complete restated filing rather than a delta against the original — the entire <formData> payload is re-supplied. To identify the latest authoritative report for a given series-month, join originals and amendments by seriesId plus periodOfReport and order by filedAt. Amendments can appear long after October 14, 2016 even though no new original N-MFP1 reports are accepted after that date.