Account connection
Configure the supported provider account for the school.
SchoolPay integration
Connect SchoolPay records to the rest of your school data.
Let SchoolPay continue handling the payment channel while TriedSM connects those records to student accounts, academic periods and operational reporting.
TriedSMConnected school platform
Connected reconciliation
- Account connection
- Overlapping synchronisation
- Duplicate protection
- Run visibility
Kampala, UgandaLocal support
Connected reconciliation
A reliable path from provider event to student account.
TriedSM monitors synchronisation runs and preserves the operational context needed by the school.
Overlapping synchronisation
Fetch recent records regularly while daily runs cover a longer reconciliation window.
Duplicate protection
Use provider event keys and idempotent allocation workflows to avoid repeat records.
Run visibility
Review synchronisation status and investigate records that require attention.
What changes
Keep payment collection and school reporting connected
TriedSM connects people and records so the next task is clearer, decisions are better supported and the school retains a dependable history.
Discuss your school workflow01
Avoid replacing a payment channel families already know.
02
Reduce repeated spreadsheet handling.
03
Link collections to the right student context.
04
Maintain a clearer reconciliation trail.
Questions and answers
Understand the fit before you decide.
Every school is different. These are the questions most relevant to this workflow.
Does TriedSM collect the SchoolPay payment?
SchoolPay remains the payment channel. TriedSM synchronises supported records for student allocation, reconciliation and reporting.
Can we still import spreadsheets?
Yes. Schools can use the CSV workflow for supported records alongside configured integrations.
Built for your school. Supported from Kampala.
See how TriedSM connects the work that matters to you.
Book a focused walkthrough for your administrators, academic leaders and bursars.