Attachment C FAC124 PunchOut Business Requirements and Technical Specifications.docx

1 Ashburton Place Boston, MA 02108

Pre-Award Vendors PunchOut Requirements

Table of Contents

COMMBUYS

The Commonwealth’s eProcurement system is BuySpeed, re-branded as COMMBUYS. Also referred to as Commonwealth’s market center, is hosted by the Operational Services Division. This procurement technology establishes a single point of service–in short, enables all Commonwealth eligible purchasing agencies to conduct all purchasing and sourcing activities for goods and services.

Commonwealth’s Purchasing Entities Eligible entities include:

· Cities, towns, districts, counties and other political subdivisions;

· Executive, Legislative and Judicial Branches, including all Departments and elected offices therein;

· Independent public authorities, commissions and quasi-public agencies;

· Local public libraries, public school districts and charter schools;

· Public hospitals owned by the Commonwealth;

· Public institutions of higher education;

· Public purchasing cooperatives;

· Non-profit, UFR-certified organizations that are doing business with the Commonwealth;

· Other states and territories with no prior approval by the State Purchasing Agent; and

· Other entities when designated in writing by the State Purchasing Agent.

COMMBUYS Catalog Overview The Sourcing Lead determines the type of catalog is most appropriate for the contract. Below are the catalog types and characteristics that each will fulfill, your Sourcing Lead or contract will specify the type of catalog you will be required to set up.

Hosted/Line Item requires that you record at least one item. This style of catalog is appropriate for vendors with defined items and prices.

PunchOut is an online portal for purchasing that you host on an internal website. This style of catalog uses the web-based catalogs that a supplier hosts on their site. This is an ideal way for vendors to keep their style of branding while still offering their products to state agencies.

Hybrid: PunchOut and Zero Dollar Catalog Line Item in some instances, you can’t record certain purchases from vendors/contracts which are G2B (PunchOut) enabled. Therefore, creating a single vendor blanket with a generic /miscellaneous item to allow for recording of items not on the PunchOut, such as custom quoting, after the fact purchases, Vendor will need to COMMBUYS to review orders for a zero dollar catalog item orders.

The Sourcing Manager will work with the vendor to determine if another catalog ( services on contract) is required to meet the following criteria:

· Custom quoting

· Competitive quoting PunchOut Catalog A G2B PunchOut catalog (or sometimes referred to as PunchOut website) is an online catalog hosted by the vendor and connects to COMMBUYS via data transfer protocols. A G2B PunchOut catalog contains unique pricing and items based on your contract award.

COMMBUYS is a Level One PunchOut; allows order initiation through COMMBUYS yet order management and search capability remains on the vendors system. COMMBUYs Punchout supports commodity purchasing only. The development of a PunchOut catalog is at discretion of OSD contract manager.

Successful PunchOut integration is dependent on a vendor’s business model, previous implementation experience and allocated resources. The typical implementation is dependent on these factors and can take anywhere between 3 weeks and 6 months.

Ideal PunchOut Candidates It is an ideal way for vendors to support large commodity-based catalogs, to keep their style of branding, provide up to date details about items such as availability and, current pricing within their own application. Vendor should explore a punchout if catalogs and business model entails:

· Maintain Large scale Commodity based catalog over 35k line items

· Frequent Prices changes ( daily , weekly, monthly)

· Looking to minimize pricing and invoicing errors Technical Requirements: BuySpeed Whitepaper cXML: Vendors are required to adhere to BuySpeed PunchOut technical requirements and cXML USER Guide: http://xml.cxml.org/current/cXMLUsersGuide.pdf and BuySpeed G2B White Paper, attached.

Browser Compatibility and Operational Requirements COMMBUYS supports industry standard browsers. Vendors are required to test, support, and ensure compatibility of our application. COMMBUYS supports these known and common browsers:

· Mozilla Firefox

· Safari

· Google Chrome

PunchOut must adhere to the following requirements:

· Operational and functional 24 hours a day and seven days a week

· Adhere to the contract agreement

· Enable the Commonwealth eligible entities to purchase Vendor Prequalifying Questionnaire :

Vendors will be required to complete a prequalifying questionnaire listing the following (which will be required as contract terms); Sample questionnaire all requirements. Questionnaire ( pg12-14)

· Circle the PunchOut features/functionality supported

· Receipt of Alternate ID in XML and Print on Invoice

· Label products and Services as Environmentally Preferable

Account Mapping and New Account Setup Requirements

· Account Mapping: The Commonwealth provides an Address _Ids report in which vendor are required to map to their accounts. This is a dynamic fluid process entailing mapping to multiple ship-to/bill-to accounts. Vendor will provide to Operations with the mapped accounts at project completion.

· New Account Support: Vendors are required to provide documentation outlining the new account set-up and turnaround time. All documentation will be housed in as an attachment in COMMBUYs for buyers’ ease and provided to the Helpdesk to expedite service.

Order Fulfillment Requirements: PO Acknowledgment or Order Confirmation

· Order Fulfillment: The Commonwealth requires vendors to capture the buyer email in the XML code and will email buyer either a PO Acknowledgment or Order Acknowledgment. In the event the PunchOut is inaccessible, the vendor must accommodate buyer’s offline order fulfilment via phone, email or fax.

Vendor Management Reporting

· Reporting: Vendors are required to provide PunchOut spend in OSD mandated reports.

COMMBUYS Vendor Profile Maintenance

· All vendors must maintain their profile in COMMBUYS using the seller administration role. Vendor’s name displayed in COMMBUYS for PunchOut link is determined by profile name.

Vendor and COMMBUYS System Maintenance

· Vendor Maintenance: A notification of schedule maintenance should be sent to COMMBUYS team prior to 10 days at commbuys@mass.gov

· COMMBUYS Maintenance: COMMBUYS scheduled maintenance usually occurs on the second weekend of the month only on Saturday or Sunday with system back online by 3:00am Sunday.

Ongoing Technical Support Vendors are required to provide technical support to resolve any network, XML, purchase order and delivery issues. The contact information must include name, email and phone number.

Technical Support

Vendor: User Conduct Guidelines The PunchOut must adhere to the following User Conduct:

· The vendor must not knowingly use the website in any way that causes, or is likely to cause, the site or access to it to be interrupted, damaged or impaired in any way

· The vendor must ensure that any content you upload onto the site (including photographs) is not obscene, offensive, defamatory or racist and does not breach any law or regulation or any intellectual property rights of a third party or any right or duty owed to a third party. This means that if any of the content you upload is copyright protected, you must obtain the copyright owner’s written permission in order to use it. In the event that you become aware of any content which breaches any of the above rules, please notify us immediately by emailing commbuys@mass.gov

· The PunchOut must not use the site to misrepresent your identity or affiliation with any person or organization. The PunchOut must not use the site to send junk or spam email

· OSD reserves the right to remove any inappropriate or unauthorized content from any page.

· The vendor must not attempt to bypass the network firewall

· The vendor must not use any part of this website which you are not authorized to use or devise ways to circumvent security in order to access part of this web site which you are not authorized to access. This includes but is not limited to scanning networks with the intent to breach and/or evaluate security, whether or not the intrusion results in access

· The vendor must not use or attempt to use this website for any unlawful, criminal or negligent purpose. This includes but is not limited to password cracking, social engineering (defrauding others into releasing their passwords), denial-of-service attacks, harmful and malicious destruction of data, and introduction of computer viruses and intentional invasion of privacy.

Customer Data

· Service Provider shall not collect, access, or use user-specific Customer Data except as strictly necessary to provide Service to Customer. No information regarding Customer’s use of the Service may be disclosed, provided, rented or sold to any third party for any reason unless required by law or regulation or by an order of a court of competent jurisdiction. This obligation shall extend beyond the term of the Agreement in perpetuity.

· At no time may any data or processes which either belong to Customer, or are intended for Customer’s exclusive use, be copied, disclosed, or retained by Service Provider for subsequent use in any transaction that does not include Customer.

· Three (3) months after the termination or expiration of the Agreement or upon Customer’s earlier written request, and in any event after Customer has had an opportunity to export and recover the Customer Data, Service Provider shall at its own expense destroy and erase from all systems it directly or indirectly uses or controls all tangible or intangible forms of the Customer Data and Customer’s Confidential Information, in whole or in part, and all copies thereof except such records as are required by law. To the extent that any applicable law prevents Service Provider from destroying or erasing Customer Data as described in the preceding sentence, Service Provider shall retain, in its then current state, all such Customer Data then within its right of control or possession in accordance with the confidentiality, security and other requirements of this Agreement, and perform its obligations under this section as soon as such law no longer prevents it from doing so. Service Provider shall, upon request, send a written certification to Customer certifying that it has destroyed the Customer Data and Confidential Information in compliance with this section.

PunchOut Metrics/Compliance The intent of the metrics is to motivate the vendor toward optimal performance and service. OSD contract manager reserves right to disable PunchOut for the following but not limited to: service availability, technical quality, security break, inaccessiblity and pricing and product (off catalog items on PunchOut) issues.

· PunchOut Issues Handling: Not responding to any issues, on or off contract purchases, pricing, vendor process, account set-up or site related, within two business days or as otherwise specified in the contract terms.

· Internal Exception Handling: Not establishing a process to support any internal order failure (exception) that occurs after order transmittal and acceptance, and which prevents order processing.

· Not responding to customer within one hour. The vendor must email buyer, order resolution within 24 hours. If issue requires further review, the vendor must provide buyer with a timeframe for resolution. Contract manager will review all issues impacting order fulfillment issues to ensure contract adherence. If vendors do not comply, the contract manager reserves the right to inactivate the PunchOut.

· Change in XML code, vendor must contact the buyer if there will be a delay in order processing

Vendors not compliant with agreed upon contract terms related to PunchOut functionality and service requirements according to the Commonwealth’s operating procedures may be disabled without notice.

Sample PunchOut Capability Questionnaire

COMMBUYS

Punchout Capability Questionnaire Please complete survey. Your answers help determine your organization feasibility to implementing a PunchOut with Operational Services Division.

Please return the completed form to your contract manager

Vendor Name:

DATE:

Statewide Contract Number:

UNSPSC Code:

Category Awarded:

Contract Manager:

Punchout Project Go-Live date per contract award:

Business Contact Name:

Email:

P:

C:

Technical Lead Contact Name

· A yes indicates that Commonwealth buyers will be not charged taxes

· A yes indicates your organization can support a PunchOut and a purchase order in XML.

· A yes indicates you will return a 200 code according to BuySpeed standards,

· A yes indicates you do not accept the order and will return a 500 code.

If the Commonwealth receives any response from other than a 200 code, it will be interpreted as a failure and the PO will remain at 'Ready to Send' status resulting in incomplete transaction

· A yes indicates your Punchout site can display buyer specific pricing.

· A yes indicates your Punchout site supports product blocking

· A yes indicates your Punchout site can display EPP information.

· A yes indicates your Punchout site may be able to control buying

Can you map to multiple ship-to and Bill to addresses to a single purchase order?

Other Comments :

Sample PunchOut Features and Functionality Questionnaire

Order Fulfillment

Do you List out-of-stock and have back order notification process?

Overnight delivery, Core Charges, HazMat

Copyright © 2017 Commonwealth of Massachusetts -OSD

Wednesday, July 05, 2023

June 7, 2021 Page | 11 image2.emf

BuySpeed G2B White Paper 13.X.DOCX

G2B Solution

White Paper

BuySpeed G2B 13.X

TABLE OF CONTENTS

TABLE OF CONTENTS 2

G2B Introduction 3

The XML Document 4

Transportation Methods 4

NOTES: 4

Transaction Set 4

Payment Terms 7

Initiating Punchout Transactions in BuySpeed 7

Purchasing Card 14

G2B Integration Contacts 15

APPENDIX 1 – PunchOut 16

PUNCHOUTSETUPREQUEST SPECIFICATION 16

PUNCHOUTSETUPREQUEST SAMPLES 18

OPERATION TYPE - CREATE 18

APPENDIX 2 – PunchOutOrder Message 21

PUNCHOUTORDER MESSAGE RESPONSE SPECIFICATION 21

PUNCHOUTORDER MESSAGE SAMPLE 24

APPENDIX 3 – Purchase Order 27

PURCHASE ORDER SPECIFICATION 27

PURCHASE ORDER SAMPLE 30

APPENDIX 4 - Acknowledgment 35

PURCHASE ORDER ACKNOWLEDGMENT SPECIFICATION 35

ACKNOWLEDGMENT (ACCEPT - 200) SAMPLE 36

ACKNOWLEDGMENT (REJECT - 500) SAMPLE 36

APPENDIX 5 – Invoice Detail Request 37

INVOICEDETAILREQUEST SPECIFICATION 37

INVOICE SAMPLE 40

About Periscope Holdings, Inc. 43

G2B Introduction

The BuySpeed eProcurement Solution supports government to business (G2B) integrations with direct customers or third party trading partners. Once a G2B integration is established with a G2B-enabled vendor, clients can shop customized online catalogs and electronically exchange procurement transactions between the BuySpeed eProcurement Solution and the G2B-enabled vendor system.

Clients can access customized online product catalogs by punching out to a customer-specific online catalog and return the product data to the BuySpeed eProcurement Solution. Additionally, clients can submit electronic purchase orders directly to the G2B enabled vendor site using industry standard XML protocols. Purchase Orders submitted in this fashion usually process directly through the vendors order entry system for fulfillment, saving hours or days in processing time and improving product shipping times.

Customers utilizing the BuySpeed eProcurement Solution for G2B integrations benefit from:

· Customized product catalogs (customer-specific products and pricing)

· Electronic management of procurement transactions

· Lower procurement costs

· Reduced approval cycle times

· Increased data accuracy

· Improved spend management

In general, to provide optimal benefit to clients, it is advised that the integration utilize both a PunchOut and electronic purchase order solution. This document provides guidance and reference material to IT professionals to establish a G2B Integration through BuySpeed. Additionally, it provides specifications and samples for the G2B transaction set including: PunchOut, PunchOutOrder Message, Purchase Order, and Purchase Order Acknowledgement. Also included in the document are the G2B process flow, G2B Integration contacts, and other information relevant for establishing a G2B Integration. For more information, see the G2B Integration contacts section to speak to someone directly.

If the vendor does not already have a Punchout relationship with Periscope, a project must be setup with Periscope to implement the new Punchout. Any new Punchout relationships not implemented through Periscope will not be supported as part of Periscope’s standard maintenance and support agreement.

The XML Document

XML (“eXtensible Markup Language”) is a markup language for documents containing structured information. An XML file is a very flexible text file designed to transfer data between systems. There are many different protocols of XML; however, BuySpeed supports the major protocols that exist in the procurement industry. These protocols include xCBL, cXML, and OCI. To read more about cXML, the standard protocol for G2B Punchouts, visit cXML.org.

In addition, BuySpeed now supports the return of NIGP Code to Punchout Requisitions and POs. If the Punchout Vendor passes NIGP Code via cXML, that code will now be added to the item created on the Punchout Requisition or PO in BuySpeed.

Transportation Methods

The vendor enabled G2B site can be accessed via an HTTPS post using Secure Sockets Layer (“SSL”) to protect the data. HTTPS is an HTTP protocol layered over the SSL protocol to allow secure transmission of data using encrypted data streams. SSL is a transaction security standard that provides data encryption, server authentication, and message integrity.

NOTES:

1. In order to post XML over HTTPS, the HTTP header setting “Content-Type” must be ‘text/xml‘.

2. The HTTP authentication method should be set to either anonymous or basic with no user ID or password in the HTTP header.

3. Sites that are hosting BuySpeed and looking to allow punch-out’s, must configure their firewall rules to allow TCP and UDP outbound traffic from the server hosting BuySpeed at the transport layer and HTTP(S) at the application and presentation layer.

Transaction Set

PunchOut

See Appendix 1 for Specifications & Sample(s)

· PunchOut is defined by accessing an authenticated, Vendor G2B PunchOut catalog from the BuySpeed eProcurement Solution. The operation type field can be one of three values: create – to create a new PunchOutOrder Message; edit – to edit an existing PunchOutOrder Message; and inspect – to view the details of an existing PunchOutOrder Message. If operation type is edit or inspect, then the Cart ID of the PunchOutOrder Message will be required in the PunchOut document. At this time only the create operation type is supported.

· PunchOut ―edit / allows the user to retrieve a PunchOutOrder Message (Cart) and modify it. A new Cart ID is returned in the PunchOutOrder Message and the old Cart ID is disabled.

· PunchOut ―inspect / allows the user to simply view the contents of the order on the G2B vendor site.

PunchOutOrder Message

See Appendix 2 for Specifications & Sample(s)

The PunchOutOrder Message contains the contents of the shopping cart created from the G2B vendor PunchOut catalog. This document is sent back to the URL that is provided in the postback URL of the PunchOut document.

Purchase Order

See Appendix 3 for Specifications & Sample(s)

The Purchase Order contains product information plus billing and shipping information.

Purchase Order Acknowledgement

See Appendix 4 for Specifications & Sample(s)

The Purchase Order Acknowledgement is immediately sent from the G2B vendor site to BuySpeed after the G2B vendor has received an electronic purchase order. The Purchase Order Acknowledgement is a system-to-system response (synchronous) that contains a status code and description.

· Status Code = “200”:

· PO was successful.

· Response will include PO number.

· For sample Purchase Order Acknowledgement of successful PO.

· The G2B vendor will send the following email notification to the email address provided on the PO (cXML/Request/OrderRequest/OrderRequest/Header/ShipTo/Address/Email):

PO acknowledgement indicating that the G2B vendor received the order.

· Time sent: when PO is received by the G2B vendor.

· Status Code = “500”:

· PO failed due to one or more issues.

· Response will contain the error description of the first error encountered, along with original PO details.

Invoice Detail Request

See Appendix 5 for Specifications & Sample(s)

The Invoice Detail Request is an optional transaction supported within BuySpeed. This transaction originates from the G2B vendor and allows the settlement process to occurring electronically. This document is sent back to the URL that has been shared with the G2B vendor.

Figure 1 - Supported G2B Transactions

G2B INTRODUCTION

Payment Terms

Purchase Order (Terms)

BuySpeed defaults the purchase as a “terms” order if a PCard number is not sent in the PO. The conditions of “terms” orders are setup with the G2B enabled vendor prior to starting the G2B integration.

Initiating Punchout Transactions in BuySpeed

Browser Settings

Before you can initiate a Punchout, you must disable any pop-up blocker software or configurations in your browser. In addition, IE8 has added an XSS filter that comes enabled that could interfere with the Punchout process. This is a Punchout vendor issue, so some vendors might trigger this filter while others have code that disables this filter in your browser. This filter can also be disabled within the browser but this is managed as a global setting across the board and not just for the Punchout vendor.

Setup of G2B Master Blanket

The first step that must be performed is to setup your G2B Master Blanket for the Punchout vendor in question. The following screenshot shows a the pre-requisite G2B Master Blanket in the appropriate status ready for executing Punchout transactions for the vendor in question.

Configure Punchout Settings

The second step will be to setup and configure the Punchout connection settings with the G2B vendor. The step is normally performed by Periscope IT staff in conjunction with the vendor who provides account and Punchout URL settings.

Please note that it’s very important that “CXMLv2” needs to be selected when configuring the Maintain Punchout Vendor page settings, and that Punchout Submit Type needs to be “xml”, in order for you to be able to take advantage of BuySpeed’s full G2B Punchout functionality.

The Invoice Import Allowed enables the acceptance of the cXML InvoiceDetailRequest transactions.

To determine the post-back URL on the InvoiceDetailRequest, see the Invoice Import Authentication form as displayed in the image above. This is the location of the servlet that is responsible for accepting invoice transaction returned by G2B enabled vendors.

Initiating the Punchout

Once the Master Blanket has been set up and the system has been configured to communicate with the Punchout vendor, you are ready to execute a release from the Master blanket. This is initiated from the ‘Shopping Cart’ icon located in the upper right hand area of BuySpeed. Clicking this icon puts you on the following page.

You use the Vendor dropdown option to select your Punchout vendor and click the ‘Punchout’ button. At this point a separate browser window will appear using the pre-configured account authentication and URLs associated with the G2B vendor and logs you into the G2B vendor site.

Every G2B vendor site will differ, but all follow the shopping cart model and search functionality that allows you to search and place items into your cart. When completed, the G2B vendor will provide a mechanism to ‘checkout’ and return your shopping cart to BuySpeed.

Once you check out, the shopping cart is created within BuySpeed as an in-progress requisition release. At this point it will function just like any BuySpeed direct release with any approval path workflows that may have been configured for this type of purchase.

Once the requisition is approved it will be converted into a purchase order release that will be in Ready to Send status ‘3PRS’.

Clicking the Save & Continue button will transmit the purchase order release to the G2B vendor and complete the transaction on the BuySpeed side.

Purchasing Card

BuySpeed supports PCards through the G2B process. PCard information is delivered via the purchase order. The expiration date and card holder name are required. The vendor determines the type of card based on the first digit of the card number.

· 3 – AMEX

· 4 = VISA

· 5 = Master Card

· 6=Discover

For security purposes, BuySpeed encrypts the credit card number, expiration date, and card holder name within the BuySpeed database.

G2B Integration Contacts

Business Development

For vendors or clients who wish to implement BuySpeed’s G2B feature with an ecommerce site, contact Ken McFarland V.P. of Sales & Marketing to inquire on getting started with the BuySpeed G2B feature. 512-666-9387

Services Delivery Manager

The overall project manager responsible for delivery of the punch-out implementation within BuySpeed. Will work with the customer, internal technical lead, and the punch-out vendor. Contact Chris Kennedy V.P. of Consultative Services to inquire on services for delivery of G2B integrations. 512-666-9390

Technical Lead

Responsible for the technical details of reviewing the punch-out vendor’s capabilities and ensuring all technical requirements are being satisfied between BuySpeed and the punch-out vendor. Contact Greg Flores V.P. of Technology to inquire on technical specifications and requirements for G2B integration setup. 512-666-9403

BuySpeed Support Desk

Provides troubleshooting of the BuySpeed G2B implementation once it has been deployed to the production environment.

· Phone: 888.472.9102

· Email: support@buyspeed.com

APPENDIX 1 – PunchOut

(BuySpeed sends to G2B Vendor)

PUNCHOUTSETUPREQUEST SPECIFICATION

Element cXML Mapping Information

Required

Validation / Notes

Customer’s Authentication

Domain cXML/Header/From/Credential@domain

Yes

Set to valid cXML Domain such as “NetworkId”, “DUNS”, “AribaNetworkUserId”, “Phone”, or “TaxID”.

Customer User ID cXML/Header/From/Credential/Identity

Yes

Unique value that is used to authenticate the customer’s PunchOut session.

Deployment Mode cXML/Request/PunchOutSetupRequest/@deploymentMode

Yes

Values are “test” or “production”.

Operation Type cXML/Request/PunchOutSetupRequest/@operation

Yes

Values are “create”, ”edit”, “inspect”.

Postback URL cXML/Request/PunchOutSetupRequest/BrowserFromPost/URL

Yes

URL that the punchout vendor will use to submit the PunchOutOrder Message Response back to.

Part ID to support Edit and Inspect operations cXML/Request/PunchOutSetupRequest/SelectedItem/ItemID/SupplierPartID

No

Only required if Operation Type= Edit or Inspect

Cart ID cXML/Request/PunchOutSetupRequest/SelectedItem/ItemID/SupplierPartAuxiliaryId

No

Only required if Operation Type = Edit or Inspect

Notes:

Shared Secret/Password

Not all vendor punchout sites require a SharedSecret in the Header Sender Credential for authentication.

PUNCHOUTSETUPREQUEST SAMPLES

OPERATION TYPE - CREATE

<cXML payloadID="1253832687927.1966498874653534823" timestamp="2009-09-24T17:51:27-0500">

<Header>

<From>

<Credential domain="NetworkId">

<Identity>ctybal050509-T</Identity>

</Credential>

</From>

<To>

<Credential domain="DUNS">

<Identity>153531108</Identity>

</Credential>

</To>

<Sender>

<Credential domain="NetworkId">

<Identity>ctybal050509-T</Identity>

<SharedSecret/>

</Credential>

<UserAgent>phi/BSO-8.2.0</UserAgent>

</Sender>

</Header>

<Request>

<PunchOutSetupRequest operation="create">

<BuyerCookie>1253832687927.1966498874653534823</BuyerCookie>

<Extrinsic name="User">Administrator System</Extrinsic>

<Extrinsic name="Identity">ctybal050509-T</Extrinsic>

<BrowserFormPost>

<URL>https://arizona.buyspeed.com/bso82ora/g2b/receiver.sdo?param=__9000000085__create__DOCID__SPO__SPO__3__3__AGENCY10-0000211&amp;user=BUYSPEED&amp;origin=BSO</URL>

</BrowserFormPost>

<Contact role="user">

<Name xml:lang="en">Administrator System</Name>

<Email>mlepine@goperiscope.com</Email>

<Phone name="Office">

<TelephoneNumber>

<CountryCode isoCountryCode="US">1</CountryCode>

<AreaOrCityCode>555</AreaOrCityCode>

<Number>5550212</Number>

</TelephoneNumber>

</Phone>

</Contact>

<ShipTo>

<Address addressID="3">

<Name xml:lang="en">State Procurement Office - State Procurement Office</Name>

<PostalAddress>

<DeliverTo>Jean Clark, State Procurement Administrator</DeliverTo>

<Street>100 N. 15th Avenue</Street>

<Street>Suite 100</Street>

<City>Phoenix</City>

<State>AZ</State>

<PostalCode>85007</PostalCode>

<Country isoCountryCode="US">United States</Country>

</PostalAddress>

<Email>mlepine@goperiscope.com</Email>

<Phone name="work">

<TelephoneNumber>

<CountryCode isoCountryCode="US">1</CountryCode>

<AreaOrCityCode>602</AreaOrCityCode>

<Number>5425511</Number>

</TelephoneNumber>

</Phone>

</Address>

</ShipTo>

<SelectedItem>

<ItemID>

<SupplierPartID>AAA</SupplierPartID>

<SupplierPartAuxiliaryID/>

</ItemID>

</SelectedItem>

</PunchOutSetupRequest>

</Request>

</cXML>

APPENDIX 2 – PunchOutOrder Message

(G2B Vendor sends to BuySpeed from PunchOut session)

PUNCHOUTORDER MESSAGE RESPONSE SPECIFICATION

Element cXML Mapping Information

Validation / Notes

From vendors authentication domain cXML/Header/From/Credential@domain

Set to “DUNS”.

From vendors authentication identity cXML/Header/From/Credential/Identity

Set to the vendors DUNS number.

To customer’s authentication domain cXML/Header/From/Credential/@domain=”NetworkId”

Return value from PunchOut setup.

To customer’s authentication identity cXML/Header/From/Credential/Identify

Return value from PunchOut setup.

Senders (vendor) authentication Domain cXML/Header/Sender/Credential/@domain=”DUNS”

Value set as “DUNS”

Sender (vendor) authentication identity cXML/Header/Sender/Credential/Identity

Value set to the vendors “DUNS” number.

Vendor’s shared secret cXML/Header/Sender/Credential/SharedSecret

Value usually empty or set to some placeholder value by the vendor

User Agent cXML/Header/Sender/Credential/UserAgent

Value usually empty or set to some placeholder value by the vendor

Deployment Mode cXML/Request/@deployment=”test”

Value set to “test” for test site / “production” for production site.

Currency Code cXML/Message/PunchOutOrderMessage/PunchOutOrderMessageHeader/Total/Money/@currency

Value is ISO currency code.

Total Amount cXML/Message/PunchOutOrderMessage/PunchOutOrderMessageHeader/Total/Money

Total value of Cart.

Quantity cXML/Message/PunchOutOrderMessage/ItemIn/@quantity

Quantity of line item.

Part ID cXML/Message/PunchOutOrderMessage/ItemIn/ItemID/SupplierPartID

Vendor part number used in their order entry system.

Cart ID cXML/Message/PunchOutOrderMessage/ItemIn/ItemID/SupplierPartAuxillaryID

Vendor cart id number.

Currency Code cXML/Message/PunchOutOrderMessage/ItemIn/ItemDetail/UnitPrice/Money/@currency

Value is ISO currency code.

Unit Price cXML/Message/PunchOutOrderMessage/ItemIn/ItemDetail/UnitPrice/Money

Unit Cost of Line Item.

Product Description cXML/Message/PunchOutOrderMessage/ItemIn/ItemDetail/Description

Description of Line Item.

Unit of Measure cXML/Message/PunchOutOrderMessage/ItemIn/ItemDetail/UnitOfMeasure

Value set as “EA” (each).

UNSPSC Code cXML/Message/PunchOutOrderMessage/ItemIn/ItemDetail/Classification/@domain=UNSPSC

See UNSPSC section.

Manufacturer PartID cXML/Message/PunchOutOrderMessage/ItemIn/ItemDetail/ManufacturerPartID

Manufacturer part number.

Manufacturer Name cXML/Message/PunchOutOrderMessage/ItemIn/ItemDetail/ManufacturerName

Manufacturer name.

PUNCHOUTORDER MESSAGE SAMPLE

<cXML version="1.0" payloadID="20090924175200355.1527qQdkxiq+w+dRpQNPVKGQlc7|oMs-44323.c0a81e17f70de40f000023ed@imqa3" timestamp="2009-09-24T17:52:00-CDT">

<Header>

<From>

<Credential domain="DUNS">

<Identity>153531108</Identity>

<SharedSecret></SharedSecret>

</Credential>

</From>

<To>

<Credential domain="NetworkId">

<Identity>ctybal050509-T</Identity>

<SharedSecret></SharedSecret>

</Credential>

</To>

<Sender>

<Credential domain="NetworkId">

<Identity>ctybal050509-T</Identity>

<SharedSecret></SharedSecret>

</Credential>

<UserAgent></UserAgent>

</Sender>

</Header>

<Message>

<PunchOutOrderMessage>

<BuyerCookie>1253832687927.1966498874653534823</BuyerCookie>

<PunchOutOrderMessageHeader operationAllowed="edit">

<Total>

<Money currency="USD"> 2.99</Money>

</Total>

<Shipping>

<Money currency="USD"> 0.00</Money>

<Description xml:lang="en">shipping charges</Description>

</Shipping>

<Tax>

<Money currency="USD"> 0.00</Money>

<Description xml:lang="en">tax charges</Description>

</Tax>

</PunchOutOrderMessageHeader>

<ItemIn quantity="1" lineNumber="1">

<ItemID>

<SupplierPartID>4UG98</SupplierPartID>

<SupplierPartAuxiliaryID>WWG4UG98</SupplierPartAuxiliaryID>

</ItemID>

<ItemDetail>

<UnitPrice>

<Money currency="USD">2.99</Money>

</UnitPrice>

<Description xml:lang="en-US">Indoor/Outdoor Caulk, Container Size 10.1 Ounces, Style Window/Door 100% Silicone Rubber Sealant, Color Clear, Watertight, Flexible</Description>

<UnitOfMeasure>EA</UnitOfMeasure>

<Classification domain="UNSPSC">31201606</Classification>

<ManufacturerPartID>GE012A</ManufacturerPartID>

<ManufacturerName>GENERAL ELECTRIC</ManufacturerName>

</ItemDetail>

<Shipping>

<Money currency="USD"> 0.00</Money>

<Description xml:lang="en">shipping charges</Description>

</Shipping>

<Tax>

<Money currency="USD"> 0.00</Money>

<Description xml:lang="en">tax charges</Description>

</Tax>

</ItemIn>

</PunchOutOrderMessage>

</Message>

</cXML>'

APPENDIX 3 – Purchase Order

(BuySpeed sends to G2B Vendor)

PURCHASE ORDER SPECIFICATION

Element cXML Mapping Information

Validation / Notes

From vendors authentication domain cXML/Header/From/Credential@domain

Set to “DUNS”.

From vendors authentication identity cXML/Header/From/Credential/Identity

Set to the vendors DUNS number.

Deployment Mode cXML/Request/@deploymentMode

Values are “test” or “production”.

PO Number cXML/Request/OrderRequest/OrderRequestHeader/@orderID

Purchase Order Number.

PO Date cXML/Request/OrderRequest/OrderRequestHeader/@orderDate

Date Purchase Order was issued.

PO Type cXML/Request/OrderRequest/OrderRequestHeader/@type

Value set to “New”.

ShipTo Organization Name cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/Name

Ship To Organization.

ShipTo Contact Name cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/PostalAddress/DeliverTo

Order and Ship To contact name.

ShipTo Street Address Line1 cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/PostalAddress/Street

Ship To Street Address 1

ShipTo Street Address Line2 cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/PostalAddress/Street

Ship To Street Addrss 2

ShipTo City cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/PostalAddress/City

Ship To City

ShipTo State cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/PostalAddress/State

Ship To State

ShipTo Zip cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/PostalAddress/PostalCode

Ship To Zip

ShipTo Phone cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/Phone/TelephoneNumber/Number

Ship To Phone

ShipTo Country cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/PostalAddress/Country/@isoCountryCode

Ship To Country

ShipTo Contact Email Address cXML/Request/OrderRequest/OrderRequestHeader/ShipTo/Address/Email

Ship To Contact email address.

BillTo Organization Name cXML/Request/OrderRequest/OrderRequestHeader/BillTo/Address/Name

Bill To Organization.

BillTo Contact Name cXML/Request/OrderRequest/OrderRequestHeader/BillTo/Address/PostalAddress/DeliverTo

Bill To contact name.

BillTo Street Address Line1 cXML/Request/OrderRequest/OrderRequestHeader/BillTo/Address/PostalAddress/Street

Bill To Street Address 1

BillTo Street Address Line2 cXML/Request/OrderRequest/OrderRequestHeader/BillTo/Address/PostalAddress/Street

Bill To Street Addrss 2

BillTo City cXML/Request/OrderRequest/OrderRequestHeader/BillTo/Address/PostalAddress/City

Bill To City

BillTo State cXML/Request/OrderRequest/OrderRequestHeader/BillTo/Address/PostalAddress/State

Bill To State

BillTo Zip cXML/Request/OrderRequest/OrderRequestHeader/BillTo/Address/PostalAddress/PostalCode

Bill To Zip

BillTo Phone cXML/Request/OrderRequest/OrderRequestHeader/BillTo/Address/Phone/TelephoneNumber/Number

Bill To Phone

Credit Card Number cXML/Request/OrderRequest/OrderRequestHeader/Payment/@number

Credit card type is determined by the first digit of the credit card number; 3=AMEX; 4=Visa;5=MC;

6=Discover

Credit Card Expiration Date cXML/Request/OrderRequest/OrderRequestHeader/Payment/@expiration

Expiration Date: Format YYYYMM

Credit Card Name cXML/Request/OrderRequest/OrderRequestHeader/Payment/@name

Card Holder Name

Quantity cXML/Request/OrderRequest/ItemOut/@quantity

Line item quantity

Part ID cXML/Request/OrderRequest/ItemOut/ItemID/SupplierPartID

Line Item Part Number from PunchOutOrder Message.

Cart ID/Line Item Number cXML/Request/OrderRequest/ItemOut/ItemID/SupplierPartAuxillaryID

Line Item Cart ID from the PunchOutOrder Message.

Unit Price cXML/Request/OrderRequest/ItemOut/ItemDetail/UnitPrice/Money

Line Item Unit Price from PunchOutOrder Message.

PURCHASE ORDER SAMPLE

<cXML payloadID="1253832916890.5035431423174533229" timestamp="2009-09-24T17:55:16-0500">

<Header>

<From>

<Credential domain="NetworkId">

<Identity>ctybal050509-T</Identity>

</Credential>

</From>

<To>

<Credential domain="DUNS">

<Identity>153531108</Identity>

</Credential>

</To>

<Sender>

<Credential domain="NetworkId">

<Identity>ctybal050509-T</Identity>

<SharedSecret/>

</Credential>

<UserAgent>phi/BSO-8.2.0</UserAgent>

</Sender>

</Header>

<Request>

<OrderRequest>

<OrderRequestHeader orderDate="2009-09-24T17:55:16-0500" orderID="AGENCY10-0000211000001" type="new">

<Total>

<Money currency="USD">2.99</Money>

</Total>

<ShipTo>

<Address addressID="3">

<Name xml:lang="en">State Procurement Office - State Procurement Office</Name>

<PostalAddress>

<DeliverTo>Jean Clark, State Procurement Administrator</DeliverTo>

<Street>100 N. 15th Avenue</Street>

<Street>Suite 100</Street>

<City>Phoenix</City>

<State>AZ</State>

<PostalCode>85007</PostalCode>

<Country isoCountryCode="US">United States</Country>

</PostalAddress>

<Email>mlepine@goperiscope.com</Email>

<Phone name="work">

<TelephoneNumber>

<CountryCode isoCountryCode="US">1</CountryCode>

<AreaOrCityCode>602</AreaOrCityCode>

<Number>5425511</Number>

</TelephoneNumber>

</Phone>

</Address>

</ShipTo>

<BillTo>

<Address addressID="3">

<Name xml:lang="en">State Procurement Office - State Procurement Office</Name>

<PostalAddress>

<DeliverTo>Jean Clark, State Procurement Administrator</DeliverTo>

<Street>100 N. 15th Avenue</Street>

<Street>Suite 100</Street>

<City>Phoenix</City>

<State>AZ</State>

<PostalCode>85007</PostalCode>

<Country isoCountryCode="US">United States</Country>

</PostalAddress>

<Email>spo@azdoa.gov</Email>

<Phone name="work">

<TelephoneNumber>

<CountryCode isoCountryCode="US">1</CountryCode>

<AreaOrCityCode>602</AreaOrCityCode>

<Number>5425511</Number>

</TelephoneNumber>

</Phone>

</Address>

</BillTo>

<Payment>

<PCard expiration="200901" name="Edward Clark" number="4111111111111111">

</Payment>

<PostalAddress>

<DeliverTo>Edward Clark, State Procurement Administrator</DeliverTo>

<Street>100 N. 15th Avenue</Street>

<Street>Suite 100</Street>

<City>Phoenix</City>

<State>AZ</State>

<PostalCode>85007</PostalCode>

<Country isoCountryCode="US">United States</Country>

</PostalAddress>

</OrderRequestHeader>

<ItemOut lineNumber="1" quantity="10.0">

<ItemID>

<SupplierPartID>348037</SupplierPartID>

<SupplierPartAuxiliaryID>348037</SupplierPartAuxiliaryID>

</ItemID>

<ItemDetail>

<UnitPrice>

<Money currency="USD">30.08</Money>

</UnitPrice>

<Description xml:lang="en">Office Depot(R) Brand Copy Paper, 20 Lb, 104 Brightness, 8 1/2quot x 11quot, Case Of 10 Reams</Description>

<UnitOfMeasure>CS</UnitOfMeasure>

<Classification domain="UNSPSC">unknown</Classification>

<ManufacturerPartID/>

<ManufacturerName xml:lang="en"/>

<Extrinsic name="Tax">0.0</Extrinsic>

<Extrinsic name="Freight">0.0</Extrinsic>

</ItemDetail>

</ItemOut>

</OrderRequest>

</Request>

APPENDIX 4 - Acknowledgment

(G2B Vendor sends to BuySpeed)

PURCHASE ORDER ACKNOWLEDGMENT SPECIFICATION

Field cXML Mapping Information

Validation / Notes

Status Code cXML/Response/Status/@code

“200” = successful and accepted; “500”= rejected

Status Text cXML/Response/Status/@text

If status code = “200”, will either display an ok message or po#. This varies by G2B vendor; If status code = “500”, then PO data and error description is provided. This varies by G2B vendor.

ACKNOWLEDGMENT (ACCEPT - 200) SAMPLE

<cXML payloadID="2009-09-24.17:55:19-0500.32554596@gebopsqa" timestamp="2009-09-24T17:55:19-0500">

<Response>

<Status code="200" text="OK" />

</Response>

</cXML>

ACKNOWLEDGMENT (REJECT - 500) SAMPLE

<cXML payloadID="20090605134849146.7185PfV+Zsf|aj1fDl1ChEoV2idRhAo-443185.c0a81cb9f70d1c07000037b4@wmqa3" timestamp="2009-06-05T13:48:49-CDT" xml:lang="en-US">

<Response>

<Status code="500">Output buffer too small.</Status>

</Response>

APPENDIX 5 – Invoice Detail Request

(G2B Vendor sends to BuySpeed)

INVOICEDETAILREQUEST SPECIFICATION

Element cXML Mapping Information

Required

Validation / Notes

Domain cXML/Header/From/Credential@domain

No

Set to valid cXML Domain such as “NetworkId”, “DUNS”, “AribaNetworkUserId”, “Phone”, or “TaxID”, “sitewide”.

Identity cXML/Header/From/Credential/Identity

Yes

Unique value that is used to identify the sender or network provider performing the transmission.

Domain cXML/Header/To /Credential/@domain

No

Set to valid cXML Domain such as “NetworkId”, “DUNS”, “AribaNetworkUserId”, “Phone”, or “TaxID”, “sitewide”.

Identify cXML/Header/To/Credential/Identity

Yes

Unique value that is used to identify the receiver of the transmission.

Domain cXML/Header/Sender/Credential@domain

Yes

Should be set to sitewide.

Identity cXML/Header/Sender/Credential/Identity

Yes

Unique value that is used to identify the sender or vendor submitting invoice transaction. BuySpeed will use this for authentication purposes.

SharedSecret cXML/Header/Sender/Credential/SharedSecret

Yes

Unique value that is used for authentication. BuySpeed will use this for authentication purposes.

UserAgent cXML/Header/Sender/UserAgent

No

N/A invoiceID cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader@invoiceID

Yes

Vendor invoice number. Must be unique for the vendor.

Purpose cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader@purpose

Yes

Always set to ‘standard’.

Operation cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader@operation

Yes

Always set to ‘new’ in conjunction with the purpose of ‘standard’.

invoiceDate cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader@invoiceDate

Yes

Formatted as YYYY-MM-DD HH:MM:SS and should reflect the day invoice was submitted.

Extrinsic - Description cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/Description

Yes

This value will map to the invoice header description field.

Extrinsic – RemitText cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/RemitText

Yes

This value will map to the header invoice Remit Text field.

Extrinsic – PaymentDate cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/PaymentDate

Yes

This value will map to the header invoice payment date field.

payloadID cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailOrderInfo/OrderReference/DocumentReference@payloadID

Yes

The purchase order number that this invoice is tied to.

invoiceLineNumber cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailItem@invoiceLineNumber

Yes

The invoice line item number.

quantity cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailItem@quantity

No

The quantity that is being invoiced.

finalPay cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailItem@finalPay

Yes

Should always be ‘N’.

currency cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailItem/GrossAmount/Money@currency

No

Should always be set to “USD”. Does not load.

money cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailItem/GrossAmount/Money

No

The line item gross amount being invoiced on the line item.

currency cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailItem/NetAmount/Money@currency

No

Should always be set to “USD”.

money cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailItem/NetAmount/Money

Yes

The line item net amount being invoiced on the line item.

lineNumber cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailItemReference@lineNumber

Yes

The line number of the purchase order line being invoiced.

SupplierPartID cXML/Request/InvoiceDetailRequest/ InvoiceDetailOrder/InvoiceDetailItemReference/ItemId/SupplierPartID

No

Line Item Part Number from PunchOutOrder…