Defining Country Data

This chapter discusses how to:

• Define a default retroactive processing method.

• Define triggers and segmentation events.

• Identify proration rules.

• Identify rounding rules.

• Set up pay entities and pay groups.

• Assign and view print classes.

• Define Swiss online processing options,

• Define Swiss installation options.

• Set up postal codes.

Defining a Default Retroactive Processing Method

The Default Retro Method and the On Conflict Retro Method for Switzerland are both corrective. These options are set on the Country Setup page. The core retro functionality suits all Swiss requirements.

The override retroactive to forwarding processing method is only used for net payments. The Net Payment accumulator (CH_00_54) is forwarded to the Earning element (CH_00_54f). The Final Payment element (CH_00_72), or CH_00_74 if negative, is the sum of CH_00_54 and CH_00_54f.

Global Payroll for Switzerland does not support retroactive transaction processing for the previous year. Therefore, it is recommended that during implementation that you set the retro limit to the first of January.

Additionally, several reports provide a special presentation of the results of retroactive processing. As there are no retroactive transactions that can be used for previous years, yearly reports do not process retroactive information. These reports always show the most recent results.

As a result, the presentation of retroactive information is limited to monthly and quarterly reporting. This section provides an overview on how the system handles retroactive results in these reports:

Reports with end user options:

• Pay Balance CHE (GPCHTX06)

  If Print Detail Report check box is selected, the system displays the retroactive details. The delta amounts are displaced under the month where they occurred and accumulated. They are printed in bold under the current month of the payroll. The delta amounts count only in the totals of the current month to mirror the general ledger view on the numbers. If Print Detail Report check box is deselected, no details about the periods of delta will display, only the (inside the report) forwarded amounts are to the current amounts.

• Pay Element Summary CHE (GPCHAL08)

  If the Print Detail Report check box is selected, the system displays the retroactive details separately for each month in which they originated. If the Print Detail Report is deselected, the system accumulates the retroactive transactions for all retro months in one amount.

• Personal Statement (GPCHSI03)

  The Original Month, Most Recent Month, and As of Month radio buttons are used to list data as of the selected period in which data was generated. The system saves the personal attributes for each payroll run, in case those items that were changed in the past want to be viewed again. By choosing one of these options, you can track the history of the data change.

Reports with retroactive results in delta and reversal mode:

• Payslip (GPCHAL10)

  For elements that only have changes to amounts or base pay, the system displays a new row that includes a leading asterisk (*). For elements that only have changes to percent or rate, the system reverses the old rows and displays new rows with complete data. Retro rows that have the same percent and rate are accumulated into one row.

• Pay Balance CHE (GPCHTX06)

  For elements that only have changes to amounts or base pay, the system displays only the changed row. For elements that have changes to percent or rate, the system reverses the old rows and displays new rows with complete data for these reports:

• FAK Contributions (GPCHAL04)*

• Source Tax - Monthly and Quarterly (GPCHTX02)*

• Military Service - Monthly (GPCHE01)*

Note. * If a change is for amounts only, the system creates a new row; otherwise the old row is reversed and the system additionally creates a new row.

See Also

Defining Retroactivity Defaults

Defining Triggers and Segmentation Events

In Global Payroll, the mechanism used to detect online data changes that should result in a system action is called a trigger. Examples of common data changes that might use triggers are the hiring of a new payee, a change in pay rate, and a change in job location. There are three types of triggers: iterative, retroactive, and segmentation.

Before you can use a trigger to process a payee, perform segmentation, or perform retroactive processing, you must set up a trigger definition. The definition indicates that when a particular change to the database occurs, the system should generate the desired trigger. You define trigger event IDs on the Trigger Definition page (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Triggers, Trigger Definitions) in the Global Payroll core application.

The following table lists records with triggers for Global Payroll for Switzerland.

Note. Global Payroll for Switzerland is designed to have a retroactive limit as of January 01 of the current year.

The following table lists segmentation events for Global Payroll for Switzerland:

Adjusting Trigger Effective Dates

When you define retro triggers on the Trigger Definitions-Field Values page, you can enter a positive or negative number in the Offset Days field to increase or decrease the retro trigger effective date in relation to the date of a field value change. For example, if you enter -1 in the Offset Days field for one of the values listed in the Field Values group box, and you retroactively enter that value into the database with an effective date of January 1, 2000, the system automatically adjusts the trigger effective date to December 31, 1999 (one day earlier). The system then processes pay periods going back to December 1999 rather than January 2000.

Global Payroll for Switzerland uses the offset days feature to define the triggers for retroactive terminations entered in the JOB record using the Action field (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Triggers, Trigger Definitions, Trigger Definitions. Click the List Field Values link on the Trigger Definitions page).

Note that the offset for termination triggers is -1.

The reason for this offset is that the PeopleSoft system considers the effective date of a termination entered in the Action field in JOB to be the first day that a payee is no longer working (in other words, the day before the termination is the last day the payee is considered active); however, the effective date of the trigger generated in response to this termination is identical to the termination date. This can create problems when the termination date in the JOB record is equal to the pay period begin date (meaning, the last day worked is the last day of the prior pay period). For example, assume that you enter a termination in JOB on February 1 after processing and closing the January calendar. In this situation, the system generates a trigger with an effective date of February 1, which is within the current period—a period in which the payee is "inactive" and is not picked up for processing. Because there is no trigger in the prior, closed period (January), this period will not be recalculated and any rules set up to generate termination payments will not be processed. To avoid this problem, Global Payroll for Switzerland sets the offset days for the TER, RET, LOA, LOF, TWP, and TWB action values in the JOB record equal to -1.

Important! If you define additional action values to trigger retroactive termination payments, you should set the offset days to -1.

See Also

Setting Up Triggers

Identifying Proration Rules

In addition to the 16 proration rules supplied for all countries, Global Payroll for Switzerland includes one additional rule: pseudo proration. CH_AB_PSUEDO uses CH_AB_COUNT_ALL as the numerator, and the variable CH_AB_ONE as the denominator.

Identifying Rounding Rules

In addition to the 61 rounding rules supplied for all countries, Global Payroll for Switzerland includes 6 additional rules.

Setting Up Pay Entities and Pay Groups

Before setting up Swiss options, you need to define the pay entity and pay group on the Pay Entities and Pay Groups pages. The simplest setup is to keep company and pay entity as a one-to-one relationship, where the keys are identical. However, the pay entity can also be designated as a legal entity.

A company with the features of the legal entity must exist. If you have several companies combined into one legal entity, than you can associate additional companies with the Bracket element (CH_00_BLENTTY) of the legal entity (select Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Elements, Supporting Elements, Brackets).

These companies obtain their payroll features from the leading legal entity. The system only displays these associated companies on selected reports for the purposes of sorting, selecting or for stating the related company.

Since companies and legal entities do not need to have a one-to-one relationship, you may set up the companies and legal entities within your organization using a matrix that could look something like this:

See Also

Defining Pay Entities

Defining Pay Groups

Assigning and Viewing Print Classes

For multiple reports the layout and contents is determined by a print class. You can select a specific print class on the run control page before running a report. Print Classes are defined using the GP Core List Set feature. You can use the delivered list sets or build your own print classes.

See Managing Applications and List Sets.

This table displays that delivered list sets that work best with the reports displayed in the right hand column:

To make changes to the delivered print class, access the Element Group Attributes page (select Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Elements, Define List Set. Then click the Element Group Details icon).

This table describes how to use the fields on the Element Group Attributes page for the CH_GPCHDM12 and CH_GPCHDM21 list set:

Note. Not all columns are used for every report. For the payslip report the system defines all components in one line. Thus, under element names only earnings and deductions and the selected columns correspond to the required component. For legal reports a dedicated line is required. This means that you will only see one column checked. This selection needs to match the defining component.

For example, if the Auto Assignment component base (CH_AH_D11_Base) is selected, then Print Base needs to be selected as well. For the Personal Statement report the system supports only Print Group 1 and Print Group 2. In Print Group 1, assignments appear under the Base Salary chapter. In Print Group 2, assignments appear under the Insurance Deductions chapter.

To use components for legal reports you need to first allow assignment of components in the list set by selecting GP_ENT_EGELN_VW in the Entry Prompt ID field on the Entry Type Prompts page (select Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, System Settings, Entry Type Prompts).

This table describes how to use the fields on the Element Group Attributes page for the CH_GPCHSI03 list set:

See Selecting Entry Types and Displaying Record.Field Combinations.

Defining Swiss Online Processing Options

To define Swiss online processing options, use the Online Processing Setup CHE (GPCH_EG_ONL_SETUP) component. This section discusses how to define Swiss Online Processing Options.

Page Used to Define Swiss Online Processing Options

Defining Swiss Online Processing Options

Access the Online Processing Setup CHE page (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Framework, Processing, Online Processing Setup CHE, Online Processing Setup CHE).

Note. Before you use the dashboard in Global Payroll for Switzerland, you need to specify the parameters that are explained here.

The Java architecture requires the ELM Transmit process be setup in advance. These properties are delivered with the PeopleSoft application. You can modify the property setup as needed.

Here is a brief description of the properties for the ELMTransmit process:

PeopleSoft provides the data with defaults that point to the swissdec test receivers. You need to adjust these values, according to their IT environment and then send the data to the swissdec production receiver.

You can find more information about the meaning of these fields in the swissdec guidelines and the swissdec tech doc that describes the full ELM Xml.

See http://www.swissdec.ch/software-hersteller/definitionen_standards.htm

Defining Swiss Installation Options

To define Swiss installation options, use the Installation Options CHE (GPCH_AL_INSTALL) component.

This section discusses how to define Swiss installation options.

Before you print reports in Global Payroll for Switzerland, you need to specify default choices for names, addresses, phone, and email. For example, you might want to print a payee's primary name and home address on a payslip.

Page Used to Define Swiss Install Options

Defining Swiss Installation Options

Access the Installation Options CHE page (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Framework, Processing, Installation Options CHE, Installation Options CHE).

Report Security

Select this option to enforce report security on the Personal Statement (GPCHSI03), Payslip (GPCHAL10) and Pay Balance (GCHTX06) reports. Report security limits the users than can view report results.

Setting Up Postal Codes

This section provides an overview of Swiss postal code maintenance and discusses how to update postal codes.

Understanding Postal Code Maintenance

Global Payroll for Switzerland is delivered with Swiss postal codes. The system uses the postal codes to validate and prompt for municipality codes. You can view the contents of the Postal Code table and load updates from the Swiss Post website.

Updating the Postal Code Table

To update the Postal Code Table:

1. Download the latest update from the Swiss Post website. Note the file path.

2. Use the Load files page to enter the file path and load the updates to the Postal Code table.

When you load updated postal codes to the Postal Code table (GPCH_POSTAL_CD), the system writes to the table only the codes that are different from the existing ones. New records are marked with a timestamp. Using this timestamp, you can identify all records that were written into the system by a specific user action. You can therefore view and, if necessary, delete all records associated with a particular time stamp.

Pages Used to Update Postal Codes

Updating the Postal Code Table

Access the Load Files page (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Framework, Organizational, Postal/Municipality Codes CHE, Load Files).

Postal Codes File	Enter the complete path to the file in which you downloaded the postal code updates from the Swiss Post website.
Load Data	Click to load the postal code data into the Postal Code table.

Maintaining Swiss Payroll Salary Bases

Calculations for salary bases are contained in the standard version of the application. You can, however, add or change salary bases in some cases. Intern bases, which are maintained only by the producer, are not discussed here.

For the recommended accumulators buildup, use the normal types of salary via CH_00_0. For all standard accumulators we provide a custom entry, which is already a member of the standard accumulator.

The naming convention for the custom entry is CH_XX_CYY, where XX stands for positions 4 to 5 and YY stands for the positions 8. For example, CH_00_C0 is the custom entry for CH_00_0.

This enables you can add customer earnings to custom accumulators to avoid any overlap with any additional delivery of standard accumulators. For example, if you had a customer earning called Cust_Salary, which contributes to all legal bases, then you would add this earning to accumulator CH_00_C0, which is the custom entry for standard accumulator CH_00_0.

Refer to the illustration below for a graphical representation of how accumulators are used in the Global Payroll for Switzerland application:

Appendix: Global Payroll for Switzerland Accumulators provides an overview by functional category of the accumulators that you need to maintain.

The Appendix lists the accumulators for these functional categories:

• Subtotals

• Social Insurances

• Source Tax

• Tax Statement 2006 (and later)

• Statistics

• Source Tax Reporting

• Other Reporting Controls

The salary bases delivered in the standard version of the application are sufficient in most cases. You, however, can further define salary bases and their respective accumulators to meet your own needs.