Most coaching centres and schools do not have a collection problem. They have a matching problem. A guardian pays through a mobile wallet, another uses a bank transfer, a third pays cash at the branch, and a fourth sends money through a relative's account. The money arrives. The question is which student it belongs to, which instalment it settles, and whether the receipt already issued agrees with the bank statement.
Reconciliation software is bought to answer that question reliably. The budget is often discussed as if it were the price of an app, but much of the cost sits in identity data, payment channels, exception handling and the finance team's time. This guide breaks those components down, gives you a scoping formula and a percentage model for planning, and sets out a 90-day rollout that produces evidence before you scale.
What the work actually includes
- Payment capture: connections to the channels you use, or a controlled import for statements and cash receipts.
- Student identity: a stable student ID that links a payer, a student, a guardian and a fee plan, including siblings and third-party payers.
- Fee ledger: instalments, waivers, scholarships, late adjustments, refunds and advance payments held against future dues.
- Matching rules: automatic matching on reference, amount and date, with a queue for anything ambiguous.
- Exception handling: unapplied payments, partial payments, duplicates, wrong references and reversals, each with an owner and a deadline.
- Reporting and audit: daily collection summaries, branch-level close, reconciliation evidence and a history that survives staff turnover.
If a proposal covers only the first item, it is a payment gateway integration, not a reconciliation system. The ledger and the exception queue are where the operational value is created.
Seven factors that move the budget
- Number of payment channels. Each channel has its own statement format, settlement timing and reference behaviour. Four channels cost more to integrate and test than two.
- Branches and collection points. Every branch adds users, cash-handling rules and a close routine. Multi-branch consolidation is a design decision, not a report.
- Fee-plan complexity. Instalments, subject-wise fees, transport, discounts, sibling waivers and mid-term changes all create matching exceptions.
- Identity quality. Duplicate student records, missing guardian phone numbers and payments made from someone else's wallet are a common reason a project stalls.
- Accounting integration. Posting to an existing ledger, or exporting to Excel, changes the integration effort and the control model.
- Settlement and cut-off rules. A payment initiated before midnight but settled the next day needs an explicit accounting rule. So does a refund processed in a different period.
- Internal finance capacity. A team that can own the exception queue needs less managed support than a team with one part-time accountant.
The cost model, line by line
Build the budget in two columns: one-off implementation and recurring operation. Mark every line as internal, vendor or pass-through.
- Discovery and data audit: channel inventory, student record quality, fee plan review and exception volumes.
- Integration and import: channel connections, statement imports, reference formats and retry behaviour.
- Identity and ledger setup: student ID rules, payer mapping, opening balances and fee plan configuration.
- Matching rules and exception workflow: rule design, queue ownership, escalation and audit notes.
- Reporting: daily collection, branch close, unapplied payments, refunds and month-end reconciliation.
- Training and change management: branch cashiers, accounts staff and the person who owns the close.
- Recurring support: channel changes, rule tuning, user administration, monitoring and release management.
- Pass-through charges: payment provider fees, SMS costs and bank charges, shown separately rather than buried in the software price.
- Internal time: data cleanup, user acceptance testing, parallel running and ongoing exception review.
A scoping calculator for your spreadsheet
Use observable counts and round each division up. One workable formula is:
scope points = (payment channels x 3) + (branches x 2) + (fee plans) + (monthly transactions / 1,000) + (manual matching hours per week x 2)
A centre with four channels, three branches, eight fee plans, 4,000 monthly transactions and fifteen hours of manual matching scores 12 + 6 + 8 + 4 + 30 = 60 points. The score is a way to compare proposals at similar scope, not a price.
Also rate the current state from 0 to 3 on four dimensions: identity, channel coverage, matching automation and audit evidence. Zero means absent, one means spreadsheet-based, two means documented but manual, three means tested and owned. The distance to the target state is the real project.
A percentage model for the implementation budget
When you have a total implementation figure, allocate it deliberately rather than letting the integration consume everything. A defensible planning split is:
- Integration and payment capture: 25-35%.
- Student identity and fee ledger: 15-20%.
- Matching rules and exception workflow: 20-25%.
- Reporting, audit and close: 10-15%.
- Training and change management: 5-10%.
- Contingency: 10%.
These are planning ranges, not market rates. Their purpose is to expose a proposal that puts most of the budget into gateway integration and leaves none for the queue where staff will spend their days. Normalise the weights so the total equals 100% for your scope; the balance matters more than the exact split.
Questions to ask before signing
- How will you identify a student when the payer is a relative or a sibling?
- What happens to a payment that arrives without a usable reference?
- Can a refund or reversal be traced to the original receipt and the accounting period?
- How are cash receipts and branch deposits reconciled alongside digital payments?
- Which reports does the finance team sign off, and at what time each day?
- Who tunes the matching rules after launch, and how are changes tested?
- What data export and audit history do we keep if we end the contract?
A 90-day rollout
- Days 1-15: audit channels, student records, fee plans and the current close process. Quantify exceptions by type.
- Days 16-35: agree student ID and payer mapping, clean the worst duplicate records and define the fee ledger.
- Days 36-60: connect two channels, run matching in parallel with the existing process, and measure the automatic match rate.
- Days 61-75: open the exception queue to a small finance team, assign owners and set a daily clearing target.
- Days 76-90: add the remaining channels, run a full branch close, compare results and document the operating routine.
Metrics that prove the investment
- Automatic match rate, measured separately for each channel.
- Number and value of unapplied payments, with ageing.
- Hours spent on manual matching and the daily close.
- Exception queue clearance time and repeat exception rate.
- Duplicate receipts and corrected receipts per month.
- Guardian queries about payment status, and the time to resolve them.
Reconciliation for tuition fees sits inside Education Operations, alongside admissions, batches and fee workflows. The pricing page explains how a branch rollout is scoped. For the finance routine that follows collection, read how daily payment reconciliation changes year by year.
Sources
- Bangladesh Bank, Mobile Financial Services statistics, accessed 17 November 2026.
- PCI Security Standards Council, accessed 17 November 2026.
- NIST SP 800-63-4, Digital Identity Guidelines, accessed 17 November 2026.
- DataGuidance, Bangladesh data protection overview, 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 *.