Getting started | ISP Billing Documentation

Initial setup

Initial setup determines the quality of every record created later. Before entering customers, contracts, or services, collect company identity and tax details, sites, official contacts, logo, domains, numbering policies, catalog, collection methods, and operator responsibilities.

Prepare a coherent test environment. Gateways and providers offering a test mode must use credentials, webhooks, and endpoints from that same environment. A successful save proves field validation, not the complete journey.

Requesting the first ISP account

On the public Register your first account page, choose the licence according to the number of customers to manage. Included modules are part of the licence; add-ons require a paid licence. The summary is a preview: the server independently checks prices, availability, and the total.

Complete the company, contact, administrator, and document details. Provide at least one of certified email or SDI code, use a valid international phone number, and upload PDF or image files up to 10 MB. All mandatory agreements must be accepted.

The verification email contains a link valid for 24 hours. After staff review and approval, the new ISP receives the password-setup email and WhatsApp welcome template. The Master receives a separate internal notification by email and Telegram.

1. ISP identity and general settings

Open Settings → General and complete company name, tax identity, addresses, contacts, public references, logo, and global preferences. Review them as a customer would see them because they can appear on documents, messages, and portals.

Check time zone, date format, currency, and public-link domain. Incomplete identity propagates to invoices, contracts, email, and Customer Area.

2. Operator accounts, roles, and security

Create a named account for each operator and grant the minimum suitable role. Separate administration, billing, support, network, sales, and reseller duties where responsibilities differ. Test with the real role because a full administrator does not represent normal staff access.

Enable two-factor authentication, verify recovery contacts, and remove unused accounts. Dashboard menus, widgets, and notification families are permission-sensitive.

3. Enable and configure required modules

Use the module catalog to identify only what the ISP’s operating model needs. For each module distinguish licence availability, active state, role permissions, internal settings, and any external provider account.

After activation, open the module’s Settings, complete credentials, mappings, and rules, and use the built-in test where available. Establish which system is authoritative for each data set before moving on.

4. Prepare CRM and classifications

Configure customer and supplier numbering, groups, custom fields, initial states, preferences, and Customer Area access. Decide which fields are required for individuals, businesses, and public administrations.

Create one complete demonstration record and inspect its dashboard, addresses, contacts, preferences, documents, and portal accounts before importing a large list.

5. Build the service catalog

Define product name, category, type, price, VAT, billing cycle, activation charge, renewal behavior, advance or arrears billing, rechargeability, and technical provider. Use separate catalog entries for commercially different offerings.

For every service define what happens on creation, activation, suspension, renewal, and termination. Test automatic provisioning only in the authorized environment and always reread the returned state.

6. Documents, numbering, and tax settings

Configure document types, sequences, series, PDF templates, issuer header, VAT, stamp duty, due dates, and descriptions. Verify invoices, credit notes, receipts, and electronic documents separately.

Generate one demonstration document and inspect net amount, tax, total, rounding, address, tax identity, due date, and PDF layout before any bulk issue.

7. Payments and reconciliation

Define accepted methods and distinguish offline methods, online gateways, saved cards, recurring charges, and direct debit. Configure environment, keys, callback or webhook, fees, and payment-registration rules for each gateway.

Complete one test payment from document to authorization, portal return, webhook, paid state, remaining balance, and expected accounting movement. A successful redirect without the callback is not a complete reconciliation.

8. Communication channels

Configure SMTP, SMS, WhatsApp, and APP notifications according to the channels actually used. Prepare senders, templates, consent, recipients, limits, and error handling. Providers have different rules and do not automatically share credentials or templates.

Send only to authorized demonstration recipients and verify sender, variables, attachments, queue state, and provider outcome.

9. Simulate the first customer lifecycle

Create or complete the demonstration customer.
Prepare a quote or contract when required.
Assign the correct service.
Complete provisioning and verify its state.
Generate the first invoice.
Perform a test payment.
Open a ticket and add a reply.
Review Dashboard, Customer Area, and customer history.

The cycle is complete only when each step is visible in the next module and all states agree.

Recommended setup order

Complete identity and general settings.
Configure security, users, roles, and permissions.
Enable required modules and dependencies.
Prepare CRM, groups, and custom fields.
Build the service catalog and lifecycle rules.
Verify numbering, tax, and document templates.
Configure gateways and payment methods.
Prepare communication channels.
Run the complete demonstration cycle.
Review Dashboard, operating queues, and portals.

If one step fails, correct the configuration feeding it before proceeding with production data.

How to know the setup is ready

Setup is ready when a normal-permission operator can complete the journey without administrator assistance, data is correct in lists and PDFs, demonstration messages arrive, and operating queues show no unexplained errors.

Record the responsible person, test date, environment, and outcome. Keep external request identifiers where useful, never the credential used.

Initial checklist

ISP identity and public details reviewed
Named accounts and two-factor security verified
Roles tested with ordinary permissions
Required modules configured
CRM numbering, groups, and fields ready
Service lifecycle and catalog validated
Tax settings and sample PDF checked
Gateway, callback, and payment state verified
Communication channels tested safely
Complete demonstration lifecycle reconciled