Core terms you'll meet across the UI. The order follows the natural commercial flow: from prospect to payment, then configuration entities. All concepts described correspond to modules active in the current version.
A person or company who showed interest but is not yet a customer. Has status, source, owner, temperature (Hot / Warm / Cold), activity history, optional tags and custom fields. Managed in Sales → Leads; the BX Leads module offers an alternative full-page view.
Conversion: the Convert to customer button creates a Customer + Contact from the lead fields. The original lead is kept as archive.
The company (or individual) you do business with. Holds:
A person tied to a Customer. Has its own email + password for the customer portal. Granular per-contact permissions: can see invoices / contracts / estimates / projects. One contact is primary = default notification recipient.
Sales quote for a Customer or a Lead. Statuses: Draft, Sent, Open, Revised, Declined, Accepted, Expired. On Accepted it can be converted to Invoice or Project in one click.
A more narrative variant of an estimate, with WYSIWYG body, electronic signature (signer, IP, date) and public-link acceptance. Can auto-convert to Customer and Invoice on accept (see setting Auto convert leads to clients when proposal is accepted).
Agreement with a Customer over a period (start_date → end_date) or open-ended. Has WYSIWYG content, attachments, comments, internal notes, renewals and signature (manual or electronic). Full details in the Contracts guide.
Fiscal document issued to a Customer. Statuses: Unpaid, Paid, Partially Paid, Overdue, Draft, Cancelled. Supports multiple lines (Item / free description), discounts (percent or value), per-line VAT, own currency, recurrence, attachments, partial payments. For Romania/Moldova: built-in e-Factura ANAF and FISC MD.
"Pre-fiscal" document — payment request without immediate accounting obligation. On payment it converts into a fiscal Invoice.
Reversal fiscal document — full or partial against an already-issued Invoice. Use cases: customer refund or credit applied to other invoices.
Money transaction applied to an Invoice. Supports partial payments, multiple methods (bank transfer, cash, card, online gateway). Recording a payment automatically updates the invoice status (Paid / Partially Paid).
Container for deliverables to a Customer. Has start_date, deadline, status, billing type, milestones, files, gantt, notes, time tracking. See the detailed Project Management guide.
Unit of work assigned to one or more Staff. Common fields: name, description, priority (1–4), start/due date, assignees, followers, milestone, custom fields, tags. Supports subtasks (hierarchy), dependencies, time tracking (live timer + manual), recurring (auto-repeat), checklists, comments, files.
Child task of a parent. Useful for splitting a large task without polluting the top-level plan. Hierarchy depth is technically unlimited. Parent status does not auto-update when children complete — manual control by design.
An important point on a project's timeline. Not a task — a marker. Renders as a vertical diamond in Gantt and as a counter on the project Overview.
A logged time interval against a task: start, end, duration, hourly_rate, billable yes/no, note. Created via live timer (Start/Stop) or manually. Drives invoices via Project → Invoice tracked time and timesheet reports.
Catalogable element that appears on lines of invoice / proforma / estimate / proposal / contract / purchase order. Has: name, description, unit price, currency, VAT, unit of measure, tags, attachments. The TSync Warehouse module adds stock, AVCO, lot, GRN, transfers.
Hierarchical grouping for Items, taxes, expenses, knowledge base articles. See Drag-drop categories for fast reorg.
Commercial brand attached to an Item. Used in reports and filters; see brand management.
Admin / collaborator account. Has: name, email, phones, departments, role (or granular permissions), avatar, custom fields, active/inactive status. Different from Contact (which is a person at a customer).
Predefined set of permissions (read/create/edit/delete) on entities: invoices, estimates, contracts, projects, tasks, items, leads etc. "own" vs "global" attribute — see only entities you created/are assigned to, or all of them.
Logical group of Staff (Sales, Support, Production). Used for ticket routing and report filters.
Extra admin-defined field on any entity (Customer, Lead, Invoice, Project, Task, Item, Contract, Staff). Types: text, textarea, select, date, number, link. Shows in form, optionally in lists, optionally in PDF.
Free-form label attachable to entities (most often Tasks, Leads, Items). Drives quick filters and report grouping.
Support request from a Contact (or internal). Has status, department, assignee, priority, attachments, message thread. Can be created from incoming email (IMAP cron).
An event on the calendar (internal or assigned to Staff). Shows in the global Calendar view + on project/task details. Syncs with Google Calendar when the integration is configured.
Public or internal knowledge base article. Used for customer self-service or staff onboarding. Supports categories, helpful-vote and search.
The currency invoices are issued in. The system has a base currency (used for aggregated reports) and allows issuing documents in other currencies with a configurable rate.
Tax percentage (e.g. VAT 19%, VAT 9%, VAT 0%, exempt). Defined in Tax rates editor. Applied per line, not per document.
Accepted payment method (bank transfer, cash, POS card, online gateway). Configurable globally or per Customer.