TRIAL Trial run - not yet ready for production use. InvoiceNET® ERP and this website are open to everyone for trial and testing, and are not yet ready for production use. Please do not keep real business records here: data entered during the trial may be reset, and features may change. Tell us what you find through Suggestions & Feedback. Open the feedback form
InvoiceNET®ERP Software for Business

Colour

These are the themes of InvoiceNET® ERP itself. Your choice is remembered on this device.

Help centre / Payroll

Attendance Type

An attendance type is the unit of everything payroll counts — worked days, overtime hours, leave, produced pieces, trips. Pay templates, attendance entries and leave policies all reference these types, and Rate Options says where each type's rate comes from.

1Purpose #

  • Defines ONE countable payroll item — a day of attendance, an hour of overtime, a leave day, a produced piece, a trip — with its unit and whether it adds to or deducts from pay.
  • Attendance/leave/production entries record quantities of these types ; pay templates price them; payroll multiplies the two.
  • Leave-based types are what the Leave Policy master's Leave Type picker offers; shift rules and site rates also reference types from here.
  • Seeded rows marked System (Basic Salary, Days, Weeks) are the backbone of salary calculation — leave them be.

2Your first attendance type, step by step #

Suppose overtime is paid per hour at a fixed standard rate. The page opens in Add mode.

  1. Type OverTime into Name . It is required and must be unique across all types.
  2. Pick Base Type OverTime — the base type tells payroll what kind of quantity this is (attendance, overtime, leave, production, trips...).
  3. Pick Unit Name HRS . Units come from the Unit master — create the unit there first if it is missing.
  4. Leave Calculation Type on + so the item adds to pay; a deduction item (absence, unpaid leave) uses - .
  5. Leave Primary Group ON. Switch it OFF only to nest this type under another one via Under Group (for grouped reporting).
  6. Pick Rate Options : Default takes the rate from the pay template; Formula opens the formula box; Rate Defined Here opens the Standard Rates grid; Manual means the rate is keyed at entry time; Rate From Site-Master reads the work-site rate.
  7. If you chose Rate Defined Here , press Add Rate , set the effective date and the rate. With Branch-Wise Rate ON (ERP edition only) each row names its branch; otherwise rows sit on your login branch.
  8. Press Save (F5) and confirm. The type and its rates are saved together — if anything is wrong, nothing is half-saved.
  9. Now use it: add the type to a pay template, record it in attendance entries, or point a leave policy at it if it is a leave type.

3How to use it #

  1. Find (F2) lists every type; pick one to load it with its standard rates.
  2. Add (F3) starts a new type with the cursor in Name.
  3. Add Rate appends a standard-rate row; Remove marks one for deletion on the next save.
  4. Save (F5) commits the type and its rates together in one transaction.

4Field details #

  • Name is required and unique — pay templates, batches and policies reference the type by this name. Print Name is what payslips print instead, when set.
  • Base Type : Attendance, OverTime, Leave, Production, BasicSalary, Others, Trips or Extra Remunaration — what kind of quantity the type counts.
  • Unit Name is the counting unit, from the Unit master (DAY, HRS, NOS, MONTHS...).
  • Calculation Type : + adds the item's amount to pay, - deducts it.
  • Primary Group / Under Group : a non-primary type nests under another type for grouped reporting; a primary type has no parent (the legacy form disabled Under Group for primaries).
  • Rate Options : Default (pay template), Formula, Rate Defined Here (the grid below), Manual, or Rate From Site-Master.
  • Formula : -999 divides BasicSalary by the days in the month; -888 divides the template's AssessableValue by the days in the month.
  • Deduct From Gratuity — days of this item (unpaid leave, absence) reduce the gratuity calculation.
  • Is Fixed Item — added to payroll from the pay-template allocation even with no entry recorded.
  • Calculate Qty From In-Time And Out-Time — the entry's quantity is computed from the punched times.
  • Standard Rates : one row per branch per effective date; the newest date at or before the payroll period wins. The rate applies when the employee has no pay-template allocation for this type.

5Shortcut keys #

  • F2 Find · F3 Add · F4 Modify · F5 Save · Esc Cancel.
  • Enter moves to the next field; off the last rate cell it appends a new rate row.
  • 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? #

  • Unit Name comes from the Unit master, table UNIT . If it is empty, no units exist yet — create DAY, HRS, NOS there first; the database refuses a type whose unit does not exist.
  • Under Group lists the types already saved here — it is empty until this master has records, and it only matters when Primary Group is OFF.
  • Branch (in the Standard Rates grid) is your user-scoped branch list — the branches assigned to your user for the selected company. If it is empty, your user has no branch allocation; an administrator assigns branches in user management. The Standard Rates area appears with Rate Options = Rate Defined Here ; the Branch-Wise Rate switch and the Branch column are ERP edition only.
  • Base Type , Calculation Type and Rate Options are fixed lists and are never empty.

7Rules and integrity #

  • Unique name. The type name carries its own unique index, so it is checked before saving and again on the server.
  • Name, Base Type, Unit Name and Rate Options are required ; Primary Group and Calculation Type default to Y and + .
  • A primary group has no parent — switching Primary Group ON clears Under Group, exactly like the legacy form.
  • One rate per branch per effective date. The rate table's key is type + branch + date — checked here and on the server with the same message.
  • Rates save row by row. Editing a type does not delete and re-insert its rates, so their identities survive an edit; the type and its rates save in one transaction .
  • Renames propagate. Pay templates, paybill batches, leave policies and product mappings follow a rename automatically; ID-based references (entries, requests, shift rules, site rates) never notice it.
  • Deletes are guarded. Deleting a type removes its standard rates with it, but the database refuses the delete while templates, entries, policies, requests or any other referencer still has rows.
  • Without the ERP licence the branch-rate area stays hidden and a save leaves any stored rate rows exactly as they are.

This is the help InvoiceNET® ERP shows beside the Attendance Type screen. Whether you have the screen depends on the modules of your licence and the rights your administrator has given you.

See this screen for yourself

The demo is the real product, with a company of your own.

Something went wrong. Please reload the page. Reload ×