Streamlining management at schoolSecurity & your dataEverything it doesBlog
EduBoldBook a demo

Everything it does

Everything EduBold does, on one page.

If you are evaluating vendors against a requirements list, take this page into the meeting. Every line here is checked against the source code, not written from a sales deck.

01 / 09

Admissions and students

Parents apply on your own website and follow their own application through to the offer. One screen then holds everything about the child who arrives.

  • A twenty-state pipeline, from enquiry to enrolled
  • Siblings detected at application, and the discount applied across the family
  • Sixteen areas of a student on one screen, including health and guardians
  • New, lateral, transfer and re-admission handled as different things

02 / 09

Fees and payments

A rule engine rather than a fee module. Conditions read the student’s own record, so a fee that only some children pay, only in some years, is a rule rather than a special case.

  • Conditions chained with AND and OR, against any student attribute
  • A dry run before anything is billed, and a rollback afterwards
  • Late fines by charge, head, amount band and branch
  • A per-student ledger, and a defaulters report that remembers the calls

03 / 09

Accounts

Real double-entry books that the fee and payroll modules post into themselves. There is no export, no import and no month-end data entry.

  • Trial Balance, Balance Sheet, P&L, Cash Flow and Fund Flow
  • Your auditor’s own schedules, numbered their way
  • Companies Act Schedule III mapping and Schedule II depreciation
  • Bank statement import with automatic matching, and Tally ledger mapping

04 / 09

Compliance

The statutory forms an Indian school actually files, produced from your own data rather than from a spreadsheet somebody keeps.

  • Form 16 in bulk, and Form 24Q with the TRACES FVU file
  • GSTR-1 and GSTR-3B
  • PF, ESI and professional tax, with ceilings you hold as data
  • Old and new tax regime, with regime-aware surcharge

05 / 09

Payroll and HR

Attendance is the payroll input, so the month arrives already calculated. Finalising a run posts it to the ledger.

  • Sixteen component types and thirteen calculation types
  • Loss of pay prorated from attendance, without a retype
  • Voluntary PF handled the way it actually works
  • NEFT and RTGS files generated to bank specification

06 / 09

Academics, timetable and exams

The timetable generates itself, then finds its own clashes and offers ranked ways out of them. Your assessment scheme is configuration, not convention.

  • Automatic generation, with conflict detection and ranked fixes
  • Versioning with rollback, so a worse timetable is undone
  • Teacher preferences and workload scored
  • Report cards configured to the way your school already prints them

07 / 09

Attendance and leave

One engine for students and staff, fed by the biometric devices you already have.

  • Biometric devices post straight into the register, and log their own failures
  • A leave policy engine: entitlement, accrual, carry-forward, expiry
  • Two-stage approval, the manager and then HR
  • Working day patterns and overtime

08 / 09

Library, inventory and communication

The library runs as a department with a budget rather than as a searchable list, and what the school owns is tracked down to who is holding it.

  • Circulation by barcode, copies tracked by accession number
  • Acquisition from purchase request to vendor quotation to payment
  • A library budget with commitment, utilisation and projection
  • Campaigns aimed from the records as they stand, with a delivery log per parent

09 / 09

The platform

Multi-branch, with each school isolated from every other and the trust able to see across them.

  • Separation the database itself enforces, rather than the software asking nicely
  • Roles, and control over exactly what each person can do, with a reason recorded for the access they were given
  • An audit log with export, and IP whitelisting
  • Scheduled reports, emailed, with your own branding
Rows of empty wooden desks in a classroom with daylight through the windows

Next

Bring your requirements list to the demonstration.

This list is maintained from the source code rather than from a sales deck, so you can take it into the meeting and check it line by line.

Read us your list and we will go through it with you, item by item, in the call.