ISP billing software
Invoices raised on the billing cycle, reminders sent by SMS, payments taken through bKash, Nagad and SSLCommerz or in cash — and a line that switches itself back on once the bill is paid. One ledger for a broadband ISP in Bangladesh, instead of a spreadsheet and a phone that never stops ringing.
A billing month
The same five things every cycle, in the same order. Each is a switch in the panel, so you decide which of them run on their own.
Each renewal invoice is raised from the subscriber's package, dues are recalculated, and whatever is past its date is marked overdue. A price you change later applies to the next invoice — never to one already sent.
The subscriber gets an SMS with a short payment link. It opens their bill and takes the money there — no account to sign in to, no app to install.
bKash, Nagad or SSLCommerz at checkout; cash handed to a collector; or money sent to your own bKash or Nagad number and read off the payment SMS. Every one of them settles the same invoices in the same ledger.
Overdue subscribers are suspended at midday rather than at midnight, so the message telling them arrives while they can still do something about it. With parking turned on they are slowed down instead of cut off, and any web page they open shows them how to pay.
The payment settles their open invoices and the connection comes back on its own — on the router, through the same sync that suspended it. Nobody at the office has to press anything.
Collections
Most subscribers do not use a checkout page. Billing software that only counts the payments that do leaves the rest to be typed in by hand.
Checkout straight from the bill. The payment is confirmed with the gateway itself before the invoice is marked paid, not taken on the browser's word.
The collector app on a phone holding that SIM reads each payment SMS, and the money is matched to whoever sent it by their number and what they owe. When it is not certain, it waits for a person — it is never guessed.
A collector sees their own area and records cash at the door. It lands in the same ledger as an online payment, so the day's figures agree.
Their bill, an online payment, a package change and a complaint — without a phone call to the office.
The ledger
Invoices, payments, dues and resellers are one set of records, so the number on the dashboard and the number in the report are the same number.
A price set once on the package, and a PDF invoice for every bill. Changing the price later does not rewrite what was already sent.
Move a subscriber up or down in the middle of a cycle and they are charged for the days on the new package, not for a whole month either way.
A reseller sees only their own subscribers, and their due to you is tracked. When they pay your number, the payment SMS clears it the same way a subscriber's clears a bill.
What each person can see and do is set per role — a collector, the support desk, an accountant — rather than left to trust.
Revenue, packages sold and subscribers added, with dues and wallets tracked per subscriber.
Due reminders, expiry notices and a receipt when a payment arrives, sent on schedule — and a Telegram message to the office when money comes in.
Questions
Yes. Keep a phone at the office with that SIM and the collector app on it. It reads the payment SMS, and each payment is matched to a subscriber by the number it came from and the amount they owe. When the answer is not certain — two subscribers on one number, an amount that matches nobody — it waits in a queue for someone to confirm.
A few days before the line expires — three by default, and you choose — they get an SMS with a link to pay, and a reminder once it is overdue. At midday the overdue line is suspended — or, with parking on, slowed down and pointed at a page that tells them how to pay. The moment they pay, it comes back. Each of those steps can be switched off.
No. Invoices and payments live in the records, not on the router. The work that does need the router — switching a line back on after a payment — is held and retried when it answers again.
Connect your MikroTik and the PPPoE secrets and profiles already on it are read in, so the subscriber list is not retyped. Set up your packages, match each subscriber to one, and the next invoice comes from the system rather than from you.
No. Each ISP has a database of its own and a panel on its own subdomain. There is no shared table to leak from.
The rest of SKYNITY
Billing, the routers and the fibre share one set of records, so a payment, a package change or a failing ONU is the same fact everywhere it shows up.
Tell us how many subscribers, which routers and what packages, and the demo is set up the way you actually run.
Request a demoor email support@skynity.net
SKYNITY