Staffing Organization

Recommendation, 2007 April 15

Editors:

Kim Bartkus, HR-XML Consortium

Contributors:

Gail Bubsey (Kelly Services ), Kim Bartkus (HR-XML Consortium), Barbara Johnson (Adecco NA), Tara Ryan (Adecco), Kazuko Sugamura (Manpower Japan), Takahiro Fujiwara (EAST Co., Ltd.), Magali Munoz (Manpower France), Bruno Alcotte (Manpower France), Rémy Bailly (Randstad), Yves Berdah (VidiorBis), Serguei Dounaevetski (Manpower France), Patrice Aranega (Adecco France)

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.

Table of Contents

1 Overview.. 2

1.1 Objective. 2

1.2 Scope. 2

1.2.1 Major Components. 2

1.2.2 Items within Scope. 3

1.2.3 Items Outside of Scope. 3

2 Business Process. 3

3 Schema Design. 4

3.1 Staffing Organization. 4

3.1.1 Schema Diagram.. 4

3.1.2 Data Dictionary. 4

3.2 Payment Info. 5

3.2.1 Schema Diagram.. 5

3.2.2 Data Dictionary. 5

3.3 BankAccountInfo. 8

3.3.1 Schema Diagram.. 8

3.3.2 Data Dictionary. 8

3.4 Reference Id Info. 10

3.4.1 Schema Diagram.. 10

3.4.2 Data Dictionary. 10

4 Implementation Considerations. 11

4.1 Data Privacy. 11

4.2 Bank Account Information. 12

4.3 Associating Information to an Organization. 12

4.3.1 Reference Info. 12

4.3.2 Payment Info. 13

5 Appendix A - Document Version History. 14

6 Appendix B – Related Documents. 14

1 Overview

Changes were made to the base SIDES specification based on feedback from the European and Japanese Chapters. If available, localized items are documented in section 4 Implementation Considerations or in individual country documentation. Refer to Appendix A - Document Version History for details.

1.1 Objective

The Staffing Organization schema 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

· 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.

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

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ StaffingOrganization	- StaffingOrganizationType - (1/1) typeOfOrganization - TypeOfOrganization - required xml:lang - - Organization - [see include/import] - S (1/) PaymentInfo - PaymentInfoType - S (0/) ReferenceIdInfo - StaffingReferenceIdType - S (0/*) UserArea - [see include/import] - S (0/1)	Contains information about the staffing customer, supplier, or intermediary.
/ [StaffingOrganizationType] / typeOfOrganization	- TypeOfOrganization -	Specifies the role or context of the organization in the transaction. [Example(s): Customer, supplier, intermediary, administrator ]
/ StaffingOrganization/ 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.
/ StaffingOrganization/ ReferenceIdInfo	- StaffingReferenceIdType - S (0/*)	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

/ StaffingOrganization/ 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.
/ StaffingOrganization/ PaymentInfo/ OrganizationId	- EntityIdType - S (0/1)	Unique identifier for the organization. It may be an internal identifier assigned by the sender.
/ StaffingOrganization/ PaymentInfo/ OrganizationalUnitId	- EntityIdType - S (0/1)	Unique identifier for the organizational unit. This may be an internal identifier assigned by the sender.
/ StaffingOrganization/ PaymentInfo/ 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. ]
/ StaffingOrganization/ PaymentInfo/ TaxEvaluation	TaxType - xsd:string - S (1/1) Description - xsd:string - S (0/1) TaxRounding - RoundingRuleType - S (0/1)	Contains information as to what taxes are being applied and how the rounding method is used in their calculation.
/ StaffingOrganization/ PaymentInfo/ TaxEvaluation/ TaxType	- xsd:string - S (1/1)	The classification or name of the tax or the taxing entity.
/ StaffingOrganization/ PaymentInfo/ TaxEvaluation/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ StaffingOrganization/ PaymentInfo/ TaxEvaluation/ TaxRounding	- RoundingRuleType - S (0/1)	Contains rounding requirements to round the tax evaluation.
/ StaffingOrganization/ PaymentInfo/ 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.
/ StaffingOrganization/ PaymentInfo/ 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 structured details about payment terms.
/ StaffingOrganization/ PaymentInfo/ PaymentCondition/ Structured/ PaymentMode	- xsd:string - S (1/1)	Specifies the method of payment. [Example(s): Cheque, Bank Draft, Credit Card ]
/ StaffingOrganization/ PaymentInfo/ 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 = pay on receipt ]
/ StaffingOrganization/ PaymentInfo/ 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 ]
/ StaffingOrganization/ PaymentInfo/ 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. ]
/ StaffingOrganization/ PaymentInfo/ PaymentCondition/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ StaffingOrganization/ PaymentInfo/ BankAccountInfo	- BankAccountInfoType - S (0/1)	Contains information about the bank account of the person or organization being referenced in the transaction.
/ StaffingOrganization/ PaymentInfo/ Capital	xsd:extension base: xsd:decimal currencyCode - CurrencyCodeType -	Money available for the start of the business endeavor.
/ StaffingOrganization/ PaymentInfo/ 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. ]
/ StaffingOrganization/ PaymentInfo/ 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. ]
/ StaffingOrganization/ PaymentInfo/ 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 ]
/ StaffingOrganization/ PaymentInfo/ FinancialGuarantee/ Amount	xsd:extension base: xsd:string currencyCode - CurrencyCodeType -	The monetary value of the associated item. [Example(s): Bill rate, invoice item, compensation, allowance. ]
/ StaffingOrganization/ PaymentInfo/ 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. ]
/ StaffingOrganization/ PaymentInfo/ 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
/ [RoundingRuleEnumType]	xsd:restriction base: xsd:string [Enumerations]: RoundDown, RoundHalfDown, RoundUp, RoundHalfUp, RoundHalfEven, RoundCeiling, RoundFloor	Globally scoped data type. See element or attribute declaration for definition.
/ [RoundingRuleType]	resultDigit - xsd:integer - RoundingMethod - RoundingRuleEnumType - S (0/*)	Globally scoped data type. See element or attribute declaration for definition.
/ [RoundingRuleType] / resultDigit	- xsd:integer -	The position of the digit to which the rounding methodology is applied. [Example(s): If the roundingDigit = 3, and the value is 123.4567, the rounding will be applied to the 6 (the 3rd digit to the right of the decimal point). ]
/ [RoundingRuleType]/ RoundingMethod	- RoundingRuleEnumType - S (0/*)	The methodology used for rounding. [BusinessRule(s): See RoundingTypes.xsd for definition of rounding methodologies. ] [Example(s): RoundUp, RoundHalfDown, RoundFloor ]

3.3 BankAccountInfo

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
/ [BankAccountInfoType]	BankInfoByJurisdiction - [complexType] - S (0/*) BankAccountForeign - xsd:string - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [BankAccountInfoType]/ 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) BankAccountType - xsd:string - S (0/1) BankAccountHolder - xsd:string - S (0/1)	Contains identifying information about a particular bank account associated with a particular branch, governed by the laws for a particular regulatory area (jurisdiction).
/ [BankAccountInfoType]/ 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. ]
/ [BankAccountInfoType]/ 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.
/ [BankAccountInfoType]/ 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): SIDES: Used in the context of a Bank Transfer ]
/ [BankAccountInfoType]/ BankInfoByJurisdiction/ BankAccountNumber	- xsd:string - S (1/1)	Indicates the number of a bank account.
/ [BankAccountInfoType]/ 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.
/ [BankAccountInfoType]/ BankInfoByJurisdiction/ BankAccountType	- xsd:string - S (0/1)	Indicates type of account. [Example(s): Checking, Savings ]
/ [BankAccountInfoType]/ BankInfoByJurisdiction/ BankAccountHolder	- xsd:string - S (0/1)	Name of the person or institution that is the holder of the bank account.
/ [BankAccountInfoType]/ 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.4 Reference Id Info

3.4.1 Schema Diagram

3.4.2 Data Dictionary

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ ReferenceIdInfo	- StaffingReferenceIdType - S (0/*)	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. ]
/ ReferenceIdInfo/ StaffingCustomerId	- EntityIdType - S (0/*)	Unique id used to identify the staffing customer.
/ ReferenceIdInfo/ StaffingCustomerOrgUnitId	- EntityIdType - S (0/*)	Unique id used to identify a particular organizational unit of the staffing customer.
/ ReferenceIdInfo/ StaffingSupplierId	- EntityIdType - S (0/*)	Unique id used to identify the staffing supplier.
/ ReferenceIdInfo/ StaffingSupplierOrgUnitId	- EntityIdType - S (0/*)	Unique id used to identify a particular organizational unit of the staffing supplier.
/ ReferenceIdInfo/ OrderId	- EntityIdType - S (0/*)	Unique identifier for a staffing order.
/ ReferenceIdInfo/ HumanResourceId	- EntityIdType - S (0/*)	Reference to a specific HumanResource.
/ ReferenceIdInfo/ IntermediaryId	- EntityIdType - S (0/*)	Unique identifier for a Vendor Management System or 3rd party responsible for staffing management
/ ReferenceIdInfo/ PositionId	- EntityIdType - S (0/*)	Reference to a uniquely identifiable position.
/ ReferenceIdInfo/ BillToEntityId	- EntityIdType - S (0/*)	Unique id used to identify the billing information.
/ ReferenceIdInfo/ AssignmentId	- EntityIdType - S (0/*)	Identifier of the assignment eventually agreed to by the trading partners. [BusinessRule(s): SIDES: Post assignment revisions via a HumanResourceDocument ]
/ ReferenceIdInfo/ TimeCardId	- EntityIdType - S (0/*)	Unique id used to identify the time card.
/ ReferenceIdInfo/ InvoiceId	- EntityIdType - S (0/*)	Unique id used to identify the Invoice.
/ ReferenceIdInfo/ MasterOrderId	- EntityIdType - S (0/*)	Reference to a master order or project. Used to link multiple orders.
/ ReferenceIdInfo/ StaffingOrganizationId	- EntityIdType - S (0/*)	Unique id used to identify the staffing organization.

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.

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
2006-Mar-01	Added Reference Id's to match other SIDES schemas: MasterOrderId and StaffingOrganizationId. Added TaxEvaluation structure to PaymentInfo. Changed BankAccountInfo to not be localized. Added BankAccountType and BankAccountHolder to BankAccountInfo.
2007-Apr-15	Approved by Consortium

6 Appendix B – Related Documents

Reference	Link
SIDES Documentation	http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/SIDES.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Assignment.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/HumanResource.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingAction.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingOrder.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingOrganization.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/SIDESReusableModules.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingInvoice.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingWorkSite.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/ExtendedTimeCard.html http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/JP/SIDESJPLocalizations.html
SIDES schemas	http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Assignment.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/BankAccountInfo.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/ContactInfo.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/CustomerReportingRequirements.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/HumanResource.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Invoice.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Localizations.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Rates.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/ResourceScreening.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingAction.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingContactType.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingOrder.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingOrganization.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingPosition.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingPositionHeader.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingShift.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingWorkSite.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingWorkSiteEnvironment.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/TimeCardAdditionalData.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/JP/JPLocalizations.xsd http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/FR/FRLocalizations.xsd
SIDES reference examples	http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Assignment.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/ContactInfo.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/EntityContactInfo.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/CustomerReportingRequirements.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/HumanResource.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/HumanResource_SocialInsurance.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Invoice.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Rates.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/ResourceScreening.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingAction.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingOrder.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingOrganization.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingOrganization_TaxEval.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingShift.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingWorkSite.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/StaffingWorkSiteEnvironment.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/TimeCardAdditionalData.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/JP/Assignment_ContractRequirements.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/JP/StaffingPositionHeader_NoLimitStaffing.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/NL/ExtendedTimeCard_1.xml
OAGIS Invoice and instance	http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Invoice.xsd (a stand alone version - see http://www.openapplications.org/ for the original) http://ns.hr-xml.org/2_5/HR-XML-2_5/SIDES/Invoice.xml
User Area	http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/HRXMLExtension.html http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/UserArea.xsd