NIC 663002 - Management of pension funds
NIC 663002 classifies management of pension funds as a final six-digit business activity under Section L and Division 66. Use it when this activity is the main source of revenue.
Source Verification for 663002
4 of 4 factors passing
- Verified in official source - Found in NIC_2025.xlsx official MoSPI release dataset.
- International crosswalk available - No official ISIC/NACE/CPC/ISCO correspondence table is bundled in this build input set.
- Migration from previous edition - Legacy migration candidates present from NIC 2008: 3.
- Complete hierarchy chain - All parent levels exist: Section > Division > Group > Class > Sub-class (5 levels).
- Official size/threshold documented - No official code-level size or threshold dataset is included in this source bundle.
- Trade or export crosswalk match - No official NIC-to-HS/export correspondence table is bundled in this source bundle.
- Legacy national crosswalk - Legacy link exists via NIC 2008 converter layer (3 linked legacy codes).
NIC 2008 -> NIC 2025 Mapping for 663002
NIC 2008 links are discovery matches from the local converter layer. Verify final migration decisions against official source documents.
What Management of pension funds Means Under NIC 2025
NIC 663002 is the final six-digit endpoint for Management of pension funds. It should be selected only when the enterprise's primary business activity matches this title more closely than 663001 Management of mutual funds, 663003 Activities of asset management including portfolio management, on a fee or contract basis, 663099 Other fund management activities n.e.c..
When to Choose 663002 Over Nearby Codes
Choose 663002 only when operations, invoices and revenue narrative align with Management of pension funds. If the activity also includes 663001 Management of mutual funds, 663003 Activities of asset management including portfolio management, on a fee or contract basis, 663099 Other fund management activities n.e.c., compare those pages before filing.
In this section
Common Questions About NIC 663002
Does NIC 663002 cover regulated professional or financial work?
Use the code that matches the service actually provided. Financial intermediation, insurance, real estate, legal, accounting, consulting, engineering, advertising and R&D are separated into different professional service families.
Can an advisory firm use NIC 663002 if it serves another industry?
Usually the firm's own service determines the NIC code, not the client's industry. For example, a consultant serving manufacturers is still a consulting or professional service business if advice is the revenue activity.
How do I verify that NIC 663002 is correct before filing?
Check the parent hierarchy, compare 663001 Management of mutual funds, 663003 Activities of asset management including portfolio management, on a fee or contract basis, 663099 Other fund management activities n.e.c., and confirm that the official title matches the main revenue activity. For regulated or filing-critical decisions, verify the source row in the MoSPI dataset.
What happens if I use the wrong NIC code in Udyam or MCA registration?
A wrong code can cause mismatched business descriptions, follow-up questions or later compliance cleanup. It is better to compare nearby codes before filing than to correct a weak classification later.
Is there a legacy NIC 2008 equivalent for NIC 663002?
Use the legacy converter only as a migration aid. Old NIC 2008 matches can suggest where to look, but NIC 2025 should remain the primary reference for new code selection.
Before you select NIC 663002
NIC 663002 should be selected only when the official title matches the main revenue-generating activity. If the business also trades, transports, processes, installs or supports the same product or service, compare nearby NIC pages before filing. This reduces the risk of choosing a code that describes the product being handled rather than the activity your enterprise actually performs.
Data Source and Verification Date
Source layer
Official NIC 2025 Excel and PDF from MoSPI.
Last verified
2026-04-21 from the generated NIC 2025 source layer used in this build.
Disclaimer
This is an independent reference tool. Verify filing-critical decisions in official sources.