Go-Live Document

@SchoolName

@City @State

Document Name	Created by	Date
ERP Go Live Document	@SupportContact	@currentdate

Document Name	Verified by	Date
ERP Go Live Document	@PrincipalName	@Date

Table of content

1. Executive Summary

2. Student & Staff Graphical Summary

3. Go Live Status

4. Activities Performed

5. Module Wise Feature List with Status

6. System Policies - Static

Vedanta ERP is working with @SchoolName, City from @startdate to digitise the school management process. The Go Live Checklist provides a summarise status of implementation of Vedanta ERP

@studentcountgraphclass

@staffcountgrpahbydepartment

2. Go Live Status

@Livestatustable

2.2.2 Activity Perfomed During Go Live

@Feecategory
@FeeParticulars

2.2.3 Creation of Fee Terms

@FeeTerms

2.2.4 Creation of Subject Fee

@SubjectGroup fee

2.2.5 Fee Term & Fee Particular Mapping

@feetermnparticularmapping

2.2.6 Classwise Fee Structure update

@feestructure

2.2.7 Fee receipt for Payment

5.1 Role Based Access

5.1.1 User role specific access will be allowed by system. Roles according to profile is created in system
5.1.2 User Role of any user can be changed at school level by any authorized Staff.
5.1.3 Only Authorized users can view User name of any staff / Student & update the password.
5.1.4 User login details can be sent by SMS.

5.2 Fee Collection Process

5.2.1 Monthly Invoices will be generated by system as per the defined dates in fee setup.
5.2.2 If Any invoice status stands as Unpaid /Partial Paid / Advance Paid then balance amount.
5.2.3 Once Next fee term invoice created then no payment can be done for old term invoice.
5.2.4 Fee can be collected by Authorized users only.
5.2.5 Back date entries are blocked in system, only authorized users can do back date payment.
5.2.6 Default payment date well be as per number of days for back days mentioned.
5.2.7 Priorities of Fee Particular set & will be followed as per fee setup. Only authorized users
5.3.3 Only One Discount category can be applied to single student. If need manual discount.
5.3.4 Discount will be Applicable only from the date of discount start date selected at the time.
5.3.5 In case of change in discount category first discount need to be removed & assign new discount category.
5.2.8 In case of multiple payment mode for a single student payment then separate payment.
5.2.9 Incorrect payment entries can be cancelled by the authorized users.
5.2.10 Cancelled payment receipt number will not be removed from day book. It will show cancelled amount &

5.3 Discount policy

5.3.1 Discount policy is applied by tagging of approved discount category available in system.
5.3.2 Discount Category report is available in system to guide them about available discounts.
5.3.3 Only One Discount category can be applied to single student. If need manual discount.
5.3.4 Discount will be Applicable only from the date of discount start date selected at the time.
5.3.5 In case of change in discount category first discount need to be removed & assign new discount category.