Reviewed by GFS Research Desk.
A mutual fund NAV and a portfolio disclosure answer different, date-bound questions. NAV is a per-unit value for the date shown; a portfolio disclosure is a holdings snapshot for its own reporting date. A later NAV can move even when you are looking at the same latest published snapshot. First match the scheme label and dates, then read each record for its limited purpose.
A reader may open a mutual fund’s latest portfolio disclosure, see familiar holdings and weights, then notice that the NAV on a newer date has changed. It can look like a contradiction: “If the portfolio looks unchanged, why did the NAV move?” Usually, the first issue is not a contradiction. It is a date-and-document mismatch.
This guide explains the mutual fund NAV vs portfolio disclosure date problem. It does not assess a scheme, compare funds, predict a NAV, or tell anyone to transact. The relevant scheme’s current official documents remain the source for a live question. Treat every figure below as a reading method, not a conclusion about a holding.
Two records, two clocks
An official NAV record identifies a scheme, plan, or option and a NAV date. A portfolio disclosure identifies holdings and related fields as of a stated reporting date. A factsheet can add a third date: its reporting month or issue date. The dates may be close together, but they are not automatically interchangeable.
| Record | Main question it can help answer | Date to capture | What it cannot establish alone |
|---|---|---|---|
| NAV record | What per-unit value was published for this identified scheme record on this date? | NAV date | Every holding, trade, valuation input or reason for a change |
| Portfolio disclosure | What holdings and disclosed fields were shown for the stated snapshot date? | Portfolio “as on” date | Today’s holdings, today’s valuation, or a future NAV |
| Factsheet | What summary metrics did the publisher report for its stated period? | Factsheet month and issue date, if shown | A live portfolio or a personal outcome |
| SID, Kim, or addendum | What scheme terms, objective, and stated disclosures apply in that document version? | Version/effective date | A current NAV explanation by itself |
SEBI’s Master Circular for Mutual Funds is a regulatory reference for mutual-fund disclosure and operational material. [S1] AMFI publishes official NAV access points, including NAV history and a daily NAV file. [S2][S3] Those sources make the discipline important: identify the exact record and date before carrying a number into another document.
A hypothetical date map
Imagine a fictional scheme record. Its portfolio disclosure says “as of 31 July”; its factsheet is labeled July; and an official NAV page shows a NAV dated 5 August. The 5 August NAV is later than the 31 July snapshot. It would be a mistake to describe the July holdings table as proof that every input to the 5 August NAV was unchanged.
This illustration does not say that any one kind of holding will rise or fall, and it is not a formula for forecasting. It shows only the order of documents:
| What the reader sees | Safe observation | Unsafe leap |
|---|---|---|
| Portfolio snapshot dated 31 July | The document reports holdings for its stated date | The list is a live portfolio on 5 August |
| NAV dated 5 August | A per-unit value is displayed for 5 August | One named holding caused the move |
| Similar rounded top-holding weights | The displayed rounded entries look similar | No other line, valuation or liability could have changed |
| No explanatory note on the page | The page does not provide a complete explanation | A reason can be filled in from a headline or social post |
What a portfolio disclosure is good for:
A portfolio disclosure can be a valuable reading document. It can help a reader identify the disclosed scheme, snapshot date, securities or asset classes shown, issuer or instrument labels, quantities or market values where shown, portfolio weights, and notes. It can also help check whether a claim about a particular disclosure period is actually visible in the document.
Use it as evidence for a sentence with a bounded scope: “This official disclosure reports this field for this identified scheme as of this stated date.” That is more reliable than converting a snapshot into a live dashboard or a prediction.
When inspecting a disclosure, keep the document’s own headings. Do not silently combine fields from different periods. A portfolio page may be updated or replaced; save the title, the printed “as on” date, and the access date. If a page does not show a date, do not assume the date from the file name, search result, or browser history.
What NAV history is good for
AMFI’s NAV tools are useful for locating a dated NAV record for the labeled scheme entry. [S2][S3] They are not a portfolio database, a return forecast, a tax calculator, or an explanation engine. A reader who wants a historical comparison still needs to make the period explicit and ensure that scheme, plan, and option labels match.
A later NAV can be a valid later observation even when a portfolio disclosure has not yet been updated for that later date. The honest conclusion is limited: the reader has two records with different reporting dates. It is not an invitation to attribute the difference to one company, one market event, or a manager action without scheme-specific evidence.
A document stack for a live question
For a current factual check, collect only the documents that answer separate parts of the question:
- an official NAV record for the date under discussion;
- the most recent official portfolio disclosure, with its printed “as on” date;
- the current factsheet if a summary metric is relevant
- the current SID, KIM, and addenda if the question concerns stated scheme terms; and
- the official source’s notes or contact route if the record itself leaves a field unclear.
Do not upload a statement, PAN, bank record, password, PIN, or one-time code to a comparison tool or a chat. Public document literacy does not require sharing a household’s private account information.
Use the interactive date-gap explainer
The accompanying NAV and portfolio date-gap explainer asks you to select the relationship between two dates and the type of record in hand. It teaches what to verify next; it does not calculate a return or produce a fund verdict. Enter no personal or scheme-specific account data. If dates or labels are missing, the correct result is “not enough evidence yet.”
Frequently asked questions
Ques: Does a portfolio disclosure show today’s NAV?
Ans : No. A portfolio disclosure and NAV record have their own stated dates. Read the date printed on each document rather than treating either as timeless.
Ques: Can I explain a NAV move by one top holding?
Ans : Not reliably from a top-holdings view alone. The view may be incomplete, dated, rounded, or missing notes. Use only an explanation supported by the relevant official record.
Ques: Is a factsheet the same as a portfolio disclosure?
Ans : No. A factsheet is usually a summary document for its stated period; a portfolio disclosure is a holdings-oriented record for its own snapshot date. Preserve both labels and dates.
Ques: What if the scheme name looks the same in two places?
Ans : Also match the plan, option, and date where shown. A shortened name is not always enough to prove that two figures describe the same record.
Ques: What if the portfolio document has no visible date?
Ans : Do not infer it. Record that the date is not shown and locate a dated official disclosure before interpreting it beside a NAV.
Ques: Does a later NAV prove the portfolio has changed?
Ans : It proves only that a NAV is displayed for a later date for the identified record. It does not, by itself, identify holdings, causes or the current portfolio.
Disclaimer:
This is written for educational and informational purposes only. Nothing here constitutes investment advice or a recommendation to buy or sell securities. All data is sourced from publicly available information. Investments in securities markets are subject to market risks — please read all offer documents carefully before investing.