Module FAQ
Quick answers for the modules that generate the most daily support questions: Sales, Purchasing, Products and Inventory, and Accounting.
This page is meant for fast operational answers. If the issue touches transaction history, balances, stock, or journals, continue to the detailed module documentation before making changes.
Sales
Check the product default price, selected unit, discount rules, customer group, and any price formula used by the company. If the transaction comes from a sales order or POS, confirm that the expected pricing source matches the workflow.
Check whether the transaction is still draft, not approved yet, not delivered yet, or configured to reduce stock at a different step. Also confirm the product, warehouse, transaction date, and selected unit.
Start with the customer, date, detail lines, total value, receivable or cash account, tax, and payment fields. If the form depends on approval, also check the related document status such as sales order or delivery order.
Purchasing
Common causes are invalid document status, different supplier, mismatched division or department, or the source document already being fully consumed by the next process. Also review date filters and user access rights.
Review purchase price, discount, tax, supplier down payment, extra charges, and whether the purchase invoice has actually been posted. If returns or payable adjustments exist, compare them with the correction transactions as well.
Use it when many purchase orders need to be created at once from clearly defined demand, such as branch requests or stock planning. Even in mass entry, review supplier, quantity, price, and receiving schedule before saving.
Products and Inventory
Check transaction date, warehouse or department, product unit, approval, and whether inventory adjust, moving, in, out, or cost repost has already been run. Differences may also appear after backdated transactions change historical balances.
Check product active status, product group, POS point mapping, default unit, and role-based product filters. Make sure the product is allowed for the module you are currently using.
Cost repost is usually needed after inventory corrections, backdated changes, wrong costing, or imports that change stock order. Run it only after a backup and when no one else is actively editing stock transactions.
Accounting
Review default accounts, transaction dates, approval, posting summary, backdated transactions, and whether cut-off or closing book has already been executed. Also compare division, department, and report period filters.
Closing book is used when the accounting period is final and current profit and loss must be moved into retained earnings. Cut-off is used when a new opening balance needs to be created and older history must be limited. Both require backup and finance review first.
Identify the root cause, impacted tables or transactions, the safe backup point, and the effect on journals, balances, and reports. For this type of technical action, review Maintenance / Backup and Restore before changing anything.