Fee collection looks like a payment problem until the first dispute. Then it becomes a record problem. The question is not only whether the parent paid, but which student, which batch, which instalment, which discount and which receipt. A system that collects money without answering those questions creates more work than the register it replaced.
This budget model is for coaching centres, schools and training institutes in Bangladesh that already collect fees through a mix of cash, bKash, Nagad, bank transfer and cards. It separates the one-time build from the running charges and gives you a calculator you can complete before requesting quotes.
What the workflow includes
- A student ledger with enrolment, batch, fee plan and concession records.
- Invoice or demand generation on a schedule, including partial payments and instalments.
- Collection through the channels the institute already accepts.
- Receipts that can be reissued and verified, not reconstructed from memory.
- Daily matching of provider statements to student ledgers.
- Follow-up of dues, with a record of who contacted whom.
- Reporting by batch, branch, month and collection channel.
Seven cost components
- Ledger and data setup: student records, fee plans, concessions, opening balances and branch structure.
- Workflow configuration: invoicing rules, instalments, late fees, partial payment handling and approval limits.
- Channel integration: gateway, MFS or bank collection, including callback handling and settlement references.
- Receipts and communication: templates, SMS or messaging costs and a parent-facing view.
- Reconciliation: statement import, matching rules, exception queue and daily close.
- Training and migration: staff training, parallel run and correction of historical balances.
- Support and maintenance: fixes, provider changes, reporting adjustments and monitoring.
Score the complexity before pricing
Use six inputs and score each from one to three. The total gives a rough effort band. It is a planning aid, not a quote, and it should be replaced by measured effort after discovery.
| Input | Low (1) | Medium (2) | High (3) |
|---|---|---|---|
| Branches | One | Two or three | Four or more, with separate cash handling |
| Fee plans | One plan per batch | Several plans and instalments | Many plans, concessions and course changes |
| Collection channels | Cash and one digital channel | Three channels | Four or more, including bank and cards |
| Partial payments | Rare | Regular | Common, with carry-forward balances |
| Refunds and transfers | Rare | Monthly | Frequent, with approval rules |
| Reporting needs | One summary | Batch and branch reports | Consolidated and audit-level reporting |
A low total describes a ledger replacement with a single collection point. A high total describes a multi-branch finance system with policy rules, reconciliation and parent communication. The difference is not the payment button; it is the number of states a student balance can be in.
The cost formula
First-year cost = build effort + migration + training + provider charges + messaging + support.
Build effort comes from the complexity band multiplied by your blended day rate. Migration is records to clean and reconcile multiplied by review time. Training is roles multiplied by sessions, plus written guides. Provider charges are set by the gateway or MFS agreement and should be taken from the merchant rate card, never from an article. Messaging is the number of notices multiplied by the contracted rate. Support is a monthly line, not a promise.
Keep provider charges outside your build budget. They scale with collection volume and belong in the finance model, where the person who owns the merchant relationship can see them.
First-year worksheet
| Line | Basis | Owner | Confidence |
|---|---|---|---|
| Discovery and fee-plan mapping | Fixed phase, paid on sign-off | Academic head | High |
| Ledger and workflow build | Complexity band × blended rate | Product owner | Medium |
| Channel integration | Per provider, including callback testing | Technical lead | Medium |
| Historical data migration | Students × records to reconcile | Accounts lead | Low |
| Receipt and notice templates | Template count × review cycles | Admin lead | High |
| Training and parallel run | Roles × sessions plus one fee cycle | Branch manager | Medium |
| Provider charges | Merchant rate card × expected volume | Finance | Medium |
| Messaging | Notices × contracted rate | Admin lead | Medium |
| Support and maintenance | Monthly retainer or internal hours | Finance | High |
| Contingency | 10–20% of build and migration | Sponsor | Hold |
Cost drivers that surprise institutes
- Opening balances. Historical dues are rarely clean. Every disputed balance consumes migration time.
- Concessions and scholarships. A discount that exists in a principal's approval email but not in a rule becomes a manual exception every month.
- Partial payments. A student paying part of an instalment creates a carry-forward state that must be visible to the front desk and the accounts team.
- Branch cash. Cash collected at a branch needs a close process, a deposit record and a reconciliation owner.
- Refunds and batch transfers. Both change the revenue allocation, not only the payment status.
- Parent communication. One message template is cheap; personalised statements across thousands of students are not.
Measure the baseline
Before the project starts, record four figures for a normal month: accounts staff hours spent on fee collection and follow-up, average days from due date to collection, unmatched receipts at month end, and parent queries about payments. Repeat the measurement three months after launch. The comparison is the business case; a vendor claim is not.
Also record the number of fee corrections made after a receipt was issued. That figure exposes how much of the current process depends on informal adjustments.
Questions for a vendor
- How will the system represent a partial payment and a carry-forward balance?
- Which providers are supported directly, and which require a manual import?
- How are refunds, batch transfers and concessions approved and recorded?
- Can a receipt be verified after a student leaves or a branch closes?
- What does the daily reconciliation report contain, and who is expected to use it?
- How is historical data migrated, and who resolves disputed balances?
- What happens if a provider changes its API or settlement file?
A 90-day rollout that protects the ledger
Weeks 1–3: clean student and fee-plan data, and agree the opening balance policy. Weeks 4–6: configure the ledger and invoice rules, then run one batch in parallel with the register. Weeks 7–9: add one digital collection channel and test duplicate callbacks, partial payments and refunds. Weeks 10–12: train the front desk and accounts team, run a full fee cycle, and close the month with a signed reconciliation.
Do not switch off the old register until one complete cycle has been reconciled. The parallel run is the cheapest insurance the project will buy.
Where our team fits
We build fee ledgers, collection workflows and reconciliation reports for education institutes under Education Operations. Scope and starting points are on the pricing page. If you are still comparing collection models, read automated tuition fee collection workflow options compared.
Sources
- Bangladesh Bank, Mobile Financial Services statistics, accessed 17 November 2026.
- bKash Developer Portal, accessed 17 November 2026.
- PCI Security Standards Council, accessed 17 November 2026.
- GSMA, Mobile Money programme, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.