Zayeen FAQ

The most common causes are inactive status, filters that are too narrow, or user access rights that limit visible data. Also check whether the record was actually saved and whether it belongs to the period you are reviewing.

Start with required fields, number format, dates, accounts, master data references, and the validation message shown on screen. If the form has detail lines, also review quantity, price, discount, tax, or approval status on each line.

Make a backup before restore, direct database edits, maintenance SQL, cut-off, cost repost, empty transaction, or any other mass change that can affect transaction history. See Maintenance / Backup and Restore for the detailed guidance.

Make sure the POS point already exists, the user has the correct access, the cash or shift setup is ready, and the default printer or payment setup is not empty. For the full workflow, open the POS Start page.

Use Print Designer for HTML or EJS-based print templates. Before changing a production template, create a copy or keep a backup so you can roll back quickly if the output is wrong.

Use Report Designer. Review the query, parameters, and output fields that the report uses. If the report becomes empty or starts failing after a change, roll back to the last stable version or use a safe duplicate.

Cut-off is used to move opening balances and limit historical transactions in older periods. It affects journals, stock, balances, and reports, so only run it after a backup and after finance fully understands the impact. See the Cut Off page.