Accounts and contacts

Accounts are the customer master. One account = one commercial entity. Everything about that customer — sales, ops, finance — rolls up here.

Account fields

• Legal name, trading name.
• Tax numbers (VAT, GST, ABN, UEN, EIN).
• Addresses — billing, shipping, registered office.
• Industry, size, parent group.
• Segment (key account, mid-market, SMB).
• Owner (sales / account manager).
• Credit limit + payment terms — see credit control.
• Preferred currency, preferred language.
• Contract references.

Contacts

Multiple contacts per account, each with role flags:

• Billing — receives invoices.
• Ops — daily ops comms.
• Booking — authorised to book shipments.
• Technical — EDI / API setup.
• Portal — has customer-portal access.
• Primary — default contact.

Contacts can also have portal roles — viewer, approver, admin.

Duplicate prevention

Creating an account fuzzy-matches on legal name, domain, and tax number. Suggests merging or linking (e.g. subsidiary relationship).

Hierarchy

Accounts can have parent-child relationships (groups with multiple legal entities). Reporting rolls up to the group. Credit limits can sit at group or entity level, per tenant policy.

Integrations

• Sync to accounting system (Zoho, QuickBooks, Xero) — see integrations.
• Enrichment from Clearbit, ZoomInfo (optional).

Roles and access

Who sees an account:

• Owner + their team (default).
• All commercial users (tenant policy).
• Finance (always).
• Ops only for accounts with active shipments (configurable).

Fine-grained RBAC — see security / RBAC.

Activity on an account

The account page shows every touch: shipments, invoices, payments, activities, portal sessions, tickets. Single source of truth for "where do we stand with this customer".