Open Company Data in Mozambique: Official Sources, APIs and Reuse Rights
Open company data guide
Open company data in Mozambique: official sources, access limits and safe reuse
Mozambique can support a useful company-intelligence workflow, but it is not a clean open-register market. The safest editorial position is to combine official business-service, procurement, tax, regulator and LEI sources while holding unstable gazette, open-data, IP, licensing-candidate and JavaScript-only routes out of the live evidence chain until crawler checks pass.
Key takeaways
- Best current route: use the SRN legal-entities registration portal for registration-workflow context, UFSA for procurement context, Autoridade Tributaria for tax-identifier boundaries, Banco de Mocambique for regulated financial-sector context and GLEIF for sparse but clean identifier enrichment; keep BAU and APIEX as held candidates until DNS, certificate and crawler access pass.
- Not a bulk-register country: this article does not verify a free, official, crawler-stable company-register bulk download or API that can be used as a national company master file.
- Publication caution: BAU public routes, e-BAU, the gazette route, the candidate open-data portal, INE microdata catalogue, IP route and stock-exchange app route remain held because this cycle observed bot blocks, DNS failures, timeouts or JavaScript-only shells.
- Reuse boundary: tax identifiers, licence references and procurement appearances can help validate entities, but they do not create permission to assemble marketing contact lists.
- CompaniesData value: Mozambique needs source separation, date stamping, transliteration, Portuguese/English label normalization and confidence scoring more than blind aggregation.
Editorial methodology
This refresh used an official-source-first method. Each candidate source was checked with a normal browser-like user agent and with Googlebot and Bingbot profiles, then classified by source authority, access model, observed crawler behavior, reuse posture and risk. A source was allowed into the linked Resource Pack only when it returned expected official content under all three profiles and did not expose a bot-protection page, JavaScript-only shell, DNS failure, timeout, 403, 415 or 503 response. That standard is stricter than a normal editorial citation review because search engines and compliance users need stable, inspectable public pages, not just pages that work in a human browser.
The result is deliberately conservative. Mozambique has official routes that are valuable for business intelligence, but several routes that would normally be central to a country guide are not stable enough for live-link publication in this cycle. The article therefore separates clean linked sources from held research sources. Clean sources are linked in this refreshed article after final QA. Held sources remain useful for internal research notes, but should not be turned into live article links until a later crawl-access check proves that the public page or downloadable file is reachable and semantically meaningful.
Claims in this article are limited to what the source set supports. It is fair to say that Mozambique has official business-service, procurement, tax-authority, financial-regulator, investment-guide and LEI reference routes. It is not fair to say that Mozambique offers a complete free open company-register API, a universal bulk company register, or a marketing-ready contact database. This distinction matters because commercial users often want a single national company dataset, while the public evidence in this cycle points to a stitched, multi-source workflow with gaps.
Coverage, access and update-risk analysis
Mozambique should be treated as a source-mapped but controlled-access jurisdiction. The clean routes cover pieces of the business-data picture: incorporation and service process guidance, procurement and supplier context, tax-identifier context, regulated financial institutions and LEI records, with licensing-guide candidates held for final access clearance for a small number of globally active legal entities. Those pieces can support due-diligence research, entity matching and enrichment. They do not produce full national coverage.
The main coverage gap is the lack of a verified, freely reusable, crawler-stable national company-register feed. BAU and e-BAU remain important for business services, but the final 2026-06-14 source-live gate held BAU public routes because strict profiles saw DNS/certificate access failures. The SRN legal-entities portal is the cleaner linked process route in this update. e-BAU looked available to a browser profile but returned an application-blocked response to bot profiles, so it cannot be treated as a search-safe evidence link. Gazette and open-data routes also failed source QA, which means historical incorporation notices and downloadable public datasets cannot yet be made part of the live source chain.
The update risk is high. Several Mozambican public-sector routes appear to move, time out, or vary by user agent. A deep article should therefore show access dates, avoid overpromising automation, and make clear that operational users need repeated source checks before relying on a route for production ingestion. CompaniesData should store the observed URL, access date, HTTP status, content type, title, bot-profile result and reason for inclusion or hold. Without that audit layer, a previously valid source can quietly become a challenge page, app shell or dead hostname.
Source Matrix
| Source | Owner | Authority | Access model | Reuse note | Limitation |
|---|---|---|---|---|---|
| Government of Mozambique / Servicos de Registo e Notariado | legal-entities registration portal | public online registration/process portal | Use as official legal-entities registration workflow evidence; not as a reusable national company database. | Caution: process-submission evidence only; no bulk register, no all-field reuse and no contact-data permission. | |
| Functional Unit for Procurement Supervision | official procurement source | public procurement portal | Use for procurement-source context and supplier/public-contract references where lawful. | Caution: Procurement records are a subset of the economy and should not be merged into contact lists. | |
| Mozambique Tax Authority | official tax authority | public web portal with controlled taxpayer services | Use for tax-identifier and NUIT context only; do not infer permission for marketing reuse. | Caution: Tax identifiers and taxpayer services are sensitive public-sector contexts, not lead-enrichment feeds. | |
| Central Bank of Mozambique | official financial regulator | public regulator website | Use as regulator context for supervised institutions and financial-sector source mapping. | Caution: Regulator pages cover licensed/supervised institutions, not all companies. | |
| Central Bank of Mozambique | official financial regulator | public regulator guidance | Use as process evidence for financial-institution licensing. | Caution: Licensing guidance is not a complete financial-institution dataset. | |
| Global Legal Entity Identifier Foundation | high-quality global identifier dataset | public API | Open API metadata can support legal-name and address normalization with attribution to GLEIF terms. | Caution: LEI coverage is sparse and biased toward entities needing financial-market identifiers. |
Claims allowed and not allowed
Claims this source set supports
- Official process context: the SRN legal-entities portal can support registration-workflow explanation, while BAU remains held until access clears.
- Procurement overlay: UFSA can support supplier and public-contract research when procurement evidence is kept separate from master-company identity.
- Tax and identifier context: Autoridade Tributaria can support NUIT and tax-administration boundaries, with privacy cautions.
- Financial-sector overlay: Banco de Mocambique can support regulated financial-institution and licensing context.
- Identifier enrichment: GLEIF can support sparse LEI-based matching for internationally visible entities.
Claims this source set does not support
- No complete national bulk register: this cycle did not verify a free official national company-register bulk file or API.
- No clean gazette/open-data route: gazette, open-data, INE, IP and stock-exchange routes remain held until crawler-visible semantic access improves.
- No BAU/e-BAU bot-safe claim: BAU public routes remain held because final QA observed access failures, and e-BAU remains held because bot profiles received application-blocked responses.
- No beneficial-ownership completeness: this cycle did not verify a clean public beneficial-ownership dataset.
- No marketing permission: tax identifiers, procurement appearances, licence references, names, addresses, emails or phone numbers are not permission for lead lists.
Source-by-source deep dives
SRN legal-entities portal and held BAU routes
The SRN legal-entities portal is the clean linked route in this update for explaining official registration-process context. It exposes a public page for Registo de Entidades Legais, including online submission context for sociedades comerciais, but it should not be described as a reusable company database, API or bulk download.
BAU remains source-relevant for business-service orientation, but its public site and service catalogue are held from live links after the final source-live gate observed access failures. For CompaniesData, these routes are useful as process labels only after access is stable; the data model should not infer legal status, current registration standing, director data or contact details from them.
UFSA: procurement and supplier context
UFSA gives Mozambique a clean official procurement source route. Procurement data is commercially valuable because it can reveal suppliers, public buyers, contract notices and the sectors where companies interact with the state. It is also easy to misuse. A company appearing in procurement material is not the same as a company appearing in a national register, and procurement records should be treated as event-based evidence rather than master-company data.
The recommended use is to model procurement as a separate evidence table: buyer, supplier name as published, procurement process, publication date, reference number, source URL, amount if public, sector and extraction confidence. CompaniesData can then match supplier names against canonical entities with a confidence score. That workflow preserves the public-contract meaning of the source and avoids blending procurement appearances into unverified sales lists.
Autoridade Tributaria: NUIT and tax-identifier boundary
The Mozambique Tax Authority is relevant because NUIT and tax-registration context often appear in business verification workflows. This route needs a strict privacy and lawful-use boundary. Tax identifiers may be public in some contexts and controlled in others, and taxpayer services are not a permission layer for scraping or lead generation. The safe article posture is to explain that tax-authority routes can help users understand identifier structure and official tax-service context, while warning that private reuse, enrichment and outreach need a separate lawful basis.
CompaniesData should keep tax-derived fields separate from marketing fields. Recommended fields include identifier type, issuing authority, source context, verification date, confidence, and restrictions. Do not label tax routes as email, phone, lead or prospecting sources. If contact enrichment is discussed for international users, the article should point to CompaniesData.cloud as the owned service context and avoid recommending outside contact-data vendors.
Banco de Mocambique: regulated financial-sector context
Banco de Mocambique is a strong official regulator source for financial-sector context. The central bank site and its licensing guidance help explain how supervised institutions are licensed and what regulatory perimeter applies to banks or financial entities. This is a high-authority source, but it is sector-limited. It can improve confidence for banks, financial institutions and regulated service providers; it should not be presented as a register of all Mozambican companies.
The data model should treat regulator records as a sectoral overlay. A regulated entity can have fields such as regulator, licence category, status label as published, source page, access date and confidence. Matching those records to a canonical company profile is valuable, but the match should be reversible and evidence-linked because legal names, trading names and Portuguese/English labels may not align perfectly.
APIEX licensing guide candidate: held pending access clearance
APIEX remains a relevant licensing and investor-guidance candidate, but this cycle could not resolve its PDF host from the publishing environment. That makes it unsuitable as a live linked source in the refreshed article. The safe editorial posture is to keep APIEX in the research artifact, mention licensing-guide coverage only as a candidate, and re-test the route before any future material update.
If a later cycle confirms stable PDF access for browser, Googlebot and Bingbot profiles, the guide can support practical licensing explanation. Until then, it should not be used to make source-chain or database-coverage claims.
GLEIF: sparse but clean identifier enrichment
GLEIF is a high-quality global identifier source and the cleanest API route in this cycle. It reported Mozambique LEI records through a public API, which makes it useful for cross-border matching, address normalization and entity-name reconciliation. Its main weakness is coverage. LEI records represent entities that have obtained an LEI, usually because of financial-market, regulatory or counterparty needs. They are not representative of all companies in Mozambique.
The recommended CompaniesData use is enrichment, not base coverage. Store LEI, registration authority references where present, legal name, address, status, managing LOU, last update and GLEIF metadata. Then link the LEI record to a Mozambique canonical entity only when names, addresses and identifiers support the match. This improves quality for internationally visible entities while preserving honest coverage limits.
Held source routes and why they are not live links yet
The following routes remain in the research file rather than the linked article evidence chain: BAU public site, BAU service catalogue, APIEX Mozambique Business Licensing Guide, e-BAU integrated service platform, Imprensa Nacional / official gazette route, Mozambique open data portal candidate, INE MozData microdata catalogue, Industrial Property Institute candidate, Bolsa de Valores de Mocambique. The reasons are practical rather than editorial preference: this cycle saw bot-profile blocking on e-BAU, DNS failures on gazette and open-data candidates, timeout behavior on INE microdata and IP routes, and a JavaScript-only shell on the stock-exchange route. A later refresh can re-test these sources, but a public article should not ask readers or crawlers to rely on routes that fail semantic access checks.
Holding those links does not mean the sources are unimportant. In a fully mature Mozambique profile, the gazette route could add incorporation notices, INE microdata could add enterprise-frame or economic context, IP routes could support trademark enrichment, and the stock exchange could support listed-company coverage. The current editorial decision is simply that they need final source clearance before publication.
Practical options for users
- Manual verification: start with the SRN legal-entities registration portal for process orientation, and revisit BAU only when access checks clear, then use regulator or procurement routes only when the company is in the relevant sector or public-contract context.
- API enrichment: use GLEIF for Mozambique LEI records, but label it as sparse international identifier coverage.
- Bulk data: do not assume national-register bulk access. The verified source set does not prove a complete official company bulk file.
- Procurement research: treat UFSA records as event evidence and match suppliers to canonical entities with confidence scoring.
- Tax identifiers: use tax-authority context for understanding identifiers, not for building outreach lists.
- Regulated entities: use Banco de Mocambique as a sector-specific source for supervised financial institutions and licensing context.
- Licensing guidance: keep APIEX as a researched candidate and cite it only after DNS, content and crawler checks pass in the final cleanup.
Missing data gaps
The most important gap is a crawler-stable official company-register dataset with clear reuse terms, current legal status and downloadable or API access. Without that, Mozambique remains a country where a commercial data product needs careful source fusion. Other gaps include officer and beneficial-ownership availability, historical gazette coverage, reliable enterprise statistics routes, trademark data availability, and stable listed-company pages that expose content without client-side rendering.
Marketing-contact data is a separate gap and should not be solved by scraping official pages. Official public-sector records may contain names, addresses or identifiers for administrative transparency, but that does not make them contact-permission sources. A responsible article should mention contact enrichment only strategically and point international readers to CompaniesData.cloud for owned, compliant data services rather than sending them to outside contact-data vendors.
Recommended data model
- Canonical entity: legal name, normalized name, language/script notes, jurisdiction, legal form, registration identifier if verified, status if verified, source confidence and last reviewed date.
- Source evidence: source owner, URL, access date, HTTP status, bot-profile result, title, content type, reuse note and claim allowed/not allowed.
- Identifier overlay: NUIT context, LEI, regulator identifiers, procurement supplier references and licensing references, each stored with source provenance.
- Event tables: procurement events, licensing events, regulator events and gazette notices should remain separate from master-company records.
- Risk fields: privacy caution, controlled-access marker, no-bulk marker, bot-block marker, stale-source marker and marketing-use restriction.
- Normalization fields: Portuguese/English labels, transliteration variants, address components, province/city normalization and confidence score.
CompaniesData normalization and enrichment value
CompaniesData can add value in Mozambique by doing the difficult work that raw sources do not do: separating official source types, maintaining access-date evidence, normalizing names across Portuguese and English contexts, mapping sector-specific regulator records to entities, and distinguishing sparse identifier enrichment from national coverage. The product value is not only collecting links; it is preventing users from treating partial public evidence as a complete company register.
A high-quality Mozambique record should show what is verified, what is inferred, and what is missing. For example, a company may have a procurement appearance and a tax identifier context but no verified national-register record in the accessible source set. Another entity may have an LEI and a central-bank licensing reference but no broader official company profile. CompaniesData can represent those situations honestly with confidence scoring and source-specific evidence rather than flattening everything into a single unqualified row.
Reuse checklist
- Source authority checked: prefer official government, regulator, procurement, tax and standards bodies before third-party aggregators.
- Access model recorded: mark whether the source is public web, API, PDF, controlled service, JavaScript-only, timed out or blocked for crawlers.
- Reuse rights reviewed: distinguish narrative citation, public-record reuse, API terms and no-bulk/no-scrape situations.
- Privacy boundary added: do not convert tax, licence or procurement data into marketing contact data without a lawful basis.
- Bot/crawler access tested: reject sources that only show real content to a browser but challenge Googlebot or Bingbot profiles.
- Evidence separated: keep procurement, regulator, LEI and tax evidence as overlays until canonical company identity is verified.
Grouped Resource Pack
Clean official and high-quality routes for this article
Registo de Entidades Legais: official route. legal-entities registration workflow and process-submission context. Not a bulk register and not contact-data permission.
- BAU public site and service catalogue: held from live-link publication after final QA observed DNS/certificate access failures on 2026-06-14.
UFSA procurement portal: official route. procurement, public contracts and supplier-reference context. Procurement records are a subset of the economy and should not be merged into contact lists.
Autoridade Tributaria de Mocambique: official route. NUIT/tax identifier context and privacy boundary. Tax identifiers and taxpayer services are sensitive public-sector contexts, not lead-enrichment feeds.
Banco de Mocambique: official route. regulated financial-sector context. Regulator pages cover licensed/supervised institutions, not all companies.
Banco de Mocambique licensing of institutions: official route. financial licensing workflow and regulator coverage limits. Licensing guidance is not a complete financial-institution dataset.
GLEIF LEI records for Mozambique: official route. cross-border identifier enrichment and normalization. LEI coverage is sparse and biased toward entities needing financial-market identifiers.
Held research routes pending source clearance
- APIEX Mozambique Business Licensing Guide: held from live-link publication. PDF guidance needs date/version checks before operational use.
- e-BAU integrated service platform: held from live-link publication. Browser 200 was observed, but Googlebot/Bingbot profiles received 503 Application Blocked.
- Imprensa Nacional / official gazette route: held from live-link publication. DNS resolution failed from the publishing environment.
- Mozambique open data portal candidate: held from live-link publication. DNS resolution failed from the publishing environment.
- INE MozData microdata catalogue: held from live-link publication. Search results show the catalogue, but direct source QA timed out from this environment.
- Industrial Property Institute candidate: held from live-link publication. Connection timed out from this environment.
- Bolsa de Valores de Mocambique: held from live-link publication. The fetched page returned a JavaScript-app shell, so crawler-visible semantics are weak.
FAQ
Is there a free open company register API for Mozambique?
This cycle did not verify a free, official, crawler-stable national company-register API or bulk file. GLEIF offers a clean API for LEI records, but that is sparse identifier coverage, not a national company register.
Can procurement records be used as company data?
Yes, but only as procurement evidence. UFSA records can help identify suppliers and public-contract relationships, but they should be matched to canonical entities with confidence scoring and not treated as full company profiles.
Can NUIT or tax-authority data be used for marketing?
No broad marketing permission should be inferred from tax-authority context. Tax identifiers and taxpayer services are administrative data contexts. Any contact enrichment needs a separate lawful basis and should be handled through a compliant owned workflow such as CompaniesData.cloud for international users.
Why are some official sources held back?
Because public source QA found bot blocks, DNS failures, timeouts or JavaScript-only pages. A source can be official and still unsuitable as a live article link until it returns stable, crawlable, semantically meaningful content.
What is the best practical approach today?
Use SRN legal-entities portal context, UFSA for procurement context, Autoridade Tributaria for identifier boundaries, Banco de Mocambique for financial-sector regulation and GLEIF for sparse identifier enrichment. Treat APIEX as a researched licensing candidate until final access checks pass. Keep each evidence type separate.
How should CompaniesData handle Mozambique?
CompaniesData should maintain a source-risk log with access dates, crawler checks and held-source reasons. The finished page should be a reference guide, not a thin programmatic country page.
Official sources used in this article
The linked article source chain includes: Registo de Entidades Legais, UFSA procurement portal, Autoridade Tributaria de Mocambique, Banco de Mocambique, Banco de Mocambique licensing of institutions, GLEIF LEI records for Mozambique. Held sources are documented in the normalized source QA artifact but intentionally excluded from live links until they pass final clearance.
Leave a Reply
Want to join the discussion?Feel free to contribute!