Fees and finance
Fee collection that posts to a double-entry ledger, so the fee register and the accounts are the same numbers.
Built for the people who run it
- Finance officers and bursars
- Accounts sections
- Fee counters
- Students and parents
What usually prompts the call
- The fee register and the books of account are kept separately and disagree.
- Defaulter lists and collection reports are prepared by hand before every meeting.
- A stored balance and its transactions drift apart, and the difference is found at audit.
- Budget-versus-actual is keyed into a spreadsheet instead of read from the ledger.
What it does
Which of these are included in a deployment is set out in the proposal for that institution.
Fee structures
Fee heads, structures by programme, instalments with due dates, and assignment to students.
Fee collection
Collection at the counter and online through a payment gateway, with receipts and settlement tracking.
Late fees and reminders
Late-fee rules and reminders to students with dues.
Fee reports
Collection, dues and head-wise reports, and each student's own fee statement.
General ledger
A chart of accounts with journals that must balance before they can be posted.
Posting control
Posted entries cannot be edited; a correction is a reversing entry. Nothing posts into a closed period.
Financial statements
Trial balance, profit and loss, balance sheet and cash flow, with drill-down to the ledger.
Budgeting
Budget heads and versions, with budget-versus-actual read from posted balances, by cost centre or programme.
Payables and receivables
Vendors, bills and payment runs; customers, invoices, receipts and credit notes; ageing on both.
Bank and statutory
Bank statement import and reconciliation, with data for GST returns and TDS certificates.
How it runs, start to finish
An illustration of a typical sequence. Your own process is configured during implementation.
Define fee heads and the structure for each programme.
Assign fees to students with instalment dates.
Collect at the counter or online; a receipt is issued.
The receipt posts to the ledger.
Reconcile against the bank statement.
Read statements and budget-versus-actual from the ledger.
What institutions have said
Excerpts from signed letters. Each is dated; follow the link to read it in full.
We are satisfied with the operation of OLT Campus software & Support / Services provided by the company.
Read the case study
Frequently asked
Do we have to take every module?
No. Institutions take the modules that address their current problem and add others later. Which modules are included is set out in your proposal; nothing on this site should be read as meaning every module is part of every deployment.
What does the software cover?
Admissions; academics and student administration, including electives, examinations, grading and transcripts; fees and finance; HR and payroll; institutional operations such as stores, hostel and transport; and placement and executive education. Each area is described on its own solution page.
Which systems does it integrate with?
Payment gateways, biometric attendance devices, email, SMS and WhatsApp messaging, and single sign-on are covered in the integration directory, which states for each whether it is built in, configured per institution, or assessed per project. Integration with another institutional system is assessed case by case.
See fees and finance with your own workflow
Tell us how your office works today and the demonstration will follow that.