Panaceum covers the whole service lifecycle: from order and invoice to renewal, suspension and data erasure. Below is what the system does and which rules it applies by default.
The invoice is issued ahead of renewal, reminders follow a schedule, suspension and data erasure run by a policy the client can see.
A late fee accrues as a percentage or a fixed amount; a partial payment reduces the balance without closing the invoice.
VAT follows the customer country, EU B2B reverse charge is validated against VIES, and the gateway fee lands as a separate invoice line.
Invoice and credit note in A4 are generated from the same data, with the numbering and VAT lines your accountant expects.
EUR, PLN and more: base currency, rates and rounding rules are configurable, amounts always travel as strings.
Cancellation flows can offer a discount or a credit; the coloured button always means keeping the service.
Creation, limit changes, suspension and deletion run as queued tasks with retries and a full call journal.
Price recalculation, new limits on the panel and an entry in the service history in a single step.
Slots, disk space, backups and a dedicated address are sold as add-ons to a specific server, never in the abstract.
Exchange rate, coefficient and markup rules with rounding to a defined step for dedicated servers and VPS.
Renewals, reminders, suspensions and erasure follow the schedule, not manual work.
You see what the system would do, but nothing is created or deleted until you switch to live mode.
Overview, servers, invoices, add-ons and tickets in a dark and a light theme, responsive down to a phone.
A ticket is attached to a specific server, priority follows the client package, and there are exactly four ticket states.
Hints for the agent, a short summary and a draft reply, always with a disclaimer. It never answers the client on its own.
Referral accruals and single sign-on into the partner area.
Contacts, theme, two-factor authentication and trusted devices.
Email, Telegram and Discord: billing, provisioning and support events with separate rules for incidents.
The policy is set in the settings and visible to the client: dates and amounts are stated directly, without vague wording.