...
Introduction
An approval process is the method a state or ULB uses to approve anything from documents, invoices, budgets, and purchase orders.
Sub schemes are defined under the schemes by the Centre or state government to be associate with a fund and for a time. The Sub scheme shall be defined under a scheme.
Data Table
Sr. No. |
...
Actions
...
Assistant
...
Supervisor
...
Approver
...
1
...
Forward
...
Yes
...
No
...
No
...
2
...
Create and Forward
...
Yes
...
Yes
...
Yes
...
4
...
View
...
Yes
...
Yes
...
Yes
...
5
...
Comment
...
Yes
...
Yes
...
Yes
...
6
...
Verify and Forward
...
Yes
...
Yes
...
No
...
7
...
Reject
...
No
...
Yes
...
Yes
...
8
...
Send Back
...
No
...
Yes
...
Yes
...
9
...
Approve
...
No
...
No
...
Yes
Procedure
Data Definition
...
Sr No: Defines the serial no of the line item
...
Action: The action refer to the steps which are processed while performing the steps Finance process
...
Assistant: A person who is in charge of initiating the action in the Finance process.
...
Supervisor: A person who is in charge to review the action initiated before approving
...
Scheme Code* | Sub Scheme Name * | Sub Scheme Code * | Valid From * | Valid To * | Department Code | Initial Estimate Amount | |
1 | 10 | Storm Water Drains | 1003 | 01/05/2018 | 01/06/2021 | PHS | 2500000 |
2 | 20 | Solid Waste Management- SWM | SBM02 | 01/06/2017 | 01/07/2020 | TP | 1000000 |
3 | 30 | Street Lights | 5001 | 01/03/2016 | 30/04/2019 | TP | 2000000 |
Note: Data given in the table is a sample data.
Procedure
Data Definition
Sr No | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
|---|---|---|---|---|---|
1 | Scheme Code | Alphanumeric | 50 | Yes | A unique code assigned to individual Scheme, this will facilitate the user to assign the sub scheme under the individual scheme and also helps in tracking the utilization of the Scheme. Click on Schemes to view the scheme master data. |
2 | Sub Scheme Name | Text | 50 | Yes | The Sub Scheme Name will facilitates the user to record the transaction against the individual sub scheme and also helps in tracking the utilization of the sub scheme. |
3 | Sub Scheme Code | Alphanumeric | 50 | Yes | A unique code assigned to individual Sub Scheme |
4 | Valid From | Date | N/A | Yes | The Date on which the Scheme Started, this will help to facilitate the receive of funds from Central Sponsored Schemes and State Sponsored Schemes. |
5 | Valid To | Date | N/A | Yes | The Date on which the Scheme will End, this will help to facilitate the end date by when the funds from Central Sponsored Schemes and State Sponsored Schemes need to be utilized. |
6 | Department Code | Text | 250 | No | The sub scheme can be linked to the individual department, so user while recording the transaction can assign the department. Click ULB's Departments for the master data. |
7 | Initial Estimate Amount | Numeric | 50 | No | The initial Estimate Amount approved amount under the sub scheme can be updated while creating the sub scheme master record. This will facilitate the user in utilizing the amount within the estimated amount. |
Steps to fill data
Download the workflow template attached to this page.
Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.
Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
Identify all
...
sub schemes with the
...
State..
Start filling the data starting from serial no. and complete a record at once. repeat this exercise till the entire data is filled into a template.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
Checklist
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.
Common Checklist
This checklist covers all the activities which are common across the entities.
Sr. No | Checklist Parameter | Example |
|---|---|---|
1 | Make sure that each and every point in this reference list has been taken care of. |
Validations
This data should be collected at State level
Entity Specific Checklist
This checklist covers the activities which are specific to the entity.
Sr. No. | Activity | Example |
1 | The date format should be as per example and the Start date should be greater than the current date and end date. | DD/MM/YYYY : [Allowed] YYYY/DD/MM : [Not allowed] |
2 | The name should be unique and should not contain any special characters | AMRUT : [Allowed] #AMRUT! : [Not allowed] |
3 | The scheme name mapped should be as per the scheme master entity | AMRUT, SWM |