In 2016, Workday introduced – PECI (Payroll Effective Change Interface) – designed to improve users’ visibility of pay transactions. PECI is a full-stack integration. It transmits each payroll change for each worker sequentially and includes the effective date and data entry date for each change.
Capabilities:
- Supports Effective dating / Sequence of records to represent all worker effective changes.
- PECI sends payroll data to and receive payroll data from a third-party payroll vendor.
- PECI can scan up-to additional 2 pay periods of all kinds of worker changes,
- PECI connectors give more effective detailed data.
- PECI connector gives ability to scan for all effective changes even in future pay periods.
- Allows to add field overrides for most of the relevant sections that e.g. allows us to handle additional fields for multiple positions correctly.
- In PECI, Full Extract is indicated using a launch parameter.
- We can Reduce troubleshooting time by viewing payroll errors at the worker level.
- PECI sends hire and termination data to a third-party payroll vendor immediately upon creation.
- PECI tracks the status of the integration and identify any necessary corrective actions without leaving Workday.
Limitations
- PECI has the limitation of handling only 150,000 worker records. As this is quite a new solution PECI has some minor glitches, but still it is one of the most powerful connectors currently available in Workday.
- It can run up to 50 pay groups per one instance. If we have more than that, we can categorize the PECI by region based to keep the limit of pay groups per instance to less than 50.
- PECI does not include contingent workers in output files. If company employs contingent workers, we can use the Worker Effective Change Interface (WECI) integration to transmit contingent worker data.
- PECI requires grid. We can have grid enabled for only 1 active tenant in an environment, either implementation or implementation preview, at a time.
Types of Extract Supported
Payroll Effective Change Interface supports all effective and Incremental extracts:
- All Effective extract: All worker data changes that are effective within the pay period, regardless of entry date.
- Incremental extract: Worker data changes that are effective within the current or prior pay periods entered after the last successful integration run datetime.
Payroll Effective Change Interface Launch Parameters:
| Launch Parameter | Description and Notes |
|---|---|
| Pay Group | Specify 1 or more Pay Groups to include in the integration run. |
| Pay Period Selection Option | Specifies the pay period for the integration run. |
| Primary Run | Specifies that this integration run isn’t ad hoc. Workday updates the last successful run date to the current date after we run the integration. |
| Pay Group Members | Specifies individual workers to include or exclude in the integration run. Use this launch parameter with the Exclude Members/Only Include Members launch parameter. |
| Exclude Members/Only Include Members | Specifies if workers included in the Pay Group Members launch parameter are included or excluded from the integration run. |
| Change Detection | Specifies if the integration run includes changes entered since the last successful run or all changes in the pay period. |
| Full Snapshot | The Full Snapshot launch parameter seeds the client downstream payroll processor with all the worker information, before launching the integration for the first time. Example: Run Full Snapshot for the Dec 1-31, 2015 period to prepare for processing Jan 1-31, 2016 payroll. For the processed Pay Group, Full Snapshot sends: All active employees in the Pay Group as of effective date Dec 31, 2015, and entry time of the integration run. All terminated employees that were part of the Pay Group at the time of termination. Information for all active and terminated workers effective as of Dec 31, 2015, and as of the entry moment of the integration run. Change detection capabilities aren’t provided for Full Snapshot, so disable the Transaction Log or the output file will be empty. |
| Last Successful Run Date | Displays the date and time of the last successful run date. Editable. |
| Merging Pay Groups | Specify all the Pay Groups that we want to merge with the Pay Group from the parent integration run. |
| Merging Past Events | Specify the integration events that we want to merge with the parent integration event. |
| Update Worker Last Successful Run Date | If selected, updates the last successful run date for each worker to the start date and time of the integration run. |
| Effective Stack Sync Run | Disables the Transaction Log service configured for this integration. The integration runs in full Effective Stack mode for the entire employee population. |
| Override As of Entry Date Time | Specifies how far back Workday searches for transactions by entry date. |
Use Cases: We can use PECI when
- Payroll vendor requires full-stack integration.
- Customer has moved to Workday from a legacy third-party ERP that used a full-stack integration model.
- There are up to 150,000 workers per pay group.
- There is a need to refresh internal data warehouses with Workday data several times per day.