Security entity for Payroll

Multiple legal entities

For organizations with multiple legal entities:

• A Security Entity must only include one legal entity. Define the legal entity on every HR organization unit that is marked as “Is an Entity.”
• We recommend implementing a security entity structure by legal entity if the HR organization has multiple legal entities and data should be secured by legal entity.
• Employees cannot have multiple work assignments with different legal entities. This requires multiple resource records. These employees must have a unique login for each resource record by legal entity.

Payroll Administrator functions

The Payroll Administrator Role is responsible for these functions when Security Entity is enabled:

• Administration
  • Creating and maintaining payroll configuration
  • Creating and maintaining Configurable Field by Country
• Setup codes
  • Creating and maintaining setup codes that are not definable by security entity
  • Creating and maintaining setup codes with a blank security entity
  • Running actions on setup codes with a blank security entity. For example:
    • Update Employee Deductions
    • Update Linked Deductions
    • Create Group Recurring Time Records

Rules

Follow these rules for security entity:

Function	Rule
Payment schedule	Security entity is required.
Tax deductions	Security entity must be blank.
Deduction payment group	Security entity must be blank if grouping tax deductions.
Bank code	The bank code defined on Configurable Field by Country must have a blank security entity. This is the default bank code for the HR organization. It defaults to employee payments for any security entity if a bank code is not found on the related HR organization unit. The bank code must be defined on every HR organization unit, including parent and children. If left blank, then the bank code from Configurable Field by Country defaults to employee payments.
Time record batches	Time record batches are not definable by security entity because auto batch numbering can be enabled on Configurable Field by Country. Use separate batches and include “security entity” in the batch description.

Follow these rules for pay structure and deduction structure:

• Use these considerations when defining pay or deduction structure:
  • If either the pay structure or the deduction structure is shared across all security entities, then leave the Security Entity field blank on all components of the related structure.
  • If either the pay structure or the deduction structure is defined by security entity, then define security entity on all components of the related structure.
• Edits are displayed for the ActorOrgUnit Payroll Administrator when attempting to create the pay structure or deduction structure with codes that have Security Entities that are not aligned. For example:
  • Pay structure includes shift tables, pay codes, pay summary groups, pay summary group relations, and pay classes.
  • A shift table with a security entity cannot be tied to a pay code that has a blank security entity.
  • A pay code with a security entity cannot be tied to a pay summary group with a blank security entity.
• Exception: Pay classes and deduction classes defined with a blank security entity are allowed to group data across security entities for easier set up in year-end configurable fields.

Security entity is not allowed for setup data that is used across Security Entities.

Function not definable by Security Entity	ActorOrganizationUnit Payroll Administrator
Configurable Field By Country	Inquiry Only Access to perform BSI Connection Testing
Payroll Configuration	Inquiry Only
Bank Routing Numbers	Inquiry Only
Remuneration Codes	Inquiry Only
Tax Deductions	Inquiry Only
Tax Provider Codes, Authorities, Categories	Inquiry Only
Resident Codes, Additional Tax Codes	Inquiry Only
Defined Contribution Limits and Rules	Inquiry Only
Garnishment Rules, Types, Formula Numbers	Inquiry Only
Compliance Document setup	Inquiry Only
Workers Compensation Policies, Classifications	Not accessible
Regulatory	Not accessible