A chart of accounts, vouchers and ledgers built for how an institution actually keeps books, reading from the collections and salaries the system already recorded.
Book a demoThe accounts clerk exports fee collections, exports payroll, and types both into a separate accounting package. Somewhere in the retyping a figure changes, and nobody finds out until the trustees ask why two reports disagree.
Then the question arrives that always arrives: what did we actually spend on transport last term. Answering it means opening three systems and hoping the headings were used consistently.
When collections and salaries post from the same records that produced them, there is nothing to retype and nothing to reconcile.
Grouped by the job it does rather than listed as one long set of features.
Income and expense heads structured the way an institution thinks - by campus, department or activity - rather than a generic business template.
Payment, receipt and journal vouchers with approval before they post, so a correction is a document rather than a quiet edit.
Account ledgers with running balances that you can open on any head and read from opening to today.
Cash and bank positions, deposits and transfers between accounts, without a parallel spreadsheet.
Movements between funds and campuses recorded as transfers rather than as an expense in one place and income in another.
What came in, what went out and against which head, for a term or a year, without assembling it first.
Close a period so figures stop moving underneath a report that has already gone to the board.
Each campus visible on its own and consolidated for the group, from the same entries.
The statements a school actually needs for its trustees, its auditors and its own planning.
The fee collection typed in twice. Once by the accounts office in the fee system, again into the accounting package. The two figures now differ by whatever was mis-keyed, and reconciling them is a monthly ritual.
The expense charged to the wrong head. Transport fuel posted against general maintenance. Moving it needs to leave a trail rather than silently changing history somebody already reported on.
The period that would not stay closed. A late voucher is backdated into a month the board has already seen. The report is now wrong and nobody knows it.
The campus that keeps its own books. Each site uses slightly different heads, so the group figure is an interpretation rather than a total.
These are the cases worth testing in a demo. Bring the messiest one you have.
The same records, presented differently depending on the job.
Maintains the chart of accounts, posts and approves vouchers, closes periods and produces the statements.
Income, expenditure and campus comparison without asking the accounts office to prepare something.
A traceable path from a statement back to the voucher and the transaction that produced it.
Nothing. Financial detail is not something a teaching role has any reason to open.
Fee collections post from the fee module rather than being exported and retyped, so the collection figure in the accounts is the collection figure the office recorded.
Payroll posts the same way. Transport and hostel charges arrive against the heads they belong to rather than as an unexplained lump. Campus structure is the same structure the rest of the institution uses.
That is why month end becomes a review rather than a rebuild: the entries were made once, by the people who knew what they were.
The parts of the institution this touches most.
The two reports that disagree and the heading nobody uses consistently. Those are the useful things to look at.
Book a demo