ISP billing and collection
Veloxiom bills subscribers from the same database that authenticates them. Plans, invoices, payments, reminders and suspension are one chain, not four integrations — which is why a payment can restore a connection in seconds and a failed charge can never disconnect a customer who has paid.
What the billing engine does
- Recurring invoicing per connection or per billing account, with proration from the activation date, per-customer billing day and multi-currency totals with correct VAT rounding.
- Consolidated or independent invoices for customers with several connections: one invoice with a line per service, or separate invoices per site when the customer asks for it.
- Prepaid and postpaid in the same installation, including daily prepaid accrual for subscribers who top up.
- Contract commitments of 12 or 24 months with a configurable early-termination fee (remaining months, percentage, fixed amount, with a cap), charged as a separate invoice so the original stays untouched.
- Late fees as an optional, capped, non-retroactive surcharge issued as its own invoice.
- Dunning with reminders, grace periods per customer, soft suspension to a captive portal and hard disconnect — all rule-driven.
Getting paid without chasing
Collection is where most providers lose hours. Veloxiom supports card auto-pay, SEPA Direct Debit mandates on IBAN, one-off card and bank transfer, and — for Greece — ΔΙΑΣ RF payment codes that make an incoming transfer match its invoice automatically.
Bank statements can arrive by themselves: CAMT.053 and MT940 host-to-host delivery over SFTP, a bank CSV upload, or an open-banking aggregator connection. Each transaction is matched in stages — RF code, invoice number in the description, VAT number, name and amount, then a unique open invoice for the amount — and whatever stays unmatched goes to a manual pairing screen with the reason recorded.
Greek tax compliance is part of billing, not a plugin
ΑΑΔΕ myDATA submission happens from the same invoice record, and the returned MARK is stored on the invoice — so a failed submission is visible next to the document instead of inside a connector's log. Credit notes reference the original invoice, and submitted invoices are locked against silent edits.
Why it matters that billing and RADIUS share a database
When a subscriber pays at 23:00, the payment is matched, the invoice is settled and the session is restored by a RADIUS Change-of-Authorization — with nobody logging in. When billing is a separate system, that same event becomes a support call the next morning. See RADIUS and MikroTik management for the network side.
Frequently asked questions
Is Veloxiom priced per subscriber?
No. It is self-hosted and licensed per installation, so growth does not turn into an increasing per-subscriber cost.
Can I run one invoice for a company with many branches?
Yes — several connections can be linked to one billing account with a line per service, and any branch can be switched to independent invoicing.
Will enabling automation charge or disconnect anyone retroactively?
No. Late fees, commitments and dunning rules start from the day you enable them and have per-run caps, so historical balances are never charged or cut off by surprise.
Can I export everything?
Yes. It is your database and your server: invoices with line items, payments, VAT numbers and submission identifiers are all exportable.