HR-XML 3.0 Standards, 2009 September 23.
Menu: [ Home | Guidelines | BODs | Nouns | Global elements | WSDL | Packages | Code Lists | Master Index ]
Trace back: » ch36s03 | ch37 | ch37s03 | ch38s03 | ch39 »
Table of Contents
This document describes approaches to using HR-XML's TimeCard noun. HR-XML's TimeCard allows the capture of time-worked data as well as information about associated expenses and allowances.
The architecture and data model of the TimeCard within the HR-XML 3.0 library has changed significantly compared to the prior 2.* versions. However, the 3.0 version of the TimeCard, is intended to support the same scenarios supported by prior versions of the HR-XML Library.
Within the context of time-card support, an important difference between the 3.0 version of the HR-XML library prior versions is that the "TimeCardConfiguration" schema has been deprecated and is no longer included. The TimeCardConfiguration schema was intended as a means to pre-provision and maintain time and attendance systems with data about the population of employees whose time and expense submissions were to be managed. TimeCardConfiguration also supported provisioning time and attendance systems with identifiers relevant to proper allocation of time and expenses to accounts, cost centers, etc.
Within the time card the most significant changes have occurred in the TimeInterval and TimeEvent containers. Both containers have been modified to make them more comparable to the Rates container that is available in the StaffingAssignment and StaffingResource. This makes it possible to reuse information without difficult transformations. The major changes are:
- Addition of Submitter container
- Addition of Approver container
- Possibility to specify expenses within a TimeInterval/TimeEvent
- Possibility to specify customer classes
Note
It is recommended that implementers use HR-XML's IndicativeData or HRMasterData nouns to provision time and attendance systems with information about individuals who will be reporting time and expenses. Provisioning a time and attendance system with the proper set of accounting IDs and classification codes is something that can be accomplished using the "oa:Fields" noun within the Open Applications Integration Specification (OAGIS). For example, the oa:SyncFields BOD combining the sync verb with the oa:Fields noun could provide a means to synchronize account IDs and code values among systems.
Many jurisdictions have protective wage-hour laws that address topics such as record keeping, compensable hours, meal allowances, and the like. Likewise, there may be jurisdiction-specific tax rules regarding the reporting and substantiation of expenses and allowances. The Time Card specification is sufficiently flexible to be used within many jurisdictions, but does not contemplate nor enforce the legal requirements of specific jurisdictions. Please consult competent legal counsel on the wage-hour and tax laws applicable within your jurisdiction to learn how they may impact time and expense reporting and record keeping.