How to Import a CAS Statement and Track Mutual Funds Accurately
Your mutual funds are scattered across AMCs and apps. A Consolidated Account Statement (CAS) is the cleanest way to rebuild the full picture — then keep it current.
What a CAS statement is — and why importers care
A Consolidated Account Statement (CAS) is a PAN-level view of mutual fund holdings and transactions across AMCs, typically sourced through CAMS and KFintech infrastructure. For Indian investors, it is often the fastest way to answer: which schemes do I actually hold, in which folios, and at what unit balances?
Importing a CAS into a portfolio tracker turns a static PDF or statement into living holdings you can mark to market, combine with equity demats, and review for SIP discipline. Capitallytics does not buy or sell funds for you — import supports tracking and analytics only.
This guide explains how to obtain a CAS, what to check before import, how to fix common mismatches, and how to keep mutual fund tracking accurate after the first upload.
CAS vs AMC apps vs distributor dashboards
AMC apps show products from one fund house. Distributor or broker apps show what you bought through that channel. CAS aims to span folios linked to your PAN — including older investments you forgot after a job change or advisor switch.
None of these alone guarantee perfect performance math. Apps may emphasize absolute gains; CAS may lag a day; your tracker needs transaction dates for XIRR-style analysis. Use CAS as the holdings backbone, then refresh and reconcile.
| Source | Best for | Watch out for |
|---|---|---|
| CAS (CAMS/KFintech) | PAN-wide folio discovery | Timing lag; password-protected PDFs |
| AMC app | Scheme documents, corporate actions | Only that AMC's funds |
| Distributor / broker app | SIPs placed on that platform | Missing direct plans elsewhere |
| Portfolio tracker import | Unified marks + allocation | Needs clean mapping on first import |
How to obtain a CAS statement
Request a CAS through the official CAMS or KFintech CAS portals (or via your RTA email statement flow), using the PAN and email/mobile registered with folios. Choose a detailed statement if you need transactions, not only current holdings.
Ensure the email on file matches across folios where possible — orphaned older folios sometimes use an outdated address and will not appear until you update KYC with the AMC/RTA.
Save the statement securely. Treat it like a bank statement: it contains scheme names, folios, and personal identifiers. Share it only with tools you trust for import processing.
Prepare the file before you import
Confirm the statement period covers the folios you care about. If you recently opened a new SIP, a CAS generated before the allotment will omit it — wait for the next cycle or add that folio manually.
Prefer machine-readable exports when your tracker supports them; otherwise use the PDF workflow your platform documents. Unlock password-protected PDFs only in a private environment using the password format your RTA provides.
Skim for duplicates: the same folio should not be imported twice from CAS and a second CSV. Decide which pipeline is canonical for mutual funds going forward.
Import into Capitallytics and review the preview
In the portfolio tracker import flow, upload the CAS and review the parsed schemes, folios, quantities, and cost fields before confirming. This review step catches OCR or mapping errors early.
Check scheme names against what you expect — mergers and renames are common. Units should match your last known balance within normal NAV-day timing. Investigate large gaps before you accept the import.
AI-assisted parsing and insights, where available, are grounded in the document and your portfolio data. They are not autonomous portfolio managers and do not place SIP orders.
After import: NAVs, SIPs, and performance
Once holdings exist in your tracker, valuations should follow scheme NAVs as market data updates. Pair the live book with planning tools: the SIP calculator helps model future contributions; it does not replace your actual SIP mandates at the AMC or distributor.
For annualized performance on irregular SIPs and redemptions, see our guide on calculating XIRR for mutual funds automatically. Absolute gain alone often misranks SIP books.
Keep equity demat holdings separate in data model but combined in allocation views so a flexi-cap fund plus direct stocks do not hide overlapping sector bets.
Fixing common CAS import issues
Missing folio: KYC/email mismatch or statement generated too early. Update RTA records and re-request CAS.
Wrong units: pending units, recent redemption, or importing an outdated statement. Re-download and re-import, or adjust with a transaction sync if your workflow supports it.
Duplicate schemes: two imports of the same folio. Delete the duplicate row; keep a single source of truth.
Direct vs regular plans: labels differ; economic exposure may be similar but expense ratios differ — do not merge them blindly if you are comparing costs.
A simple ongoing mutual fund tracking routine
Monthly: refresh NAVs, confirm SIPs credited, glance at category weights versus your target allocation.
Quarterly: pull a fresh CAS or transaction export; reconcile tracker vs statement; archive the file for your records.
Annually: review overlapping funds (multiple large-cap schemes doing the same job), expense ratios, and whether SIPs still match goals — educational review, not a trade recommendation.
Related reading and next steps
For the broader habit of mutual fund portfolio tracking, read our mutual fund portfolio guide. For return methodology, use the XIRR article. For contribution planning, experiment with the SIP calculator, then execute changes only through your registered SIP platforms.
Capitallytics is educational analytics software. It does not provide personalized investment advice or execute mutual fund transactions.
Start Free Tracking
Unified multi-asset portfolio analytics, live NSE/BSE prices, and AI investment intelligence — free to start.
Read-Only Access
Strict read-only layer endpoints. Your capital cannot be touched or transferred.
Bank-Grade Encryption
AES-256 bit end-to-end encryption protecting your asset data.
Data Privacy Secured
Zero data selling. No ad-networks. Fully isolated rows.
Secure Auth
Industry-standard secure authentication protocols.