Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Introduction

Alongside rates, the Trade License application process does require certain documents as an attachment of proof. The proof can be defined by 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.

Data Table

Sr. No

*Trade Sub- Type Code

*Trade Subtype Name (Eng)

*Application Type

*Document 1

*Document 2

*Tenant ID

1

TRADE_BAKERY

Small Bakery

New

PAN/VOTER ID

LAND LEASE

MOGA23

2

TRADE_BAKERY

Small Bakery

Renewal

PAN/VOTER ID

ELEC BILL

MOGA23

Procedure

Field(s) Description

  • Sr.No: Defines the serial no of the line item.

  • Trade Sub Type Code: Unique Identifier for Trade Sub Type which is used as a reference for child configuration mapping.

  • Trade Sub Type Name (Eng): Nomenclature of “Trade Sub Type ” in English.

  • Application Type: Type of application for which the documents related to trade are configured. It can either be new or renewal.

  • Document 1: The Primary Document Required as a verification parameter. This is configurable on the application type.

  • Document 2: The Secondary Document Required as a verification parameter. This is configurable on the application type.

  • Tenant ID: The Boundary (State/ULB) for which the data is being collected.

PS: The number of documents can be increased depending upon the State/ULB requirement.


Steps to fill data

  • 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).

    • The format of the Trade Sub Type Code will either be predefined or can be a continuous numeric/ alphanumeric sequence as per the requirement.

  • Fill in the *Document 1 & *Document 2 columns. The input in these respective columns must be adhered to codes as per Documents Master.

  • Fill in the Tenant ID accordingly. The input of this column must be by defined boundary code (ULB Code/Other) as per the boundary master.

Validations

  • All the fields with * sign are mandatory to be filled in. Without this information, the system configurations cannot be executed.

  • A “single entry” should be made against the respective column. Incase of multiple entries, continuation must be followed.

  • The “Trade Sub Type Name” must be provided in the required language as mentioned against the respective column.

  • The format of Trade Sub Type Code must be informed to the individual/team responsible for filling in the master data.

  • The Code for Document 1 & Document 2 must be as per the Documents Master and not any random code.

  • The Tenant ID must be by the code defined as per the Boundary Master, depending on the requirement (ULB/ State Level).

Attachments

  • Following is the blank template for Trade License Documents Attachment.

  • Refer to “Trade License Documents” in the uploaded template. This consists of sample data for reference.

  • No labels