Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Module roadmap
Details coming soon..
For traders to do business in India, ease in redundant procedures and regulatory processes is of paramount importance. DIGIT-Trade License increases procedural efficiency and improves the accessibility and transparency of information thus enabling the business to flourish and function with ease.
Apply for trade license, ensure compliance with trade safety guidelines, and lots more
DIGIT-Trade License (TL) enables local government to regulate the trade and protect the interest of the public at large against the health hazard and inconvenience which a business may cause. With DIGIT-TL traders can obtain the trade certificate in a simplified manner and ensure compliance with rules and safety guidelines issued by the government. The module offers the citizens and governance bodies a convenient and transparent means of processing trade licenses.
The Trade License application makes the process of obtaining a Trade License easy, smooth, and transparent. The module, hence, removes the need for manual processing and streamlines the key trade license management functions to provide a better user experience.
DIGIT Trade License module enables citizens to -
Apply for new trade license or renew an existing trade license.
Upload all the relevant documents required for the license.
Make payment for the Trade License (New/Renewal) fee using the online payment gateway.
Receive notifications and alerts by emails or SMS for new application status updates and pending renewals.
Download Trade License, Payment & Acknowledgement Receipts online.
DIGIT Trade License module enables employees to -
Create flexible role-based workflows.
Configure license fees calculation logic.
View custom dashboards for module statistics.
Filter search results using advanced configurable search parameters.
This section contains all docs and information required to understand the TL module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the TL module.
Functional Specifications
TL Roadmap
TL User Manual
Product Brochure
TL Workflows
Master Data Configuration Template
TL Service Configuration
Implementation Handbook
Demo Script
Navigation Tips
Click on the embedded links within the content to browse topic details
Use the Contents links available on the right side of the screen to move to a specific heading
Find the list of Related Docs links at the bottom of each page to browse through additional product details
Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on TL module deployment.
#147/J, 1st floor, 10th Cross, 12th Main, 3rd Block, Koramangala, Bangalore 560034
+91 80 4125 5708
contact@digit.org
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Learn more about TL workflows and its configuration
Details coming soon..
Functional overview for stakeholders
The Trade License product provides a digital interface, allowing citizens to apply for the Trade License and subsequently make the trade license fee payment online.
The Trade License product enables:
Ease of doing business — Traders can apply for new licenses, renewals, amendments, and supplemental licenses
Regulatory Tracking — Administrators can track and manage regulatory processes
Shorter Timelines — It streamlines and automates business licensing processes and helps a business to be set up quickly
Data-driven decision making — The application collates valuable information on the economic activity and employment opportunities in a ULB
The list below summarizes the key features supported by the TL module -
Registration, Login and Creation of User Profile
Applying for a Trade License
Trade License Issue
Modifications to a Trade License
Renewal of Trade License
Payments and Fee
Dashboards and Reports
General Features
Key capabilities offered by this functional component -
OTP Based Login for Citizen via Web/Mobile App
OTP Based Login for Employee via Web/Mobile App
Provision for language selection during first time registration for both Employee and citizens
Provision of creating a personalized Profile for Citizens and employees on Web App
Login Credentials for the various hierarchies of employees
Role-based access for performing different actions relating to Trade License modules
User can apply for a new TL from the system. User can select the type of license to apply. The user enters trade details, owner details and documents after which application can be reviewed and submitted. Similarly, a counter employee can also apply for TL on behalf of the citizen. The system has a workflow integration which enables stage-wise approval before Approval for issuing the Trade License.
Key capabilities offered by this functional component -
Citizen can Apply for a new Trade License through mobile app/ Web
Citizen/CSC can capture Trade details, Trade Units, Accessories, Owner Details, Address, purpose, Date of issuance, License number etc.
Citizen/CSC Upload Documents
Citizen/CSC can calculate Breakup Based on Selected Trade
Citizen/CSC can select Multiple Accessories for the Trade
Citizen/CSC can Apply for Multiple Trade Licenses
Citizen/CSC can Download/Print Application Summary
Citizen/CSC can Download/Print Trade Reference No
Citizen/CSC can View the applied licenses
The system has the facility to deliver the service online & through SEWA KENDRA.
The portal displays all the information including the processes and documents required for the convenience of the citizen.
The system has the facility to assign a unique identification number based on the license type, which will be used for all future transactions of the license.
The system has the facility to assign the application to the respective Inspector for survey and verification. After the application is submitted, it goes to the document verifier. The next step after document verification is field inspection. After the field inspector’s approval, the TL is approved by the approver.
Key capabilities offered by this functional component -
Document Verifier, Verifies & Forwards or Rejects the application
Licensing Inspector, Verifies and Forward the Application
Licensing Inspector, Sends Back or Rejects the Application
Licensing Inspectors Approves the Application
Citizen, Pays for the license post verification process online or at the CSC
CSC, Collects Fee post verification.
The system allows the printing of license and sending the license through e-mail.
The system allows the SMS alerts to the applicant regarding the date of inspection/visit by the inspector, approval/rejection of the application.
The system allows the inspector to enter the field visit details and a field visit report is generated and automatically routed to the superintendent.
The system has the facility to edit/update the Application based on the Inspection report against the application.
The system has the facility to provide a hassle-free renewal process for citizen and employee ease, leading to increased revenues, by reducing unlicensed trades. The system allows sending of SMS and Email notifications and reminders based on the renewal cycle.
Key capabilities offered by this functional component -
The citizen can pay for the license post verification process
CSC, Collects Fee post verification.
The system allows intimating the applicant about the payment of the license fee through SMS/ e-Mail.
The system allows the Generation of receipt for the payment
The payment modes enabled are Card(offline), cash, cheque, DD
Following reports offered by the module -
Cancelled Receipt Register Report
TL Collection
TL Application Status- showing the number of licenses approved/rejected.
TL ULB Wise Status
State Dashboard: View Reports for Total Licenses, Licenses Issued, Payment Collected, Payment Distribution
Notifications - The system has the capability to send notifications to citizens. These notifications can be sent for various steps like - verification completion, payment reminder, payment confirmation. These notifications can be sent in the language chosen by the ULB through all channels - SMS, Whatsapp, Email.
Configurable Masters - The system provides the following masters that can be configured as per the State’s requirements:
Charges & Calculation : Calculation Engine, Rebate, Penalty,
Rate Master
State Masters: Trade Ontology, Documents List, Accessories, Ownership, Employee Data Mapping, Boundary Data Mapping, Fee Matrix (License Fees)
System specification in compliance with the Ease of Doing Business (EODB) BRAP 2019
The computerized and automatic Trade License system offered by eGov, facilitates citizens who seek to apply for a Trade License within any Urban Local Body with a transparent, speedy, hassle-free and user-friendly procedure. Trade License (TL) is one of the components of a smart city that ensures a check on all the trade practices and increases the ease of conducting business within the state. Keeping in mind the benefits associated with the product offered, the proposed system is about to be implemented in 500+ ULBs across the country in 15 states. (For details on product features refer to Section-2)
For the offered product, the implementation process can be divided into seven major distinctive stages. Each stage has a predefined entry and exit criteria, roles & responsibilities to assure objective monitoring and decision making for the overall success of the engagement. The whole implementation lifecycle is typical of 38-42 weeks for the State, keeping in mind the entry and exit criteria defined at the beginning and end of each stage are met on time recommended.
Exhibit 1: Phases of Implementation.
Stage Zero is that of program setup and onboarding which is a pre-requisite for the initiative to kick-off and requires setup of the governance model, implementation Team and decision regarding other significant elements of the initiative like funding and procurement process. Stage One requires scoping of the initiative and decisions on the priorities for implementation by the State Implementation Team. In stage two, the State Team will work upon identifying and finding solutions to the significant gaps in the product offered with respect to the need of the State. Configuration and customization of the product offered is the primary objective of stage four. This involves working on various aspects of State-specific needs and incorporating them into the product offered. In stage five, post doing UAT and including all the necessary feedback on the product, the roll-out of the product is done at the State level (Go Live) from a couple of ULBs to pan State coverage in batches. Finally, in stage 6 sustenance and ongoing improvements are worked upon while the product is already functioning in the State. (For details on implementation plan refer to Section-3)
Implementation of Trade License (TL) requires meticulous planning and close coordination between various stakeholders at the center and State level. The success of the initiative is dependent upon many factors like strong Program governance, availability of the trained resource, financial planning, targeted Implementation Team onboarding, focus on last-mile capacity building and ensuring necessary support to Urban center. Achievement of all these factors will provide the most effective and efficient roll-out and adoption of the Trade License System in the State.
The purpose of this document is to give an overview of the Trade License System (TLS). The Trade License product provides a digital interface, allowing citizens to apply for the Trade License and subsequently make the payment online.
The Trade License product enables:
Ease of doing business — Traders can apply for new licenses, renewals, amendments, and supplemental licenses
Regulatory Tracking — Administrators can track and manage regulatory processes
Shorter Timelines — It streamlines and automates business licensing processes and helps a business to be set up quickly
Data-driven decision making — The application collates valuable information on the economic activity and employment opportunities in a ULB
The TL product features can be broadly classified as the following modules:
Registration, Login and Creation of User Profile
Applying for a Trade License
Trade License Issue
Modifications to a Trade License
Renewal of Trade License
Payments and Fee
Dashboards and Reports
General Features
This section provides an overview of the methodology for State-wide implementation of TL. The Implementation of TL is distributed across seven distinct stages. Each stage has a predefined entry & exit criteria and roles & responsibilities. This is to ensure objective monitoring and decision making for the overall success of the program. Details of each stage are defined in this section.
Note: This document is specific for States that have more than 30 ULBs
TL implementation program is expected to be completed approximately between 38- 42 weeks with the resource deployment by the State and System Integrator (SI) Team (as defined below). However, it is critical that activities and exit criteria set for each stage are achieved to adhere to this timeline.
This is a set of initial critical activities undertaken on receiving a letter of Enrolment or MOU from the State. Successful completion of these activities assures that the program is started with crucial personnel, System Integrator (SI) Teams, and funds.
*Details of TL cell is mentioned in section 4 of the handbook
System Integrator and state will agree on program scope, program timelines, and budgeting & resourcing.
This stage envisages the in-person interaction of crucial State officials and implementation System Integrator (SI) Teams to kick-start the program. This stage may require multiple interactions/meetings with different interest groups. The principal objective of these interactions is to identify scope and planning strategies for phasing/ rollout, create an active collaboration & Governance approach and agree on a high-level timeline for the engagement.
*Exploration is required to understand the Inter and Intra Departmental Jurisdictions of Local Governments with respect to Trade License.
#Details of TL cell is mentioned in section 4 of the handbook
State Baseline Data: A Baseline Template is provided to collect certain vital information like no. of transactions, revenue collected in the last FYs, collection mode, budget data, etc. This data must be collected pre-rollout
During the Solution design stage, key State officials and members, who are subject matter experts, are expected to share State acts and policies and help interpret the same for the System Integrator (SI) Team. This stage baselines the State-specific product features in the Product Configuration report.
Pilot ULBs Specific Product Data Configuration: Master data is required from the Product Perspective for go live. For e.g.: Boundary Data, List of Employees etc. A Master Data Template will be provided for the collection of this particular data type.
This stage consists of a series of developments in accordance with the detailed project plan to ensure smooth functioning of the customised product. Master Data Collection & Environment Setup will be achieved in this phase. Further monitoring and maintenance strategies are put in place.
During this stage, demonstration of the product followed by a hands-on session is conducted for the ULB officials. Necessary training of ULB officials and resources required for UAT is conducted and identified respectively. The establishment of the State support Team and required processes are initiated in this stage.
Note: The Nodal Officer is responsible to identify the ULB officials who are associated with the TL process on ground and will be working with the technological Product in the respective ULBs
On successful Go-Live in the Pilot ULBs, and further fine tuning to stabilize the product, the solution will be rolled out to the rest of the ULBs in phases. Guidance and support from the State Team will be required to create the rollout plans and assure the necessary infrastructure for training and deployment is available at each ULB.
Note: The rollout phase needs to be detailed out for iterative activities of onboarding ULBs in batches.
Note: Only once all the stages are complete in one batch of rollout of around 30 ULBs, the next batch begins. There are multiple phases of rollout. The second batch begins after the first batch has successfully fulfilled all the criteria of the Rollout Phase. Typical timeline for closure of rollout in each batch is 5-6 weeks (in a batch of 30 ULBs)
The final stage consists of strategies to ensure the sustenance of the product in the State. Systems are put in place to ensure the continuous tracking of data and provisions are made to improve the product if new data suggests.
This section outlines the activities involved in each stage of the implementation along with responsibility and accountability of critical stakeholders - State, eGov Team and System Integrator Team onboard.
TL Cell: TL Cell is the government-appointed body chaired by the Principal Secretary/Secretary, Urban Development Department with members from Urban Development Department etc.
Resource requirements for the TL cell required to be formed by the State
Note:
Designation mentioned above are as per designations already driving TLs implementation at the State level.
The description of each designation is explained below.
These are the preferred figures. In the case of Domain Expert, 2 people is subject to availability
Description of resource persons:
Project Head: Is the Head of the TL Cell who will drive the project from the State’s Side
Domain Expert: Person who is well aware of the on-ground scenario, well versed with the act, GOs passed, Prevalent Business processes, Deviations from the acts, TL Rates/ slabs applicable
Nodal officer (EO/Commissioner/ Senior Official): the project coordinator in each district to drive the project centrally. Monitor usage post Go Live- point of escalation for Implementation Team, Seasoned and worked in Multiple ULBs on various modules and has a good understanding of TL, Facilitate and Track data collection Post Go Live, Monitors and facilitates adoption of application. point of contact for eGov, SI and at the HQ level.
MIS Expert: Day to day tracking of the data specific to ULBs, data entry, reporting and review to senior officials
eGOv Team: eGov Team is the technical partner of the project which will provide all necessary support to the State concerning the implementation, Program Designing etc.
System Integrator (SI)Team: SI Team will be responsible for consulting, program management and the implementation of products in the ULBs in close collaboration with the TL cell, technical partner (eGov) and various other stakeholders.
Guidelines to read the tables below:
Execute - One who owns the accountability to complete the activity
Consult - One who may initiate, guide and in the process, handhold the execution of the activity
Note: Stage 0 is where the TL cell and SI team is formed, hence there are only two entities playing a role which is that of eGov and the state leadership. Once the TL cell and SI team is finalised, their role begins in the following stages.
Vision:
Defining the time frame to go live, the time frame to scale it pan state, the value proposition of the programme for the state and year-on-year financial targets and adoption targets
Project Plan:
A detailed plan of Program schedule/timelines, implementation phases, team structure and ongoing support and maintenance required.
System Integrator:
The Entity/Company which collates all the subsystem required for the project and integrates them to achieve the program objective
Program Charter:
Outline of implementation plan agreement with priority applications and broad timelines, program governance model, program success metrics and capacity building.
Acceptance Letter/MOU:
Formal Acceptance/Sign Off of the Client State with a clear mandate of the Program
Program Success Metrics:
Defining the parameters (which are measurable) prior to the program, on which the success of the program is to be measured on the completion of the program
Project steering committee:
The key body within the governance structure which is responsible for the business issues associated with the project that are essential in ensuring the delivery of the project outputs and the attainment of project outcomes.
Project governance:
Set of policies, regulations, functions, processes, procedures and responsibilities that define the establishment, management and control of projects, programmes and portfolios.
Scoping:
List of activities measured against time taken to complete them in accordance with the project goals
Baseline data:
Set of information that serves as a foundation to compare other data acquired afterwards
Project Kick off meeting:
Meeting with the project team and the client of the project. This meeting would follow definition of the base elements for the project and other project planning activities
Fitment Study:
GAP Study of the Existing/Required Field Process Vs Product
Data migration:
Existing Records of the functional activities need to be moved into the Database of the newly released Application
Data collection:
Required data for the roll-out of the applications, which needs to be collected from the existing functional process
Data validation approach:
This approach enables the sanctity of the Data with built-in validation by Design
Data synchronization:
The process of establishing consistency among data from a source to a target data storage and vice versa and the continuous harmonization of the data over time.
Pilot Implementation:
Any new process is tested out as pilot in one or two instances before pan implementation
Pilot ULB:
The ULB's Selected for the pilot implementation are called pilot ULB’s.
Roll out:
On successful clearance of the Pilot, the Process/Application/Services are implemented across all Offices/ULB's
Deployment:
Deployment defines the complete package of Software components set up in a particular environment
Customization:
Details of changes to be made in the Product to comply with the needed field process
Configuration:
Defining existing content such as Options and Variables based on the requirements on the ground
Product walkthrough:
Explaining the users step-by-step through a set of actions that they need to take to achieve a specific outcome
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
to view module capabilities and product functional specifications.
All content on this page by is licensed under a .
Reform No.
Reform Area
Weightage (score)
Recommendation
Remarks
80
Sector Specific
2
Implement an online application system with the following features:
i. Online submission of application without the need to submit physical copy of application
ii. Eliminate physical touchpoint for document submission
iii. Allow option of online payment of application fee
iv. Allow applicant to track status of application online
v. Applicant can download the final certificate online
Already available in the system
List of Functionalities
Corresponding Features
Registration, Login, Creation of User Profile
Provision for Language Selection during first-time registration via Mobile/ Web App.
OTP Based Login for Citizen/ Employee via Mobile/ Web App
Login Credentials for the various hierarchy of employees
Provision of Personalized Profile for Citizen/ Employee on Web App
Applying for a Trade License
Citizen/CSC: Enters Trade Details, Trade Units, Accessories, Owner Details.
Citizen/CSC: Upload Documents
Citizen/CSC: ULB Wise Trade Selection
Citizen/CSC: Calculation Breakup Based on Selected Trade
Citizen/CSC: Multiple Accessories Field Count
Citizen/CSC: Multiple Trade License.
Citizen/CSC: Download/Print Application Summary
Citizen/CSC: Download/PRINT Trade Reference No
Citizen/CSC: View the applied licenses.
Citizen: Pays for the license post verification process.
CSC: Collects Fee post verification.
Trade Licence Issue
Document Verifier : Verify & Forward/ Reject the application
Licensing Inspector: Verify and Forward/ Send back/ Reject the Application.
Licensing Officer: Approve/ Send back the Application
Licensing Officer: Reject/ Cancel the Application
Modification to a Trade License
Edit/ Update the Application based on the Inspection report against the application.
Renewal of a Trade Licence
Renew trade license.
Payment and Fee
Configurable Workflow Rights : Edit & Payment Collection
Payments & Collection : Various Payment Modes
Dashboards and reports
Cancelled Receipt Register Report
TL Collection
TL Application Status- showing the number of licenses approved/rejected.
TL ULB Wise Status
State Dashboard: View Reports for Total Licenses, Licenses Issued, Payment Collected, Payment Distribution
General features
Notifications : SMS Notifications
Charges & Calculation : Calculation Engine
Charges & Calculation : Rebate/ Penalty- Date Based
Charges & Calculation : Ad-Hoc Rebate/ Penalty
Charges & Calculation : Exemptions Trade Type & Owner Type
Configuration masters
Configurable Workflow Rights : Edit & Payment Collection
Configurable Verification & Approval
Stage 0 - Program Setup/ On-Boarding |
Duration | 4-6 weeks |
Entry Criteria | Acceptance Letter/MoU by State |
Exit Criteria |
|
Stage 1 - Program kick-off |
Duration | 4-6 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Stage 2 - Solution Design |
Duration | 4-6 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Stage 3 – Configuration & Customization |
Duration | 6-8 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Stage 4 – UAT & Go Live |
Duration | 2-3 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Stage 5 – Rollout |
Duration | 5-6 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria | State-wide Rollout in batches:
|
Stage 6- Sustenance and Ongoing Improvement |
Duration | Ongoing process |
Entry Criteria |
|
Key Ongoing Activities |
|
Resource Name | No. Of Resources |
Project Head | 1 |
Domain Expert | 2 |
District Nodal Officer | 1 per district |
MIS Expert | 4 |
Stage 0 - Program Setup/ On-Boarding |
Task/Activity | eGov | State Leadership |
Appoint of TL Cell | Consult | Execute |
Finalise funding for the program | Consult | Execute |
Define state -specific procurement process | Consult | Execute |
System Integrator(SI) Team sign-up/onboarding | Consult | Execute |
Finalise Trade License Program Vision | Consult | Execute |
Stage 1 - Program kick-off |
Task/Activity | eGov | TL Cell | SI Team |
Identify & agree on scope and exclusions | Consult | Consult | Execute |
Identify pilot ULBs | Execute | Consult |
Project Kickoff - Implementation Methodology Presentation | Consult | Consult | Execute |
Product Walkthroughs | Consult | Execute |
Define Project Steering Committee structure and Project Governance process | Consult | Consult | Execute |
Define phases of deployment/ rollout | Consult | Execute |
Agreement on Deployment Priorities and high-level delivery timelines | Consult | Execute |
Identify and study all TL process | Consult | Execute |
Finalize Program Success Metrics for Adoption and Governance adhering to the vision of the program | Consult | Consult | Execute |
Stage 1 - Program kick-off |
Task/Activity | eGov | TL Cell | SI Team |
Internal Capacity Building, program logistics at State and ULBs, as per the current scenario | Execute | Consult |
Collection of baseline data to measure end line target for the product (Revenue generated, total properties in ULBs etc.) | Consult | Execute | Consult |
Circulation of baseline data collection templates to the state/SI Team | Execute | Consult |
Stage 2 - Solution Design |
Task/Activity | eGov | TL Cell | SI Team |
Standardisation of all TL processes | Consult | Execute |
Define criteria for success | Execute | Consult |
Initiate policy change, if needed based on Processes defined | Consult | Execute | Consult |
Conduct Product familiarisation workshop | Consult | Execute |
Initiate collection of master data from pilot ULBs | Consult | Execute |
Finalise data migration/collection/sync-up approach | Consult | Execute |
Finalise data validation approach | Execute | Consult |
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc. | Execute | Consult |
Dashboard design finalisation for Program Tracking | Execute | Consult |
Stage 3 – Configuration & Customization |
Task/Activity | eGov | TL Cell | SI Team |
Setting up development environments | Consult | Execute |
Development/customisation of reports and dashboards | Consult | Execute |
Development/Integration of portal | Consult | Execute |
Third-Party Integrations (Payment gateway, Handheld/pos device) | Consult | Execute |
Updation of user manuals and other key documents | Consult | Execute |
Preparation & execution of Test Cases | Consult | Execute |
Setup monitoring, support & maintenance processes, tools and dashboards | Consult | Execute |
TL legacy data collection from Pilot ULBs (at least) | Consult | Execute |
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc. | Execute | Consult |
Verification and Migration of Pilot ULB data | Consult | Execute |
Identification of participants for UAT session | Execute | Consult |
Stage 4 – UAT & Go Live |
Task/Activity | eGov | TL Cell | SI Team |
UAT Environment Setup | Consult | Consult | Execute |
Issues/bug identification and resolution | Consult | Execute |
Regression UAT and sign off from Pilot ULBs/ State | Execute | Consult |
Setting up the Production environment | Consult | Execute |
Setting up Support Centre & processes (Help Desk) | Execute | Consult |
Training user | Execute | Consult |
Training Trainer | Consult | Execute |
Stage 4 – UAT & Go Live |
Task/Activity | eGov | TL Cell | SI Team |
Training the Support Resources | Consult | Execute |
Marketing & promotion activities | Execute | Consult |
Go Live & launch event | Consult | Execute | Execute |
Setup of review and monitoring cadence/team | Execute | Consult |
Stage 5: Rollout |
Task/Activity | eGov | TL Cell | SI Team |
ULB configurations phase wise as per the Project Plan | Consult | Execute |
Verification and Migration of ULB data phase wise as per the Data Agreement Sign Off provided by the State | Execute | Consult |
Establishment of bug ticketing tool for resolving ground level issues by the state team | Consult | Execute |
Training the Users at the district level | Execute | Consult |
Pan State Roll Out – Phase wise | Consult | Execute | Execute |
Stabilise product | Consult | Execute |
Stage 6- Sustenance and Ongoing Improvement |
Task/Activity | eGov | TL Cell | SI Team |
Adoption Review Meetings as per the vision defined for the program | Consult | Execute | Consult |
TL Cell Focuses on Using data for:
| Execute | Consult |
Plans of ongoing Sustenance in Place with respect to:
| Consult | Execute | Consult |
Areas | Assumptions |
Infrastructure |
|
Project Scope |
|
State Team |
|
Documentation |
|
Training |
|
Implementation |
|
PROGRAM |
IMPLEMENTATION |
PRODUCT |
This page provides configuration details for TL master data templates
The DIGIT-Trade License application makes the process of obtaining a Trade License easy, smooth, and transparent. The module, hence, removes the need for manual processing and streamlines the key trade license management functions to provide a better user experience.
DIGIT Trade License module enables citizens to -
Apply for new trade license or renew an existing trade license.
Upload all the relevant documents required for the license.
Make payment for the Trade License (New/Renewal) fee using the online payment gateway.
Receive notifications and alerts by emails or SMS for new application status updates and pending renewals.
Download Trade License, Payment & Acknowledgement Receipts online.
DIGIT Trade License module enables employees to -
Create flexible role-based workflows.
Configure license fees calculation logic.
View custom dashboards for module statistics.
Filter search results using advanced configurable search parameters.
Receipt Register
Application Status
Cancelled Receipt Register
ULBwise Collection Report
ULBwise Application Status
Define Trade Types
Map Trade Category to listed Trade Types
The Trade Type can be defined as the next (2nd) level classification of Trade. There can be multiple trade types and the list may vary from one State/ULB to another.
The table above contains sample Trade Type data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Select the relevant Trade Category Code from the available drop-down list of Trade Category. This will map the listed Trade Type to the corresponding Trade Category.
Enter a unique Trade Type Code to identify the type of trade.
Enter a Trade Type Name (In English).
Enter the Trade Type Name (In Local Language).
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Once the are defined, the next task is to -
All content on this page by is licensed under a .
Sr. No. | Trade Type Code* | Trade Type Name* (In English) | Trade Type Name* (In Local Language) | Trade Category Code* |
1 | TRADE_TYPE_MEDICAL | Hospital | अस्पताल | TC1 |
2 | TRADE_TYPE_HOTEL | Hotels | होटल | TC2 |
Sr. No. | Checklist Parameter | Example |
1 | The format of the Trade Type Code defined should be alphanumeric and unique | TRADE_TYPE_MEDICAL TRADE_TYPE_HOTELS |
2 | Trade Type Name (in either language) should not contain any special characters | Hospital: [Allowed] #Hospital! : [Not allowed] |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Trade Type Code | Alphanumeric | 64 | Yes | The Code assigned to the Trade Type. Eg: TRADE_TYPE_MEDICAL is assigned to Hospitals |
3 | Trade Type Name (In English) | Text | 256 | Yes | Name of the Trade Type in English. Eg: Goods, Services etc. |
3 | Trade Type Name (In Local Language) | Text | 256 | Yes | Name of the Trade Type in Local Language (as decided). Eg: Service is described as “सर्विस” in Hindi |
4 | Trade Category Code | Reference | 64 | Yes |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Trade Type can be further sub-classified into Trade Sub Type depending on the trade ontology existing in the ULBs or States. Hence, Hotels can be further classified into Dhabas in North India or Udupis in South India.
Once the Trade Type(s) are defined, the next task is to -
Define Trade Sub Types
Map Trade Types to corresponding Trade Sub Types
The table above contains sample data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Select the relevant Trade Type Code from the Trade Type master data. This will map the listed Trade Sub Type to the selected Trade Type.
Enter a unique value for Trade Sub Type Code.
Enter the English name for Trade Sub Type Name (English).
Enter the local name for the Trade Sub Type Name (Local Language).
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Configuration Data Templateconfiguration-data-template-trade-master-3- (1).xlsx - 17KB
Sample Data Templatesample-configuration-data-template-trade-master-filled-3-.xlsx - 19KB
Structure sub type is the second level of classification of the premises where the trade has to be established and conducted. This is mostly used as management information in the trade detail.
The table above contains sample data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.
Contact the person who shared this template with you to discuss and clear your doubts.
Enter the relevant structure sub types with its proper mapping with structure type.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
A separate entity-specific checklist is not needed for this entity data template.
Configuration Data Templateconfiguration-data-template-structure-subtype_v1-1-.xlsx - 10KB
Sample Datasample-configuraion-data-structure-type-and-subtype-2-.xlsx - 9KB
Once the Trade Ontology is defined, the next step is to allocate the license fee associated with the Trades.
Dependent on the Trade Classification Level (Types/ Subtypes), the fee allocated might be the same across the Sate or could vary from ULB to ULB. There could be a distinct fee(s) for two different types of applications (new and renewal).
Following are the key tasks to be executed :
Allocate the License Fee according to Trade Classification Level (Types/Subtypes).
Map the License fee with respective Trade Classification Level.
The table above contains sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
Identify the “Trade Sub Types” that exists at a ULB/ State level.
Collect the above information and feed it below the “Trade Sub Type Name” column accordingly. The Description of Trade Sub Type Name must be provided as per the language specified in the respective column.
Add the “Trade Sub Type Code” respectively against the identified trade type(s).
Fill in the New License Fee & New Renewal Fee accordingly. The New License Fee & Renewal Fee can be the same as well as distinct, depending on the by-laws/ mandate followed by the State/ULB.
Fill in the fields related to Units of Measurement (UOM Unit, From/To) for the available trades only.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Configuration Data Templateconfiguration-data-template-trade-master-4-.xlsx - 23KB
Sample Data Templatesample-configuration-data-template-trade-master-filled-4- (1).xlsx - 24KB
This service is used to issue a license to the user after verification. The service is designed in such a way that it can be used to serve different type of licenses. Currently used to issue trade licenses, perform stakeholder registration and issue lockdown pass. The service is integrated with workflow where we can define the steps for approval of the application. Once the application is approved the license is generated.
Before you proceed with the documentation, make sure the following pre-requisites are met -
Java 8
Kafka server is up and running
egov-persister service is running and has tl-services persister config path added in it
PSQL server is running and database is created
Used for license generations in trade licenses, stakeholder registration and issue lockdown pass
Define roles to applicants on successful application to access Building Plan Approval services at the time of stakeholder registration
Generate application number and license number
Support workflows
Provide notification on various status changes for an application
Add MDMS configs required for Trade License and BPA stakeholder registration and restart MDMS service
Deploy the latest version of tl-services service
Add tl-service persister yaml path in persister configuration and restart persister service
Add Role-Action mapping for API’s
Create businessService (workflow configuration) according to trade license and stakeholder registration
Add tl-service indexer yaml path in indexer service configuration and restart indexer service
Following application properties in the Trade License service are configurable.
The trade-license service is currently used to issue trade licenses, perform stakeholder registration and issue lockdown pass.
Provide backend support for the different license registration process.
Mseva and SMS notifications on application status changes.
The elastic search index for creating visualizations and Dashboards.
Bpa Stakeholder registration provides new roles to the user to access the Building Plan Approval system.
Supports workflow which is configurable
To integrate, host of tl-services service should be overwritten in the helm chart.
{servicename}/_create/ _create should be added as the create endpoint for creating any license in the system
{servicename}/_search/ _search should be added as the search endpoint. This method handles all requests to search existing records depending on different search criteria
{servicename}/_update/ _update should be added as the update endpoint. This method is used to update fields in existing records or to update the status of the application based on workflow.
In all below endpoints if the service name is BPAREG it is treated as a stakeholder registration application and if it is TL or if it is absent then the application is treated as trade license application.
Stakeholder registration APIs:- https://www.getpostman.com/collections/d18b79ccfb69ee8bb526
Trade-License APIs:- https://www.getpostman.com/collections/99f98723c45f97024831
The Trade Category List can be defined as the primary or the 1st level classification “head” for trade(s) defined at a ULB/State Level.
The table above contains sample Trade Category data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Enter a unique Trade Category Code for each trade head.
Enter the Trade Category Name. Some trade categories are already defined in the master. Add new categories as required.
Enter the Trade Category Name (Local Language).
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Configuration Data Templateconfiguration-data-template-trade-master-2-.xlsx - 17KB
Sample Data Templatesample-configuration-data-template-trade-master-filled-2-.xlsx - 19KB
An illustrative guide to using the TL module
The Trade License (TL) module offers the citizens and governance bodies a convenient and transparent means of processing trade licenses. Trade license is the permission issued by the local governing bodies to carry on specified business or trading activity within the authorized area. It is a mandatory document required to run a business or commercial activity of any type.
The TL module enables citizens to apply for trade licenses or renew existing licenses online. It facilitates the governing bodies to validate and approve the license applications.
This section guides you through the details of using the TL module for each role. Click on the relevant role below to learn more about how to use the TL system.
The Code assigned to the . Eg: TC1 For Goods, TC2 for Services
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by is licensed under a .
Sr. No.
Trade Sub Type Code*
Trade Sub Type Name* (In English)
Trade Sub Type Name* (In Local Language)
Trade Type Code*
1
TRADE_SUBTYPE_CLINIC
Clinic
क्लिनिक
TRADE_TYPE_MEDICAL
2
TRADE_SUBTYPE_DHABA
Dhaba
ढाबा
TRADE_TYPE_HOTEL
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Trade Sub Type Code
Alphanumeric
64
Yes
The Code assigned to the Trade Sub Type. Eg: TRADE_TYPE_Dhaba is assigned to Hotels
2
Trade Sub Type Name (In English)
Text
256
Yes
Name of the Trade Sub Type in English. Eg: Clinic
3
Trade Sub Type Name (In Local Language)
Text
256
Yes
Name of the Trade Sub Type in Local Language (as decided). Eg: Dhaba is described as “ढाबा” in Hindi
4
Trade Type Code
Reference
64
Yes
The Code assigned to the Trade Type. Eg: TRADE_TYPE_MEDICAL is assigned to Hospitals
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
The format of the Trade Sub Type Code defined should be text and unique
TRADE_SUBTYPE_CLINIC
2
Trade Type Name (in either language) should not contain any special characters
Clinic: [Allowed]
#Clinic! : [Not allowed]
Sr. No.
Code*
Structure Sub Type* (In English)
Structure Sub Type* (In Local Language)
Structure Type Code*
1
PUCCA
Pucca
पक्का
IMMOVABLE
2
KUTCHA
Kutcha
कच्चा
IMMOVABLE
3
HDV
Hand Driven Vehicle
हाथ चालित वाहन
MOVABLE
4
MDV
Motor-Driven Vehicle
मोटर चालित वाहन
MOVABLE
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Code
Alphanumeric
64
Yes
Unique code to identify each and every record uniquely
2
Structure Sub Type* (In English)
Text
256
Yes
Structure sub type in English
3
Structure Sub Type* (In Local Language)
Text
256
Yes
Structure sub type in local language e.g. in Hindi, Telugu etc.
4
Structure Type Code*
Reference
64
Yes
Unique code of structure type to establish the mapping with Structure Type
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of.
Sr. No
Trade Sub Type Code*
Trade Sub Type Name (In English)
New License Fee*
Renewal License Fee*
UOM
UOM From
UOM To
1
TRADE_SMALL_BAKERY
Small Bakery
2500
2000
Workers
1
20
2
TRADE_SMALL_BAKERY
Small Bakery
3000
2500
Workers
21
30
2
TRADE_MED_BAKERY
Medium Bakery
5000
4500
Workers
1
30
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Trade Sub Type Code
Reference
64
Yes
The Code assigned to the Trade Sub Type. Eg: TRADE_SMALL_BAKERY is assigned to Bakery
2
Trade Sub Type Name (In English)
Text
256
Yes
Name of the Trade Sub Type in English. Eg: Small Bakery
3
New License Fee
Decimal
(6,2)
Yes
The fee charged when the license applied for the respective trade for the first time.
4
Renewal License Fee
Decimal
(6,2)
Yes
The fee charged when the license applied for the respective trade for the renewal.
5
UOM
Text
64
No
The Units of Measurement” associated with the Trade. Eg: Workers is the UOM associated with the trade “Bakery”
6
UOM From
Integer
6
No
Initial Range from which the “Units of Measurement” is applicable for a Trade
7
UOM To
Integer
6
No
Final Range to which the “Units of Measurement” is applicable to a Trade
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
Trade Type Name (In either Language) should not contain any special characters
Small Bakery: [Allowed]
#Small_Bakery! : [Not allowed]
Property
Value
Remarks
egov.idgen.tl.applicationNum.format
PB-TL-[cy:yyyy-MM-dd]-[SEQ_EG_TL_APL]
The format of the TL application number
egov.idgen.tl.licensenumber.format
PB-TL-[cy:yyyy-MM-dd]-[SEQ_EG_PT_LN]
The format of the TL license number
egov.idgen.bpa.applicationNum.format
PB-SK-[cy:yyyy-MM-dd]-[SEQ_EG_TL_APL]
The format of the Stake holder application number
egov.idgen.bpa.licensenumber.format
PB-SK-[cy:yyyy-MM-dd]-[SEQ_EG_PT_LN]
The format of the Stake holder license number
egov.tl.max.limit
100
Max number of records to be returned
citizen.allowed.search.params
tenantId, applicationNumber, limit, offset, licenseNumbers
The search parameters on which citizen can search
employee.allowed.search.params
tenantId, applicationNumber, applicationType, status, mobileNumber, fromDate, toDate, licenseNumbers, oldLicenseNumber, limit, offset
The search parameters on which employee can search
persister.save.tradelicense.topic
save-tl-tradelicense
The name of kafka topic on which create request is published
persister.update.tradelicense.topic
update-tl-tradelicense
The name of kafka topic on which update request is published
persister.update.tradelicense.workflow.topic
update-tl-workflow
The name of kafka topic on which update request is published
Title
Link
Local Setup
API Swagger Documentation (Trade License)
API
Description
{servicename}/_create, _create
This API is used to create an application for the license in the system. Whenever an application is created an application number is generated and assigned to the application for future reference.
{servicename}/_search, /_search
This API is used to search the applications in the system based on various search parameters like mobile number, the application number, status etc.
{servicename}/_update, _update
The _update API is used to update the application information or to forward the application from one state to another.
In the case of the stakeholder registration if the application reaches the last stage the role depending on the license type is given to the user.
{servicename}/{jobname}/_batch, /_batch
Searches trade licenses which are expiring and send a reminder SMS to owner's of the licenses
Sr.No.
Trade Category Code*
Trade Category Name* (In English)
Trade Category Name* (In Local Language)
1
TC1
Goods
सामग्री
2
TC2
Services
सर्विस
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Trade Category Code
Alphameric
64
Yes
The Code assigned to the Trade Category. Eg: TC1 For Goods, TC2 for Services
2
Trade Category Name (In English)
Text
256
Yes
Name of the Trade Category in English. Eg: Goods, Services etc.
3
Trade Category Name (In Local Language)
Text
256
Yes
Name of the Trade Category in Local Language (as decided). Eg: Service is described as “सर्विस” in Hindi
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
The format of the Trade Category Code defined should be alphanumeric and unique
TC1: Goods
TC2: Services
2
Trade Category Name (In either Language) should not contain any special characters
Goods: [Allowed]
#Goods! : [Not allowed]
User Role | Scope of Action | Role Description |
Citizen | Apply for Trade License Pay for license Track status of the license application Download payment receipts | Individuals and business entities |
Counter Employee (CE) | Apply for a Trade License Complete the Payment for Trade License Keep a track of the status of the Trade License Download/Print payment receipts, applications, TL certificate | Counter employees who assist citizens and file new trade license applications or renewal applications on their behalf |
Document Verifier (DV) | Verify and forward Send Back Edit | Employees responsible for verifying the supporting documents submitted by citizens for new trade license or renewal of existing licenses |
Field Inspector (FI) | Verify and forward Send Back Reject Edit | Employees who go on to the field (i.e. location of trade) and physically verifies the information provided by the applicant is correct, checks safety precaution followed by the trade owner |
Approver | Approve Send Back Reject Cancel TL | The employee who has the final authority to approve or reject the application |
This section illustrates the steps for different employee user roles at the ULB level
DV is responsible for verifying the supporting documents uploaded by the applicants or the counter employee on behalf of the applicant.
The DV can
Trade license applications are rejected if the supporting documents uploaded by the applicant fails to comply with the license requirements or the details provided in the form are incorrect.
To reject applications navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The DV verifies and forwards the TL application to the Field Inspector if the DV finds all information and documents provided by the applicant correct.
To verify and forward the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Verify and Forward button. Select the relevant Assignee Name from the list of available employees for subsequent processing.
Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Verify and Forward button.
The TL application is assigned to the selected Assignee for subsequent processing.
To edit applications navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Edit button. Change any details in the form as required.
FI is responsible for verifying the field details provided by the applicants.
The FI can
FI sends back the applications to the citizens if some vital information is missing in the application or there is a mistake in the information provided.
To send applications back to the citizen navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Send Back to Citizen button. Enter any Comments stating why the application is sent back.
Click on the Upload Files button to upload any files or images in context to the application. Click on the Send Back to Citizen button.
The system displays a success acknowledgement message stating that the application is sent back to the initiator.
The FI can send back the TL application to the DV if there is any mistake or lapses in the document verification process.
To send back applications to the DV navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Send Back button.
Select the Assignee Name who will be responsible for verifying the application. Enter any Comments as additional information to the assignee stating why the application is sent back. Click on the Upload Files button to upload any files or images in context. Click on the Send Back button.
The application is assigned back to the selected assignee for verification of documents.
Trade license applications are rejected if the supporting documents uploaded by the applicant fails to comply with the license requirements or the details provided in the form are incorrect.
To reject applications navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The FI verifies and forwards the TL application to the Approver if the information and documents provided by the applicant are correct.
To verify and forward the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Verify and Forward button. Select the relevant Assignee Name from the list of available employees for subsequent processing.
Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Verify and Forward button.
The TL application is assigned to the selected Assignee for subsequent processing.
To make any changes in the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Edit button. Change any details in the form as required.
The Approver is responsible for the final approval of the TL application.
The Approver can
The Approver can send back the TL application to the FI or DV if there is any mistake or lapses in the document verification process.
To send back applications to the DV or FI navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Send Back button.
Select the Assignee Name who will be responsible for verifying the application. Enter any Comments stating why the application is sent back. Click on the Upload Files button to upload any files or images in context. Click on the Send Back button.
The application is assigned back to the selected assignee for verification of application.
Trade license applications are rejected if the supporting documents uploaded by the applicant fails to comply with the license requirements or the details provided in the form are incorrect.
To reject applications navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The Approver signs off the TL application once the information and documents provided by the applicant are found correct. The TL Certificate is issued once the application is approved.
To approve the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Approve button.
Select the relevant Assignee Name from the list of available employees for subsequent processing. Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Approve button.
The TL application is approved and the TL Certificate is issued to the applicant. Click on the Download or Print button to download or print the TL Certificate.
Along with the rates, the Trade License application process does require certain documents as an attachment of proof. The proof can be defined by a set of documents ranging from
Identification Proof (Drivers License/ Voter Card/ Adhaar/ Pan etc.)
Trade Premises Proof (Lease Agreement, Electricity Bills, etc).
Misc Documents (Affidavit, Self- Declaration, etc).
The Number and the Documents required could vary across the State, ULB(s), and might be dependent on Trade Subtypes, all of which are totally configurable on DIGIT.
The table above contains sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify the “Trade Sub Types” that exists at a ULB/ State level.
Collect the above information and feed it below the “Trade Sub Type Name” column accordingly. The Description of Trade Sub Type Name must be provided as per the language specified in the respective column.
Add the “Trade Sub Type Code” respectively against the identified trade type(s).
Fill in the *Document 1 & *Document 2 columns respectively.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Configuration Data Templateconfiguration-data-template-trade-master-4- (1).xlsx - 23KB
Sample Datasample-configuration-data-template-trade-master-filled-4-.xlsx - 24KB
The structure type is the first level of classification of the premises where the trade has to be established and conducted. This is mostly used as management information in the trade detail.
The table above contains sample data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.
Contact the person who shared this template with you to discuss and clear your doubts.
Enter the relevant structure types.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
A separate entity-specific checklist is not needed for this entity data template.
Configuration Data Templateconfiguration-data-template-structure-type_v1-1- (1).xlsx - 10KB
Sample Datasample-configuraion-data-structure-type-and-subtype-1-.xlsx - 9KB
A comprehensive guide to an effective module demo
Learn how to apply for new trade license, renew and pay trade license fee
Citizens represent individuals, communities, or business entities who are the system end-users. The TL module allows business owners to apply for a trade license online or even apply for renewal of an existing license.
The citizen can also approach the Counter Employee (CE) to submit new TL applications or raise renewal requests for existing licenses.
The Citizen or CE role can -
Download payment receipts, license certificates, or applications
Citizens or CE can apply for a new trade license through the DIGIT web portal or the DIGIT mobile app. To apply for a new TL click on the Trade License card available in the Citizen Services section of the DIGIT home page.
Click on the New Application button on the screen. This will open the TL application form page.
The system displays the Required Documents - Trade License list. Click on the Print button to get a hard copy of the documents list for reference.
Click on the Apply button to proceed with the trade license application. The form sections are available on the top of the page.
The New Application form page contains various sub-sections -
Trade Details
Owner Details
Documents
Summary
The system displays the Trade Details page. The page contains 4 panels - Trade Details, Trade Unit, Accessories, and Trade Location Details.
In the Trade Details panel, enter the following details.
Select the applicable Financial Year. Select the relevant License Type from the drop-down list. Enter the Name of Trade. Select the appropriate Structure Type and Structure Sub Type. Enter the Trade Commencement Date. Enter the Trade GST No. if applicable. Enter the Operational Area (Sq Ft). and the Number of Employees for the listed trade.
In the Trade Unit panel, provide the following details -
In the Accessories panel, enter the following details -
Enter the following details in the Trade Location Details panel -
Select the City. The system displays the registered city by default. Enter the Property ID/UID, Door/House No., Building/Colony Name, Street Name, Mohalla, and Pincode for the listed premises. Click on the map icon to provide the GIS coordinates for the location. Enter the Electricity Connection No. for the listed premise.
Click on the Next Step button to move to the Owner Details section.
Select the Type of Ownership and the Type of Sub-Ownership. Provide the following information in the Owner Information section.
Enter the owner Mobile No., Name, Father/Husband’s Name. Check Father or Husband to indicate the Relationship of the given name with the owner. Check the applicable Gender of the owner. Enter the Date of Birth of the owner. Enter the owner’s Email ID, PAN No., Correspondence Address. Select the applicable Special Owner Category from the drop-down list.
Click on the Next Step button to move to the Documents section.
Click on the Upload File button to browse and upload the required documents for processing the TL. Click on the Next Step button once all the documents are uploaded.
The Application Summary page provides all the information filled in by the applicant. The Application Summary panel on top of the page provides the Trade License Tax and Total Amount details. This amount has to be paid by the applicant.
Click on the View Breakup button to fetch the fee details.
The Trade License Application No. is displayed along with this message. Click on the Download button to download a copy of the application. Click on the Print button to print the application.
Citizens can renew their existing trade applications on the DIGIT portal. CE can also apply for TL renewal on behalf of the citizens. To renew TL navigate to the home page and then click on the Trade License option. Click on My Applications. Click on the Renew Now button on the specific license.
The system will display the license details. Click on the Take Action button. Click on the Edit button to make any changes to the existing license details. Click on the Submit for Renewal button to apply for renewal.
The Trade License is submitted for renewal.
To search for a submitted application or track the status of submitted applications navigate to the Trade License home page.
Enter at least one of the listed search parameters in the Search panel. The listed search parameters include
Application No.
Trade License No.
Owner Mobile No.
Application Type
From Date
To Date
Application Status
Click on the Search button. The system displays the records matching the listed parameter.
Click on the Application No. link. The screen displays the application details. Scroll down the page to view the details.
Click on the Take Action button and click on Edit option to edit the form details. The Task Status panel on the top of the Application displays the current status of the application.
Click on the View History button on the top right corner of the Task Status panel to view the actions taken on the application to date.
Applicants have to pay the license fee once the TL application is approved. The application status changes to Pending for Payment. To make payment for the trade license fee click on your Application No. to open the application. Click on the Take Action button.
Click on Pay. Enter the payment details. The system allows you to pay by cash, cheque, or credit/debit card. Click on the Cash, Cheque, Credit/Debit Card tab depending on the preferred payment method.
Enter payment details as requested on the screen. Click on the Generate Receipt button to confirm the payment. The screen displays the success acknowledgement message along with the Payment Receipt No.
Once the payment is complete the Trade License Certificate is issued. Click on the Download or Print button to download or print the Payment Receipt and Trade License Certificate.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Select the applicable Trade Category, Trade Type, Trade Sub Type, UOM (Unit of Measurement), and UOM value. Click on the icon to add more trade units.
Select the applicable Accessories for the listed trade. Select the corresponding UOM for the selected accessories. Enter the UOM value. Enter the Accessory Count. Click on the icon to add more accessories.
Scroll down the page to view the filled-in details. Click on the Edit icon to make any changes to the application. Click on the Submit Application button. The system displays the Application Submitted Successfully acknowledgement message.
All content on this page by is licensed under a .
Sr. No.
*Trade Subtype Code
*Trade Subtype Name (In English)
*Application Type
*Document 1
*Document 2
1
TRADE_SMALL_BAKERY
Small Bakery
New
PAN/VOTER ID
LAND LEASE
2
TRADE_SMALL_BAKERY
Small Bakery
Renewal
PAN/VOTER ID
ELEC BILL
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Trade Sub Type Code
Reference
64
Yes
The Code assigned to the Trade Sub Type. Eg: TRADE_SMALL_BAKERY is assigned to Bakery
2
Trade Sub Type Name (English)
Text
256
Yes
Name of the Trade Sub Type in English Eg: Clinic
3
Application Type
Text
256
Yes
Type of application for which the documents related to trade are configured. It can either be new or renewal
4
Document 1
Reference
256
Yes
The primary document required as a verification parameter. Refer to the Standard Document List
5
Document 2
Reference
256
Yes
The Secondary Document required as a verification parameter. Refer to the Standard Document List
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
Trade Sub Type Name (In either Language) should not contain any special characters
Small Bakery: [Allowed]
#Small_Bakery! : [Not allowed]
Sr. No.
Code*
Structure Type* (In English)
Structure Type* (In Local Language)
1
IMMOVABLE
Immovable
अचल
2
MOVABLE
Movable
चल
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Code
Alphanumeric
64
Yes
Unique code to identify the records uniquely
2
Structure Type* (In English)
Text
256
Yes
Structure type in English
3
Structure Type* (In Local Language)
Text
256
Yes
Structure type in local language e.g. Hindi, Telugu etc.
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of