The Sales area brings together the primary customer-facing transaction records used by AIUNIFY CRM.
The Sales menu itself is permission-sensitive. Users see the transaction areas their accounts are permitted to access.
The deployed CRM registers Sales menu entries for:
Each entry is displayed according to the applicable access checks.
Proposals are used to present proposed business terms, services, products, or work to a prospect or Customer.
Proposals have their own lifecycle, communication, related-record, and conversion capabilities covered in later chapters.
Estimates represent estimated charges for products or services before an Invoice is issued.
Use an Estimate when your business process calls for a formal estimate rather than an immediate Invoice.
Invoices represent amounts billed to Customers.
Invoice records can contain customer information, line items, totals, dates, status, notes, activity, communication history, and related payment information according to the functions available in the CRM.
Payments record amounts received against applicable Invoice activity.
Payment visibility can be available to users who have Payments access or appropriate access to related Invoice information.
Credit Notes represent credits associated with Customer financial activity.
The CRM supports Credit Note operations such as applying credits, reminders, notes, and refund-related workflows where permitted.
Items are reusable sales items used when building applicable transaction records.
Use existing Items when they correctly represent what is being quoted or billed. Configuration and maintenance of organization-wide financial setup values are outside this User Operations Manual unless exposed as part of your ordinary user role.
Several financial or commercial record types are registered outside the collapsed Sales menu but remain part of Customer operations, including:
These areas are also permission-controlled and are covered in dedicated chapters later in this manual.
Sales transactions should be connected to the correct Customer whenever the transaction is Customer-based.
Before creating a new transaction:
Although each Sales record type has its own workflow, several concepts appear repeatedly:
The exact values available for organization-wide financial catalogs are determined by the deployed tenant configuration. Ordinary users should select from the values presented by the CRM.
Depending on your permissions, Quick Actions can provide shortcuts for creating records such as:
Quick Actions start the same kind of operational record workflow without requiring you to navigate through every menu level first.
Do not use an Invoice merely because a Customer is expected to buy something if the business process actually requires a Proposal or Estimate first.
Likewise, do not create a new Estimate or Invoice if the correct record already exists and only requires an authorized update.
The following chapters move from this overview into the individual Sales workflows, beginning with Proposals and then continuing through Estimates, Invoices, Payments, Credit Notes, Items, Subscriptions, Expenses, and Contracts.
Operational principle: Choose the CRM record that accurately represents the business event, associate it with the correct Customer, and maintain the history on that record instead of creating unnecessary duplicates.