Quick answer
When a school ERP stops working, first find the scope: one user, one device, one module, or everyone. Most issues come from logins and permissions, internet or devices, wrong fee or grading rules, failed integrations such as the payment gateway or SMS, or data errors. Fix the cause, log it, and escalate platform faults to the vendor with evidence.
- Check scope first: one person, one module, or the whole school.
- Many problems are settings or data, not software bugs.
- Log every incident with time, user, screen, and screenshot.
- Agree response times with your vendor in writing before you need them.
How do you diagnose a school ERP problem?
- Define scope. Is it one user, one role, one device, one module, or everyone?
- Check the basics. Internet, browser version, app version, and whether the vendor status page reports an outage.
- Reproduce it. Repeat the steps and note the exact time, screen, and message.
- Check recent changes. New fee rule, permission change, app update, or data import in the last day?
- Fix or escalate. Fix settings or data yourself; escalate platform faults with evidence.
What are the most common school ERP problems and fixes?
| Problem | Likely cause | Fix |
|---|---|---|
| Cannot log in | Wrong username, expired password, deactivated account, wrong role | Reset password, check the user is active and has a role |
| User sees wrong data or nothing | Permissions or class assignment | Check role, campus, class, and section access |
| Screens are slow | Internet, old browser, very large reports | Test another network, update browser, filter reports |
| Fee paid but shows unpaid | Gateway callback failed or payment not reconciled | Check gateway transaction ID, reconcile manually, report to vendor |
| Wrong fee amount | Fee plan, concession, or late fine rule | Correct the rule and regenerate affected invoices |
| Attendance not showing | App offline and not yet synced | Open the app on a connection and sync; check for errors |
| SMS not delivered | Provider balance, sender ID, or number format | Check message logs, balance, and numbers |
| Report card totals wrong | Grading rule, missing marks, or wrong subject mapping | Check rule setup and missing entries before publishing |
| Timetable clashes | Teacher or room assigned twice | Use conflict detection and fix assignments |
| Duplicate students | Repeated imports or manual entry | Merge records and set duplicate checks |
What if the system works but nobody uses it?
- Make the ERP the only place for key tasks, such as fee payment, report cards, and leave requests.
- Retrain by role, in short sessions, using real tasks.
- Ask champions which screens slow people down, and simplify them.
- Track usage by role and follow up where it is low.
What support terms should a school ask for?
| Term | What to agree |
|---|---|
| Severity levels | What counts as critical (for example nobody can log in, fees cannot be collected) |
| Response and resolution times | Per severity level, during school hours and outside them |
| Channels | Phone, email, chat, ticket portal |
| Status page | Where outages and maintenance are announced |
| Backups and restore | How often, and how fast data can be restored |
| Escalation | Named contacts beyond first-line support |
How do you prevent school ERP problems?
- Test changes to fee and grading rules on a few students before applying them to all.
- Schedule imports outside busy periods and validate counts after.
- Review user accounts each term and remove leavers.
- Run a test report card before every results day.
- Keep a simple incident log and review it each month.
When should a school switch to a new ERP?
Switch when problems are structural, not occasional: the vendor cannot fix recurring faults, the system cannot handle your curriculum or fee rules, data cannot be exported, mobile apps are unreliable, or support is consistently slow. Before switching, export all data and read the school ERP implementation guide.
How SchoolOS helps you find and fix issues
SchoolOS keeps an audit trail of changes, notification logs with delivery stats, conflict detection in the timetable, and app diagnostics in the iOS and Android apps. Nectar, the AI in SchoolOS, can flag unusual patterns such as fee payments that did not reconcile, for staff to review. Talk to us if your current system keeps failing.
Frequently asked questions
Why can I not log in to the school ERP?
Usually a wrong or expired password, a deactivated account, or a missing role. Ask the school admin to reset the password and check the account.
Why does the fee show unpaid after I paid online?
The payment may not have been confirmed back to the ERP. Keep the transaction ID and share it with the school office to reconcile.
Why is the school app slow?
Check your internet and update the app. If everyone is slow at the same time, it may be a platform issue for the vendor.
Who fixes problems in a school ERP?
The school admin fixes settings, accounts, and data. The vendor fixes platform faults, integrations, and bugs.
Can lost data be recovered?
If the vendor keeps regular backups, yes. Ask how often backups run and how fast a restore can be done.
How do we report a problem to the vendor?
Use the support channel with the user, time, screen, steps, and a screenshot. This speeds up the fix.