s for CSS Schemes on e-lekha 1. The Current Code Of Accounts (COA) adopted by the Civil Accounts Organisation captures the i) 3 digit Demand for Grant No. ii) 13 Digit Functional Description comprising of (Major Head 4 + Sub Major 2 + Minor Head 3 + Sub Head 2 + Detail 2 ) iii) 2 Digit Object Head viz. Salaries, Office Expenses, TA, etc iv) 1 Digit Category viz. Plan, Non Plan, Charged, Voted, Public Account 2. The COA do not capture the geographical location, the destination implementation agency, the scheme definition and hierarchy which is essential for segmented reporting on schemes geographical location wise, schemes wise, agency wise. The COA also does not identify the type of release (eg. Expenditure or Transfer). In order to circumvent the problems (as listed in 1 and 2 above) vis-à-vis Schemes monitoring on e- Lekha as a single windows interface for all schemes of the Government of India, a sanction ID to capture all the required subsidiary information along with the COA is elaborated as below: The proposed Scheme Monitoring on e-lekha would include: Scheme Definition and Multi Hierarchy structure with Parent child relationship so as to enable reporting against different levels. Geographical Entity definition (Adoption of Census Codes) Multi level Agency Stake Holder Definition again with hierarchical relationships. Definition of Sanction as Expenditure or Transfer. NIC-ACID- e-lekha-psmsig Page 1 of 9 Version: 1.00 Release: 05032008
Report showing present detailed accounting head wise information for Plan Schemes NIC-ACID- e-lekha-psmsig Page 2 of 9 Version: 1.00 Release: 05032008
1. Agency / Stake Holder Master Creation and Maintenance. e-lekha would facilitate the creation and maintenance of an Agency Master with proper hierarchical relationship of Parent Agencies and Child Agencies on e-lekha by respective Program Divisions and down the line sub agencies. It would also facilitate the creation and maintenance of Userids and defined access rights to agencies / sub agencies. 2. Maintenance of Geographical Location codes as per Census directory. e-lekha would also facilitate the mapping of each agency in the agency masters with appropriate geographical location. This would be required to be maintained by respective program managers and down the line agencies. NIC-ACID- e-lekha-psmsig Page 3 of 9 Version: 1.00 Release: 05032008
3. Creation and Maintenance of Scheme Codes and their definition and multilevel hierarchies. The Scheme definition of all Schemes and their associated hierarchies up to the Scheme Name would be maintained by the Planning Commission and any further sub classification of schemes below the scheme by Program managers would be facilitated on e-lekha. The schemes / sub schemes would then be mapped with their respective accounting codes as per the Detailed Demand for Grants by respective Controllers NIC-ACID- e-lekha-psmsig Page 4 of 9 Version: 1.00 Release: 05032008
4. Entry of Sanctions for and generation of Unique Sanction ID for Plan Releases by Ministries / Departments on e-lekha. The above three masters as mentioned in 1,2, and 3 above would become a mandatory requirement for Program Divisions for generation of Sanctions on e-lekha. Respective Program Divisions would have to feed in the Sanctions pertaining to Schemes on e-lekha where they would have to select the Scheme Code (as per Scheme definition master), Agency Code (as per Agency Master which is already mapped with location codes), its associated detailed expenditure head of accounts as per COA in the detailed demand for grants (which would be validated against the head of accounts already mapped in the Scheme Definition). The type of Sanction whether (Expenditure / Transfer / Both) would also be flagged at the time of Sanction ID generation. Once all the above information is fed and validated the e-lekha application would generate a Unique 19 digit Sanction ID (Token). This sanction ID (details as below) would have to be printed from the e- Lekha application and should accompany the sanction and bill which is sent to PAO by the Department DDO. The PAO would return all such sanctions back to the DDO which do not have the accompanying printout of the Unique 19-digit Sanction ID generated on e-lekha. NIC-ACID- e-lekha-psmsig Page 5 of 9 Version: 1.00 Release: 05032008
4.1 Generation of Unique Sanction ID Sanction ID Structure (19 Char) 1. Scheme Code: 4 Char viz. AIDP 2. (T)ransfer / (E)xpenditure 3. Implementing Agency Code: 4 Char 4. Grant No: 3 Char viz. 035 5. Financial Year: 4 Char viz. 0708 6. Running Sl.No.: 3 Char A Sanction ID could be something like AIDPT02980350708028 NIC-ACID- e-lekha-psmsig Page 6 of 9 Version: 1.00 Release: 05032008
Sanction ID Creation Workflow. Annexure I Sl. Field Name Remarks No. 1 Controller Will be populated based on the user logged in. 2 Plan Scheme Populated based on the Controller selected and the Financial Year Passed. 3 PAO Populated based on the Controller Selected 4 DDO Populated based on the PAO Selected 5 Sanction Type User Selection 6 Agency Populated based on the user logged in for selection 7 Location Block Read-only; Will be populated based on the Agency Selected (State, District, Block) 8 Grant Only the grants mapped with the selected Controller will be populated for that financial year for selection 9 Function Head Populated based on Plan Scheme Selected for selection (15 Digit fully qualified Accounting Head as per DDG) 10 Object Head Populated based on Plan Scheme Selected for selection 11 Category All plan categories 12 Amount User Input NIC-ACID- e-lekha-psmsig Page 7 of 9 Version: 1.00 Release: 05032008
Process Flow Diagram Annexure II A Creation of Program Implementing Agency Master State District Sub-District Block Selection of Geographic Hierarchy as per Census 2001 Administrative / Spending Unit (A / S) Agency Name / Code Sub Agency Name / Code Sub-Sub Agency Name / Code B Plan Scheme Definition and Codification Program Level 1 Sub Program Sarva Shiksha Abhiyan Level 2 Scheme Codification of Plan Schemes with Hierarchy Scheme Code (SSA) Code Mapping of each Scheme Code by different Grant Controllers up to the defined Accounting Units viz. Grant No. (3), Major Head (4), Sub-Major (2), Minor (3), Sub-Head (2), Detail (2), Object (2) NIC-ACID- e-lekha-psmsig Page 8 of 9 Version: 1.00 Release: 05032008
C Capture of Sanctions and Generation of Unique Sanction ID Select Plan Scheme Code from B Exists? Y N Request Plan Scheme Code Creation to CGA Resource Flow Type? Transfer (T) / Expenditure (E)? Select Beneficiary Details from 1. Geographical Hierarchy 2. Program Implementing Agency Code 3. Administrative Unit / Spending Unit (A/S) A Generation of Unique Sanction ID Exists? Y N Enter Beneficiary Details and create Code Sanction ID Structure (19 Char) 1. Scheme Code: 4 Char viz. AIDP 2. (T)ransfer / (E)xpenditure 3. Implementing Agency Code: 4 Char 4. Grant No: 3 Char viz. 035 5. Financial Year: 4 Char viz. 0708 6. Running Sl.No.: 3 Char A Sanction ID could be something like AIDPT02980350708028 Select appropriate Head of Accounts from selection list as per mapping of Plan Schemes done in with Amount. B Generate Unique 19 Digit Sanction ID Print Sanction and send to DDO NIC-ACID- e-lekha-psmsig Page 9 of 9 Version: 1.00 Release: 05032008