Tätä artikkelia ei ole vielä käännetty suomeksi.
Not to be confused with Person groups, Payment groups collect people who should be paid something (e.g. salary, wage, bonus, etc) on the same schedule. A persons' membership to a group, indicates they should be compensated according to its payment periods.
This information can be used to filter personnel for reporting, integrations, and payroll.
Payment groups are created and managed from Employees > Payment groups. The Payment groups menu option is only visible to administrators.
A list of all Payment groups is shown, with the option to add new payment groups1 or view the details and members of a group by clicking the view icon2.
Creating a new payment group
To create a new payment group, provide a code, name and description. Then configure payment periods.
Code: a unique code for a payment group. Two payment groups cannot have same code.
Name: payment group name. Name is also unique and two payment groups cannot have same name.
Description: a detailed description for a payment group.
Payment periods represent information about when salary should be paid, and for what dates a given salary is for. Payment periods can be added individually or generated many at a time. Any existing payment group can be freely edited. Below is a breakdown of the salary payment fields:
- Payment period dates - The payment beginning and end dates represent the inclusive range from which salary is calculated for the related payment date.
- Payment date - The date upon which salary should be paid. This field automatically avoids non-banking days by moving the payment date to the first earlier banking day.
- Accounting value date (Book keeping date) - (Optional) The date on which the salary information for this payment period was recorded to bookkeeping.
The 'Add multiple payment periods' button, facilitates generating multiple lines of payment periods.
Please note: This tool automatically avoids payment dates falling on non-banking days. The following generation options are available.
- Monthly - Generates a payment period for each month for the period of repetition selected.
- Twice a month - Generates two payment periods for each month for the period of repetition selected.
- Bi-weekly - Generates two-week-long payment periods from the start date to the repeat until date.
Individual lines of salary information can also be added when needed. For example, in an exceptional payment situation for the whole payment group, or where a payment group does not follow a regular payment repetition.
When a person is linked to a Payment group, it indicates that their salary should be paid according to its' salary payment dates.
Membership can be set from either a persons' information (Employees > Persons > Person Info) or from the payment group management (Employees > Payment groups). Membership can be defined with a start date using the validity controls. This allows the configuration of a person to join and/or switch payment groups in advance of the required change date.
The Nepton Payroll product utilises the Payment group information to ensure that all peoples' worktime events for a salary period have been approved, salaries are calculated correctly, and that salaries can be paid on time.
Worktime integration rulesets
Rules for collecting and sending salary data to other systems can use the payment group(s) as a filter so that only the data for the desired people is included. Please see the Ruleset documentation for more details and examples.
Many features around Nepton include the option to filter and/or select people. The Payment group can be used as a filter so that only people from the desired payment group(s) are included/shown.
This can be very useful for reporting purposes. For example, you can report upon the absences of your monthly paid workers, from a specific person group, in only a few clicks.
In the future, Payment groups will be used to make approval recommendations in Nepton more intelligent and to provide proactive notifications when a supervisor should perform approvals to avoid payroll delays.