Account model
A customer account owns commercial and operational records. Authorized users sign in to the portal and can be associated with the account according to access policy. Contacts support billing, technical, and notification responsibilities without duplicating the account story.
Customer workspace
Use the customer profile as the source of truth for identity, addresses, taxes, currency, services, invoices, payment methods, credits, quotes, tickets, email history, notes, and activity. Record important operator decisions in notes or activity instead of relying on private memory.
Onboarding checklist
- Verify legal name, billing address, tax location, currency, and language.
- Invite the correct portal users and test password recovery.
- Confirm notification preferences and billing contacts.
- Create or import the service through a controlled order workflow.
- Review the first invoice, payment method, and next due date.
- Confirm the customer can see services, invoices, payments, and support actions.
Privacy and lifecycle
Collect only necessary data, limit staff access, protect exports, and define retention. Before deleting or anonymizing a customer, understand the effect on invoices, transactions, tax records, tickets, and audit history.
The account tabs
An account opens on its summary and every other view is a tab across the top. Each tab is a different question about the same customer.
Summary
The whole account on one page: active services, unpaid invoices, credit balance, open tickets and net income, with the account switches — tax exemption, automatic card processing, overdue reminders, late fees — that change how billing treats this customer. Each switch saves as soon as it is flipped.
Profile
Contact and billing address, currency, group, status and language. This address decides tax, so a correction here restates tax on invoices generated afterwards, not on those already issued.
Users
The people who may sign in to this account. A user is an identity with a password; an account is the commercial record. One user can be associated with several accounts, which is how an agency manages clients without sharing a password.
Contacts
Additional addressees for billing, technical or support correspondence who do not sign in. A contact receives the message types you assign to it and nothing else.
Products and services
Everything this customer is subscribed to, with billing terms, next due date and status. Opening a service shows its product, cycle, amounts, payment method, subscription reference and admin notes, plus its addons and the upgrade path.
Billable items
One-off or recurring charges added to this customer’s next invoice — time, quantities, or a fixed amount — each with the date it should be invoiced on.
Invoices
Every invoice raised against the account, filterable by status. Bulk actions apply from the footer of the list to the rows you tick.
Quotes
Proposals, their stage and the dates that frame them. A quote becomes an invoice when it is accepted rather than existing alongside one.
Transactions
Money in and out, with gateway and fees. This is the record to reconcile against the payment provider; the invoice list is not.
Donations
Gifts made by this donor, with their own lifecycle. See Donations.
Tickets
Support history for the account, including tickets opened by any of its users or contacts.
Emails, notes, and log
What the product sent this customer, what your team recorded about them, and what changed on the account. Notes are internal and never shown to the customer; the log is filterable by date, wording, administrator and IP address.
Credits
Credit held on the account and how it was applied. Credit is consumed automatically against new invoices unless the account says otherwise.