Settings that matter

Config, not code

Every company-specific rule in this product (grace periods, lateness thresholds, the leave year, bonus conditions, rounding) lives in a settings table, never in an if statement written for one customer. That is not a style preference: the moment a rule lives in code instead of configuration, this stops being a product one person can run for many companies at once. A change to your policy is a form submission, not a deployment.

Settings are grouped into five sections. This page covers what each one is for and the entries most worth a look in your first week; the settings screen itself always shows the current value and a plain-language explanation beside it.

General

Dates, times and language for the account as a whole, plus whether calendar events like birthdays and work anniversaries are shown, and to whom.

Payroll

How salary is calculated and paid: the pay cycle's start day and pay day, whether a month is costed on calendar days or a fixed basis, how paisa amounts round, the overtime multiplier and whether overtime is paid at all, whether EOBI is deducted from the employee's own share, whether a manager can see the salary of the people reporting to them, and the payslip's format.

Attendance

What counts as late, half day and outright absent: three separate minute thresholds, each a setting, so a factory floor and an office with a different shift culture can each pick numbers that fit them. How many late marks cost a full day, whether lateness reduces pay, and the check-in geofence radius in metres also live here (never below 50 metres; see Attendance and check-in for why).

Leave

The leave year's start month, whether unused days carry forward and the most that can, and the sandwich rule, off by default because it is a genuine surprise the first time it applies to someone. See Leave for what each of these actually does to a balance.

Notifications

Whether people are told when a decision is made on their leave, expense, loan or attendance request, and whether a helpdesk reply notifies whoever opened the ticket. Each one is a real switch: if nothing in the product reads a setting, it does not appear here, because a switch that changes nothing is worse than no switch: someone turns it on, tells a colleague it is on, and nothing happens.

Where this stops

Statutory figures (FBR tax slabs, EOBI and PESSI/SESSI rates, minimum wage) are never a company setting. They are versioned platform configuration, published once when the law changes, and every company gets the update at the same time. A company can configure how its own policy works; it cannot configure what the law says.