Reviewed by GFS Research Desk.
A mutual-fund factsheet can place NAV, a portfolio table, expense information, returns and a Riskometer on one page. They may not describe the same date. To read the page accurately, record the exact scheme, plan and option, then attach an “as-of” date and source note to each field. A page publication month is not automatically the valuation date of every number on it.
Read a mutual-fund factsheet as a bundle of dated records, not one live dashboard. Match each figure to its own heading, period and as-of date: NAV history, portfolio, return table, expense disclosure and Riskometer can use different reference dates. Compare a figure only with another record that has the same identity, measurement and relevant date. Mark an absent date as unresolved.
The reader problem: one PDF, several clocks
A factsheet is useful because it brings scheme information together. That convenience can also hide timing differences. A portfolio table may be a month-end snapshot. A NAV series may be displayed through a later business day. A return column may use a defined period ending on its own date. An expense figure can be labelled with a different effective or reporting date. A Riskometer is a dated label, rather than a promise about the next market move.
If those records are silently treated as simultaneous, a reader can create a comparison that the documents do not support. For example, a dated portfolio snapshot cannot explain every later NAV movement. A NAV displayed after month-end does not prove the holdings table was updated on that day. A monthly document cover date does not repair a missing date inside a table.
The regulatory and scheme-document framework is the relevant primary reference, while a current Scheme Information Document (SID), Key Information Memorandum (KIM), addenda and official AMC disclosure remain the scheme-specific source. AMFI’s NAV History and Other Data pages are official industry routes for published data. This draft is dated 1 August 2026 and intentionally states no live NAV, expense ratio, scheme return, Riskometer value or portfolio weight. Check the current official record for a live question.
Start with a factsheet identity card
Before interpreting any percentage, create a small record. The purpose is evidence hygiene, not a scheme score.
| Field | Record exactly | Why it matters |
|---|---|---|
| Scheme identity | Full scheme name, plan and option | Similar names can describe different data series |
| Document identity | Factsheet title, file name, displayed month and access date | A file can be replaced or archived |
| Field label | The heading exactly as printed | “As on” can attach to one table, not the whole page |
| Reference date | Date beside the relevant NAV, portfolio, return, expense or label | Stops a past observation becoming “today” |
| Measurement | NAV, percentage of net assets, return method, expense disclosure or risk label | A percentage needs a definition |
| Source path | Official AMC document or official industry page | A search result is not the underlying record |
| Unresolved note | Missing date, unclear plan, absent footnote or version conflict | A blank is not a zero or an assumption |
Keep the scheme, plan and option in every row. A direct-plan figure and a regular-plan figure can be different series; a growth option and another option can also have different labels or records. Do not use a shortened app name to bridge an identity gap.
A five-date map for a typical factsheet
1. Document publication or cover date
The cover may say a month, issue date or “factsheet” period. That field identifies the document edition. It does not establish that every table was calculated on the cover date. Read it as a container label first. Then look inside each section for a stated “as on,” “for the period ended,” “effective from,” or methodology note.
If a page only displays a month, record the month exactly rather than turning it into the last calendar day. A fund’s reporting convention and business-day treatment may matter. The current document, including any addendum, is the correct place to resolve that detail.
2. NAV observation date
NAV is a per-unit value published for a stated date. A NAV History record can help identify a dated value after the scheme, plan, option and date are matched. It is not a portfolio list and it does not disclose every reason a value changed.
Suppose a hypothetical factsheet contains a NAV line marked 31 July and a portfolio table marked 30 June. The disciplined statement is that the two sections describe different reference dates. It is not valid to claim that the 30 June holdings explain the entire movement to 31 July. Market movement, subscriptions, redemptions, accruals, expenses, valuation conventions and later transactions are not resolved by those two labels alone.
3. Portfolio disclosure date
A portfolio disclosure is a snapshot. Its “as on” date belongs next to every observation drawn from its holdings, sector, maturity, cash or percentage-of-net-assets tables. The portfolio date and the publication date can differ. A later download date also does not make the underlying snapshot current.
Read the column heading and notes before adding weights. “Percentage of net assets,” market value and units are not interchangeable measures. A top-holdings panel may exclude cash, derivatives, receivables, liabilities or other positions presented elsewhere. If the totals cannot be reconciled from the file and its notes, write “not reconciled”; do not invent the missing balance.
4. Return-period end date
A performance table has its own data recipe: scheme identity, start and end dates, period length, method and any benchmark label. A one-year figure may be annualised, while a short-period figure may be absolute; the table’s methodology decides. The return period end date does not turn an older portfolio disclosure into a current holdings record.
Do not replace the stated end date with a newer NAV because it seems more useful. That creates a new calculation rather than reproducing the published number. Likewise, a result in a factsheet cannot establish a reader’s cash-flow-based experience without the reader’s dated transaction record.
5. Expense disclosure and Riskometer dates
Expense information and the Riskometer must be read as separately labelled disclosures. Preserve the exact label, document location and date. Do not infer an expense figure from a return difference, and do not describe a Riskometer level as “safe,” “unsafe,” or a forecast. The label communicates risk under its applicable framework; it cannot determine a household’s capacity for loss, tax position or holding-period outcome.
When a factsheet does not state the date or basis beside one of these fields, the honest output is limited: “shown in this document, reference date not located.” The next document to consult is the current SID, KIM, factsheet notes, applicable addendum or official AMC disclosure—not a generic online summary.
A comparison only becomes valid after alignment
Use this test before putting two figures side by side:
- Identity: Are the AMC, scheme, plan and option the same?
- Field: Are both values actually the same measurement?
- Date: Do the records use the same as-of date or clearly stated period end?
- Method: Does the source explain the calculation, denominator or label?
- Source: Is each figure traceable to an official file or official data route?
- Limit: What does the pair still fail to establish?
A comparison can be descriptive without becoming a verdict. For example: “The official document reports a portfolio snapshot as of one date and a NAV as of another date.” It cannot become: “therefore this portfolio caused the later NAV move,” “therefore the scheme will behave similarly,” or “therefore a reader should take an action.”
A safe three-column working sheet
A household can maintain a private, minimal sheet without copying credentials or account details:
| Document field | Dated evidence | Boundary |
|---|---|---|
| Portfolio percentage | Official table heading, as-of date and footnote | Does not establish current holdings or a future trade |
| NAV | Official NAV date and exact plan/option | Does not establish personal gain, tax or an applicable transaction NAV |
| Return | Period end, method and benchmark label | Does not predict a future return or reproduce personal cash flows |
| Expense disclosure | Label, source and stated date/basis | Does not alone calculate a personal cost or outcome |
| Riskometer | Exact level, source and displayed date | Does not assess personal suitability |
Use masked folio references, if any are needed at all. Keep OTPs, passwords, bank information, identity documents and transaction instructions outside a comparison worksheet. This article does not ask for them.
What to do when dates genuinely conflict
First, preserve both records. Note the document names, access date, exact headings and the apparent conflict. Next, look for an addendum, footnote, methodology page or newer official version. Do not overwrite an older file; it may establish what was disclosed at the time.
If the conflict concerns a real transaction, use the official AMC, registrar or service route with the dated records. Ask a narrow factual question, such as which document version applies or what the particular field’s as-of date means. A factsheet reader cannot adjudicate an account record, confirm a transaction result, or replace the applicable scheme documents.
Limits of the factsheet-date map
The map improves interpretation, not prediction. It cannot tell which scheme will perform better, whether a reader should transact, whether an expense figure is applicable to a particular holding, or whether a current portfolio has changed since its disclosure date. It cannot calculate taxes, resolve an account discrepancy or establish eligibility for any facility.
Use the map to make uncertainty visible. A dated, well-labelled observation is more useful than a fresh-looking number whose identity, method or time reference is unknown.
FAQs
Ques : Does a factsheet month mean every number is from the last day of that month?
Ans : No. Treat the month as a document label unless each section states its own reference date. Check headings and notes for the portfolio, NAV, return, expense and Riskometer fields.
Ques : Can I use today’s NAV with last month’s portfolio table?
Ans : You can record both dates, but they describe different observations. The pair does not establish why the NAV changed after the portfolio snapshot.
Ques : Is a portfolio publication date the same as the portfolio date?
Ans : Not necessarily. Preserve both when shown. The portfolio “as on” date is the date for the disclosed snapshot; publication identifies when the file was released.
Ques : Does a Riskometer label predict the next return?
Ans : No. It is a risk communication label under the applicable framework, not a return forecast or a personal conclusion.
Ques : Can an expense figure be compared across plans without more checks?
Ans : Only after matching the exact scheme identity, plan, option, source, label and stated date or basis. Do not infer a personal cost from a headline figure.
Ques : What if the factsheet does not state an as-of date?
Ans : Mark the field unresolved, retain the document edition and consult the current official scheme document, addendum or official service route for clarification.
Related GFS reading and document routes
- GFS Insights: https://gayatrifin.com/insights
- Mutual Fund Document Stack Reading: https://gayatrifin.com/insights/mutual-fund-document-stack-reading
- GFS contact route for general service enquiries: https://gayatrifin.com/contact
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.