Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Education Technology 5 min read

Digital tuition fee reconciliation: a step-by-step guide

A ten-step routine for reconciling tuition fees from bKash, Nagad, cards and bank transfers, with owners, evidence and a daily close.

E
EncryptTechBD · 0 comments
Open notebook, phone and laptop on a white desk
Photo: JESHOOTS.com / StockSnap

A parent pays by bKash on a Friday evening. The confirmation reaches the parent, the gateway records the payment, the bank settlement arrives later, and the student ledger still shows the term fee as unpaid. Nobody has done anything wrong; the three records simply close on different clocks. Reconciliation is the routine that makes them agree before a parent has to call.

Prerequisites

  • One student ID per learner, with duplicate family records merged before the term starts.
  • A fee schedule per programme, batch and term, including approved discounts and waivers.
  • A named owner in accounts, a backup and a documented escalation route.
  • Access to each channel's merchant portal, settlement report and transaction search.
  • An agreed daily cut-off time for posting payments.
  • A receipt template showing student ID, term, amount, channel and reference.

The ten-step routine

Roles first: the registrar owns the student and fee master, accounts owns the daily routine, the finance controller approves adjustments and signs the monthly close, and IT owns gateway and portal access. One named backup covers each role.

  1. Freeze the student and fee master. The registrar confirms each active student, batch and fee plan; finance attaches approved discounts. Output: a dated fee schedule. Acceptance: every active student has one plan and every exception has a named approver.
  2. Issue one payment reference per student per term. Encode the student ID and term, not the phone number, and print the reference on the invoice, the SMS and the gateway checkout. Output: a reference register. Acceptance: a payment can be traced to one student without opening a chat thread.
  3. Capture the payment at source. Use the gateway callback where it exists, or a controlled manual entry with the transaction ID where it does not. Store the channel reference as a unique key. Output: a payment record with source and time. Acceptance: a duplicate callback cannot create a second payment.
  4. Import the settlement file on a fixed schedule. Download the channel report at the same time each day and store the file unchanged. Output: an archived statement with its control total. Acceptance: any date in the audit period can be reproduced exactly.
  5. Match in three passes. First by exact reference, then by amount, date and payer identifier, then by manual review. Never match on amount alone when several students pay the same fee. Output: matched, partial and unmatched lists. Acceptance: every unmatched line has an owner and a reason code.
  6. Post to the student ledger and issue the receipt together. The ledger entry carries the channel reference, not a note that money arrived. Output: a receipt the parent can verify. Acceptance: confirmation reaches the parent within one working day of settlement.
  7. Work exceptions as a queue. Assign a reason code such as late reference, wrong student, partial amount, duplicate, bank charge or unknown payer. Output: an ageing report. Acceptance: nothing older than the agreed resolution window is left unassigned.
  8. Handle refunds, waivers, advances and bounces through an approval matrix. A refund reduces a settled payment; it never deletes the original record. Output: an adjustment linked to its source. Acceptance: the ledger and the channel statement both explain the adjustment.
  9. Close the day with three control totals. Compare what the channel collected, what the bank or wallet settled and what the ledger posted. Output: a signed daily close. Acceptance: differences are listed and carried forward, not forced to zero.
  10. Reconcile the month to the bank and the accounting system. Review unapplied cash, fee dues and refunds, then sign the month off. Output: a reconciliation pack. Acceptance: it agrees to the bank statement and the finance ledger without a manual plug.

The evidence file

Each close should leave a small, repeatable pack: the fee schedule version, channel statements as downloaded, the match report with counts and totals, the exception log, adjustment approvals and the sign-off. Keep it outside the mailbox of the person who prepared it, for the period your auditors and tax advisers require. The test of the file is simple: could a different accountant reproduce the close from it without asking a question?

Common mistakes

  • Editing a settled transaction instead of posting an adjustment.
  • Using a parent's phone number as the only key; one number can pay for three siblings.
  • Reconciling weekly and finding a duplicate after the receipt was issued.
  • Treating the gateway fee as a student shortfall.
  • Accepting a screenshot as proof of payment.
  • Letting one person both post and approve adjustments.
  • Closing the month with an unexplained suspense balance.

Metrics for the first term

  • First-pass match rate, by channel.
  • Unapplied cash and its age.
  • Receipt lag, measured from settlement to parent confirmation.
  • Exception ageing and the top three reason codes.
  • Fee dues accuracy at the end of each month.
  • Refund turnaround from approval to payment.

Channel notes for Bangladesh

bKash and Nagad differ in reference format, callback behaviour and settlement reporting, so keep the matching rules channel-specific rather than forcing one rule across both. Card settlements arrive through a different report and carry chargeback rules; do not blend them into the mobile wallet file. Bank transfers often arrive with a narration typed by the parent, which makes them the most manual channel and the one that needs the clearest payment instructions. Keep the merchant statement, the bank credit and the student ledger in one filing structure, so a parent's query can be answered from a single screen.

Building this into an education platform

We build fee collection and reconciliation into Education Operations, alongside admissions, attendance and results. The pricing page sets out how a term-length build is scoped. For the wider reconciliation discipline behind this routine, read daily payment reconciliation, year by year.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes