Sales Overview Public

Sales

Standalone ERPat Sales module: clients, customers, invoices, estimates, estimate requests, the public estimate-request intake form, sales matrix/summary, client groups, and stores. Controllers, views, routes, menu and config are owned by this package and loaded at runtime through the HMVC compatibility layer (App_Router + module package paths). Sales-domain.

Guide version: r1 Module version: 1.0.0 Updated: 2026-07-30 Estimated time: 2 min
You are viewing version r1 of this guide. View the current version
End-user documentation

Sales

Customer revenue operations for clients, customers, estimates, invoices, estimate requests, public request intake, stores, client groups, and sales reports.

Where users startSales
Primary goalHelp a beginner understand what the module does and how to operate it safely.
Last reviewed2026-07-10

Purpose and What Problem This Solves

The Sales module centralizes customer and revenue workflows. It helps teams maintain customer records, send estimates and invoices, process public requests, group clients, manage stores, and review sales performance.

Plain-language rule: If a user can explain what record they are creating, why it exists, who owns it, and what happens next, they are ready to use the module responsibly.

Who normally uses this module

Sales teams Account managers Billing staff Store managers Finance reviewers Customers using public request forms

What You Can Do Here

  • Create and maintain client/customer records and groups.
  • Prepare estimates, convert approved work into invoices, and track billing status.
  • Collect estimate requests from a public intake form.
  • Maintain store records and sales matrix summaries.
  • Coordinate with Finance, Projects, POS, and Procurement workflows.

Core Concepts and Terms

Learn these words first. Most user mistakes happen when a beginner opens a form without knowing what the record represents.

Client or customer

The person or organization buying from the business.

Estimate

A proposed price or scope before billing becomes an invoice.

Invoice

The billing document requesting payment for goods or services.

Estimate request

A customer-submitted inquiry asking for pricing or scope response.

Client group

A segmentation label for reporting, access, pricing, or organization.

Store

A selling or business location used in sales and related operations.

Beginner Quick Start

Use this first-run path in a training database or with a supervised account before handling live records.

  1. Create client groups and confirm required customer fields.
  2. Add a client/customer record with accurate billing, contact, and tax details.
  3. Create an estimate or handle a public estimate request.
  4. Convert approved work to invoice and confirm payment workflow with Finance.
  5. Review sales reports for outstanding estimates, invoices, and revenue trends.
Before using live data: confirm the module is enabled, your role has the right permissions, required master data exists, and you know the rollback or correction process for mistakes.

Standard Operating Procedures

These SOPs describe the routine operating pattern. Your company policy may add approvals, attachments, or segregation-of-duties controls.

Actor: Sales representative

Handle a new estimate request

  1. Review the request details, customer contact information, and requested service or product.
  2. Create or match the client record to avoid duplicates.
  3. Prepare an estimate with scope, price, validity, taxes, and terms.
  4. Send the estimate and follow up before expiration.
Actor: Billing user

Create an invoice

  1. Confirm the customer, billable items, quantities, prices, tax, due date, and payment terms.
  2. Create the invoice from an approved estimate or directly when policy allows.
  3. Send the invoice and record delivery or customer acknowledgement.
  4. Track payment status and escalate overdue balances according to policy.
Actor: Account manager

Maintain customer records

  1. Search before creating new customers to avoid duplicates.
  2. Keep contact, billing address, tax, group, and assigned owner fields current.
  3. Record important customer notes in the correct module surface.
  4. Archive inactive or duplicate records only after checking transaction history.

Industry Notes and Good Practice

  • Sales data quality begins with customer records. Duplicate customers split revenue history and confuse support.
  • An estimate is not an invoice. Use estimates for proposal and approval; use invoices for billing and receivables.
  • Clear terms reduce collection problems. Include due dates, taxes, validity, and accepted payment methods.
  • Public estimate request forms should set customer expectations about response time.

Controls, Data Quality, and Review Checklist

Use this checklist during onboarding, monthly review, and process audits.

  • No duplicate active customer for the same buyer unless there is a clear business reason.
  • Estimates have validity dates, clear scope, pricing, and terms.
  • Invoices have due dates, tax treatment, and accurate line items.
  • Outstanding estimates and overdue invoices are reviewed regularly.

Related ERPat areas

Finance for receivables and payments Projects for delivery work POS for store selling Inventory for item catalog

FAQ and Troubleshooting

Should I create a customer before an estimate?

Yes, or match an existing customer, so the sales history remains connected.

Can an invoice be changed after sending?

Follow your billing policy. Material changes may require revision, credit note, or a new invoice.

Where do public estimate requests arrive?

They appear in the estimate request workflow for review and conversion.

What should beginners learn first?

Customer search, estimate creation, invoice creation, payment status, and sales report filters.

Report a content problem