How to Build a Licence Map for a Sri Lanka Project

A licence map helps a project team identify which planned activities may be ready to start and which areas require further confirmation before investing in office space, staff or systems. It does not guarantee that a registration, licence or approval will be granted; it is a working framework for reducing rework, assigning ownership and managing dependencies.

For businesses entering Sri Lanka, a common mistake is to ask which licences are required before clearly defining what the business will actually do. Under the same corporate entity, software development, cross-border services, goods imports, platform operations, payment arrangements, warehousing and delivery, and sales to the public may each raise different regulatory questions, require different professional input, and follow different preparation sequences. A licence map should therefore begin with business activities, not with the name of a particular licence.

What Is a Project Licence Map?

A project licence map is an internal project tracker that brings the following information into one view:

• Specific business activities planned in Sri Lanka;
• The customers, counterparties, payment flows and goods flows connected to each activity;
• Potentially relevant authorities, registrations or sector-specific permissions;
• Preconditions that may need to be completed before an activity starts;
• Information or documents to be provided or confirmed by the company, a local service coordinator and appropriately licensed professional firms;
• Open questions, risk priority and decision deadlines.

It is not legal advice and cannot replace formal confirmation from relevant authorities or instructed licensed professionals. Its value is that it allows management to see dependencies early, rather than discovering that an activity still requires further review after a lease has been signed, employees have joined, or customer contracts have been substantially negotiated.

Step One: Break the Business Plan into Verifiable Activities

Avoid describing the project only as a “technology company”, “trading company” or “platform business”. These labels are usually too broad to assess a licensing pathway. A more effective approach is to break the project into activities that can be described, assigned and verified.

For example, a digital business may include several activities at the same time:

• Providing software development or operational support to overseas clients;
• Hiring local developers, customer service staff or sales personnel;
• Offering subscription services to business customers;
• Collecting service fees through third-party channels;
• Processing user information or transaction data;
• Procuring, importing or selling equipment; and
• Promoting services to local consumers.

For each activity, add four questions: Where is the service recipient located? Which entity signs the contract? Which entity receives payment? Where is the work actually performed? For projects with potentially higher regulatory exposure, also describe whether they involve public funds, financial information, medical information, education certification, telecommunications resources, restricted goods, transport, or consumer-facing transactions.

The purpose of this step is not for the business to decide on its own whether a licence is needed. It is to ensure that the facts are described fully. If the facts are unclear, any later licensing assessment may be misaligned with the actual business model.

Step Two: Create an Activity–Regulatory Matter–Precondition Table

A licence map should be maintained as a live project table rather than prepared as a one-off document. The following structure can be used as an internal template:

Business activity	Project facts	Matters to confirm	Preconditions	Owner	Current status
Providing professional services	Service scope, client location, delivery method	Whether sector entry or registration requirements apply	Entity, contracts and professional input	Project lead	To be confirmed
Hiring local employees	Initial roles, work location, employment model	Labour and employee onboarding arrangements	Employer entity, role plan	HR lead	In preparation
Engaging foreign personnel	Position, work scope, Sri Lanka stay arrangements	Visa and work-related arrangements	Company documents, job description	Administration lead	To be confirmed
Importing equipment or goods	Product category, use and supply-chain route	Import, product or sector-related matters	Goods information, supplier documents	Supply-chain lead	To be confirmed

The “matters to confirm” column should use neutral wording, such as “confirm whether additional approval is required” or “confirm whether product or sector restrictions apply”. Do not state an unreviewed preliminary view as a final conclusion. This helps prevent the team from treating an early assessment as a confirmed requirement.

Step Three: Separate Entity Formation, Operating Permissions and Ongoing Obligations

The area most often missed in a licence map is not company incorporation itself, but the operating conditions that arise after the company has been formed. It is useful to manage the project across at least three layers.

1. Entity Layer

The entity layer considers how the company will enter the market, whether its proposed registered business scope aligns with the intended activities, and whether relevant documents should be reviewed further by a company secretary, lawyer, tax adviser or other professional firm. Company formation is the foundation for later steps, but it should not be treated as an automatic clearance for every planned business activity.

2. Launch Layer

The launch layer focuses on what needs to be confirmed before the project begins providing services externally, signing contracts, receiving payments, hiring staff, importing goods, opening a physical location or carrying out market-facing activities. Different activities may have different launch conditions. A project should therefore not be reduced to only two statuses: “company incorporated” or “not incorporated”.

3. Ongoing Operations Layer

The ongoing operations layer covers matters that need to be maintained after the project has started, such as record retention, filings, employee administration, contract updates, product changes and changes to the business scope. The licence map should include a “review trigger” field. When the project adds a new customer category, payment method, product category, office location or cross-border transaction arrangement, the team should reassess whether its previous conclusions remain relevant.

Step Four: Map Dependencies Before Building the Project Timeline

Many projects are delayed not because one application step is inherently difficult, but because prerequisite information has not been prepared early enough. A licence map should show what each confirmation depends on, rather than simply listing tasks.

Common dependencies include:

• The activity description affects entity documentation, contract structure and licensing assessments;
• Information about shareholders, directors or authorised signatories affects incorporation and subsequent bank account and contracting arrangements;
• The office address and actual operating location may affect the preparation approach for certain activities;
• The initial staffing plan and foreign personnel plan affect the sequencing of HR and immigration coordination;
• Product details, supply-chain documents and technical descriptions may affect the assessment of import or sector-related matters;
• Customer location, payment routes and data-processing arrangements may affect tax, contractual and compliance-related professional input.

In the project plan, “awaiting confirmation” should be shown as a separate status rather than assumed to progress in parallel with company registration. Before committing externally to a launch date, management should identify which items have been completed and which remain only at the preparation or consultation stage.

Step Five: Assign a Confirmation Source and Supporting Evidence to Each Question

A reliable licence map should not simply state “confirmed”. Each key conclusion should ideally record the source of confirmation, confirmation date, supporting documents and conditions for the next review.

The following allocation of responsibilities may be useful:

• The company: provides an accurate and complete description of its business model, products, staffing plan and transaction flows;
• MMD Business Support: helps structure requirements, coordinate document checklists, identify local resources, arrange communications and follow up on project milestones;
• Appropriately qualified professional firms: undertake company registration, legal, tax, audit, immigration and relevant licence-related professional work according to the specific project;
• Relevant authorities or official channels: provide the final applicable information within their areas of responsibility.

Official channels of the Sri Lanka Department of Registrar of Companies, Inland Revenue Department, Department of Immigration and Emigration, Department of Labour and Board of Investment of Sri Lanka can be starting points for checking project-related information. The latest publicly available requirements and professional advice should be relied upon. Where sector regulation is involved, the relevant regulator should be identified rather than relying only on a general company incorporation checklist.

Risk Flags to Include in a Practical Licence Map

Consider adding red, amber and green indicators to the map. These indicators should represent project-management priority, not a prediction of approval outcomes.

• Red: The business is planned to launch, but key regulatory matters, entity conditions or professional input have not yet been confirmed;
• Amber: An initial route has been identified, but documents, owners, business details or prerequisite steps are still incomplete;
• Green: Materials and responsibility allocation required for the current stage have been identified, with a mechanism retained for future review.

Two practices should be avoided in particular. First, do not directly apply licence names based on a competitor’s experience or on requirements in another jurisdiction. Second, do not treat a service provider’s verbal view as a formal conclusion. The applicability of licensing, tax, labour, immigration and sector-entry requirements generally depends on the project’s actual activities, not only on its company name or broad industry classification.

Prepare This Information Pack Before a Readiness Review

If you want to prepare an initial licence map for your project, organise the following information first:

1. Your business activity description, including differences between the first phase and later phases;
2. Whether target customers are businesses, consumers, government bodies or channel partners;
3. The contracting entity, payment-receiving entity and service-delivery location;
4. Whether the project involves imports, warehousing, physical stores, equipment installation or local delivery;
5. Whether it processes sensitive data, transaction data or data related to regulated sectors;
6. The entity type you intend to select and the proposed arrangements for shareholders, directors and authorised signatories;
7. Your initial roles, whether foreign personnel are planned, and the expected office model;
8. Key commercial decisions that have been made and those that remain open.

The more complete the information, the easier it is to distinguish between regulatory questions requiring further confirmation and commercial questions that have not yet been decided internally. The former should be checked through appropriate channels; the latter should be decided by the project team first.

This content is provided for general information only and does not constitute legal, tax or immigration advice. Specific requirements should be confirmed against the latest guidance from relevant Sri Lankan authorities and instructed licensed professional firms.