DEPLOYMENT GUIDE

WORKDAY CLOUD CONNECT FOR PAPAYA GLOBAL

1
© Copyright 2022 PAPAYA GLOBAL, Inc. ALL RIGHTS RESERVED. PAPAYA GLOBAL
Proprietary and Confidential. These materials may not be reproduced in any format without the
express written permission of PAPAYA GLOBAL, Inc. This document must be always kept strictly
confidential. It must not be disclosed to any person without the prior written consent of
PAPAYA GLOBAL, Inc.
PAPAYA GLOBAL, Inc. provides this publication "as is" without warranty of any kind, either
express or implied, including, but not limited to, the implied warranties of merchantability or
fitness for a particular purpose. PAPAYA GLOBAL, Inc. is not responsible for any technical
inaccuracies or typographical errors which may be contained in this publication. Changes are
periodically made to the information herein, and such changes will be incorporated in new
editions of this publication. PAPAYA GLOBAL, Inc. may make improvements and/or changes in
the product and/or the programs described in this publication at any time without notice.
PAPAYA GLOBAL, the PAPAYA GLOBAL logo, and PAPAYA GLOBAL are trademarks of PAPAYA
GLOBAL, Inc. All other marks are the property of their respective owners.

2
Revision History

Date Version Description Author

May 23 2022 1.0 Initial Version Idan Hadari
Aug 10 2022 1.1 Update to new version and address Idan Hadari
comments
Dec 12 2022 2.0 5 Countries National ID’s – France, Idan Hadari
Germany, Netherlands, Singapore and
Spain

Dec 12 2022 2.0 Time Off Idan Hadari

3
TA BLE OF CONTENTS

Introduction .................................................................................................................................... 6

Glossary of Terms............................................................................................................................ 6

CER TIFIED INTEGR ATIONS ........................................................................................................ 9

Workday Setup................................................................................................................................ 9

Papaya Global Setup ..................................................................................................................... 11

Cost Centers ............................................................................................................................... 12

Departments .............................................................................................................................. 12

Earning Codes ............................................................................................................................ 13

Staffing Events / Business Processes ............................................................................................ 13

Operations ................................................................................................................................. 15

Workday Feature Adoption .......................................................................................................... 15

Integration Instances .................................................................................................................... 17

Employee Demographic Data (PECI) ......................................................................................... 17

Employee Time off Data ............................................................................................................ 18

Customizations .......................................................................................................................... 18

Employee demographic data Integration Configuration .............................................................. 18

Integration Services ................................................................................................................... 19

Field Overrides ........................................................................................................................... 19

Integration Attributes ................................................................................................................ 19

Integration Maps ....................................................................................................................... 19

Demographic Data Integration Sequence Generator................................................................ 19

Time off Data Integration Sequence Generator ........................................................................ 20

4
 File Delivery ............................................................................................................................... 20

Implementation Steps................................................................................................................... 20

Outbound integration Workday to Papaya Global .................................................................... 20

Initial Data Load ............................................................................................................................ 21

Country-Specific Requirements .................................................................................................... 22

Country Identifiers ................................................................................................................ 22

Time Off Integration...................................................................................................................... 22

Workday Configuration ............................................................................................................. 22

Point of entry validations .......................................................................................................... 24

Unsupported Functionality ........................................................................................................... 25

Papaya global Support Contacts ................................................................................................... 25

Appendix ....................................................................................................................................... 25

5
INTRODUCTION

The Global Payroll Cloud (GPC) program strongly recommends that a certified
CCTPP integration consultant is engaged to help with the deployment of your GPC
Certified integration.

The purpose of this document is to assist the Implementation Resource on how to integrate
Workday and Papaya Global using the Certified Integration solution.

The Deployment Guide provides instructions that will assist in the process of integrating data
from Workday into Papaya Global for payroll processing including detail on the configuration
and deployment of the certified integration in the Client’s tenant.

The Deployment Guides intended audience is a Workday Implementation Consultant(s).

Important note: The tenant needs to be Grid Enabled. Also, if the customer is not using a
Workday hosted tenant, please reference Appendix.
Refer to Community to confirm location of tenant. If then tenant does not reside in Ashburn,
Portland or Dublin, then the tenant is externally hosted.

GLOSSARY OF TERMS

Certified Integration An integration system configured and developed for

each country to manage the data flow between
Workday and Papaya Global. Certification is
achieved after meeting all requirements from
Workday.
Client Workday Client using the Workday eco system for
HCM capabilities and requiring payroll services
supported by Papaya Global.
Cloud Connect for Third An integration template that enables organizations
Party Payroll to connect to any number of third-party payroll
applications, including Papaya Global.

6
Data Dictionary Data mapping document containing Workday fields
mapped to Papaya Global fields required for payroll
processing. A separate mapping column will exist for
each country.
Global Payroll Cloud Global Payroll Cloud is Workday’s partner program
with third party payroll processors. Workday’s
carefully selected global payroll partners agree to
build, own and maintain certified bi-directional
integrations that minimize the effort and cost for
our customers to implement payroll in 100+
countries across the globe. Workday certifies
interoperability between Workday and the
partner’s payroll system.
GPC Certification Partner built payroll integrations must meet
Workday GPC standards related to the design,
development and documentation. Workday
oversees the testing of each integration to verify the
identified use cases generate the expected results
and the data is successfully loaded to the Payroll
Partner’s system. Validation of the payroll results
should be handled as part of the payroll
implementation between the customer and the
Global Payroll Partner.
Demographic Data Worker Personal, Position, Compensation and Leave
of Absence data.
Time off Data Worker Leaves (Quota and Accrual Based) data.
Deployment Guide Document to assist implementation consultants who
are configuring Workday to integrate with Papaya
Global.
Implementation Certified Workday implementation resource.
Consultant Normally associated with the Workday Professional
Services team or a Workday Service Partner.

7
Import External Payslips An integration that imports employee payslips from
Integration an external third-party payroll system or other
endpoint into Workday.
Integration System The object in Workday that is used to store the
configuration for an integration.
Payroll Effective Change PECI is the payroll extract created from a Workday
Interface Cloud Connect for 3rd Party Payroll Integration that
enables you to capture all Workday events with
effective dates in the sequence they occurred.
External Payroll Results The External Payroll Results format that can be read
by Workday. The EXPR integration imports Papaya
Global earning and deduction codes and values
aligned with Workday payroll result lines to be used
for reporting.
Payroll Staffing Event A payroll staffing event is one of the following: Hire,
Termination, Request for Leave, Return from Leave,
Pay Group Transfer In (PGI), Pay Group Transfer Out
(PGO), Pay Company Transfer In (PCI) and Pay
Company Transfer Out (PCO).
User Guide Document to assist Papaya Global customers who
utilize Workday for HCM to understand how the
applications integrate with Papaya Global.

8
CERTIFIED INTEGRATIONS

The certified integration(s) have/has been designed, developed, tested and documented by
Papaya Global with Workday’s guidance and oversight. The integration(s) facilitates the flow of
data required for payroll processing from Workday to Papaya Global. The customer benefits by
receiving feature rich, pre-built, pre-tested, documented, partner maintained integrations that
minimizes your effort as compared to custom integrations. Certified integrations are available
in the Workday Solutions Library to be imported into your tenant(s) by you or your chosen
Systems Integration Partner.

WORKDAY SETUP

There are many list values that need to be synchronized across the systems. Each of these data
points is included in the certified integration. The implementation team will need to ensure

9
that all list values in Workday may be mapped to a value within the payroll system and
therefore is imperative that this is a consideration at design. The client will need to ensure to
maintain the synchronization of these lists post go-live.

The following are all fields that have list values and require a mapping between WD and Papaya
Global system.

COST CENTER
▪ Papaya Global Field: Organization_Type = COST_CENTER
▪ Definition: Used to track and categorize financial costs of employees.
▪ Client or Application defined in Papaya Global: Client
▪ System of Record: Workday
FREQUENCY
▪ Field: Frequency
▪ Definition: This is the frequency in which a pay element is specified within the extract.
▪ Client or Application defined in Papaya Global: Client
▪ System of Record: Workday

GENDER
▪ Papaya Global Field: Gender
▪ Definition: Sex. Can be defined at country level.
▪ Client-defined or Static List in Papaya Global: Client
▪ System of Record: Workday

MARITAL STATUS
▪ Papaya Global Field: Marital Status
▪ Definition: The employees marital relationship
▪ Client or Application defined in Papaya Global: Client
▪ System of Record: Workday

PAY GROUP
▪ Papaya Global Field: Pay Group/Project
▪ Definition: This group will have similar pay characteristics such as frequency of pay and
pay rate type.
▪ Client or Application defined in Papaya Global: Client
▪ System of Record: Workday

PAYROLL COMPANY
▪ Papaya Global Field: Payroll Company (Type – External Payroll)
▪ Definition: This is a payroll legal tax entity within a company. There may be more than
one payroll company per country but a payroll company cannot span multiple countries.

10
 ▪ Client or Application defined in Papaya Global: Client
▪ System of Record: Workday

PERIOD SCHEDULE
▪ Papaya Global Field: Pay Cycle
▪ Definition: This is also known as a pay calendar. It dictates when the pay group begins
and ends a pay period. The pay date is also specified although not used in any logic
within PECI. The period status will need to be maintained in both systems.
▪ Client or Application defined in Papaya Global: Client
▪ System of Record: Workday

PAPAYA GLOBAL SETUP

The following section covers the list of setup data requirements on Papaya Global that needs to
be completed first on Workday before uploading any employee specific data. This also covers
how the foundation data will remain in sync between Workday and Papaya Global.

Pr e-Requisites

Workday tenants must be GRID enabled.

A PECI Integration is per country including all its Pay groups.

The Workday pay group created under one legal entity should not span across other legal
entities or Workday external payroll companies.

There must be a 1 to 1 relation between a Workday Pay Group and a Workday Payroll
Company.

There must be a 1 to 1 Payroll Name (Pay Group) match between Workday and PAPAYA
GLOBAL Platforms. Also, Workday must periodically ensure that all employees have only one
active organization assigned at a given point in time.

The Pay Group Name is reported in the summary section of the PECI as underlined in the below
screenshot. PECI Integration system is provided per country and one file for all pay groups.

11
For additional details, refer to Workday Community on Grid Enablement configuration and
merging multiple PECI files into 1 extract:

Topic Workday Community Links

Configure https://doc.workday.com/reader/wsiU0cnNjCc_k7shLNxLEA/Mye7C3fE3mAfFRSmXutJOQ
Merge
Integration
Outputs
Set up https://community.workday.com/node/85909
Grid

Cos t Centers

We currently support one cost center per each employee. We need the cost center name and
cost center code. This will be defined as part of the initial mapping between Workday and
Papaya Global platform in the initial setup for the JE file. There is no limitation on the length on
the cost center field.

Depar tments

This will be defined as part of the initial mapping between Workday and Papaya Global
platform in the initial setup. There is no limitation on the length on the department field.

12
Earning Codes

The Workday Pay Elements that belong to Compensation or Payroll Inputs required to be
mapped with associated Papaya Payroll System Pay Elements by using tasks ‘Maintain Payroll
External Earnings’ and ‘Maintain Payroll External Deductions’.

The below Earnings and Deductions are supported

• Compensation Earnings and Deductions

• Compensation One Time Payments
• Benefits Earnings and Deductions
• Payroll Input Earnings and Deductions
• Payroll Input One Time Payments
• Time Off Earnings and Deductions

Note: The Customer and Papaya Payroll teams must work together during Implementation to
define the scope of Earnings and Deductions along with respective mappings.

STAFFING EVENTS / BUSINESS PROCESSES

Papaya Global supports key Workday staffing events and business processes required for
payroll processing. The following table displays the Workday staffing events and fundamental
business processes that are supported and not supported.

The following staffing events / business processes that are supported/not supported:

Supported Not Supported

Hire Hire – Rescind

Termination Termination - Rescind

13
 Leave of Absence
Pay Company Transfer In Return from Leave

Pay Company Transfer Out

Pay Group Transfer In

Pay Group Transfer Out

Rehire

14
Operations

Records sent from Workday will include operational instructions which will be treated in Papaya
Global Platform as per below table.

Operation PAPAYA GLOBAL Platform

isAdded Add a new instance
isUpdated End Dates and adds a new instance
isDeleted Record is not processed
No operation Record is not processed (no changes)

WORKDAY FEATURE ADOPTION

The following section covers the key optional Workday Features/Sections that are supported by
Papaya Global.

Workday Features/Data Sections Papaya Global Adoption

Personal Yes

Person Communication Yes

Person Identification Yes

Related Person Yes

Related Person Communication Yes

Related Person Identification Yes

Position Yes

Compensation Yes

Compensation Plans Yes

15
Workday Features/Data Sections Papaya Global Adoption

Education No

Payment Election Yes

Contract Yes

Leave of Absence No

Benefits Earnings & Deductions Yes

Compensation Earnings & Deductions Yes

Payroll Input Earnings & Deductions Yes

Compensation One Time Payment Yes

Payroll Input One Time Payment Yes

Costing Allocation Yes

Time Off Yes

Time Tracking No

Time Tracking Corrections No

Other Functionality

Additional Period Payments No

Import External Payslips No

External Payroll Results (EXPR) No

International Assignments No

Multiple Positions No

Multi-Component Base Pay No

16
 Workday Features/Data Sections Papaya Global Adoption

Initial Data Load No

Journal Connector No

External Tax Documents No

Global Payroll Reconciliation No

Event Driven Integration No

Payroll Batch Errors No

Import External Payroll Documents No

Addresses

Papaya Global does not support the ‘Extended’ country address format only the ‘Basic’ address
format is supported.

INTEGRATION INSTANCES

Em ployee Demographic Data (PECI)

For every country, there should be at least one PECI integration instance. The integration
system configuration has been designed to include only those fields relevant for each country.
There are other configurations such as National IDs that were designed to enforce acceptable
IDs within a country. In addition, there is data such as names, addresses, and payment
elections that are truly country-specific field-wise in Workday and the fields should only be
included that are relevant to that country.

Each country integration instance can support one or more pay groups. There is typically not a
reason to have more than one primary integration instance per country.

17
Em ployee Tim e off Data

Similar to the Demographic data Integration instance, there is one called PECI Time Integration
instance. The integration system is Global across all countries.

The Time off data integration instance can support one or more pay groups. This will be
additional primary integration instance.

When Additional Primary Integration attribute enabled, a successful primary run stores
processing and additional pay periods in the Last Extract Created. Instead of Pay Period Status,
the Last Processed Period values indicate which pay periods have been started for the pay
group/integration system combination.

Refer below community pages for information:

https://community.workday.com/service-update-notes/2020-07-03-663632
https://community.workday.com/service-update-notes/2021-02-05-733266
https://doc.workday.com/reader/wsiU0cnNjCc_k7shLNxLEA/wPRUgcLcN0zKGZSf~VPSrQ

Customiz ations

These are standard configurations. Changes to mappings specific to clients will not be
implemented in the transformation and therefore, are strongly discouraged. All customizations
must be documented and presented to the DA reviewer, Papaya Global lead and customer to
understand the changes that may be required in future releases.

DEMOGRAPHIC AND TIME OFF DATA INTEGRATION CONFIGURATION

18
Integration Ser vices

The Integration Services have been pre-configured to work with Papaya Global and should not
be changed without first consulting Papaya Global.

Field Overr ides

Currently, the Integrations don’t have any field overrides.

Integration A ttributes

The integration Attributes are configured to align with the requirements for Papaya Global and
the country integration instance. They should only be modified after discussing with Papaya
Global team.

Integration Maps

The Papaya Global list values that are application specific are included in the PECI Data
Dictionary document and can be viewed within the integration system. The client specific
values will need to be obtained from the Papaya Global implementation team. The mapping
exercise for each of the fields will need to be performed by the Workday implementation team
for each client.

Dem ographic Data Integr ation Sequence Generator

The file naming convention to be set up as specified below in Workday.

WD_<System Name>_HRMD_PECI_PAPAYA_<Date Stamp><Time Stamp>_<2 char ISO

Code>_<Seq.No>.xml

• System Name: STAG (for Stage) or PROD (for Production)

• Date Stamp format: YYYYMMDD
• TimeStamp format: HHMMSS
• Seq. No: 01, 02 and so on

19
If PGP encrypted, the extension will be ended added in the end

WD_<System Name>_HRMD_PECI_PAPAYA_<Date Stamp><Time Stamp>_<2 char ISO

Code>_<Seq.No>.xml.pgp

Time off Data Integr ation Sequence Gener ator

The file naming convention to be set up as specified below in Workday.

WD_<System Name>_TIME_PECI_PAPAYA_<Date Stamp><Time Stamp>_<2 char ISO

Code>_<Seq.No>.xml

• System Name: STAG (for Stage) or PROD (for Production)

• Date Stamp format: YYYYMMDD
• TimeStamp format: HHMMSS
• Seq. No: 01, 02 and so on

If PGP encrypted, the extension will be ended added in the end

WD_<System Name>_TIME_PECI_PAPAYA_<Date Stamp><Time Stamp>_<2 char ISO

Code>_<Seq.No>.xml.pgp

File Deliver y

The PECI files exchanged between Workday and PAPAYA GLOBAL systems use the Secure File
Transfer Protocol (SFTP) and these files can be PGP-encrypted to ensure the highest quality of
security is adhered to.

During the Workday Integration Implementation, the file exchange is set up and tested.
Configuration should be done at the client tenant level.

IMPLEMENTATION STEPS

Outbound integration Workday to Papaya Global

1. Clone the Global Integration System

20
 a. Clone the Global Demographic / Time off data integrations into Country Specific
Integrations.
b. Replace the ‘GLOBAL’ with 3 char country ISO code in Integration name.
c. Disable the unwanted fields.

2. Integration System setup

a. Map external values from internal values. Papaya Global implementation team
should provide the external values for the PECI integration system maps.
Strategy on synchronization of organizations and locations should be identified.
b. Setup the file name.
c. Set up the file delivery.

3. Payroll Interface Framework Components

a. Setup external earnings and deductions codes in Workday. Papaya Global
implementation team will need to provide the earnings and deductions with
codes.
b. Setup period schedules. If possible, load at least 2 years of periods as provided
by Papaya Global.
c. Setup payroll company and pay groups as provided by Papaya Global
implementation team.
d. Setup time codes if necessary.

INITIAL DATA LOAD

The Initial Data Load is a feature that allows us to create a full file extract from Workday to be
loaded in the Papaya Global. It utilizes the PECI integration. The integration service for
transaction log needs to be disabled or else the output will be empty.

• <XML> file containing active and employees termed up to 2 years previously will be
included on the file. This is a point in time load, so the period that is selected in the
launch parameters will be what the output will be based off of.

• When running the Initial Data Load, identify pay group, pay period, and select full
snapshot. No other launch parameters are necessary.

• Refer to the following link for additional information:

https://doc.workday.com/reader/wsiU0cnNjCc_k7shLNxLEA/fXvzOgRYUgaOgXz0Uq
GggQ

21
COUNTRY-SPECIFIC REQUIREMENTS

CO UNTRY IDE NTI FIE RS

Country Identifier Name Country Identifier Code

UK National Identifier GBR-NI

France Social Security ID (INSEE) Number FRA-INSEE

Netherlands Dutch Identity Card NLD-IDK

Singapore National Identifier NRIC or FIN

Spain Alien Identification Number (NIE) ESP-NIE

TIME OFF DATA INTEGRATION

Workday classifies Absence Management as Leave of Absence (LOA) and Time off. While
Workday’s Leave of Absence functionality is supported by Demographic Integrations through
standard country connectivity under the GPC Program, the Time Off functionality is supported
by an independent integration system.

This connector supports “Time Off Entry” only i.e., PECI reports the time off data day wise as
Individual time blocks.

Workday C onfigurat ion

1. Configure Time Off components in the in client’s Workday tenant. Time off configuration
consists of:
1. Create Time Off Type - Time off code & description
2. Create Time Off - Attach Time off code, define validations and characteristics
3. Create Time Off Plan – Group similar Time offs. Define Period Schedule, Unit of
Time, Accrual rules and Eligibility.

22
 Time off Plan Time off Type Time off

Vacation VE Vacation Execs

VNE Vacation for Non-Execs

Illness IE Illness Execs

INE Illness for Non-Execs

Earned EL Earned Leave

Relationships:
• Top to bottom - The relationship between Time Off Type → Time Off → Time Off
Plan is one to one.
• Bottom to top - The relationship between Time Off Plan → Time Off → Time Off
Type is many to one.

2. Although there are various work patterns available in Workday, the PECI time off solution
supports only the following work patterns:
• All Days or
• Workdays (Non-Holidays)
Navigation: Create / Edit Time Off Plan → Calculation → Days to Include

23
3. Quotas or Time Off Balances are not supported via PECI Integration; hence their update
should be dealt with in Workday.

4. Work schedule rules, Holiday calanders and Time periods must be configured in Workday.

5. *Make it simple* To send the Time Off Earnings and Deductions to Payroll Interface
perform configuration via the task “Maintain External Payroll Earnings” for that pay group,
maintain the External Payroll Code and use the relevant absence component of Time Off.
Papaya Payroll implementation team will need to provide the earnings and deductions with
External Payroll Code.

P oint of Ent ry Validat ions

The point of entry validations must be set up in Workday with appropriate rules to allow the
users to apply only legitimate requests and thereby the data issues in Papaya Payroll® can be
prevented. The scenarios are perhaps like:
• The time off doesn’t allow ‘Partial day absences.
• The number of ‘Units’ must be ‘1’ when the unit of time is ‘Days’.
• The Time off start date should not fall on ‘Public Holiday’ or over ‘Weekend’.
• The Time off end date should not fall on ‘Public Holiday’ or over ‘Weekend’.
• The time off overlapping is not allowed.
• The Time off and Leave of Absence must not be overlapped.

24
UNSUPPORTED FUNCTIONALITY

1) Rehire – can be supported via notification to the relevant CSM and handle manually in
the platform
2) Rescinds are not supported.
3) Post Termination changes are not supported.

PAPAYA GLOBAL SUPPORT CONTACTS

Support@papayaglobal.com

APPENDIX

Externally hosted tenants do not support the use of Workday Solutions tool. Therefore, in
order to persist the integration system(s) and/or calculated fields created by the GPC partner a
manual effort is required.

25
If SI:
Steps for creating a GPC solution within a customer tenant:
1. Request Integration System, Field Attribute, Field Override and Calculated Field
documentation from partner
2. Build Integration System
3. Update Field Attributes
If necessary:
4. Create Calculated Fields (in order)
5. Create Field Overrides
6. Update Field Overrides with Values

If GPC – Steps 2-5

26