Sales Module

This module is the chain of documents a business raises when it sells on terms: an inquiry, a priced quotation, a confirmed order, a delivery, the invoice, and the documents that correct an invoice afterwards. It shares its document engine, master data and FINAL posting status with the retail till, which has its own module: Point of Sale.

Start here.

Setting the module up? Read Configuration first: what must exist before the first invoice posts.
Doing a job — quoting, invoicing, taking goods back, chasing a payment? The Sales guides walk each one, step by step.
A number already looks wrong? Start from the symptom table in Core concepts §6: the cause, the fix, and for the commonest symptoms the troubleshooting page that goes further.

Only five sales documents post. The invoice, return, credit note, debit note and refund note reach the ledger at FINAL; a quotation, an order, a delivery order and a Sales GIN post nothing, and a credit note moves no stock. Core concepts §2 has the table, the journal lines and the diagram.

The module’s pages

Core concepts

Posting status, which documents count, availability vs balance, how a sale is reversed

Configuration

What must exist before the first invoice posts, and what each gap looks like

Use cases

The order-to-invoice desk, stock at a customer’s site, marketplace orders, and selling inside the group

Group discount

A discount off the whole document is a line, with its own GL account and e-invoice field

Identity verification and e-signature

The one eKYC screen, on a sales contract, and what it does not do

Reports

Which sales report answers which question, and commission

Best practices

Operational advice that follows from the mechanics

Sales that arrive from another system

Invoices that arrive by sync, and how to notice a feed has stopped

For developers: API notes

Where the REST API is documented

Applets in this module

Grouped by the job they do; each applet’s own page carries its fields, settings, posting proof and failure modes.

Job	Applets
Before the sale	Sales Inquiry (a request, before there is a price) · Sales Quotation (a priced offer; posts nothing) · Sales Proforma Invoice
Taking and filling the order	Sales Order (posts nothing; reduces available stock where the company links orders to invoices) · Delivery Order (moves no stock) · SO Consolidation (finalised orders billed as one draft invoice per customer, branch and sales agent)
Billing	Sales Invoice (receivable, sales and tax posted, stock out) · Recurring Sales Invoice (a scheduled run raises each invoice) · Sales Contract (the agreement a repeating sale is billed from)
Correcting a sale	Sales Return (goods back) · Sales Credit Note (money off, no goods) · Sales Debit Note (an extra charge) · Sales Refund Note (money and goods back)
Service, and stock at a customer’s site	Job Sheet · Car Workshop (a consultation that raises the job’s documents) · Customer Consignment (you invoice what sold)
Records that move nothing	Sales GIN and Sales GRN. Neither moves stock; the invoice does
Reporting, commission and hand-off	Sales Report and a supplier-facing Supplier Access report · Sales Commission (from FINAL orders, invoices, cash bills and receipts) · Custom Processor (finalised documents queued for an external system)

The rest of order-to-cash, in neighbouring modules

These steps belong to the same order-to-cash flow, joined by the same documents — the receipt voucher knocks off this module’s invoice — but their applets are filed with the module that owns the record.

Step	Applet, and the module it is filed under
Prices and price books	Pricebook — Core
The customer, its credit terms and limit, and the blacklist	Customer Maintenance — Core
Collecting: receipts knocked off against invoices, statements, debtor ageing	Receipt Voucher, Statement of Account, Debtor Report — Financial Accounting
Stock availability and reservations	Inventory
Submitting the invoice to LHDN	E-Invoice
Walk-in sales at a till	Point of Sale

What the module does not do, and what to do instead

No routed approval on a quotation, an order or an invoice. The approval engine, which e-mails approvers and records their decision, covers purchase orders and requisitions only. To separate duties on a sale, an applet setting hides FINAL and a permission gives it back to named people, so clerks save drafts and a supervisor finalises. It acts on the screens only, not on documents an integration finalises through the API (Core concepts §4 has the settings and a test).

The credit limit is a check on two screens, in one company: the Sales Order and Sales Invoice screens refuse FINAL once the customer’s credit in that company is used up. The stop the server enforces at FINAL is the blacklist (Stopping Supply to a Customer lists what it refuses and the routes it does not cover). Exposure across the group is the credit controller’s to read, company by company (Deciding on Credit).

Where the numbers on these screens come from

Each figure is either written once and kept, or worked out again when you look. The table, with one invoice followed through, is on Core concepts.

How you know it worked

The thirty-second check of one test invoice — Posting tab, journal, stock — is on Core concepts.