PLETOX FOR EDUCATION

Education HR, Payroll & Work Software
Your staff. Your students.
A more connected institute.

Bring faculty, staff and campus work into Pletox HRM. Extend your setup with the Institute ERP Power App for admissions, student records, fees, attendance, results and parent access.

PletoxAcme Institute / Staff workspaceCampus HRM

FACULTY. ADMINISTRATION. SUPPORT.

Your campus team, connected.

Staff records
48
Active projects
6
Open tasks
14
Illustrative staff work overview
Employee / TeamWork in focusStatus
Asha Shah / AdministrationOrientation planningAccepted
Rohan Patel / FacilitiesClassroom readiness taskIn progress
Neha Patil / HRStaff attendance correctionsTo review
Institute ERP Power AppStudent records / Fees / Attendance / Admissions
Illustrative preview / Sample data. Staff workspace with a separately scoped Institute ERP add-on.

THE PEOPLE BEHIND YOUR CAMPUS

Faculty and staff.
One organized people workspace.

Teaching, administration and support teams need different working patterns, but the same clarity. Keep their records, requests and responsibilities connected across departments and campus locations.

Staff profiles that stay connected

Maintain employment details, documents, campus, department and reporting manager as employees move through their journey.

Explore module

Hiring through to joining

Publish staff openings, review candidates and collect joining details. Complete the required HR review before employee creation.

Explore module

Attendance for campus teams

Configure working patterns, supported biometric or mobile attendance and corrections for faculty, administration and support staff.

Explore module

Leave with the right reviewer

Give employees balances and request visibility. Review dates and team context before deciding; submission is not approval.

Explore module

Payroll with reviewed inputs

Bring salary components, reviewed staff attendance, eligible allowances and deductions into a payroll run your team can validate.

Explore module

Self-service for employees

Let faculty and staff access enabled requests, letters, payslips and personal information on web or mobile, within their permissions.

Explore module

STAFF ATTENDANCE TO SALARY REVIEW

A clearer month-end.
For every campus team.

Different roles can have different salary structures. Keep the working-day record, approved changes and applicable salary rules together before payroll is finalized.

  • 01

    Capture the staff working day

    Set working patterns, weekly offs and attendance policies. Confirm device compatibility and enabled mobile workflows during setup.

  • 02

    Review requests and exceptions

    Resolve missing punches and corrections. Include approved leave as context, with paid or unpaid treatment following configured rules.

  • 03

    Check the run before processing

    Validate eligible allowances, adjustments and deductions alongside employee salary components, then process payroll and release enabled payslips.

Student attendance does not determine staff salary. Payroll processing and payslips do not confirm bank payment.

Explore payroll & salary
September / Staff payroll reviewIllustrative preview / Sample data

Review the inputs together.

Draft
  1. Staff attendanceCampus records and corrections
    Reviewed
  2. Approved leaveEmployee working-day context
    Recorded
  3. Salary structureApplicable components and rules
    Configured
  4. Adjustments & deductionsEmployee-level amounts to validate
    To review
Staff payroll remains an HR workflow.

Student fees and employee salary are separate records.

CAMPUS WORK WITH A CLEAR OWNER

From a campus plan to accountable work.

Keep orientation preparation, administrative follow-ups and facility tasks moving with named owners and due dates. These are staff work records, not student admissions decisions.

01

Prepare the work

Create an orientation project and assign the administration, facilities and support tasks.

02

Keep the next action visible

Record acceptance, progress and updates with the task so the next team has the context.

03

Review with responsibility

Use configured review and approval steps. Recorded completion does not automatically mean approval.

Explore tasks & projects

EXTEND PLETOX / OPTIONAL ADD-ON APP

Institute ERP Power App

Student operations deserve
their own connected record.

Go beyond staff HRM with the Institute ERP Power App from Pletox. Manage the student journey from admission enquiry and registration to profile records, fees, attendance, test results and parent access.

Student operationsParent loginSeparately scoped add-on
PletoxAcme Institute / Institute ERPStudent record
AM

Aarav Mehta

STU-026 / Foundation programme / Batch A

Admitted

Student profile

Academic year
2026-27
Programme
Foundation
Registration
REG-026

Fees summary

Total fees
Rs. 40,000
Received
Rs. 25,000
Outstanding
Rs. 15,000

Student attendance

September entries
20 days
Present
18 days
Absent
2 days

Test results

Assessment
Unit Test 1
Mathematics
42 / 50
Science
45 / 50
Illustrative preview / Sample student and amounts. Not a live record or payment gateway.

Student profile management

Keep student details and academic context organized in a record that continues beyond admission.

Fees management

Maintain student fee information, recorded receipts and outstanding amounts so the accounts team can review the position.

Student attendance

Maintain student attendance records for academic follow-up, separately from employee punches and payroll inputs.

Parent login

Give parents access to permitted information for their associated student, with account linking and visibility configured for the institute.

Test results

Organize recorded test results with the student so authorized staff and parents can refer to the relevant assessment information.

Admissions management

Manage admission enquiries, registrations and admissions with a clear stage and responsible team.

Institute ERP is an optional Power App, not automatically included in every HRM plan. Confirm modules, licensing, migration, access and any integration requirements during implementation.

FROM FIRST ENQUIRY TO A STUDENT RECORD

Keep the admissions journey
in one place.

Give the admissions team a clear view of where an applicant stands. Keep enquiries, registration and admission as distinct stages instead of assuming that every interested applicant is already a student.

  • 01

    Record the enquiry

    Capture the prospective student and programme interest. Keep the next follow-up visible to the responsible team.

  • 02

    Manage the registration

    Bring applicant details into a registration record and follow the institute's review process. Registration is not admission confirmation.

  • 03

    Confirm admission deliberately

    Record the institute's decision, then maintain the admitted student's profile and associated academic and fee information.

Institute ERP / Admission journeyIllustrative preview / Sample data
AM
Aarav MehtaFoundation programme / 2026-27
  1. 01
    Enquiry recordedProgramme interest and follow-up
    Recorded
  2. 02
    Registration receivedREG-026 / Applicant details
    Received
  3. 03
    Institute reviewAdmission decision recorded by the team
    Reviewed
  4. 04
    Admission confirmedSTU-026 / Student profile
    Admitted

Example of a completed journey. Registration does not automatically confirm admission.

Institute ERP / Parent viewIllustrative preview / Sample data

Your student's information.

Parent login
AM
Aarav MehtaAssociated student / STU-026
  1. AttendanceSeptember / 18 present, 2 absent
    Visible
  2. FeesRs. 15,000 outstanding
    Visible
  3. Test resultsUnit Test 1 / Recorded results
    Visible
Linked student access only.

Unrelated student records and staff payroll are not part of this view.

PARENT ACCESS WITH CLEAR BOUNDARIES

Less searching for updates.
More useful visibility.

Give parents a dedicated login for permitted information about their associated student. Keep academic and fee updates easy to find without exposing the institute's internal staff workspace.

  • 01

    Link the right account

    Confirm the parent account and its student association as part of setup. A parent login is not an employee self-service account.

  • 02

    Show the enabled information

    Make relevant attendance, fee information and test results available according to the institute's configured visibility.

  • 03

    Keep record ownership clear

    Staff manage their authorized workflows; parents see the permitted student view. Access does not imply unrestricted editing or visibility of other students.

ONE INSTITUTE. DISTINCT RESPONSIBILITIES.

Start with your priorities.
Connect the right workflows.

Begin with staff HRM, the Institute ERP Power App, or a planned rollout of both. Agree the access, record ownership and implementation scope before importing data.

  1. 01

    Map staff and student operations

    Define campuses, employee departments, programmes and the admissions journey.

  2. 02

    Set access and ownership

    Confirm HR, admissions, accounts, teaching staff and parent roles; agree any required data connections.

  3. 03

    Validate real working examples

    Trial staff payroll separately from a student admission, fee record, attendance entry and result.

  4. 04

    Train and roll out

    Prepare administrators, staff and parents for their own workflows, with support and migration responsibilities agreed.

See your institute's working day in Pletox.

Bring your staff process and student admission journey. Explore the right HRM and Institute ERP setup.

Book a demo today

EXPLORE STAFF HRM

The modules behind your campus team.

Confirm the HRM plan and the separate Institute ERP Power App scope.

Compare HRM plans

BEFORE YOUR EDUCATION DEMO

Staff HRM. Institute ERP.
Your questions, answered.

Understand the scope of each workspace and who can access it.

Yes. Organize employees by company, campus location, department, designation and reporting manager. Configure permissions and review responsibilities around the campus structure rather than giving every user access to every record.

Use hiring workflows to publish roles and review candidates, then move selected candidates into onboarding. Joining details and documents follow the configured HR review before employee record creation. Student admissions are a separate workflow in the Institute ERP Power App.

Reviewed attendance, approved leave and eligible adjustments provide inputs alongside configured salary rules. Resolve exceptions and validate earnings and deductions before processing. Student attendance does not determine staff salary, and payslip availability does not confirm bank payment.

The add-on covers student profile management, fees management, student attendance, parent login, test results, admission enquiries, registrations and admission management. It complements staff HRM; enabled modules, implementation and licensing scope are agreed separately.

Yes. Use the Institute ERP Power App to manage admission enquiries, registrations and admissions. Keep the applicant details and stage visible to the responsible team. Registration does not automatically mean admission is confirmed.

Parent login provides access to the permitted information for their associated student, such as enabled attendance, fee information and test results. Confirm account linking, roles and visibility during setup. A parent account must not expose unrelated students or staff payroll.

No. Fees belong to student and institute operations in the Power App; salary processing belongs to staff HRM. Configure access, record ownership and any agreed data connections deliberately. A fee balance is not a payroll input.

Yes. Scope staff HRM and the Institute ERP Power App around your priorities. Confirm licensing, migration, access setup and any integration requirements before rollout. Parent access and student records remain distinct from employee self-service.

Book a demo