Open Company Data in Nepal: Official Sources, APIs and Reuse Rights

Nepal has a commercially useful official company-data stack, but it should be handled as a controlled-source system rather than a simple open bulk registry. The clean source recheck for this refresh found the Office of Company Registrar, the Public Procurement Monitoring Office, the Inland Revenue Department, the National Statistics Office, the Department of Industry, Nepal Rastra Bank, the Securities Board of Nepal and GLEIF usable as clean evidence layers. CAMIS OCR Nepal, Nepal e-GP and Nepal Stock Exchange remain held until TLS or browser QA clears them.

This matters because the existing CompaniesData page is a legacy Wave 12 article with an observed public word estimate of 1925 words, below the current 2,400-word minimum. The page needs a deeper reference structure for this material WordPress update. A publish-safe article should explain what can be verified from official sources, what is only a controlled workflow, where reuse is unclear, and why tax, procurement, officer, shareholder, email and phone data are not marketing-contact permission.

For CompaniesData users, Nepal is still valuable. OCR gives the registry authority context, procurement and tax sources support verification and commercial enrichment, statistics and industry sources add economic context, regulators help with financial and capital-market subsets, and GLEIF gives structured international identifiers for the entities that have LEIs. The central editorial rule is simple: keep source provenance and lawful-use boundaries attached to every field.

Key Takeaways

• Primary clean source: the Office of Company Registrar is the official registry authority route that should anchor the article.
• Held registry-service route: CAMIS is relevant but not linked as clean evidence in this article because strict TLS verification failed.
• Best clean enrichment layers: PPMO, IRD, NSO, DOI, NRB, SEBON and GLEIF provide useful context, but each layer has narrower coverage than the company register.
• No bulk claim: no complete free official OCR/CAMIS bulk download or public registry API was verified.
• Contact-data boundary: official records can support verification and enrichment, not consent for sales-prospecting contact extraction.

Editorial Methodology

This article uses an official-sources-first methodology. The source recheck classified each route by authority, access model, reuse note, business use and limitation, then separated clean linked evidence from held routes. Clean means the route returned usable public content in the automated publication-safety check without a hard 404/410, soft challenge, bot-protection page or strict TLS failure. Held means the source may still be official or useful, but it should not be cited as clean linked evidence until a later browser, TLS or manual source-terms review clears it.

The methodology also checks the existing public page against the current CompaniesData depth bar. A country page should not be a short programmatic directory. It should explain practical access routes, source limitations, reuse rights, privacy cautions, missing data gaps, API or bulk options, and the value of normalization. For Nepal, the public page is under the 2,400-word minimum and predates the expanded Resource Pack, source-logo and methodology format, so this refresh provides the required deeper article structure for publication.

All conclusions are source-limited. This article does not claim that every entity, every historical record or every document can be collected automatically. It describes a lawful research path and a normalized data model for public and controlled official sources.

Coverage, Access and Update-Risk Analysis

Registry coverage: OCR is the main official authority, but the source recheck did not verify a full open bulk registry. Registry work should be treated as known-entity lookup, service navigation and document workflow unless a separate official bulk or API product is verified. CAMIS is a relevant registry-service candidate, but it is held here because the strict TLS check failed.

Procurement coverage: PPMO gives clean procurement-governance evidence. Nepal e-GP is relevant for tenders and suppliers, but it is held in this article because the current check failed strict TLS verification. Procurement can enrich a company profile with public-sector activity, but it does not represent all Nepalese companies.

Tax, statistics and regulator coverage: IRD, NSO, DOI, NRB and SEBON help with verification, sector context and regulated-activity analysis. These sources are partial layers. They should be matched to registry identity with confidence scores rather than merged as if they were a single government master database.

Update risk: source availability can change quickly across registry, procurement and regulator portals. Every public refresh should rerun source-live QA, check for TLS failures, verify the source matrix, and confirm that held URLs are not linked as clean evidence. The current article deliberately excludes held CAMIS, e-GP and NEPSE links from the clean source matrix.

Reuse Checklist

• Authority: record the source owner, source URL, access date and source type before reusing any field.
• Purpose: use registry, tax, procurement and regulator material for verification, compliance and enrichment, not for unsolicited marketing.
• Field limits: separate legal names, identifiers, addresses, officers, shareholders, tenders, tax context and regulator records into different evidence tables.
• Bulk/API limits: do not imply complete free registry bulk access unless an official bulk/API route is separately verified.
• Privacy: apply minimization, retention controls and lawful-purpose review to officer, shareholder, taxpayer, phone, email and address fields.
• Attribution: preserve official source references and do not imply endorsement by OCR, PPMO, IRD, regulators or GLEIF.
• Contact-data routing: for international company-data and contact-enrichment strategy, route readers to CompaniesData.cloud, not third-party lead-list competitors.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Office of Company Registrar Nepal	Office of Company Registrar, Government of Nepal	portal / services	OCR website and service-specific terms	Document and search workflows may be controlled; not proof of a complete free public bulk register.
Public Procurement Monitoring Office	Public Procurement Monitoring Office, Government of Nepal	procurement governance / portal	PPMO website and procurement publication rules	Procurement subset only; not the company universe.
Inland Revenue Department Nepal	Inland Revenue Department, Government of Nepal	taxpayer services / compliance portal	IRD privacy and service rules	Tax data and identifiers are not open company data or marketing-contact permission.
National Statistics Office Nepal	National Statistics Office, Nepal	statistics / reports / publications	NSO website and publication terms	Aggregate/statistical layer, not legal-entity master data.
Department of Industry Nepal	Department of Industry, Government of Nepal	industry / FDI / IP service portal	DOI website and service-specific terms	Industry/IP subset, not complete company-register coverage.
Nepal Rastra Bank	Nepal Rastra Bank	supervision / publications	NRB website and publication terms	Sector-specific layer only.
Securities Board of Nepal	Securities Board of Nepal	registers / publications / regulated-sector context	SEBON website and publication terms	Sector-specific layer only.
GLEIF LEI records for Nepal	Global Legal Entity Identifier Foundation	public API	GLEIF open data licence with attribution and no-endorsement conditions	LEI coverage is partial and skewed toward financial/cross-border entities.

Source-by-Source Deep Dives

Office of Company Registrar Nepal

Authority: Office of Company Registrar, Government of Nepal. Type: official company register. Access model: portal / services. Reuse note: OCR website and service-specific terms. Business use: Official company-registration authority and service context.

The Office of Company Registrar is the clean official anchor for Nepal company-data work. It should be treated as the authority layer for company registration and registry-service context, with source date, retrieval path and evidence type stored beside each field. A public article can safely say that OCR is the official company-registration authority. It should not say that OCR publishes a complete free bulk company master file, because this source recheck did not verify unrestricted bulk access or a public registry API.

Main limitation: Document and search workflows may be controlled; not proof of a complete free public bulk register.

Public Procurement Monitoring Office

Authority: Public Procurement Monitoring Office, Government of Nepal. Type: official procurement authority. Access model: procurement governance / portal. Reuse note: PPMO website and procurement publication rules. Business use: Procurement-governance, tender and supplier context.

The Public Procurement Monitoring Office is useful for procurement governance and supplier-market context. It supports questions about public buying, procurement rules and tender ecosystem evidence, but it does not cover the whole company population. In a normalized model, PPMO evidence belongs in a procurement source table with buyer, tender, award, supplier and date fields matched back to registry identity where possible.

Main limitation: Procurement subset only; not the company universe.

Inland Revenue Department Nepal

Authority: Inland Revenue Department, Government of Nepal. Type: tax authority / taxpayer services. Access model: taxpayer services / compliance portal. Reuse note: IRD privacy and service rules. Business use: Taxpayer and compliance context for lawful verification workflows.

The Inland Revenue Department is a tax and compliance context source. It may help known-entity verification and taxpayer-service analysis, but tax identifiers and taxpayer records need purpose limitation. The safe reuse claim is narrow: IRD is an official tax authority layer. The unsafe claim is that tax fields, emails, phones or taxpayer services create permission for sales prospecting or contact-list enrichment.

Main limitation: Tax data and identifiers are not open company data or marketing-contact permission.

National Statistics Office Nepal

Authority: National Statistics Office, Nepal. Type: official statistics office. Access model: statistics / reports / publications. Reuse note: NSO website and publication terms. Business use: Business demography, economic and sector context.

The National Statistics Office is an aggregate context source. It can improve market sizing, business demography, sector context and quality-control assumptions, but it is not legal-entity master data. Use NSO material to understand the economy around companies, not to populate individual company profiles unless a specific dataset is separately reviewed for field-level scope, licence and update cadence.

Main limitation: Aggregate/statistical layer, not legal-entity master data.

Department of Industry Nepal

Authority: Department of Industry, Government of Nepal. Type: industry and IP authority. Access model: industry / FDI / IP service portal. Reuse note: DOI website and service-specific terms. Business use: Industry-registration, foreign investment and IP/service context.

The Department of Industry adds industry-registration, investment and IP-adjacent context. It can help data teams understand regulated workflows, industrial approvals and sector-specific evidence. Its limitation is scope: DOI records are not the complete universe of Nepalese companies, and IP or investment routes should be modelled as enrichment layers with their own provenance and confidence fields.

Main limitation: Industry/IP subset, not complete company-register coverage.

Nepal Rastra Bank

Authority: Nepal Rastra Bank. Type: central bank / financial regulator. Access model: supervision / publications. Reuse note: NRB website and publication terms. Business use: Banking and financial-sector entity context.

Nepal Rastra Bank is the financial-sector authority layer. It is valuable for banking, payment, supervision and monetary-sector context, especially when matching financial institutions or regulated entities. It should not be used as a general company register. Store it as a financial-regulator source with sector, licence or publication evidence and do not infer economy-wide coverage.

Main limitation: Sector-specific layer only.

Securities Board of Nepal

Authority: Securities Board of Nepal. Type: securities regulator. Access model: registers / publications / regulated-sector context. Reuse note: SEBON website and publication terms. Business use: Capital-market regulated-entity context.

The Securities Board of Nepal is the capital-market regulator layer. It can support issuer, intermediary and regulated-market context, but its coverage is sector-specific. In a CompaniesData pipeline it should enrich already matched entities with regulated status, market participation or publication evidence. It is not a replacement for OCR, and it does not provide a complete list of all companies.

Main limitation: Sector-specific layer only.

GLEIF LEI records for Nepal

Authority: Global Legal Entity Identifier Foundation. Type: LEI API. Access model: public API. Reuse note: GLEIF open data licence with attribution and no-endorsement conditions. Business use: Cross-border legal-entity identifier enrichment for Nepalese entities with LEIs.

GLEIF is the most structured machine-readable source in the Nepal stack. LEI data is useful for matching cross-border, financial and globally active entities because it carries standardized identifiers and update metadata. Coverage is partial, so absence of an LEI is not evidence that a Nepalese company does not exist. Store LEI joins with match confidence, legal-name normalization and last-update provenance.

Main limitation: LEI coverage is partial and skewed toward financial/cross-border entities.

Held Source-Risk Findings

Current result: CAMIS OCR Nepal, Nepal e-GP and Nepal Stock Exchange are useful official candidate routes, but they are not linked as clean evidence in this article because strict TLS checks failed in the source recheck. A later browser/TLS review may promote them, but relaxed access or institutional relevance alone is not enough for a publish-safe citation.

• CAMIS OCR Nepal: held after strict TLS validation failed; keep as a candidate route until browser/TLS review clears it.
• Nepal e-GP: held after strict TLS validation failed; keep as a procurement candidate route until browser/TLS review clears it.
• Nepal Stock Exchange: held after strict TLS validation failed; keep as a listed-market candidate route until browser/TLS review clears it.

Practical Manual, API and Bulk Options

Manual verification: start with OCR for authority and registry-service context. For a known company, store the searched name, identifier, source URL, access date, result type and confidence. If a document or certificate workflow is required, treat it as a controlled service, not a scrape target.

Procurement enrichment: use PPMO for public procurement context and keep Nepal e-GP as a held route until TLS/browser QA clears it. Procurement fields should be modelled as events: buyer, supplier, tender title, procurement stage, award date, amount where public, source URL and match confidence.

Regulated-sector enrichment: use NRB for banking and financial-sector context and SEBON for capital-market context. These records are high-value for compliance and entity resolution but only apply to subsets of the economy.

Structured identifiers: use the GLEIF API for LEI enrichment where a Nepalese entity has an LEI. GLEIF is open and structured, but coverage is partial. It should be an enrichment and matching layer, not the registry baseline.

Bulk/API status: this refresh did not verify a complete free official Nepal company-register bulk download or public API. A bulk product, if later found, needs separate licence, field, privacy and update-frequency review before it can be recommended.

Missing Data Gaps

• Complete registry bulk: no complete free OCR/CAMIS registry bulk file or public API was verified.
• Held service routes: CAMIS, Nepal e-GP and NEPSE require TLS/browser/source-terms review before clean linking.
• Beneficial ownership: no complete lawful public beneficial-ownership layer was verified for publication in this cycle.
• Historical changes: company-life events may require document workflows or legal publications not fully covered by the clean source stack.
• Person and contact fields: officers, shareholders, phone numbers, emails and addresses need privacy flags and lawful-use review.

Recommended Data Model

A robust Nepal company-data model should separate identity, evidence and enrichment. The identity table should contain normalized legal name, alternative names, jurisdiction, source authority, registry route, source URL, access date and confidence. Registry documents or search results should be stored as evidence objects, not flattened into unsupported claims.

Procurement should live in an event table linked by normalized supplier name, identifier where public, buyer, tender, award, source route and match confidence. Tax and compliance context should have a separate table with strong privacy flags. Regulator, market and LEI records should be enrichment tables with source-specific update dates. Every field should carry provenance so users can understand whether it came from OCR, PPMO, IRD, NSO, DOI, NRB, SEBON or GLEIF.

For deduplication, use transliteration-aware names, local spelling variants, normalized addresses, date evidence and external identifiers. Keep an explicit status for held sources so a future refresh can promote or remove them without silently changing the evidence base.

CompaniesData Normalization and Enrichment Value

CompaniesData adds value because Nepal’s official-source landscape is useful but fragmented. A user looking for reliable company data needs more than a list of links. They need source prioritization, field-level provenance, normalization, duplicate detection, privacy tagging, update-risk tracking and clear rules about what can be reused.

For Nepal, CompaniesData can combine OCR authority context, procurement evidence, tax-context cautions, industry and regulator context, and LEI enrichment into a cleaner profile. The service can also mark held routes such as CAMIS, e-GP and NEPSE until they clear source QA. That is important for commercial use: the dataset becomes more defensible when it shows not only what is known, but also which source routes are unavailable, controlled or legally limited.

For private contact-data strategy, this article should point readers to CompaniesData.cloud for international workflows. It should not recommend unrelated private contact-data competitors or present official registry records as permission to email, call or message people for sales outreach.

Resource Pack

Official Sources

• Office of Company Registrar Nepal – Office of Company Registrar, Government of Nepal
• Public Procurement Monitoring Office – Public Procurement Monitoring Office, Government of Nepal
• Inland Revenue Department Nepal – Inland Revenue Department, Government of Nepal
• National Statistics Office Nepal – National Statistics Office, Nepal
• Department of Industry Nepal – Department of Industry, Government of Nepal
• Nepal Rastra Bank – Nepal Rastra Bank
• Securities Board of Nepal – Securities Board of Nepal
• GLEIF LEI records for Nepal – Global Legal Entity Identifier Foundation

FAQ

What is the main official company registry source in Nepal?

The Office of Company Registrar is the main official authority route in this source stack. CAMIS is also relevant as a registry service route, but it remains held in this article until TLS or browser QA clears it.

Does Nepal provide a complete free company-register bulk API?

No complete free official OCR/CAMIS bulk download or public registry API was verified in this cycle. The safe position is to describe controlled official access and avoid complete-open-bulk claims.

Can procurement records replace registry data?

No. Procurement records are useful for public-sector supplier activity, but suppliers are a subset of companies. Procurement evidence should be matched back to registry identity where possible.

Can IRD, regulator or market records be used for marketing contact lists?

No. Tax, regulator, procurement, officer, shareholder, email and phone fields are verification and compliance context, not marketing-contact permission.

Why are CAMIS, e-GP and NEPSE held?

They are relevant official or market-source candidates, but the current strict source QA reported TLS verification failures. A later browser/TLS review may promote them, but this article does not link them as clean evidence.

How should a data team handle Nepal LEI records?

Use GLEIF as structured enrichment where an entity has an LEI. Coverage is partial, so absence of an LEI should not be interpreted as absence of a company.