Staffing Organization

Recommendation, 2006 Feb 28

Editors:

Kim Bartkus, HR-XML Consortium

Kathi Dolan, Manpower

Gail Bubsey, Kelly Services

Tara Ryan, Adecco

Barbara Johnson, Adecco

Contributors:

Bruno Alcotte (Manpower), Ian Anson (Vedior), Rémy Bailly (Randstad), Kim Bartkus (HR-XML Consortium), Yves Berdah (VidiorBis), PJ Brunyks (Randstadt), Gail Bubsey (Kelly Services ), Georges Chaboud (Adia), Kathi Dolan (Manpower), Serguei Dounaevetski (Manpower), Anne-Cécile Fénech (Adecco), Barbara Johnson (Adecco), Paul Kiel (HR-XML Consortium), Ronald Kruegel (Adecco), Magali Munoz (Manpower), Nicolas Poujols (Kelly Services), Tara Ryan (Adecco), Don Simonson (Robert Half International), Jean-Philippe Umber (Adecco), Morgan Vernoux (Adecco)

©2006 HR-XML. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher.

Abstract

The HR-XML SIDES Workgroup has produced 7 major schemas and several reusable modules to allow for transmission of Staffing Industry information between trading partners. This document describes the Staffing Organization schema, its expected usage, and the business processes meant to be supported.

Status of this Document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Table of Contents

1 Overview.. 3

1.1 Objective. 3

1.2 Scope. 3

1.2.1 Major Components. 3

1.2.2 Items within Scope. 4

1.2.3 Items Outside of Scope. 4

2 Business Process. 4

3 Schema Design. 5

3.1 Staffing Organization. 5

3.1.1 Schema Diagram.. 5

3.1.2 Data Dictionary. 5

3.2 Payment Info. 7

3.2.1 Schema Diagram.. 7

3.2.2 Data Dictionary. 7

3.3 Reference Id Info. 10

3.3.1 Schema Diagram.. 10

3.3.2 Data Dictionary. 11

4 Implementation Considerations. 12

4.1 Data Privacy. 12

4.2 Bank Account Information. 12

4.3 Associating Information to an Organization. 12

4.3.1 Reference Info. 13

4.3.2 Payment Info. 13

5 Appendix A - Document Version History. 15

6 Appendix B – Related Documents. 15

7 Appendix C - Reference Example. 16

1 Overview

A detailed analysis of the Sides 1.0 modules and Cross Process Objects was conducted by a coalition of Staffing Companies in France. The purpose of the analysis was to take a regional implementation perspective and to evaluate how closely the global specifications met localized requirements. Module by module feedback was documented and requests for additions or cardinality changes were structured based on the need for backward compatibility.

These feedback documents were sent to the global Sides development team for evaluation of the applicability of the requested changes. If a requested change could be used in more than one country, then it was considered to be eligible for the global specification. It was found that at least 90% of what was requested by the French team was indeed, more widely applicable and so formed the basis of this Sides 1.1 release. The elements and/or attributes that were only applicable in France, will be documented locally and handled through HR-XML’s localization architecture.

1.1 Objective

Within the framework of SIDES, the StaffingCustomer and StaffingSupplier modules have now been replaced by a new structure called StaffingOrganization. StaffingCustomer and StaffingSupplier will be included in the release for backwards compatibility, but have been deprecated for any new development. The Staffing Organization schema, like its predecessors is used to describe the staffing supplier (company), staffing customer, or intermediary organization.

StaffingOrganization is not required to implement the core processes enabled by SIDES. However, this schema may be useful to trading partners in setting up front or back office systems or otherwise in setting up trading partner arrangements, order routing or distribution transactions.

Also, initial implementations have revealed a desire to enable some levels of electronic payment functionality. This specification will provide improved global use of the standard, and better integration points with back office systems.

1.2 Scope

1.2.1 Major Components

New schema to replace StaffingCustomer and StaffingSupplier, consisting of:

· StaffingOrganizationType with extensible enumerations of Customer, Supplier and Intermediary. This would be the primary way to distinguish the nature of the organization being sent

· A new global type called “StaffingReferenceIdInfo” that contains the full complement of SIDES related ids. It is necessary to create a new structure at the global level, to avoid conflicts with the variety of local “ReferenceInformation” elements used throughout SIDES. They will still all be EntityIdType, so ids that were established in a 1.0 environment can still be referenced.

· An include of the CPO Organization schema, which includes Worksite and WorksiteEnvironment

· PaymentInfo which is a new module based on requirements to include an organization’s banking and financial detail (depending on the business process).

1.2.2 Items within Scope

· Ability to capture detailed hierarchical and organizational structure and contact information about a staffing supplier, customer or intermediary, primarily for the purpose of setup, qualification and reporting among trading partners.

· BankAccountInfo was specifically designed for the French market. However, it could be designed for other markets in a future version.

1.2.3 Items Outside of Scope

· Capturing details about contractual terms and conditions between a staffing supplier and another staffing supplier, staffing customer or intermediary.

· Capturing customer-specific workflow data (approval, authorization structure, etc.)

· Capturing details about contractual terms and conditions between a staffing customer and staffing supplier or intermediary.

2 Business Process

The following scenarios show some of the ways that the StaffingOrganization schema may be used:

· A staffing supplier may send the XML document to one or more of its own branches or subsidiaries to facilitate efficient and consistent setup in their front or back office system.

· A staffing supplier may send the XML document to an intermediary or job board to facilitate initial setup as a new trading partner.

· A staffing supplier may send the XML document to an intermediary, staffing customer or other staffing supplier to streamline the distribution of orders in need of filling.

· An intermediary may use the data from the StaffingSupplier schema to identify whom payment should be remitted to.

· A staffing supplier sends the document to one or more of its own branches or subsidiaries to facilitate efficient and consistent setup in their front or back office system.

· A staffing customer sends the document to a staffing supplier or intermediary to facilitate the quote or credit approval process.

· A staffing customer sends the document to a staffing manager (job advertising entity) as a part of a job posting document.

3 Schema Design

3.1 Staffing Organization

3.1.1 Schema Diagram

3.1.2 Data Dictionary

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [StaffingOrganizationType]	typeOfOrganization - TypeOfOrganization - required xml:lang - - Organization - OrganizationType - S (1/) PaymentInfo - PaymentInfoType - S (0/) ReferenceIdInfo - StaffingReferenceIdType - S (0/*) UserArea - [see include/import] - S (0/1)	Globally scoped data type.
/ [StaffingOrganizationType] / typeOfOrganization	- TypeOfOrganization -	Specifies the role or context of the organization in the transaction. [Example(s): Customer, supplier, intermediary, administrator ]
/ [StaffingOrganizationType]/ Organization	- OrganizationType - S (1/*)	Contains information about the organization.
/ [StaffingOrganizationType]/ PaymentInfo	- PaymentInfoType - S (0/*)	A collection of information about the financial entities and accounts necessary to enable the electronic payment of one or more invoices.
/ [StaffingOrganizationType]/ ReferenceIdInfo	- StaffingReferenceIdType - S (0/*)	[Definition In Review: A group of identifiers used to reference specific HR-XML documents that relate to the transaction. ] [BusinessRule(s): Allows correct processing of group or batch transactions, and/or allows edit records to be generated without resending unchanged data. ] [Example(s): You can send an assignment document with a contract date change and reference (for example) the Order, Position and Human Resource documents without including them in the transaction payload. ]
/ [StaffingOrganizationTypes]	xsd:restriction base: xsd:string [Enumerations]: Customer, Supplier, Intermediary	Globally scoped data type. See element or attribute declaration for definition.
/ [TypeOfOrganization]	- [Union]: StaffingOrganizationTypes, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.

3.2 Payment Info

3.2.1 Schema Diagram

3.2.2 Data Dictionary

/ [PaymentInfoType]	OrganizationId - EntityIdType - S (0/1) OrganizationalUnitId - EntityIdType - S (0/1) VATRate - xsd:decimal - S (0/1) PaymentCondition - [complexType] - S (0/1) BankAccountInfo - BankAccountInfoType - S (0/1) Capital - xsd:decimal - S (0/1) FinancialGuarantee - xsd:string - S (0/1) CollectiveAgreement - xsd:string - S (0/1) UserArea - [see include/import] - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [PaymentInfoType]/ OrganizationId	- EntityIdType - S (0/1)	Unique identifier for the organization. It may be an internal identifier assigned by the sender.
/ [PaymentInfoType]/ OrganizationalUnitId	- EntityIdType - S (0/1)	Unique identifier for the organizational unit. This may be an internal identifier assigned by the sender.
/ [PaymentInfoType]/ VATRate	- xsd:decimal - S (0/1)	Value Added Tax rate. Standard tax rate applicable to most consumer goods in many Western European counties. [BusinessRule(s): SIDES: Rate varies by country and type of product, service or commodity. ]
/ [PaymentInfoType]/ PaymentCondition	Structured - [complexType] - S (0/1) Description - xsd:string - S (0/1)	Contains information about the terms expected for payment of a related outstanding debt.
/ [PaymentInfoType]/ PaymentCondition/ Structured	PaymentMode - xsd:string - S (1/1) PaymentTimeAllowed - xsd:decimal - S (1/1) PaymentEvent - xsd:string - S (1/1) PaymentDay - xsd:decimal - S (1/1)	Contains specific detail about payment terms.
/ [PaymentInfoType]/ PaymentCondition/ Structured/ PaymentMode	- xsd:string - S (1/1)	Specifies the method of payment. [Example(s): Cheque, Bank Draft, Credit Card ]
/ [PaymentInfoType]/ PaymentCondition/ Structured/ PaymentTimeAllowed	- xsd:decimal - S (1/1)	Specifies the amount of time allowed, generally from the invoice date, for the payment to be received before being considered late. [Example(s): 30 = 30 days net; 0 = payment due on receipt ]
/ [PaymentInfoType]/ PaymentCondition/ Structured/ PaymentEvent	- xsd:string - S (1/1)	Identifies the particular time or calendar event to which the payment is associated. [Example(s): on receipt, end of month ]
/ [PaymentInfoType]/ PaymentCondition/ Structured/ PaymentDay	- xsd:decimal - S (1/1)	Indicates the specific day that the payment is due. [BusinessRule(s): Payments received after this day may be considered late. ] [Example(s): Due the '15'th of the month. ]
/ [PaymentInfoType]/ PaymentCondition/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element. [Example(s): Description defining an Organization's mission or purpose. Description of stock plan. Description of payment terms and conditions. ]
/ [PaymentInfoType]/ BankAccountInfo	- BankAccountInfoType - S (0/1)	Contains information about the bank account of the person or organization being referenced in the transaction.
/ [PaymentInfoType]/ Capital	xsd:extension base: xsd:decimal currencyCode - CurrencyCodeType -	Money available for the start of the business endeavor.
/ [PaymentInfoType]/ Capital/ currencyCode	- CurrencyCodeType -	A three-letter code identifying the currency of a monetary amount. [BusinessRule(s): Currency is represented in accordance with ISO 4217. This may be at an individual or group level. ]
/ [PaymentInfoType]/ FinancialGuarantee	Name - xsd:string - S (0/1) Amount - xsd:string - S (0/1)	Contains information about the insurer and the amount through which an organization has an insurance. [BusinessRule(s): The insurance company would pay the workers if the organization is unable to, i.e. bankruptcy. This must be printed on an official document, such as a contract. ]
/ [PaymentInfoType]/ FinancialGuarantee/ Name	- xsd:string - S (0/1)	A descriptive identifier within the given context. [BusinessRule(s): If referencing a person, use person name. ] [Example(s): name of shift, name of stock plan, name of competency ]
/ [PaymentInfoType]/ FinancialGuarantee/ Amount	xsd:extension base: xsd:string currencyCode - CurrencyCodeType -	The monetary value of the associated item. [2] Information required to determine the amount of the deduction or benefit. [Synonym(s): AmountCalculateInfo ] [Example(s): Bill rate, invoice item, compensation, allowance. ]
/ [PaymentInfoType]/ FinancialGuarantee/ Amount/ currencyCode	- CurrencyCodeType -	A three-letter code identifying the currency of a monetary amount. [BusinessRule(s): Currency is represented in accordance with ISO 4217. This may be at an individual or group level. ]
/ [PaymentInfoType]/ CollectiveAgreement	- xsd:string - S (0/1)	A formal agreement between the employers’ organization and employees within that organization.

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [BankAccountInfoType]	xsd:extension base: FRBankAccountInfoType	Globally scoped data type. See element or attribute declaration for definition.
/ [FRBankAccountInfoType]	BankInfoByJurisdiction - [complexType] - S (0/*) BankAccountForeign - xsd:string - S (0/1)	This metadata was designed as a standard extension based on the French jurisdiction.
/ [FRBankAccountInfoType]/ BankInfoByJurisdiction	bankJurisdiction - xsd:string - required BankCode - xsd:string - S (1/1) BankWindow - xsd:string - S (1/1) BankAccountNumber - xsd:string - S (1/1) BankAccountKey - xsd:string - S (1/1)	Contains identifying information about a particular bank account associated with a particular branch, governed by the laws for a particular regulatory area (jurisdiction).
/ [FRBankAccountInfoType]/ BankInfoByJurisdiction/ bankJurisdiction	- xsd:string -	Indicates the jurisdiction that governs the regulatory requirements of a particular bank account. [BusinessRule(s): Generally identified on an account statement. If not otherwise specified, the bank's jurisdiction is the jurisdiction in which the chief executive office of the bank is located. ]
/ [FRBankAccountInfoType]/ BankInfoByJurisdiction/ BankCode	- xsd:string - S (1/1)	A unique identifier for the specific financial institution that is considered to be primary in relation to a particular account.
/ [FRBankAccountInfoType]/ BankInfoByJurisdiction/ BankWindow	- xsd:string - S (1/1)	A unique identifier for a particular teller or counter (referred to as window) in conjunction with a particular bank branch location. [BusinessRule(s): Used in the context of a Bank Transfer ]
/ [FRBankAccountInfoType]/ BankInfoByJurisdiction/ BankAccountNumber	- xsd:string - S (1/1)	Indicates the number of a bank account.
/ [FRBankAccountInfoType]/ BankInfoByJurisdiction/ BankAccountKey	- xsd:string - S (1/1)	A collection of the separate parts of a bank number. This control key is also referred to as an RIB (Repository in a Box) key.
/ [FRBankAccountInfoType]/ BankAccountForeign	- xsd:string - S (0/1)	Used to reference bank account information for a bank that resides outside of local jurisdiction in the context of the transaction. Also referred to as IBAN (International Bank Account Number).

3.3 Reference Id Info

3.3.1 Schema Diagram

3.3.2 Data Dictionary

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [StaffingReferenceIdType]	StaffingCustomerId - EntityIdType - S (0/) StaffingCustomerOrgUnitId - EntityIdType - S (0/) StaffingSupplierId - EntityIdType - S (0/) StaffingSupplierOrgUnitId - EntityIdType - S (0/) OrderId - EntityIdType - S (0/) HumanResourceId - EntityIdType - S (0/) IntermediaryId - EntityIdType - S (0/) PositionId - EntityIdType - S (0/) BillToEntityId - EntityIdType - S (0/) AssignmentId - EntityIdType - S (0/) TimeCardId - EntityIdType - S (0/) InvoiceId - EntityIdType - S (0/) UserArea - [see include/import] - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [StaffingReferenceIdType]/ StaffingCustomerId	- EntityIdType - S (0/*)	Unique id used to identify the staffing customer.
/ [StaffingReferenceIdType]/ StaffingCustomerOrgUnitId	- EntityIdType - S (0/*)	Unique id used to identify a particular organizational unit of the staffing customer.
/ [StaffingReferenceIdType]/ StaffingSupplierId	- EntityIdType - S (0/*)	Unique id used to identify the staffing supplier.
/ [StaffingReferenceIdType]/ StaffingSupplierOrgUnitId	- EntityIdType - S (0/*)	Unique id used to identify a particular organizational unit of the staffing supplier.
/ [StaffingReferenceIdType]/ OrderId	- EntityIdType - S (0/*)	Unique identifier for a staffing order.
/ [StaffingReferenceIdType]/ HumanResourceId	- EntityIdType - S (0/*)	Reference to a specific HumanResource.
/ [StaffingReferenceIdType]/ IntermediaryId	- EntityIdType - S (0/*)	Unique identifier for a Vendor Management System or 3rd party responsible for staffing management
/ [StaffingReferenceIdType]/ PositionId	- EntityIdType - S (0/*)	Reference to a uniquely identifiable position.
/ [StaffingReferenceIdType]/ BillToEntityId	- EntityIdType - S (0/*)	Unique id used to identify the billing information.
/ [StaffingReferenceIdType]/ AssignmentId	- EntityIdType - S (0/*)	Identifier of the assignment eventually agreed to by the trading partners. [BusinessRule(s): Post assignment revisions via a Human Resource Document ]
/ [StaffingReferenceIdType]/ TimeCardId	- EntityIdType - S (0/*)	Unique id used to identify the time card.
/ [StaffingReferenceIdType]/ InvoiceId	- EntityIdType - S (0/*)	Unique id used to identify the Invoice.

4 Implementation Considerations

4.1 Data Privacy

Human resources data, by its very nature, is personal data. The laws of many jurisdictions as well as codes of fair information practice require organizations to handle personal data in a way that protects individuals from loss of privacy.

The data exchange specifications developed by the HR-XML Consortium are designed to be useful across many jurisdictions and within a variety of business contexts. It is not feasible for the HR-XML Consortium to develop specific privacy guidance for every jurisdiction or business context in which the Consortium's specifications might be implemented. When implementing data exchanges using the HR-XML Consortium's data definitions (or, for that matter, using any other type of data exchange mechanism), organizations are advised to examine the privacy protections that may be required under applicable law and codes of fair information practice.

For information on protecting personal data, general references include: European Union Data Protection Directive (95/46/EC); the Association Computing Machinery Code of Ethics (1992); Canadian Standards Association Model Code for the Protection of Personal Information (1995 – PIPEDA); and U.S.-EU Safe Harbor Principles and FAQs (2000).

4.2 Bank Account Information

In many countries, financial institutions use groupings of numbers to indicate particular branches and account numbers. Different countries use different quantities of groupings, but most range between 2-5 groups of identification/routing numbers. In every day use, terms like BankWindow and BankAccountKey as stand alone fields are not well known. It is more likely that each country would think in terms of Bank Account Number Group 1, Group 2, Group 3, etc.

Examples of this "by country" variance include:

Group One (in France: Bank Code, in the US: Bank routing number), Group Two: (In France the branch number (BankWindow), in the US a personal account number, etc. In a future version, these terms will likely be genericized more, but they can still be used flexibly in the interim, or you can elect not to use the BankAccountInfo module and build to suit in the UserArea.

BankAccountInfo and its children are localized for the French market. This metadata was designed as a standard extension based on the French jurisdiction.

4.3 Associating Information to an Organization

When transmitting staffing organization information, multiple organizations may be exchanged within one instance as long as they are of the same organization type (supplier, customer, intermediary, etc). Since multiple payment information and reference information is also allowed in a single instance, the following recommendations are made to associate the payment and reference information with the correct organization or organizational unit.

4.3.1 Reference Info

The following example illustrates how to associate a reference identifier to a specific organization. The example includes two supplier organizations, Merry Staffing and Perfect People. The first reference Id connects an assignment to Merry Staffing. The second reference id ties a timecard to Perfect People.

<OrganizationName>Merry Staffing</OrganizationName>

</OrganizationId>

</Organization>

<OrganizationName>Perfect People</OrganizationName>

</OrganizationId>

</Organization>

</StaffingSupplierId>

</AssignmentId>

</ReferenceIdInfo>

</StaffingSupplierId>

</TimeCardId>

</ReferenceIdInfo>

</StaffingOrganization>

4.3.2 Payment Info

The following example illustrates how to associate payment information to a specific organization and an organizational unit. The example includes one customer organization (Polycorp Distributor) and its business unit (Macco Warehouse). Polycorp Distributor pays by bank draft due on receipt of invoice. Macco Warehouse’s payment method is by credit card due on the 30^th of each month.

<OrganizationName>Polycorp Distributor</OrganizationName>

</OrganizationId>

<OrganizationalUnitName>Macco Warehouse</OrganizationalUnitName>

</OrganizationalUnitId>

</OrganizationalUnit>

</Organization>

</OrganizationId>

<PaymentMode>Bank Draft</PaymentMode>

<PaymentEvent>on receipt</PaymentEvent>

</Structured>

</PaymentCondition>

</BankInfoByJurisdiction>

</BankAccountInfo>

</PaymentInfo>

</OrganizationId>

<PaymentMode>Credit Card</PaymentMode>

<PaymentEvent>end of month</PaymentEvent>

</Structured>

</PaymentCondition>

</BankInfoByJurisdiction>

</BankAccountInfo>

</PaymentInfo>

</StaffingOrganization>

5 Appendix A - Document Version History

Date	Description
2004-03-01	Initial Draft
2004-03-29	Updated definitions
2004-05-13	Added implementation guideline (banking).
2004-05-27	Updated example
2003-06-15	Changed bankaccountinfo to be localized. This didn’t affect the instance. Moved payment info to be a peer of organization and added org ids. Changed referenceidinfo to multiple occurrence. These modifications allow the payment info and reference id’s to be associated with a particular organization.
2003-06-16	Updated section 4.3 examples. Clarified use of localized BankAccountInfo.
2004-Aug-02	Approved by membership.
2006-Feb-28	Approved by Consortium

6 Appendix B – Related Documents

Reference	Link
SIDES schemas	http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Assignment.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/ContactInfo.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/CustomerReportingRequirements.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/HumanResource.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Rates.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/ResourceScreening.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingAction.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingContactType.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingOrder.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingOrganization.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingPosition.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingShift.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingWorkSite.xsd http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/TimeCardAdditionalData.xsd
SIDES Documentation	http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/SIDES.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Assignment.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/HumanResource.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingAction.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingOrder.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingOrganization.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/SIDESReusableModules.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingInvoice.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/StaffingWorkSite.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/ExtendedTimeCard.html
OAGIS Invoice and instance	http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Invoice.xsd (a stand alone version - see http://www.openapplications.org/ for the original) http://ns.hr-xml.org/2_4/HR-XML-2_4/SIDES/Invoice.xml
User Area	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/HRXMLExtension.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/UserArea.xsd
PersonName	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PersonName.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PersonName.xsd
PostalAddress	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PostalAddress.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PostalAddress.xsd
ContactMethod	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/ContactMethod.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/ContactMethod.xsd
PositionHeader	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/JobAndPositionHeader.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/PositionHeader.xsd
DateTimeDataTypes	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/DateTimeDataTypes.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/DateTimeDataTypes.xsd
Resume	http://ns.hr-xml.org/2_4/HR-XML-2_4/SEP/Resume.html http://ns.hr-xml.org/2_4/HR-XML-2_4/SEP/Resume.xsd
Competencies	http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/Competencies.html http://ns.hr-xml.org/2_4/HR-XML-2_4/CPO/Competencies.xsd
TimeCard	http://ns.hr-xml.org/2_4/HR-XML-2_4/TimeCard/TimeCard.html http://ns.hr-xml.org/2_4/HR-XML-2_4/TimeCard/TimeCard.xsd

7 Appendix C - Reference Example

<OrganizationName>Joe Ricci Restaurant</OrganizationName>

</OrganizationId>

<TaxId>

</TaxId>

<InternetDomainName primaryIndicator="true">pizzacorp.com</InternetDomainName>

<InternetDomainName primaryIndicator="false">joespizza.com</InternetDomainName>

<DoingBusinessAs>Joe's Pizza</DoingBusinessAs>

<LegalClassification countryCode="US" ownership="Public">Franchise</LegalClassification>

<Description>Joe's Pizza was formerly known as Joe Ricci Restaurant until it was sold to Pizza Corp in 1992.</Description>

<FormattedName>Joe Ricci</FormattedName>

</ContactName>

</ContactInfo>

<OrganizationName>Pizza Corp.</OrganizationName>

<TaxId>

</TaxId>

<InternetDomainName primaryIndicator="true">pizzacorp.com</InternetDomainName>

<LegalClassification countryCode="US" ownership="Public">Corporation</LegalClassification>

<Description>Pizza Corp. was founded in 1978 and operates 63 franchises.</Description>

<FormattedName>Susan Marriott</FormattedName>

</ContactName>

</ContactInfo>

</RelatedOrganization>

<OrganizationalUnitName>Chicago</OrganizationalUnitName>

<Description>Sales and inventory of the north and south divisions may be combined in some cases. </Description>

</OrganizationalUnit>

<OrganizationalUnitName>Wait Staff</OrganizationalUnitName>

<Description>Wait staff for Joe's Pizza</Description>

<WorkSiteName>Restaurant</WorkSiteName>

<ParkingInstructions>Park behind restaurant.</ParkingInstructions>

<EnvironmentName>Dining Area</EnvironmentName>

<DressCode suppliedByOrganization="true">x:Apron</DressCode>

<DressCode suppliedByOrganization="false">x:Long Hair Pulled Back</DressCode>

</Considerations>

</WorkSiteEnvironment>

</WorkSite>

<FormattedName>Mary Smith</FormattedName>

</PersonName>

<RoleName>Evening Shift Supervisor</RoleName>

</PersonRole>

</PersonMember>

</OrganizationalUnit>

</Organization>

</OrganizationId>

<PaymentMode>Credit Card</PaymentMode>

<PaymentEvent>end of month</PaymentEvent>

</Structured>

</PaymentCondition>

</BankInfoByJurisdiction>

</BankAccountInfo>

</FinancialGuarantee>

<CollectiveAgreement>national</CollectiveAgreement>

</PaymentInfo>

</StaffingCustomerId>

</StaffingCustomerOrgUnitId>

</StaffingSupplierId>

</ReferenceIdInfo>

</StaffingOrganization>