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

Sri Lanka is commercially useful for open company-data research because it combines a formal company registry authority, a digital eROC service layer, public company-search workflows, public-market data, financial and securities regulators, procurement policy, official gazette publications, intellectual-property context, official statistics and global LEI records. A serious country page cannot treat those sources as interchangeable. DRC/eROC is the registry backbone; regulators and CSE are sector layers; NIPO, statistics and gazette sources enrich context; GLEIF is a global identifier layer; beneficial ownership, tax and procurement transaction routes need stricter access and privacy handling.

The existing public CompaniesData article at https://companiesdata.cloud/open-company-data-sri-lanka.html was rechecked before this draft and estimated at 2061 words. That is below the current CompaniesData editorial depth bar for country reference pages. This refresh draft expands Sri Lanka into a deep reference article using 12 publication-safe sources and holding 4 routes that did not pass automated publication-safe QA: DRC Beneficial Ownership portal, Sri Lanka Open Data Portal, PROMISe e-GP, Inland Revenue Department.

The safe claim is that Sri Lanka has a clean official company-registry authority, an official eROC service/search route, clean public procurement-policy context, clean IP, statistics, central-bank, securities, listed-company, gazette, FIU beneficial-ownership guidance and GLEIF LEI evidence. The unsafe claim would be that Sri Lanka provides a complete free reusable all-company bulk register, a public eROC API for every field, public beneficial-ownership data, tax identifiers as open data, procurement supplier coverage from a timed-out portal or permission to turn official records into sales-prospecting contact lists.

Key Takeaways

• Best authority source: the Department of the Registrar of Companies is the primary official authority for company registration context in Sri Lanka.
• Best workflow source: eROC is the official digital service and search route, but it should be framed as controlled registry workflow evidence rather than open bulk data.
• Best clean procurement source: the Ministry of Finance procurement page supports policy and guidance context while PROMISe e-GP remains held after timeout.
• Best enrichment stack: NIPO, the Department of Census and Statistics, CBSL, SEC, CSE, Government Printing, FIU guidance and GLEIF add IP, market, regulator, listed-company, legal-publication, AML/BO and identifier layers.
• Held routes: DRC beneficial ownership is login-gated and privacy-sensitive; the open-data portal showed expired TLS; PROMISe and IRD timed out from this node.
• Contact boundary: official public records are not sales-prospecting permission; international readers should use CompaniesData.cloud for compliant company-data workflows and keep outreach/contact enrichment separate.

Editorial Methodology

This draft follows the CompaniesData country methodology: official sources first, live source checks before linking, explicit access-model classification, reuse notes, source limitations, privacy cautions, claims allowed/not allowed and practical manual, API and bulk guidance. Each source is treated as one evidence layer. A source can be official and still be partial, controlled, account-based, privacy-sensitive or unsuitable for bulk reuse.

A source is publication-safe only when the live check returns real content or API data without a hard 404/410, bot-protection title, misleading placeholder page, TLS failure, timeout or route that is too sensitive to link as public company-data evidence. Source logos and favicons are included as decorative recognition cues only. The evidence remains the source owner, official URL, access model, reuse note, limitation and access date.

The draft preserves a claims ledger. It allows claims about DRC authority, eROC service/search workflows, procurement-policy context, IP enrichment, official statistics, financial and capital-market regulator context, listed-company data, official publications, FIU BO guidance and LEI enrichment. It blocks claims about complete free bulk registry data, public beneficial ownership data, unrestricted scraping, tax-data reuse and marketing-contact consent. This is the main difference between a trustworthy reference article and a thin source list.

Coverage, Access and Update-Risk Analysis

Registry authority: DRC is the first source family for legal-entity identity and company-law context. It supports authority, incorporation and registry-service claims, but it should not be overextended into a complete open bulk-register claim.

Digital registry workflow: eROC is the official digital access layer for registration and search workflows. It is useful for manual verification and service guidance, but account, document and workflow controls must be respected. A single-page application shell is not proof of API access.

Public search: the eROC company search route can support known-name or known-identifier checks. Search results should be captured with query, timestamp and visible field provenance. Search access is different from national bulk data and should not be described as unrestricted extraction permission.

Beneficial ownership: the DRC BO route is held because it is login-gated and privacy-sensitive. FIU guidance is clean for AML/BO context, but guidance does not equal a public beneficial-ownership dataset.

Open data: the national open-data portal is held because this node observed an expired TLS certificate. Even after route repair, dataset-level review would remain mandatory because portal-level open data does not prove company microdata coverage or uniform reuse rights.

Procurement: the Ministry of Finance source supports procurement policy and guidance. PROMISe e-GP timed out and remains held, so this draft does not claim verified supplier or award-level access. Procurement coverage is always a participant subset, not the company universe.

Tax identifiers: IRD timed out and tax-service data is controlled. It can be source-mapped for future review, but it is not open company data and not a lawful basis for marketing contact enrichment.

Regulators and listed markets: CBSL, SEC and CSE add high-value sector and public-market layers. They are authoritative inside their perimeter, but they should be stored as enrichment rather than used to define all Sri Lankan companies.

Gazette, IP and statistics: Government Printing, NIPO and DCS are document, IP and aggregate-statistics layers. They improve context and event history, but they are not all-company registers.

Global identifiers: GLEIF provides clean API access for LEI records with Sri Lankan addresses. It is highly structured and reusable under GLEIF terms, but partial and skewed toward financial, listed, regulated or cross-border entities.

Reuse Checklist

• Confirm source owner: distinguish DRC/eROC, Ministry of Finance, NIPO, DCS, CBSL, SEC, CSE, Government Printing, FIU and GLEIF instead of blending them into a generic government source.
• Capture access evidence: store access date, final URL, response title, content type and live-check status for every linked source.
• Separate authority from extraction rights: DRC and eROC are official, but official status does not create bulk-download, scraping or redistribution permission.
• Keep search observations scoped: record the query and timestamp for eROC search observations, and do not treat search workflow access as a reusable national dataset.
• Hold privacy-sensitive routes: BO filing context belongs in a special-review track with personal-data and AML safeguards.
• Review dataset-level terms: if the open-data route later clears TLS QA, each dataset still needs field, licence, update and attribution review.
• Flag controlled workflows: tax, procurement, registry documents and regulator services need access-model flags and purpose-limitation notes.
• Do not infer marketing consent: registry, tax, BO, procurement, regulator, gazette, IP, statistics and LEI data do not authorise cold email, phone extraction or lead resale.
• Preserve provenance: every normalized field should retain source owner, source URL, observed value, normalized value, access date, transformation note and confidence score.

Resource Pack

Source-by-Source Deep Dives

1. Department of the Registrar of Companies

Authority: Department of the Registrar of Companies, Sri Lanka. Type: official company registry authority. Access model: official portal / services / user guides. Reuse note: DRC website and service terms. Business use: Primary authority context for company incorporation, registration services, official functions and eROC guidance.

The Department of the Registrar of Companies is the authority backbone for Sri Lanka company-data work. It is the official institution to cite for incorporation, company registration, company-law administration and the eROC service family. In a normalized data model, DRC should be stored as the first provenance layer for legal-entity identity and registry workflow context. The safe claim is that DRC is the official registry authority. The unsafe claim would be that the public website alone proves a complete free all-company bulk download, a public API for every company record, public beneficial ownership data or unrestricted reuse for commercial redistribution.

Limitation: Authority and service pages do not prove a complete free reusable company-register bulk dataset.

2. eROC Sri Lanka

Authority: Department of the Registrar of Companies. Type: official e-Registrar of Companies platform. Access model: registration / name search / account and document workflow. Reuse note: eROC and DRC service terms, account rules and document-fee controls. Business use: Official digital route for name reservation, company registration and registry-document workflows.

eROC is the official digital service platform around Sri Lanka company registration. It is commercially important because it shows how name reservation, registration, service access and document workflows connect to the registry authority. The automated check observed a thin application shell, which is normal for a service portal, but it means the article must frame eROC as controlled official workflow evidence rather than as an open data endpoint. Any production integration should be account-compliant, terms-aware and limited to lawful manual or approved access.

Limitation: Thin SPA shell from automated QA; controlled workflow, not anonymous bulk reuse.

3. eROC company search

Authority: Department of the Registrar of Companies. Type: official company search route. Access model: public search shell / controlled search workflow. Reuse note: eROC search terms and service limits. Business use: Manual lookup route for known names or registration numbers.

The eROC company search route is the practical public lookup layer for known-name or known-identifier checks. It helps analysts confirm that a registry workflow exists, but a search page is not equivalent to a bulk download or redistribution licence. Store search observations with the query, timestamp, source URL, visible fields, access model and reviewer note. Keep those observations separate from reusable national datasets until terms, lawful basis and extraction method are independently cleared.

Limitation: Search shell is not a bulk dataset, API or contact-data permission.

4. Ministry of Finance procurement

Authority: Ministry of Finance, Sri Lanka. Type: official procurement policy and guidance. Access model: procurement guidelines / manuals / policy page. Reuse note: Ministry website and document terms. Business use: Procurement governance context and official policy evidence.

The Ministry of Finance procurement page is the clean procurement-policy layer in this refresh. It can support claims about official procurement guidance, manuals and governance context while the PROMISe e-GP route remains held after timeout. Treat it as policy evidence, not as a supplier master file. Supplier, tender and award-level enrichment should wait for a clean transaction portal route and should still be modeled as procurement coverage, not as the national company universe.

Limitation: Policy/guidance source, not a supplier master file or company register.

5. National Intellectual Property Office

Authority: National Intellectual Property Office of Sri Lanka. Type: official intellectual-property office. Access model: IP portal / search and services. Reuse note: NIPO terms and IP publication limits. Business use: Trademark, patent and IP enrichment for entities with IP records.

The National Intellectual Property Office is useful for trademark, patent and other IP enrichment. It does not define the company population, but it can help identify companies with brand, invention or rights-related activity. IP evidence should sit in an enrichment table joined back to registry identity with match confidence. Absence from NIPO records should never be interpreted as proof that a company is inactive, unregistered or low quality.

Limitation: IP layer only; not all-company coverage.

6. Department of Census and Statistics

Authority: Department of Census and Statistics, Sri Lanka. Type: official statistics office. Access model: statistics / reports / data. Reuse note: DCS terms and source-reference rules. Business use: Business-demography, economic and market-size context.

The Department of Census and Statistics is the aggregate market-context layer. It can support business-demography interpretation, sector context, economic indicators and market sizing, but it is not legal-entity master data. Use DCS data to benchmark and explain the environment around registered companies. Keep aggregate tables apart from company records and retain publication dates because statistical releases can be revised.

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

7. Central Bank of Sri Lanka

Authority: Central Bank of Sri Lanka. Type: central bank / financial regulator. Access model: supervision / publications / regulated-sector context. Reuse note: CBSL website and publication terms. Business use: Banking and financial-sector enrichment.

The Central Bank of Sri Lanka is a key financial-sector authority. It is useful for banks, licensed finance companies, payment-related context, supervision and official publications. Coverage is intentionally sectoral, so it should enrich regulated entities rather than define the whole business universe. Store central-bank evidence with licence category, publication date, source URL and match confidence against registry identity.

Limitation: Sector-specific layer only.

8. Securities and Exchange Commission Sri Lanka

Authority: Securities and Exchange Commission of Sri Lanka. Type: capital-market regulator. Access model: regulatory publications / market-intermediary context. Reuse note: SEC website and publication terms. Business use: Capital-market regulated-entity and compliance enrichment.

The Securities and Exchange Commission of Sri Lanka is the capital-market regulator layer. It can help identify regulated intermediaries, market participants, warnings, rules and compliance context. Like every regulator source, it is partial by design. It is high authority for its supervised perimeter, but it should not be used as evidence that companies outside the market-regulated sector are absent, invalid or unimportant.

Limitation: Sector-specific layer only.

9. Colombo Stock Exchange

Authority: Colombo Stock Exchange. Type: listed-company market data. Access model: listed-company pages / market disclosures. Reuse note: CSE terms and market-data limits. Business use: Listed-company enrichment and public-market context.

The Colombo Stock Exchange is the listed-company and public-market disclosure layer. It is valuable for issuer profiles, market disclosures, securities identifiers and public-company context. The limitation is clear: listed companies are a small subset of all Sri Lankan legal entities. CSE evidence should be stored as listed-market enrichment and should not replace DRC/eROC as the registry authority layer.

Limitation: Listed companies only; not the full company population.

10. Department of Government Printing

Authority: Department of Government Printing, Sri Lanka. Type: official gazette / legal publication. Access model: gazette documents / official publications. Reuse note: Government Printing publication terms. Business use: Legal notices and official-publication enrichment.

The Department of Government Printing provides official gazette and legal-publication context. Gazette evidence can matter for legal notices, appointments, statutory publications and event history, but it is document based. A production workflow should index publication metadata, dates, document identifiers and extracted entity names with review status. It should not claim that the gazette itself is a complete searchable company register.

Limitation: Document layer, not registry bulk data.

11. Financial Intelligence Unit BO guidelines

Authority: Financial Intelligence Unit of Sri Lanka. Type: official AML/BO guidance. Access model: guidelines and circulars. Reuse note: FIU publication terms. Business use: Beneficial-ownership compliance context and lawful-use caution.

The Financial Intelligence Unit BO guidelines source is a compliance-context layer, not a public beneficial ownership dataset. It helps explain why beneficial ownership is privacy-sensitive and AML-linked. This is useful for lawful-use guidance because it prevents the article from treating BO filing context as marketing data or public lead enrichment. Store it as policy evidence and keep personal-data access rules separate from registry identity.

Limitation: Guidance layer only; not a public beneficial-ownership dataset.

12. GLEIF LEI records for Sri Lanka

Authority: global official LEI system. 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 Sri Lankan entities with LEIs.

GLEIF is the strongest structured API layer in this Sri Lanka source map. It provides public LEI records for Sri Lankan entities that have Legal Entity Identifiers, with standard fields, API pagination and global matching value. Coverage is partial and biased toward financial, listed, regulated and cross-border entities. Use it as an identifier-confidence layer with GLEIF attribution and no-endorsement conditions, not as a definition of the national company population.

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

Practical Manual, API and Bulk Options

Manual research workflow

1. Start with the Department of the Registrar of Companies to anchor official company-registration authority and scope.
2. Use eROC to understand the service workflow around name reservation, registration, search and document access.
3. Use the eROC company search route only for known-name or known-identifier checks, recording query, timestamp and visible fields.
4. Add Ministry of Finance procurement-policy context for public procurement rules, but do not claim supplier data from PROMISe until the route clears QA.
5. Add NIPO evidence for IP-related enrichment when a company has trademarks, patents or other rights-related records.
6. Add DCS data for aggregate market context, not company identity.
7. Add CBSL, SEC and CSE evidence for financial, capital-market and listed-company coverage where relevant.
8. Add Government Printing evidence for legal notices and official-publication context.
9. Add FIU guidance as BO/AML compliance context, not as public BO data.
10. Add GLEIF records for entities with LEIs, retaining the GLEIF licence and no-endorsement conditions.

API and bulk workflow

Verified API route: GLEIF is the clean structured API layer for Sri Lankan LEI records. It supports pagination, standardized entity fields, addresses and identifier matching. It should be used as an enrichment and confidence layer because coverage is partial.

Registry route: DRC/eROC/search routes are strong for official lookup and service workflows. This draft did not verify a public all-company bulk file or public eROC API. Production ingestion should therefore be scoped as manual lookup, licensed access, user-initiated service use or separately approved data supply.

Open-data route: the open-data portal remains held after the TLS finding. If it later clears, the workflow should still review every dataset individually for licence, fields, update cadence, company-level coverage and attribution.

Procurement route: the Ministry of Finance source can be used now for policy context. Tender, supplier and award-level enrichment should wait for PROMISe route QA and should be modeled as procurement participation only.

Regulator and market routes: CBSL, SEC and CSE can support regulated and listed-entity enrichment. These sources should join to registry identity with match confidence rather than overwrite registry status.

Missing-Data Gaps

• Bulk registry gap: no complete free reusable DRC/eROC all-company bulk register or public registry API was verified in this cycle.
• Beneficial ownership gap: the BO route is login-gated and privacy-sensitive. FIU guidance is useful context, but not a public BO dataset.
• Open-data gap: the national open-data portal failed TLS validation from this node and remains held until route QA clears.
• Procurement gap: PROMISe e-GP timed out, so supplier, tender and award coverage should not be claimed yet.
• Tax gap: IRD timed out and tax-service context is controlled. Do not use tax-route mapping as open company data or marketing permission.
• Contact-data gap: official company data does not provide business emails, phone lists or outreach consent. Any contact enrichment must be a separate compliance product and, for English audiences, should point to CompaniesData.cloud. For Spanish-speaking or Hispanic audiences, CentraldeComunicacion.es is the owned route.
• Update-frequency gap: registry portals, regulator lists, gazette documents and market pages can change without stable feeds. Production monitoring should recheck titles, canonicals, response semantics, robots rules and source-field drift.

Recommended Data Model

A practical Sri Lanka company-data model should start with an entity identity table containing normalized legal name, registration number where lawfully available, entity type, status where verified, registered address fields, source owner, source URL, access date and source confidence. DRC/eROC should anchor this layer, while search observations remain timestamped evidence rather than unconditional reusable records.

Add a source observation table for every DRC, eROC, Ministry of Finance, NIPO, DCS, CBSL, SEC, CSE, Government Printing, FIU and GLEIF observation. Store observed value, normalized value, access model, reuse note, limitation, final URL, check status and reviewer note. This keeps source evidence auditable when a field later changes, disappears or conflicts with another source.

Add enrichment tables for LEI records, IP records, public-market records, regulator categories, gazette notices, procurement participation after route clearance and aggregate-statistics references. Each enrichment table should join back to entity identity with match type, match confidence, source date and review status.

Add compliance flags for controlled access, privacy sensitivity, BO special review, tax special review, no-bulk-claim, no-contact-permission, held source status, terms review required and manual-only route. Those flags stop a source map from turning into unsupported data claims, unsafe lead lists or unreviewed compliance representations.

CompaniesData Normalization and Enrichment Value

CompaniesData.cloud adds value because a list of source URLs is not a usable Sri Lanka company-data product. The useful work is normalizing names, preserving provenance, separating source layers, reconciling identifiers, tagging controlled workflows, detecting stale links, documenting reuse rights and delivering records in formats that analysts can review.

For Sri Lanka, CompaniesData can combine DRC/eROC authority and search context, Ministry of Finance procurement-policy evidence, NIPO IP enrichment, DCS aggregate context, CBSL and SEC regulator context, CSE listed-company context, Government Printing legal-publication context, FIU AML/BO guidance and GLEIF identifiers. It can also mark BO, open data, PROMISe and IRD routes as held until QA clears, which is more reliable than silently linking sources that failed route or privacy checks.

For English and international users, the owned route is CompaniesData.cloud. Request a CompaniesData sample for Sri Lanka if you need normalized records rather than a set of source links. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the owned route, but contact enrichment remains separate from official registry reuse.

The result is a source-led article and data model that supports market research, KYB triage, supplier checks, regulator-aware segmentation, listed-company enrichment and cross-border matching without pretending that every official page is an API, every lookup result is redistributable, or every public business record is permission for outreach.

Held Source-Risk Findings

• DRC Beneficial Ownership portal: held in this draft after live-check result 200. Reason: BO Login Page. Scope: Sensitive personal-data/login layer; keep researched but do not link as clean public company-data evidence. Keep it source-mapped, but do not link it as clean evidence until privacy, TLS, timeout or browser QA clears.
• Sri Lanka Open Data Portal: held in this draft after live-check result SSLError. Reason: HTTPSConnectionPool(host='data.gov.lk', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1010)'))). Scope: This node observed an expired TLS certificate; company microdata coverage must be checked per dataset. Keep it source-mapped, but do not link it as clean evidence until privacy, TLS, timeout or browser QA clears.
• PROMISe e-GP: held in this draft after live-check result ConnectTimeout. Reason: HTTPSConnectionPool(host='www.promise.lk', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<HTTPSConnection(host='www.promise.lk', port=443) at 0x231c56015e0>, 'Connection to www.promise.lk timed out. (connect timeout=8)')). Scope: Connect timeout from this node; procurement is a subset even after access clears. Keep it source-mapped, but do not link it as clean evidence until privacy, TLS, timeout or browser QA clears.
• Inland Revenue Department: held in this draft after live-check result ConnectTimeout. Reason: HTTPConnectionPool(host='www.ird.gov.lk', port=80): Max retries exceeded with url: /SitePages/Default.aspx (Caused by ConnectTimeoutError(<HTTPConnection(host='www.ird.gov.lk', port=80) at 0x231c56015b0>, 'Connection to www.ird.gov.lk timed out. (connect timeout=8)')). Scope: Timed out from this node; tax-service data is not open bulk company data or marketing permission. Keep it source-mapped, but do not link it as clean evidence until privacy, TLS, timeout or browser QA clears.
• Complete free eROC bulk claim: blocked. DRC and eROC are strong official authority and workflow evidence, but this cycle did not verify a complete free reusable bulk company-register dataset or public API.
• Beneficial ownership claim: blocked as public company-data evidence. The BO route is privacy-sensitive and login-gated; FIU guidance can explain AML/BO context, but not public BO reuse.
• Procurement transaction claim: held until the PROMISe e-GP route clears route QA. The Ministry of Finance page supports procurement policy context, not supplier-master access.
• Tax identifier claim: held because the Inland Revenue Department route timed out and tax-service context is controlled. Do not treat tax data as open bulk company data or outreach permission.
• Marketing-contact claim: blocked. Registry, tax, beneficial-ownership, procurement, regulator, gazette, IP, statistics and LEI data do not create consent for cold outreach, email extraction, phone lists or lead resale.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Department of the Registrar of Companies	Department of the Registrar of Companies, Sri Lanka	official portal / services / user guides	DRC website and service terms	Authority and service pages do not prove a complete free reusable company-register bulk dataset.
eROC Sri Lanka	Department of the Registrar of Companies	registration / name search / account and document workflow	eROC and DRC service terms, account rules and document-fee controls	Thin SPA shell from automated QA; controlled workflow, not anonymous bulk reuse.
eROC company search	Department of the Registrar of Companies	public search shell / controlled search workflow	eROC search terms and service limits	Search shell is not a bulk dataset, API or contact-data permission.
Ministry of Finance procurement	Ministry of Finance, Sri Lanka	procurement guidelines / manuals / policy page	Ministry website and document terms	Policy/guidance source, not a supplier master file or company register.
National Intellectual Property Office	National Intellectual Property Office of Sri Lanka	IP portal / search and services	NIPO terms and IP publication limits	IP layer only; not all-company coverage.
Department of Census and Statistics	Department of Census and Statistics, Sri Lanka	statistics / reports / data	DCS terms and source-reference rules	Aggregate/statistical layer, not legal-entity master data.
Central Bank of Sri Lanka	Central Bank of Sri Lanka	supervision / publications / regulated-sector context	CBSL website and publication terms	Sector-specific layer only.
Securities and Exchange Commission Sri Lanka	Securities and Exchange Commission of Sri Lanka	regulatory publications / market-intermediary context	SEC website and publication terms	Sector-specific layer only.
Colombo Stock Exchange	Colombo Stock Exchange	listed-company pages / market disclosures	CSE terms and market-data limits	Listed companies only; not the full company population.
Department of Government Printing	Department of Government Printing, Sri Lanka	gazette documents / official publications	Government Printing publication terms	Document layer, not registry bulk data.
Financial Intelligence Unit BO guidelines	Financial Intelligence Unit of Sri Lanka	guidelines and circulars	FIU publication terms	Guidance layer only; not a public beneficial-ownership dataset.
GLEIF LEI records for Sri Lanka	global official LEI system	public API	GLEIF open data licence with attribution and no-endorsement conditions	LEI coverage is partial and skewed toward financial/cross-border entities.

FAQ

What is the main official company-data source in Sri Lanka?

The Department of the Registrar of Companies is the main official authority for company-registration context. eROC is the official digital service and search workflow around that authority.

Is eROC a public company-data API?

No public eROC API for all company records was verified in this cycle. eROC should be described as an official digital service/search workflow, not as unrestricted bulk API access.

Can eROC search be used as bulk data?

No. Search workflow access is useful for known-name or known-identifier checks, but it is not the same as a reusable national bulk register or redistribution licence.

Does Sri Lanka publish public beneficial ownership data?

This cycle did not verify a public beneficial-ownership dataset suitable for publication claims. The DRC BO route is login-gated and privacy-sensitive; FIU guidance can explain compliance context.

Why is the Sri Lanka Open Data Portal held?

The route showed an expired TLS certificate from this node. Even after a route fix, each dataset would still need licence, field and company-coverage review.

Why is PROMISe e-GP held?

PROMISe timed out from this node. The Ministry of Finance procurement page is clean for policy context, but supplier or award-level data should not be claimed until the e-procurement route clears QA.

Why is the Inland Revenue Department held?

IRD timed out from this node, and tax-service data is controlled. It should not be described as open bulk company data or as a source of marketing permission.

What does NIPO add?

NIPO adds intellectual-property enrichment for companies with trademark, patent or rights-related records. It is not all-company coverage.

What does the Department of Census and Statistics add?

DCS adds aggregate business, economic and market context. It helps explain the environment around companies, but it is not legal-entity master data.

What does the Central Bank of Sri Lanka add?

CBSL adds financial-sector authority and supervision context. It is a regulated-sector enrichment layer, not the full company population.

What does the Securities and Exchange Commission add?

SEC adds capital-market regulatory context and supervised-market evidence. It is authoritative inside its perimeter and partial by design.

What does the Colombo Stock Exchange add?

CSE adds listed-company and market-disclosure context. Listed companies are only a subset of Sri Lankan legal entities.

What does Government Printing add?

Government Printing adds official gazette and legal-publication evidence. It is useful for notices and event history, but it is a document layer rather than a company register.

What does FIU guidance add?

FIU guidance adds AML and beneficial-ownership compliance context. It supports lawful-use cautions but does not provide public BO records.

What does GLEIF add?

GLEIF adds structured LEI records for Sri Lankan entities that have Legal Entity Identifiers. It is API-friendly, but coverage is partial and skewed toward financial, regulated or cross-border entities.

Can public Sri Lanka company data be used for cold email?

No automatic permission follows from official or public access. Registry, tax, BO, regulator, gazette, IP, statistics and LEI data are not sales-prospecting permission. Use CompaniesData.cloud for compliant international company-data workflows.

Is this Sri Lanka draft ready to publish?

This draft can move to editorial review if QA passes, but no public update should be claimed until final source-live checks, WordPress publication and full Bing, Rank Math, Google-supported and crawler-access QA are completed.

Official Sources

• Department of the Registrar of Companies – Department of the Registrar of Companies, Sri Lanka
• eROC Sri Lanka – Department of the Registrar of Companies
• eROC company search – Department of the Registrar of Companies
• Ministry of Finance procurement – Ministry of Finance, Sri Lanka
• National Intellectual Property Office – National Intellectual Property Office of Sri Lanka
• Department of Census and Statistics – Department of Census and Statistics, Sri Lanka
• Central Bank of Sri Lanka – Central Bank of Sri Lanka
• Securities and Exchange Commission Sri Lanka – Securities and Exchange Commission of Sri Lanka
• Colombo Stock Exchange – Colombo Stock Exchange
• Department of Government Printing – Department of Government Printing, Sri Lanka
• Financial Intelligence Unit BO guidelines – Financial Intelligence Unit of Sri Lanka
• GLEIF LEI records for Sri Lanka – global official LEI system