Skip to content

Finance & Payroll

A double-entry finance office — fees in, payroll out, books that balance — with controls that survive an audit.

  • Bursars
  • Accountants
  • Head teachers
  • Boards
Request a pilot

General ledger

Term II, 2026 · UGX

Balanced
AccountDebitCredit
Tuition fees receivedJV-204112,400,000
Cash at bank — StanbicJV-204112,400,000
Staff salaries — MayJV-20428,950,000
PAYE payable — URAJV-20421,610,000
NSSF payableJV-20421,342,500
Totals21,350,00021,350,000

Posted by A. Nakato (Accountant) · awaiting approval — the creator cannot approve their own entry.

What it does

Books your auditor trusts. Approvals no one can fake.

True general ledger

Every fee, payment and salary posts as a balanced journal entry. Reports are read from the books, never assembled from a spreadsheet on the side.

Fees, plans and credit notes

Bill termly, set discounts and payment plans, raise credit notes — each one a posting, with the parent statement always reconciled.

Payroll with statutory deductions

PAYE, NSSF and WHT computed from URA and NSSF source rules, with payslips and the URA/NSSF returns produced from the same run.

Budgets, requisitions and vendors

Departmental budgets, purchase requisitions and vendor payments flow through the same ledger, so commitments and spend are always visible.

How it works

From start to settled, in three beats.

  1. 1

    Post

    A fee, payment or salary is captured as a balanced double-entry journal — never a side spreadsheet.

  2. 2

    Check

    A second authorised signer approves it. The hand that posts can never be the hand that approves.

  3. 3

    Report

    Trial balance, income statement and the URA/NSSF returns read straight from the ledger.

Why it’s different

Maker-checker, enforced in the database.

The person who posts a transaction can never be the person who approves it — and that rule lives in the database, not in a screen that can be skipped. Combined with a true double-entry ledger, the numbers you export are the numbers your auditor will find.

The mechanism

A. Nakato

posts the entry

B. Mukasa

approves it

A. Nakato cannot approve her own entry — the rule is enforced in the database, not the screen.

Compliance-grade controls that survive an export — not UI theatre.

Built in from the start — the one thing a competitor can’t bolt on later.

The artifact · PAYE, straight from the source.

Uganda’s monthly PAYE bands, applied the way URA defines them. Payroll computes deductions from these brackets at source — no hand-keyed tax tables to drift out of date.

PAYE — monthly bands

URA · resident · UGX
0 – 235,000Tax free0%
235,001 – 335,000of the amount over 235,00010%
335,001 – 410,000+ 20,000 fixed20%
410,001 ++ 25,000 fixed30%

Income above 10,000,000/month carries an additional 10% on the excess. Payroll applies all of this from source.

See the finance office in a walkthrough.

See finance on your own school’s data in a guided pilot — import, training and a full term of support included.

Request a pilot