Bangladesh ISP Billing Software: A Deployment Checklist
Evaluate local payment, SMS, VAT, MikroTik, reseller and support requirements with evidence before selecting an ISP platform in Bangladesh.
Evaluate local payment, SMS, VAT, MikroTik, reseller and support requirements with evidence before selecting an ISP platform in Bangladesh.
Local fit is an operating requirement
A billing demo can look complete while missing the workflows that determine daily success in Bangladesh: reseller price boundaries, local gateway reconciliation, Bangla communication, VAT treatment, PPPoE control, SMS delivery and support during collection peaks. Evaluation should use your own scenarios and evidence.
Collections
Verify bKash or other gateway callbacks, reconciliation, refunds and duplicate protection.
Distribution
Model group admin, operator, sub-operator and staff boundaries without data leakage.
Network
Test MikroTik access, RADIUS accounting, VPN reachability and device failures.
Compliance
Confirm invoice, VAT, retention and export requirements with qualified local advice.
Test one complete money trail
Create an invoice, collect through each intended gateway, verify the callback, post the ledger entry, issue a receipt and reconcile the provider settlement. Repeat, cancel and delay callbacks to expose duplicate or premature activation.
VAT profiles need defined scope, effective dates, rounding and correction behaviour. Request accountant review rather than accepting a software label as compliance.
Test delegated selling boundaries
A reseller should see only authorized subscribers and packages. The group-admin floor price must remain enforceable when an operator edits a package or sells to a sub-operator. Delete and special-price actions need separate permissions.
Direct URLs, autocomplete and exports deserve the same tenant tests as menus. A hidden sidebar item does not prevent cross-account access.
Test the difficult network day
Measure VPN, RouterOS API and RADIUS behaviour when a router is slow, disconnected or on an alternate port. Bulk suspension and recharge need previews, idempotency and audit trails.
Check mobile layouts used by field and collection staff, Bangla rendering, timezone, currency formatting, backups, support escalation and data export before signing.
Evidence before rollout
| Signal | Required proof |
|---|---|
| Gateway ledger | Provider transaction, invoice, payment and ledger entry reconcile. |
| Price floor | Operators and sub-operators cannot sell below authorized cost. |
| Tenant isolation | Direct URL, search, export and API tests block other accounts. |
| Network failure | Slow and unreachable routers do not corrupt billing actions. |
| Exit path | Customers, transactions and configuration can be exported. |
Put the plan into operation
- Map. Write critical billing, reseller, network and support workflows.
- Shortlist. Reject products missing non-negotiable architecture or local support.
- Script. Give every vendor the same acceptance scenarios.
- Pilot. Run one area or reseller through a complete cycle.
- Reconcile. Compare money, customers, sessions and messages.
- Contract. Document support, ownership, backups and exit commitments.
The decision standard
Choose the platform that proves your real collection, reseller, network and compliance workflows under failure—not the one with the longest feature list or the most polished dashboard.
Research basis: Bangladesh VAT and tax authority publications; Bangladesh Bank payment guidance; MikroTik RouterOS documentation. Validate implementation details against the releases, contracts, and local regulations governing your network.