Skip to main content
Spanworth

Menu

Book a demo

Fee reconciliation

When the claim and the bank book disagree.

The student says they paid. The bank book sits in another file. Accounts reconcile the two in a spreadsheet.

Friction

What breaks on paper

How the mess shows up when fees, attendance, or the timetable run in silos.

  • The claim lives alone

    A student submits amount, mode, and a reference, or proves payment in chat. Accounts cannot see that claim next to the deposit line.

  • The bank book is elsewhere

    The statement export lands in a shared folder. Parsed rows never become the working queue for open claims.

  • The spreadsheet is the record

    Someone matches lines by hand, updates status off-system, and the student waits on a reply that is not the claim they submitted.

Already live

The flow already running

How Spanworth holds the same work end to end, without a side spreadsheet.

  1. The claim

    The student opens Payments, picks the semester fee record, and submits amount, mode, reference, and receipt when the mode asks for it.

  2. The queue

    Accounts filters the Payments list by status, semester, batch, course, or date, then opens the claim to check amount, mode, reference, and receipt.

  3. The statement

    Accounts uploads the bank export. Parsed rows become the deposit lines waiting to match.

  4. The match

    High-confidence matches enter a ratify queue. Unclaimed deposits and unmatched claims stay for a manual link. Approve, reject, or send back with a remark.

  5. The record

    The student sees status on the same claim. The reconciled deposit is the record. The side spreadsheet is not.

Span

Where that record lives

Open the live capability that already closes this mess, then the role that runs it.