Sales - Acosys Documentation

When to Use

When customer invoice needs to be created.
When sales is entered directly without Sales Order or Delivery Order.
When Sales Order or Delivery Order should become final invoice.
When payment, receivable, tax, discount, reward, or stock impact must be recorded.

Open Sales / Sales.
Choose customer, division, department, date, salesperson, currency, and invoice information.
Pull Sales Order or Delivery Order when the invoice comes from pre-transaction flow.
Fill product details: quantity, unit, price, discount, tax, department, serial number, and memo.
Fill payments, customer down payment, reward, points, expenses, or additional tax when used.
Review totals, credit limit, payment amount, receivable, stock impact, and journal impact.
Click Save and follow validation messages when the application rejects the data.

Field Group	Explanation
Customer	Customer receiving the invoice and receivable balance.
Salesperson and Service Staff	Used for sales reporting and commission/service tracking.
Division and Department	Business unit and stock department.
Currency and Exchange Rate	Used when invoice currency differs from default currency.
Payment	Cash/bank/payment type, customer points, online payment, or receivable balance.

Field Group	Explanation
Customer	Customer receiving invoice and receivable balance.
Invoice Number and Date	Document identity and sales posting date.
Salesperson / Service Staff	Used for sales analysis, commission, and service reports.
Division and Department	Business unit and stock department.
Currency and Exchange Rate	Used for foreign currency invoices.
Payment Term and Due Date	Controls receivable due date.

Column	Explanation
Product	Product sold to the customer.
Unit and Quantity	Sales unit and quantity. Check conversion and stock availability.
Price	Selling price from price level, POS, or rule.
Discount	Manual or rule-based discount.
Tax	Sales tax for calculation and journal.
Department	Stock department.
Serial Number / Variant	Required when product uses serial or variant tracking.

Payments reduce receivable directly.
Customer down payment can be applied when available.
If payment is less than invoice total, the remainder becomes accounts receivable.
Credit limit validation can stop saving when customer balance exceeds policy.
Point payment depends on customer point balance and payment type configuration.

Recalculate reward and points when customer or product changes.
Sales expenses should use correct expense account.
Additional tax should be reviewed when tax is not only from item detail.
Totals should be checked after changing any reward, point, expense, or tax data.

Customer, salesperson, date, division, and department are correct.
All product lines have correct quantity, unit, price, discount, tax, and stock location.
Payment total, receivable balance, and credit limit are acceptable.
Reward, point, expense, and tax data have been reviewed.
Stock and journal impact match the intended transaction.

Customer receivable is updated when invoice is not fully paid.
Stock can be posted if not already posted by Delivery Order.
COGS and inventory journals are created according to product setup.
Sales, tax, discount, receivable, payment, and exchange-rate journals are created when applicable.

Cannot save: check customer, detail products, payment, credit limit, stock, and validation message.
Stock is doubled: check whether Delivery Order already posted inventory.
Receivable is wrong: check payment total, customer down payment, currency, and exchange rate.
Reward or points missing: recalculate and check customer/product rule setup.