Punchout Vendor Guide Implementing G2B Punchout ~21.docx

Vendor Guide for Implementing G2B PunchOuts in BidBuy

Page 3 of 22 Edited On:

Vendor Guide - Implementing G2B Punchouts PHI Approved Copy.docx

Introduction The State of Illinois eProcurement Solution, BidBuy, supports government to business (G2B) integrations with direct Vendors or third-party trading partners, called “PunchOuts”.

A PunchOut Catalog allows buyers to easily shop and buy from your website catalog. Vendors who complete a G2B PunchOut integration can create customized product catalogs reflecting contract specific items and pricing that are easily accessible to the State’s eProcurement system.

Items purchased from these PunchOut Catalogs and the associated Purchase Orders are submitted directly to the G2B enabled Vendor site using industry standard XML protocols. Purchase Orders submitted in this fashion usually process directly through the Vendor’s order entry system for fulfillment, saving hours or days in processing time and improving product shipping times.

Both State users and Vendors utilizing BidBuy for G2B integrations benefit from:

· Customer specific product catalogs maintained in one location

· Electronic management of procurement transactions

· Reduced approval times

· Increased data accuracy

This document provides guidelines for how the State will work with Vendors to manage the implementation of a new PunchOut. Please note that this guide assumes that the PunchOut being implemented is a standard implementation not requiring customization within BidBuy.

In general, to ensure optimal system integration, it is advised that the Vendor utilizes both a PunchOut Catalog and an electronic ordering solution.

The State can configure the PunchOut, so long as the Vendor conforms to the BidBuy XML standards.

Overview of BidBuy PunchOut Implementation Process The following steps will be completed by the State and/or G2B Vendor with cooperation from all parties involved, including technical and functional resources.

1. When a PunchOut is a requirement of the contract or deemed advantageous to the State, the State will initiate discussions with the vendor’s business and technical resources to discuss timelines, expectations, and business requirements.

2. Information will be required from the Vendor to initiation communication between BidBuy and the Vendor’s PunchOut Catalog. The Vendor’s PunchOut will first be initiated within BidBuy’s test environment. The Vendor must comply with the State’s PunchOut requirements for BidBuy.

To allow for test transactions between BidBuy and the Vendor’s Product Catalog, the State will create an active G2B Master Blanket Purchase Order for the contract, and perform any additional technical configurations required by BidBuy.

The following information will be required from the Vendor for BidBuy to communicate with the Vendor’s Product Catalog:

a. PunchOut URL

i. To ensure secure communications, this URL is required to utilize https.

ii. This URL will be required to consume xml transactions from BidBuy in cXMLv2 format.

iii. The Check Out or Cart information returned from this URL to BidBuy is required to be in cXMLv2 format.

b. Purchase Order URL

i. To ensure secure communications, this URL is required to utilize https.

i. This URL will be required to consume xml transactions from BidBuy in cXMLv2 format.

ii. Following the receipt of each Purchase Order, an acknowledgement xml transaction, in cXMLv2 format, is required to be sent to BidBuy.

c. Authentication Type:

i. DUNS Number

ii. Network ID

iii. Sitewide

d. User ID:

i. This will be the user name used to connect to both URL’s, PunchOut and Purchase Order URL, provided by the Vendor, and will be specific to the type of authentication selected in 2c above.

e. Password:

i. This will the password used for the user in 2d above. To avoid service disruptions of the G2B PunchOut service, the Vendor will need to notify the State when this password changes.

3. Test transactions will be performed by the State to verify:

a. All communications between BidBuy and the Vendor’s Product Catalog are working properly.

i. If errors are encountered, the State will retrieve the PunchOut details and G2B XML and collaborate with the Vendor’s business and technical resources to troubleshoot.

ii. Firewall rules allow outbound and inbound traffic from the Vendor’s domain to the BidBuy servers. These rules may need adjusted to allow communications to occur.

iii. The requirement for secure communications, https, may cause SSL certificates to be required. These can be uploaded at request, and will be identified during troubleshooting.

b. PunchOut processes are understood by the Vendor’s business and technical resources.

c. Only approved items are available for each contract and pricing is accurate.

4. Once testing has been accepted by the State and the Vendor’s business and technical resources, the State will configure the BidBuy Production environment with the necessary information to communicate with the Vendor’s PunchOut Catalog, and create an active G2B Master Blanket Purchase Order for the Vendor’s contract.

5. Vendor Setup Notes

a. If required, the State will supply the Vendor with a list of all addresses that may need to be associated with accounts for proper billing and shipping setup within the Vendor’s system. If integration is configured using these identifiers, the following items should be noted:

i. Address ID will be included in this list and must be maintained, as it is the identifier passed within the interface to identify each address.

ii. Updates to addresses within BidBuy will be sent to the Vendor on a weekly report.

1. To ensure proper billing and pricing of items ordered through PunchOuts, it will be required to ensure these address ID associates are kept up to date within the Vendor’s system.

b. Purchase Orders completed without the use of a PCard number will default the purchase terms to “terms” on the order. This requires the State to ensure the Vendor is configured with the correct conditions for “terms” orders during the integration process.

c. If issues are encountered while attempting to make the PunchOut connection, Vendors may need to ensure their PunchOut URL is set to disable the XSS filter in user’s browsers.

d. If a PCard is set up for payments, for security purposes, BidBuy encrypts the credit card number, expiration date, and the card holder name.

6. After the Vendor is live in the BidBuy Production environment, the State, along with the Vendor’s business and technical resources, will again verify the items outlined in number 3 above, to ensure all data is visible and transmitting as expected in the production environment.

Appendix A PUNCHOUTSETUPREQUEST Sample BidBuy sends a request to the Vendor’s PunchOut Catalog to initiate a connection with the Vendor’s website and to route the connection to the appropriate PunchOut Catalog to allow users to search for items related to the Master Blanket Purchase Order and add them to the Vendor’s online shopping cart.

In the below example, BidBuy is using NetworkId authentication, and the Vendor PunchOut Catalog has been configured with a DUNS ID Number. (Other methods are possible)

@domain

@deploymentMode

@operation

BuyerCookie

BrowserFormPost/URL

Contact

ShipTo

SelectedItem

<cXML payloadID="1253832687927.1966498874653534823" timestamp="2009-09-24T17:51:27-0500"> <Header> <From> <Credential domain="DUNS"> <Identity>153531108</Identity> </Credential> </From> <To> <Credential domain="NetworkId"> <Identity>ctybal050509-T</Identity> </Credential> </To> <Sender> <Credential domain="DUNS"> <Identity>153531108</Identity> <SharedSecret></SharedSecret> </Credential> <UserAgent></UserAgent> </Sender> </Header> <Request> <PunchOutSetupRequest operation="create" deploymentMode="test"> <BuyerCookie>1253832687927.1966498874653534823</BuyerCookie> <Extrinsic name="User">Administrator System</Extrinsic> <Extrinsic name="Identity">ctybal050509-T</Extrinsic> <BrowserFormPost>

<URL>

https://arizona.BidBuy.com/bso82ora/g2b/receiver.sdo?param=__9000000085__create__DOCID__SPO__SPO__3__3__AGENCY10-0000211&amp;user=BIDBUY&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> </ItemID> </SelectedItem> </PunchOutSetupRequest> </Request> </cXML>

Appendix B PUNCHOUTSETUPRESPONSE Message Sample After the Vendor’s website has successfully authenticated the PunchOutSetupRequest, it will respond with a PunchOutSetupResponse similar to the example below.

This response will redirect the user’s browsing session to the item catalog appropriate for the Master Blanket Purchase Order.

<PunchOutSetupResponse>

</PunchOutSetupResponse>

Appendix C PUNCHOUTORDERMESSAGE Vendor Response Sample After shopping within the Vendor’s PunchOut Catalog, the information about items in the user’s cart will be returned to BidBuy using a PunchOutOrderMessage. These details in BidBuy will create an in progress Requisition to be routed for approvals before converting to a Purchase Order.

In the below example, BidBuy is using NetworkId authentication, and the Vendor PunchOut Catalog has been configured with a DUNS ID Number. (Other methods are possible) cXML Segment cXML Element

Validation / Notes

Header

Sender/Credential/Identity User Name - Unique user name set up by the Vendor for BidBuy to use to associate the State’s Master Blanket Purchase Order to the correct PunchOut Catalog within their purchasing system.

PunchOutOrderMessageHeader/ @deployment Supported values are “test” or “production”.

PunchOutOrderMessageHeader/ @operationAllowed Supported values are “edit”.

PunchOutOrderMessageHeader/ Total/Money/@currency Supported values are ISO currency codes.

PunchOutOrderMessageHeader/ Total/Money Total value of Cart. Numeric values only.

PunchOutOrderMessageHeader/ Shipping/Money/@currency Supported values are ISO currency codes.

PunchOutOrderMessageHeader/ Shipping/Money Total of shipping charges for the order. Numeric values only.

Message

PunchOutOrderMessage/ PunchOutOrderMessageHeader/ Shipping/Money

Description of shipping charges included for the transactions.

PunchOutOrderMessageHeader/ Tax/Money/@currency Supported values are ISO currency codes.

PunchOutOrderMessageHeader/ Tax/Money Total of tax charges for the order. Numeric values only.

PunchOutOrderMessageHeader/ Tax/Description Description of tax charges included for the transactions.

@quantity Quantity of line item ordered.

@lineNumber Line number in the shopping cart.

ItemID/SupplierPartID Vendor part number used in their order entry system.

ItemID/SupplierPartAuxillaryID Vendor cart id number.

ItemDetail/UnitPrice/Money/@currency Supported values are ISO currency codes.

ItemDetail/UnitPrice/Money Unit Cost of Line Item. Numeric values only.

ItemDetail/Description Description of Line Item.

ItemDetail/UnitOfMeasure Unit of measure for purchased line item.

ItemDetail/Classification/@domain Configured value is “UNSPSC”

ItemDetail/Classification Commodity code for the selected item.

ItemDetail/ManufacturerPartID Manufacturer part number.

ItemDetail/ManufacturerName Manufacturer name.

Shipping/Money/@currency Supported values are ISO currency codes.

Shipping/Money Shipping charges for the line item.

Shipping/Description Description of shipping charges for the line item.

Tax/Money/@currency Supported values are ISO currency codes.

Tax/Money Tax charges for the line item.

Tax/Description Description of tax charges for the line item.

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

<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="DUNS"> <Identity>153531108</Identity> <SharedSecret></SharedSecret> </Credential> <UserAgent></UserAgent> </Sender> </Header> <Message> <PunchOutOrderMessage> <BuyerCookie>1253832687927.1966498874653534823</BuyerCookie> <PunchOutOrderMessageHeader operationAllowed="edit" deploymentMode="test"> <Total> <Money currency="USD">101.40</Money> </Total> <Shipping> <Money currency="USD">17.63</Money> <Description xml:lang="en">standard shipping charges</Description> </Shipping> <Tax> <Money currency="USD">5.85</Money> <Description xml:lang="en">tax charges</Description> </Tax> </PunchOutOrderMessageHeader> <ItemIn quantity="2" lineNumber="1"> <ItemID> <SupplierPartID>4UG98</SupplierPartID> <SupplierPartAuxiliaryID>WWG4UG98</SupplierPartAuxiliaryID> </ItemID> <ItemDetail> <UnitPrice> <Money currency="USD">32.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>CS</UnitOfMeasure> <Classification domain="UNSPSC">31201606</Classification> <ManufacturerPartID>GE012A</ManufacturerPartID> <ManufacturerName>GENERAL ELECTRIC</ManufacturerName> </ItemDetail> <Shipping> <Money currency="USD">12.95</Money> <Description xml:lang="en">standard shipping charges</Description> </Shipping> <Tax> <Money currency="USD">4.95</Money> <Description xml:lang="en">tax charges</Description> </Tax> </ItemIn> <ItemIn quantity="6" lineNumber="2"> <ItemID> <SupplierPartID>348037</SupplierPartID> <SupplierPartAuxiliaryID>WWG4UG98</SupplierPartAuxiliaryID> </ItemID> <ItemDetail> <UnitPrice> <Money currency="USD">1.99</Money> </UnitPrice> <Description xml:lang="en-US">Copy Paper, 20 Lb, 104 Brightness, 8 1/2quot x 11quot, Individual Reams </Description> <UnitOfMeasure>EA</UnitOfMeasure> <Classification domain="UNSPSC">31204879</Classification> <ManufacturerPartID>PP0194</ManufacturerPartID> <ManufacturerName>VALUE PAPER</ManufacturerName> </ItemDetail> <Shipping> <Money currency="USD">4.68</Money> <Description xml:lang="en">standard shipping charges</Description> </Shipping> <Tax> <Money currency="USD">0.90</Money> <Description xml:lang="en">tax charges</Description> </Tax> </ItemIn> </PunchOutOrderMessage> </Message>

Appendix D Purchase Order Sample Once the BidBuy Requisition has received all required approvals, upon being converted to a Purchase Order, it is then sent back to the Vendor’s purchasing website.

In the below example, BidBuy is using NetworkId authentication, and the Vendor PunchOut Catalog has been configured with a DUNS ID Number. (Other methods are possible)

OrderRequestHeader/ @deploymentMode Configured values are “test” or “production”.

OrderRequestHeader/ @orderID Purchase Order Number.

OrderRequestHeader/ @orderDate Date Purchase Order was issued.

OrderRequestHeader/ @type Configured values are “New”.

OrderRequestHeader/Total/ Money/@currency Supported values are ISO currency codes.

OrderRequestHeader/Total/ Money Total value of the Purchase Order. Numeric values only.

OrderRequestHeader/ShipTo/ Address/@addressID Address ID from BidBuy to identify this physical address. If Vendors are in need of location specific pricing, these identifiers may need to be configured and kept synchronized within the Vendor’s billing and shipping systems.

OrderRequestHeader/ShipTo/ Address/Name Name of the organization receiving the shipment.

OrderRequestHeader/ShipTo/ Address/PostalAddress/DeliverTo Name of the individual receiving the shipment at the organization.

OrderRequestHeader/ShipTo/ Address/PostalAddress/Street Address line 1 of the ship to address.

OrderRequestHeader/ShipTo/ Address/PostalAddress/Street Address line 2 of the ship to address.

OrderRequestHeader/ShipTo/ Address/PostalAddress/City City of the ship to address.

OrderRequestHeader/ShipTo/ Address/PostalAddress/State State of the ship to address.

OrderRequestHeader/ShipTo/ Address/PostalAddress/PostalCode Zip code of the ship to address.

OrderRequestHeader/ShipTo/ Address/Phone/ TelephoneNumber/Number Phone number for the shipping address.

OrderRequestHeader/ShipTo/ Address/PostalAddress/ Country/@isoCountryCode Requires valid ISO country codes.

OrderRequestHeader/ShipTo/ Address/PostalAddress/ Country Name of the country for the shipping address.

OrderRequestHeader/ShipTo/ Address/Email Email address for the contact at the receiving location.

OrderRequestHeader/BillTo/ Address/Name Name of the organization to be billed for the order.

OrderRequestHeader/BillTo/ Address/PostalAddress/DeliverTo Name of individual to contact for billing concerns.

OrderRequestHeader/BillTo/ Address/PostalAddress/Street Bill To Street Address 1

OrderRequestHeader/BillTo/ Address/PostalAddress/Street Bill To Street Address 2

OrderRequestHeader/BillTo/ Address/PostalAddress/City Bill To City

OrderRequestHeader/BillTo/ Address/PostalAddress/State Bill To State

OrderRequestHeader/BillTo/ Address/PostalAddress/PostalCode Bill To Zip

OrderRequestHeader/BillTo/ Address/PostalAddress/ Country/@isoCountryCode Requires valid ISO country codes.

OrderRequestHeader/BillTo/ Address/PostalAddress/Country Name of the country the billing address is in.

OrderRequestHeader/BillTo/ Address/Phone/ TelephoneNumber/Number Bill To Phone

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

OrderRequestHeader/ Payment/@expiration Expiration Date: Format YYYYMM

OrderRequestHeader/ Payment/@name Card Holder Name

@quantity Line item quantity from PunchOutOrder Message.

@lineNumber Line number on Purchase Order.

ItemID/SupplierPartID Line Item Part Number from PunchOutOrder Message.

ItemID/SupplierPartAuxillaryID Line Item Cart ID from the PunchOutOrder Message.

ItemDetail/UnitPrice/Money/@currency Line item currency value from PunchOutOrder Message.

ItemDetail/UnitPrice/Money Line item Unit Price from PunchOutOrder Message.

ItemDetail/Description Line item description from PunchOutOrder Message.

ItemDetail/UnitOfMeasure Line item unit of measure from PunchOutOrder Message.

ItemDetail/Classification/@domain Configured value is “UNSPSC”

ItemDetail/Classification Line item commodity code from PunchOutOrder Message.

ItemDetail/ManufacturerPartID Line item manufacturer part number from PunchOutOrder Message.

ItemDetail/ManufacturerName Line item manufacturer name from PunchOutOrder Message.

ItemDetail/Extrinsic/@name Configured values are “Tax”, to be used for the line item tax charges, and “Freight”, to be used for the line item shipping charges.

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

<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></SharedSecret> </Credential> <UserAgent></UserAgent> </Sender> </Header> <Request> <OrderRequest> <OrderRequestHeader orderDate="2009-09-24T17:55:16-0500" orderID="AGENCY10-0000211000001" type="new" deploymentMode="test"> <Total> <Money currency="USD">101.40</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>JClark@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="7"> <Name xml:lang="en">State Procurement Office – Accounts Payable</Name> <PostalAddress> <DeliverTo>Sally Jones, Senior Accountant</DeliverTo> <Street>1200 N. 18th Street</Street> <Street>Suite 800</Street> <City>Phoenix</City> <State>AZ</State> <PostalCode>85007</PostalCode> <Country isoCountryCode="US">United States</Country> </PostalAddress> <Email>spoap@azdoa.gov</Email> <Phone name="work"> <TelephoneNumber> <CountryCode isoCountryCode="US">1</CountryCode> <AreaOrCityCode>602</AreaOrCityCode> <Number>5425598</Number> </TelephoneNumber> </Phone> </Address> </BillTo> <Payment> <PCard expiration="200901" name="Edward Clark"

</OrderRequestHeader> <ItemOut lineNumber="1" quantity="2"> <ItemID> <SupplierPartID>4UG98</SupplierPartID> <SupplierPartAuxiliaryID>WWG4UG98</SupplierPartAuxiliaryID> </ItemID> <ItemDetail> <UnitPrice> <Money currency="USD">32.99</Money> </UnitPrice> <Description xml:lang="en">Indoor/Outdoor Caulk, Container Size 10.1 Ounces, Style Window/Door 100% Silicone Rubber Sealant, Color Clear, Watertight, Flexible </Description> <UnitOfMeasure>CS</UnitOfMeasure> <Classification domain="UNSPSC">31201606</Classification> <ManufacturerPartID>GE012A</ManufacturerPartID> <ManufacturerName xml:lang="en">GENERAL ELECTRIC</ManufacturerName> <Extrinsic name="Tax">4.95</Extrinsic> <Extrinsic name="Freight">12.95</Extrinsic>

<ItemID> <SupplierPartID>348037</SupplierPartID> <SupplierPartAuxiliaryID>WWG4UG98</SupplierPartAuxiliaryID> </ItemID> <ItemDetail> <UnitPrice> <Money currency="USD">1.99</Money> </UnitPrice> <Description xml:lang="en">Copy Paper, 20 Lb, 104 Brightness, 8 1/2quot x 11quot, Individual Reams </Description> <UnitOfMeasure>EA</UnitOfMeasure> <Classification domain="UNSPSC">31204879</Classification> <ManufacturerPartID>PP0194</ManufacturerPartID> <ManufacturerName xml:lang="en">VALUE PAPER</ManufacturerName> <Extrinsic name="Tax">0.90</Extrinsic> <Extrinsic name="Freight">4.68</Extrinsic>

Appendix E Purchase Order Acknowledgement Sample After the Vendor’s purchasing system receives the Purchase Order from BidBuy, a response should be returned to BidBuy indicating acceptance or rejection of the Purchase Order.

Acknowledgement (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> Acknowledgement (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">Details of error message should be here.</Status> </Response>

Appendix F

TERM DEFINITIONS

PunchOut – The act of successfully accessing an authenticated G2B PunchOut Catalog (the Vendor’s PunchOut URL provided during configuration) hosted on the Vendor’s website from BidBuy.

PunchOut Order Response – A response from the Vendor’s PunchOut Catalog indicating authentication was successful. This response will contain the URL to redirect the user’s session to for Vendor item shopping and selection.

PunchOut Order Message - Contains the contents of the shopping cart created from the Vendor’s PunchOut catalog. This document is sent back to the Vendor’s Purchase Order URL provided during configuration.

PunchOut Order Acknowledgement - An electronic acknowledgement immediately sent from the Vendor’s Purchase Order URL back to BidBuy after the Vendor has received an electronic Purchase Order. This is a synchronous response that contains a status code and a description.

· Status Code 200

· PO Successful

· Response includes PO Number

· The Vendor will send an email notification to the email address provided on the Purchase Order

· Body and subject of the email will indicate the PO was received by the Vendor and identify the PO Number and time the document was received

· The State will approve this email communication

· Status Code 500

· PO failed due to one or more issues

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