DIGIT Specifications
PlatformUrbanHealthPublic FinanceSanitation
  • Specifications Overview
    • Standardisation Approach
  • Common Service Specs
    • Access Control
    • Analytics
    • Billing
    • Collection
    • Dashboard Analytics
    • Decision Support System Ingest
    • Document Controller
    • Employee
    • Encryption
    • Filestore
    • ID Generation
    • Inbox
    • Indexer
    • Master
    • Master Data Management
    • OTP
    • Payment Gateway
    • PDF Generation
    • URL Shortening
    • User
    • Workflow
  • Domain Service Specs
    • Attendance
    • Bank Account
    • Billing Calculator
    • Birth-Death
    • Building Plan Approval
    • Building Plan Calculator
    • Campaign
    • Campaign Delivery
    • Contracts
    • Estimates
    • eChallan
    • Facility
    • Faecal Sludge Management (FSM)
    • Fire NOC
    • Fire NOC Calculator
    • Household
    • Individual
    • Inventory
    • Land
    • Muster Roll
    • National Dashboard Ingest
    • No Objection Certificate
    • Organization
    • Planning
    • Product
    • Project
    • Property Registry
    • Property Tax Calculator
    • Public Grievance Redressal
    • Registration
    • Sewerage Connection
    • Stock
    • Supervision
    • Sync
    • Trade Licence
    • Trade Licence Calculator
    • User Events
    • Vehicle Registration
    • Vendor Registration
    • Water Connection
  • Archived-docs
    • DIGIT Urban Service Specs
      • Property Tax Service
        • Property Tax Taxonomy
        • Property Tax Data Model
        • Property Tax Service API
      • Public Grievance Redressal Service
        • Public Grievance Redressal Taxonomy
        • Public Grievance Redressal Data Model
        • Public Grievance Redressal Service API
      • Trade License Service
        • Trade License Taxonomy
        • Trade License Data Model
        • Trade License API
      • Fire NOC Service
        • Fire NOC Taxonomy
        • Fire NOC Data Model
        • Fire NOC API
      • Miscellaneous Collection Service
        • Miscellaneous Collections Taxonomy
        • Miscellaneous Collections Data Model
        • Miscellaneous Collection API
      • Online Building Plan Approval Service
        • Online Building Plan Approval Taxonomy
        • Online Building Plan Approval Data Model
        • Online Building Plan Approval Service API
      • Water & Sewerage Service
        • Water & Sewerage Taxonomy
        • Water Service Data Model
        • Sewerage Service Data Model
        • Water & Sewerage Service API
      • Birth & Death Service
        • Birth & Death Taxonomy
        • Birth & Death Data Model
        • Birth & Death Service API
    • DIGIT Public Finance Management Service Specs
      • iFIX Master Data Service API
      • Adapter Master Data Service API
      • mGramSeva iFIX Adapter Service API
      • iFIX Department Entity Service API
      • Fiscal Event API
    • DIGIT Health Service Specs
      • Health Service Data Model
      • Health Service API
    • DIGIT Sanitation Service Specs
      • Faecal Sludge Management Service
        • Faecal Sludge Management Data Model
        • Faecal Sludge Management Service API
Powered by GitBook

​All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page
  • Overview
  • Actors
  • Interaction diagram
  • Process Flow
  • TL Service Entity Details

Was this helpful?

Export as PDF
  1. Archived-docs
  2. DIGIT Urban Service Specs

Trade License Service

PreviousPublic Grievance Redressal Service APINextTrade License Taxonomy

Last updated 2 years ago

Was this helpful?

Overview

The origin of a Trade License (TL) links to a mandatory license required to carry out dangerous and offensive trades and also trades that have health implications. Currently from shops to street vendors to restaurants and a lot of other trades must have a TL to carry out their business.

Why is a trade license required? The intent is to ensure trades that meet the prescribed health or safety guidelines. It ensures possible risks are inspected and meet the state’s necessary quality, health and safety standards. And, over time the trade license department has evolved into a new revenue opportunity stream for the ULB and now covers different types of trades.

Who needs a trade license? This varies from one state to another. In Chennai, registered companies do not need a TL. Every state publishes a list of all trades/trade types that need to procure a TL to carry out their business.

Actors

Citizen - Citizen is the person who intends to do business and applies for a trade license with the ULB.

Clerk - Clerk is an employee in ULB whose job is to perform first-level scrutiny of any application that is reaching ULB. He/She verifies the application checks for its correctness and has the authority to ask for more information or forward to the next officer in the hierarchy or reject citing the reasons for rejection.

Revenue Inspector - The Revenue Inspector is responsible for inspecting the place where trade is operating, checks for safety, security and sanitation compliance with the applied trade type. This actor has the authority to ask the applicant to make some modifications to comply with the rules or forward to the next officer in the hierarchy or reject citing the reasons for rejection.

Revenue Officer - The Revenue Officer is responsible for all the revenue streams in the ULB and has the authority to decide whether to issue the trade licenses considering the recommendation of the revenue inspector and the clerk. He /She can issue a license or reject the applications citing the reasons for rejection.

Interaction diagram

Process Flow

TL Service Entity Details

All content on this page by is licensed under a .

Trade License Data Model
​
eGov Foundation
Creative Commons Attribution 4.0 International License
Creative Commons License