The hard part of N-PORT isn't the XBRL submission — it's assembling position-level, derivatives, and liquidity data across custodians, fund admins, and sub-advisors every month. Milemarker makes the data part automatic.

Form N-PORT is the SEC's monthly portfolio reporting form for registered management investment companies, mandated by Rule 30b1-9 of the Investment Company Act of 1940. Funds report month-end data within 60 days; the third month of each quarter becomes publicly available after another 60-day lag. The form covers position-level holdings, derivatives detail (futures, forwards, swaps, options), counterparty exposure, repurchase and reverse-repurchase agreements, securities lending activity, Rule 22e-4 liquidity classifications, currency exposure, and monthly performance. It applies to most registered investment companies and to most ETFs — and it is the single most data-intensive recurring filing in the '40 Act calendar.

The N-PORT Data Problem

The filing itself is not the hard part. A competent filer — DFIN, Confluence, Vermilion — converts structured inputs into valid XBRL and submits to EDGAR within minutes. The hard part, the part that consumes operations and compliance calendars, is assembling the inputs. N-PORT wants position-level detail as of a specific month-end, reconciled across fund admin, custodian, and sub-advisor; derivatives with counterparty, notional, and settlement detail; liquidity classifications under Rule 22e-4; securities lending activity; currency exposure; repos and borrowings. Each of those data sets lives in a different system, in a different format, on a different cadence.

Fragmented sources are the default. The fund administrator has accounting-positioned NAV and the fund-side books of account. The custodian has settlement-positioned holdings. The sub-advisor has trade detail at the blotter level. The transfer agent has share-class flows. The risk or liquidity vendor has classifications. The security master provider has CUSIP, ISIN, LEI, and reference data. Every N-PORT cycle, someone pulls from each source, reconciles the differences, and assembles a single version of the truth by month-end plus 60.

The 60-day deadline is merciful on paper and tight in practice. By the time the custodian's month-end positions are final, the fund admin's NAV is locked, the sub-advisor's attribution is delivered, and the liquidity classifications are refreshed, the clock has already run. Reconciliation work that should have happened continuously gets compressed into the two weeks before the filing. Errors found late trigger resubmissions; resubmissions trigger SEC comment letters; comment letters trigger operational remediation that should have been avoided upstream.

Derivatives detail is the single most brittle piece when the data is assembled manually. Each derivative position needs counterparty identification (with LEI), notional amount, termination or expiration date, reference asset, pay/receive legs for swaps, exercise price for options, settlement method, and collateral posting detail. A spreadsheet that catches 95% of that data correctly is still catastrophically wrong from an N-PORT perspective because the missing 5% is where the SEC's attention lands.

Rule 22e-4 liquidity classification has its own data pipeline. Each security is bucketed — highly liquid, moderately liquid, less liquid, illiquid — based on the fund's classification methodology and its vendor's models. That classification has to be point-in-time, tied to the month-end positions, and recorded in a way that ties back to the 22e-4 program. Reassembling that data the week of filing is harder than it sounds; tying it to the underlying holdings on the warehouse side turns it into a query.

Errors in N-PORT trigger real consequences. Comment letters, resubmissions, board conversations, and — at the extreme — enforcement attention. The data quality problem that produces late-stage errors is not solvable at the filer layer. It has to be solved upstream, in the data assembly, before the filer ever sees the file.

What Automated N-PORT Data Assembly Requires

1. Daily Position Reconciliation

Fund admin, custodian, and sub-advisor positions reconciled daily so breaks surface continuously — not the week before filing. The month-end pull is a confirmation, not a scramble.

1. Security Master with CUSIP/ISIN/LEI

Every security enriched with CUSIP, ISIN, LEI, ticker, issuer, asset class, country of risk, and currency — so N-PORT's reference data fields come from a single authoritative source.

1. Derivatives Reference Data

Counterparty, notional, termination date, reference asset, settlement method, and collateral detail for every derivative — structured in the warehouse, not re-keyed from the fund admin's PDF.

1. Liquidity Classification Workflow

Rule 22e-4 bucket assignments joined to month-end positions with historical point-in-time lineage — so the quarterly liquidity disclosure is reproducible and defensible.

1. Counterparty + Issuer Data

Counterparty aggregation across repos, reverse repos, derivatives, and securities lending — enriched with LEIs and netted where appropriate for the N-PORT disclosure.

1. Audit-Ready Lineage

Every field on the filing traceable back to its source feed, ingestion timestamp, and transformation history. Regulators, auditors, and independent trustees can follow the thread.

How Milemarker Supports Your N-PORT Workflow

Milemarker pulls positions and accounting data from the fund admin (Ultimus, SEI, ALPS, SS&C, BNY Mellon, State Street), settled positions from the custodian, and trade blotters and attribution from each sub-advisor into a firm-owned Snowflake warehouse. Those feeds run daily, not monthly, which is what makes N-PORT assembly a confirmation exercise rather than a reconstruction exercise.

Normalization maps each source to an N-PORT-aware schema. Position records carry CUSIP, ISIN, LEI, issuer, asset class, country of risk, and currency. Derivatives records carry counterparty LEI, notional, termination date, pay/receive, settlement method, and collateral posting. Liquidity classifications from the risk or liquidity vendor are joined to the positions they describe. Repo, reverse-repo, securities lending, and currency exposure records are modeled explicitly, not inferred.

Reconciliation breaks are flagged early — not the week before filing. When the fund admin's market value disagrees with the custodian's, when the sub-advisor's blotter doesn't tie to settled trades, when a security lacks a CUSIP or LEI, when a derivative's counterparty isn't in the security master — each case surfaces in the warehouse as a queryable exception with full lineage. Operations fixes it in real time; the filing month sees a clean pull, not a rescue operation.

The warehouse feeds the filer. DFIN ActiveDisclosure / Arc Suite, Confluence, Vermilion — whichever filer the sponsor uses — receives an N-PORT-ready extract in the filer's required format. The sponsor's relationship with the filer doesn't change. The file quality does.

Audit lineage is preserved in Snowflake. Every position, every derivative field, every liquidity bucket, every reconciliation decision is retained with source, ingestion timestamp, and transformation detail. When a regulator follows up on a prior filing, when an auditor tests the control, when an independent trustee asks how a specific value was derived — the answer is in the warehouse, not in someone's inbox.

Before Milemarker

• 7-day scramble every filing cycle

• Derivatives detail re-keyed from PDFs

• Position reconciliation happens the week of filing

• Liquidity classifications assembled manually

• Errors surface after submission

• Prior-period lineage lives in email threads

• With Milemarker

• Continuous readiness between filings

• Derivatives structured at ingestion

• Position breaks flagged daily, not monthly

• Liquidity buckets joined to holdings in the warehouse

• Errors caught pre-filing, not post-submission

• Historical lineage queryable in Snowflake

Who This Is For

Fund Sponsors Filing 5+ Funds

Sponsors with a complex of five or more registered funds feel the N-PORT burden most acutely. Each fund has its own positions, its own derivatives, its own liquidity profile, and its own filing deadline, but they share service providers and a single operations team. A unified data layer scales across the complex without adding a parallel assembly process per fund. Firms like Flat Iron Wealth — advisory-first RIAs that have grown into proprietary fund sponsorship — find that the N-PORT workload stops scaling linearly once the warehouse is in place.

Operations Leaders Managing Multiple Filers

Operations leaders who coordinate N-PORT assembly across multiple filers (one filer for the mutual fund complex, another for the ETF series, sometimes a third for a sub-advised fund) need a consistent data source regardless of the filer relationship. Milemarker's warehouse is filer-agnostic — the same extract logic can produce DFIN-ready, Confluence-ready, or Vermilion-ready output — which decouples the sponsor's data infrastructure from the filer choice.

CCOs Accountable for Accuracy

The fund CCO is accountable for the accuracy of the filing even though the filer signs the submission and the fund administrator supplies much of the raw data. When the SEC sends a comment letter, the CCO is the one who has to explain the input. A data layer with audit lineage turns that explanation from a reconstruction exercise into a warehouse query, which materially reduces the CCO's exposure to post-filing surprises.

CFOs Tired of Q-End Heroics

Fund-family CFOs and treasurers see the N-PORT cycle as a recurring drag on the operations calendar — staff burn, overtime, filing-week heroics, and the inevitable rework that follows. Shifting the data assembly from a monthly scramble to a continuous readiness model recovers the staff hours and reduces the error rate at the same time. The CFO's interest is straightforward: a predictable, auditable process that doesn't consume the operations team every 30 days.

Frequently Asked Questions

Does Milemarker file N-PORT?

No. Milemarker is not a regulatory filer. The firm's existing filer — DFIN (ActiveDisclosure / Arc Suite), Confluence, Vermilion (FactSet), or similar — continues to own the XBRL assembly and the EDGAR submission. Milemarker assembles and validates the data feeding that workflow: positions, derivatives reference data, counterparty detail, liquidity classifications, and currency exposure. The filer receives clean, reconciled, lineage-traced inputs instead of raw pulls from multiple systems.

What filers do you work with?

Milemarker works alongside the major '40 Act regulatory filers — DFIN (ActiveDisclosure / Arc Suite), Confluence Technologies, Vermilion Reporting Suite (FactSet), and others. Output from the warehouse can be delivered as structured files in the filer's required format. The sponsor's filer relationship does not change; what changes is the quality and timeliness of the data flowing in.

How do you get derivatives data?

Derivatives data comes from the fund administrator and the sub-advisor, with enrichment from the security master. Milemarker ingests the daily positions file and the trade blotter, then joins derivatives positions to reference data covering counterparty, notional, exercise price, settlement method, and termination clauses. The result is a derivatives record that already answers the N-PORT Part C and Schedule-level questions before the filer asks.

What about Rule 22e-4 liquidity?

Rule 22e-4 liquidity classification is a dedicated data workflow, separate from the positions themselves. Milemarker ingests the fund's liquidity classifications (highly liquid, moderately liquid, less liquid, illiquid) from the risk system or liquidity vendor, joins them to the security-level positions, and exposes the bucket composition over time. The quarterly N-PORT liquidity disclosure becomes a query against the warehouse rather than a separate data pull.

How is data reconciled with the fund admin?

Milemarker runs daily reconciliations across fund admin, custodian, and sub-advisor positions. When the three sources disagree — position count, market value, cost basis — the break surfaces in the warehouse as a queryable exception with source lineage. That lets operations fix breaks continuously instead of discovering them the week before N-PORT is due. The fund admin remains the book of record; Milemarker makes sure the book agrees with everything else.

Do you support both N-PORT and Form N-CEN?

Yes. The same warehouse that holds N-PORT position-level data also holds the directors, officers, service providers, securities lending, and fund-of-funds data that feed Form N-CEN annually. Milemarker structures both data sets in parallel, so the monthly/quarterly N-PORT cadence and the annual N-CEN cadence both run against a single, consistent source. See the N-CEN filing data platform page for how the annual filing is handled.

How long does setup take?

For a sponsor already using one of the common fund admins (Ultimus, SEI, ALPS, SS&C, BNY Mellon, State Street), the first N-PORT-ready data layer is typically flowing within 4–6 weeks. Full setup — including derivatives reference data, liquidity classifications, counterparty mapping, and validation against the prior filing — takes 8–12 weeks depending on fund complexity and the number of sub-advisors involved.

Is historical filing data captured?

Yes. Milemarker can ingest prior N-PORT filings and the underlying position, derivatives, and liquidity data that supported them. That creates a continuous historical view — useful for SEC comment-letter responses, for trend analysis across quarters, and for the fund's own board reporting. Historical lineage is preserved in the same Snowflake instance the firm owns.

Related guides

Part of the Automation & Relay series:

• Data Platform for '40 Act Fund Sponsors: Unifying Fund Admin, Transfer Agent, Sub-Advisor & Custodian Data

• N-CEN Filing Data Platform: Annual Form N-CEN Made Audit-Ready

• NAV Reconciliation Automation for '40 Act Funds

• '40 Act Fund Compliance Data: Rule 38a-1, 17j-1, 22c-1 in One Data Platform

• Milemarker Relay for VPs of Technology

• Wealth Management Reporting Automation: From Manual Exports to Real-Time Dashboards