Pay Template

1Purpose #

• Defines ONE salary structure — a set of priced attendance/leave/production types — that any number of employees can share.
• Attendance entries record quantities of the types; this template prices them; payroll multiplies the two for every employee assigned to it.
• Typical templates: one per grade or category of staff (Workers, Staff, Drivers), each pricing a day of attendance, an hour of overtime, leave, and any fixed items.
• The Employee master's Pay Template field and the paybill preparation both read from here.

2Your first pay template, step by step #

Suppose factory workers earn a basic salary plus hourly overtime. The page opens in Add mode.

1. Type Workers into Name . It is required and must be unique across all templates.
2. Add a Description if the name alone will not tell templates apart later.
3. Press Add Line and pick the type BasicSalary — the Unit fills itself from the Attendance Type master.
4. Enter the monthly amount in Rate/Value .
5. Add a second line for OverTime and enter the hourly rate — or -999 to derive it from BasicSalary divided by the days in the month, or -888 to derive it from this line's Assessable Value divided by the days in the month.
6. Switch Discard In Payroll Preparation ON only for a line that should stay in the template but be skipped when payroll runs.
7. Press Save (F5) and confirm. The template and its lines are saved together — if anything is wrong, nothing is half-saved.
8. Now use it: open the Employee master and pick this template in the employee's Pay Template field.

3How to use it #

1. Find (F2) lists every template; pick one to load it with its lines.
2. Add (F3) starts a new template with the cursor in Name.
3. Add Line appends a priced line; Remove marks one for deletion on the next save.
4. Save (F5) commits the template and its lines together in one transaction.

4Field details #

• Name is required and unique — employees and history rows reference the template by this name.
• Description is free text, multiline (Enter advances; Ctrl+Enter inserts a newline).
• Type (per line) comes from the Attendance Type master; a template prices each type at most once.
• Unit follows the picked type automatically and can not be edited here — change it in the Attendance Type master.
• Rate/Value is what one unit of the type pays. -999 = BasicSalary ÷ days in the month; -888 = this line's Assessable Value ÷ days in the month.
• Assessable Value feeds the -888 formula (and assessment-based calculations).
• Discard In Payroll Preparation keeps the line but skips it when payroll is prepared.
• Extra Remuneration Rate/Value appears only when the preference Allow Employee Extra Remuneration is ON; -999/-888 work there too.

5Shortcut keys #

• F2 Find · F3 Add · F4 Modify · F5 Save · Esc Cancel.
• Enter moves to the next field; off the last line cell it appends a new line.
• Keys belong to the focused copy of the page; a dialog's own keys win while it is open.

6Why is a pick-list empty? #

• A loaded line whose type was created elsewhere still shows it — the stored value is kept selectable even if the pick source has changed since.
• Extra Remuneration Rate/Value is not a pick-list but disappears entirely when the preference Allow Employee Extra Remuneration is OFF — its stored values are preserved untouched.

7Rules and integrity #

• Unique name. The template name is the table's primary key, so it is checked before saving and again on the server.
• One line per type. The line table's key is template + type — the same type can not be priced twice; checked here and on the server with the same message.
• Every line names its type. A line without a type can not be saved (it is part of the key).
• Lines save row by row. Editing a template does not delete and re-insert its lines, so their identities survive an edit; the template and its lines save in one transaction .
• Deletes are guarded. Deleting a template removes its lines with it, but the database refuses the delete while history rows or allocations still reference it.
• Every line written is stamped with your login branch , exactly like the legacy form.