Indicative Data

Recommendation, 2007 April 15

Document Editor:

Kim Bartkus, HR-XML Consortium

Schema Editors:

Buddy Kresge, BenefitsXML

Paul Kiel, HR-XML Consortium

Contributors:

Joanne Fritz, ADP

Buddy Kresge, BenefitsXML

Vamsee Srikakolapu, CitiStreet

Chris Clark, Fidelity

Toby Shaw, Hewitt

Kim Bartkus, HR-XML Consortium

Chuck Allen, HR-XML Consortium

Paul Kiel, HR-XML Consortium

Lon Pilot, Lon Pilot, LLC

Bill Kerr, Oracle

Jean Handel Baily, SAP

 

Copyright © 2007 HR-XML Consortium, Inc.

Abstract

This document describes the specification for XML indicative data exchange between Business Process Outsourcers (e.g., TBOs, HROs, TPAs, etc.), their clients and other vendors.

 

Table of Contents

1     Overview.. 4

1.1      Objective. 4

1.1.1        Domain Issues. 4

1.1.2        Business Reasons. 4

1.2      Scope. 5

1.2.1        Major Components. 5

1.2.2        Items within the Design Scope. 5

1.2.3        Items outside the Design Scope. 5

2     Supported Business Processes. 6

2.1      Trading Partner Roles. 6

2.2      Client Setup. 6

2.2.1        Summary. 6

2.2.2        Use Case Scenarios. 7

2.2.3        Diagrams. 7

2.3      Employee Indicative Data Maintenance. 8

2.3.1        Summary. 8

2.3.2        Use Case Scenarios. 8

2.3.3        Diagrams. 9

3     Schema Design. 10

3.1      Indicative Batch. 10

3.1.1        Schema Diagram.. 10

3.1.2        Schema Elements/Attribute Details. 10

3.2      Indicative Data. 12

3.2.1        Schema Diagram.. 12

3.2.2        Schema Elements/Attribute Details. 12

3.3      Person Info. 15

3.3.1        Schema Diagram.. 15

3.3.2        Schema Elements/Attribute Details. 16

3.4      Employee Info. 19

3.4.1        Schema Diagram.. 19

3.4.2        Schema Elements/Attribute Details. 20

3.5      Employment Info. 23

3.5.1        Schema Diagram.. 23

3.5.2        Schema Elements/Attribute Details. 23

3.6      Job Position Info. 27

3.6.1        Schema Diagram.. 27

3.6.2        Schema Elements/Attribute Details. 28

3.7      Organization Info. 31

3.7.1        Schema Diagram.. 31

3.7.2        Schema Elements/Attribute Details. 31

3.8      Remuneration Info. 34

3.8.1        Schema Diagram.. 34

3.8.2        Schema Elements/Attribute Details. 34

3.9      Affiliation Info. 38

3.9.1        Schema Diagram.. 38

3.9.2        Schema Elements/Attribute Details. 38

3.10    Indicative Reusable Types. 39

3.10.1      Schema Elements/Attribute Details. 39

4     Implementation Considerations. 40

4.1      Introduction. 40

4.2      Data Privacy. 41

4.3      Information Not Known by Source System.. 41

4.3.1        Required Data. 41

4.3.2        Optional Data. 41

4.4      Effective Dating. 41

4.5      Elements Prepended with “Is”. 42

4.6      Job History. 42

4.7      Job and Position. 42

4.8      Leave of Absence. 42

4.9      Organization. 43

4.10    PayCycleFrequency and payRateFrequency. 43

4.11    UserArea Extension Element 44

4.12    IndicativeBatch.xsd vs. IndicativeData.xsd. 44

4.13    Use (not abuse) of the EmployeeGroup element 44

4.14    Use of TransactionType and changeType. 45

4.14.1      TransactionType. 45

4.14.2      changeType. 45

5     Appendix A – Open Issues. 46

6     Appendix B - Document Version History. 46

7     Appendix C – Related Documents. 46

8     Appendix D - HR Administrator Task Processing Scenarios. 47

 

1         Overview

The project will deliver several schemas to support the exchange of "indicative data." The phrase indicative data is used to describe basic employee census data (sourced from payroll or HRIS systems) that is supplied by an employer to a third-party administrator or business process outsourcer (BPO). The data transfers could be batch transfers for the purpose of initially populating the system of an outsourcing company or service providers or the transfers could be a single, real-time maintenance or corrective changes.

A comprehensive HR-XML standard for HR data is required. Creating or modifying defined HR-XML standards would simplify data exchange between companies engaged in HR related activities.  A single industry standard would revolutionize HR/benefits outsourcing administration and spur pre-programmed HR-XML by software companies.  These HR-XML standards could be defined for the conversion and maintenance of employee data as well as data error reporting. 

1.1        Objective

The objectives of this project are to provide HR-XML standards to:

·         Simplify data exchange for converting and updating participant data.

·         Encourage ERP and other software companies to pre-program additional functionality using HR-XML standards.

·         Enable real-time maintenance transactions between employer and outsourcing service providers and/or between difference outsourcing service providers.

·         Make routine data exchanges easier to setup and maintain between and among employers and payroll, benefits, consulting, actuarial, and other service providers.

1.1.1          Domain Issues

·         Current HR-XML standards lack data necessary for exchange of indicative data

·         Multiple proprietary formats exist for employee data exchange

1.1.2          Business Reasons

Adopting new HR-XML standards for indicative data exchange would:

·         Reduce the costs for all companies involved in exchanging employee data

·         Accelerate receipt of benefits and information by employees

·