Advanced PECI Topics

Overview

This chapter covers advanced PECI features you may want to take advantage of. To help you consider whether these features would make sense for your integrations, we will define each feature, discuss use cases, and explore configuration options.

Objectives

By the end of this chapter, you will be able to:

Configure an additional primary process for larger data or data that does not follow the same scheduling requirements as your other integrations.

Use the Effective Stack Sync service to run your integrations more frequently and not impact tenant performance.

Additional Primary Process

When you have multiple Payroll Effective Change Interface integration systems for a single pay group, you can enable the Additional Primary Integration attribute. You can then run any of the additional integrations as primary integrations for specific purposes.

Use the main primary process for the on cycle data feed to the third-party payroll system. Use the secondary primary system for data that are larger in volume or data that does not follow the same scheduling requirement like the other on cycle data feed.

Selecting the Additional Primary Integration attribute also allows you to configure the following integration field attributes in the Pay Group Summary section:

Additional Primary Integration System

Last Processed Periods

Last Processed Periods From

Last Processed Periods To

Effective Stack Sync

Effective Stack Sync Service is a new feature in PECI that allows you to run the batch process more frequently without impacting tenant performance. Additionally, it runs the process with the transaction logs service turned on when running every 6 hours for efficiency and behaves as though transaction log service is turned off when running it once a day as a "sweeper" process.

Use Case

PECI is designed to run as a batch process, and should not run more than once a day.

Clients want a more frequent synchronization between Workday and their third party system.

*EDI real time integration only supports hires and terminations.

There used to be an option of either running PECI with Transaction Log enabled or Transaction Log disabled.

This new Effective Stack Sync Service addresses the limitations stated.

Benefits

Effective Stack Sync lets you run integrations built from the Payroll Effective Change Interface integration template more frequently, up to every 6 hours. This enables you to refresh internal data warehouses with timely and accurate information from Workday.

Configure Integration System with Transaction Log and Effective Stack Sync Service enabled.

Set up Maintain Payroll Integration Systems for Pay Group.

Configuration

Configure Integration System with Transaction Log and Effective Stack Sync Service enabled.

Enable Transaction Log and Effective Stack Sync Service.

Set up Maintain Payroll Integration Systems for Pay Group.

Launch Parameter - Effective Stack Sync Run.

Real Time Data

Event-Driven Integration (EDI) and Local Payroll Data (LPD) are the two technologies that allow CCTPP to accomplish real time integration with third party payroll systems. LPD allows us to view and edit data that is outside the Workday tenant as though it is locally stored in Workday. EDI allows us to send time-critical data to third party systems as they are entered in Workday.

Local Payroll Data (LPD)

While the PECI integration is a great solution for transmitting payroll data to third-party payroll vendors, there may be times when the data needs to be transmitted immediately. For these times, you have the option to use local payroll data. Local payroll data allows you to immediately pass data to a third-party payroll vendor without ever leaving Workday. Based on data requirements provided by the payroll vendor:

You can modify each worker's local payroll data on a page in Workday. The page displays in the third-party payroll vendor's format.

Workday sends the new and changed local payroll data directly to the third-party payroll vendor where the data is saved. The data does not persist in Workday.

Local payroll data supports:

Payroll administrators for data entry. Employees currently cannot enter local payroll data through employee self-service.

Employees who belong to third-party pay groups. An employee must also exist in both Workday and the third-party payroll system. The employee's ID must be the same in both systems.

The third-party payroll vendor controls:

Validations performed during data entry.

Names of fields and options.

The integration depends on the availability of the third-party APIs and data. However, Workday authenticates and controls worker access to local payroll data through the Maintain Local Payroll Data
task. The local payroll vendor authorizes and controls the local payroll data displayed in Workday.

Note
:

For new workers, you must run a certified payroll integration before entering local payroll data.

You may also use local payroll data when the external payroll vendor requires fields that are not supported by Workday.

Event-Driven Integration (EDI)

The Event Driven Integration for Third-Party Payroll integration service enables you to configure business process steps that send information from Workday to your external payroll vendor automatically. Your payroll vendor validates the information and returns any errors to you. You can then correct the errors and resubmit the corrections immediately, saving time and money.

For example, when you hire, rehire, or terminate an employee, event-driven integration sends that information to your external payroll vendor through the Hire
or Termination
business processes. The payroll vendor confirms receiving the information successfully or sends back errors for you to correct.

To use event-driven integrations, you or your external payroll vendor must build two endpoints to:

Deliver the hire and termination information to the external payroll vendor.

Retrieve the status and errors from the external payroll vendor.

You also need to configure a REST API client to enable your external payroll vendor to update Workday with the processing status of hires and terminations.

Result

After the Hire or Termination business process completion step, Workday sends the employee information to your external payroll vendor. The owner of the Review Event Driven Integration step receives a successful completion message or notification of errors to correct in their My Tasks. Correct errors and resend to your external payroll vendor.

PECI to Excel

The delivered output for PECI integrations produces an XML output file and HTML audit files. However, there may be times when neither file is desirable. For these scenarios, Workday delivers a studio integration that will transform the PECI XML output into an Excel file. This output is ideal for manual reviews and submitting payroll for a relatively small group of workers.

To obtain the Excel output, you will need to create a Payroll Integration Configurable Output integration service and configure it within your PECI integration's business process. To create layouts and definitions for the Excel output file, you will need security access to the Set Up: Payroll Interface
domain in the Payroll Interface functional area.

Recommendations
:

To help avoid truncated or invalid labels in your Excel workbook, create a label for your payroll interface configurable output layout:

With less than 31 characters.

Without these characters: : \ / ? * [ or ].

To help ensure that Workday creates an output file for each pay group in your PECI integration:

Create a separate Payroll Interface Configurable Output integration system for each pay group that you want to include in your Excel output file.

Use the name of the pay group as the Input Document tag.

Limitations
:

The Payroll Interface Configurable Output functionality does not support:

Creating an Excel output for more than 5,000 workers.

Configuring field overrides.