GSA (General Services Administration)
/
Purchase Order Acknowledgment (GSA ADV)
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from GSA (General Services Administration). Contact GSA (General Services Administration) for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
GSA (General Services Administration) logo

X12 855 Purchase Order Acknowledgment (GSA ADV)

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/gsa/purchase-order-acknowledgment-gsa-adv/01HH10KJRMPYH67KNY54FSWZWF
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BAK
020
Beginning Segment for Purchase Order Acknowledgment
Max use 1
Required
N1 Loop
summary
CTT Loop
SE
030
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

PR
Purchase Order Acknowledgement (855)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
855
Purchase Order Acknowledgment
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BAK
020
Heading > BAK

Beginning Segment for Purchase Order Acknowledgment

RequiredMax use 1

To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates

Example
BAK-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original

Use to indicate an original transmission of an 855 transaction set.

07
Duplicate

Use to indicate a retransmission of a previously transmitted 855 transaction set.

BAK-02
587
Acknowledgment Type
Required
Identifier (ID)

Code specifying the type of acknowledgment

AC
Acknowledge - With Detail and Change

Use to indicate an order is being acknowledged with detail and changes. The changes may include the rejection of one or more line items. Use this code only if BEG07 in the applicable 850 transaction set was code AC.

AK
Acknowledge - No Detail or Change

Use to indicate that receipt of the order is being acknowledged without detail or change. Use this code only when BEG07 in the applicable 850 transaction set was code AK.

AT
Accepted

Use to indicate bilateral acceptance of a purchase order or acceptance of a delivery order exceeding the delivery order limitations. Use this code only if BEG07 in the applicable 850 transaction set was code AT.

RJ
Rejected - No Detail
  1. Use to indicate the rejection of an entire order. If BEG07 in the applicable 850 transaction set was code AK or AT, the entire order must be acknowledged, accepted, or rejected. If BEG07 in the applicable 850 transaction set was code AC, the entire order may be rejected.

  2. If BEG07 in the applicable 850 transaction set was code AC and the order is being accepted but one or more line items are being rejected, do not use code RJ; use code AC.

BAK-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Use to identify the award instrument number to which this transaction set applies. Cite the number from BEG03 of the applicable 850 transaction set. Contract number placed here.

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BAK04 is the date assigned by the purchaser to purchase order.
Usage notes

Use to identify the effective date of the award instrument to which this transaction set applies. Cite the number from BEG05 of the applicable 850 transaction set.

BAK-05
328
Release Number
Required
String (AN)
Min 1Max 30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

Usage notes

Use to identify the number of a release, call or delivery order against a basic award instrument to which this transaction set applies. Cite the number from BEG04 of the applicable 850 transaction set. Purchase Order/delivery order placed here.

BAK-06
326
Request Reference Number
Optional
String (AN)
Min 1Max 45

Reference number or RFQ number to use to identify a particular transaction set and query (additional reference number or description which can be used with contract number)

Usage notes

This Reference Number should be what goes out on the Purchase Order (REF with FI qualifier)

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BAK09 is the date assigned by the sender to the acknowledgment.
Usage notes

Use to identify the date this 855 transaction set was transmitted.

N1 Loop
OptionalMax 200
N1
300
Heading > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

Address information shall be transmitted using code values contained in a combination of the N101, N103, and N104 data elements. Transmit the same code values as contained in the applicable 850 transaction set. At least 2 iterations of this segment are REQUIRED with N101 citing code BY and SE.

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BY
Buying Party (Purchaser)
SE
Selling Party
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

1
D-U-N-S Number, Dun & Bradstreet

Use of the DUNS or DUNS+4 number is preferred over other codes to identify an entity.

9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix

Use of the DUNS or DUNS+4 number is preferred over other codes to identify an entity.

10
Department of Defense Activity Address Code (DODAAC)

Use to indicate either a Department of Defense Activity Address Code or a Civilian Agency Activity Address Code.

N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
N1 Loop end
Heading end

Detail

PO1 Loop
OptionalMax 100000
PO1
010
Detail > PO1 Loop > PO1

Baseline Item Data

RequiredMax use 1

To specify basic and most frequently used line item data

  • PO102 is required.
Usage notes
  1. Use this segment when BAK02 is code AC to identify a rejected line item or to identify the corrected line item information when it differs from that information contained in the applicable 850 transaction set.

  2. When one or more line items are rejected, identify the line items in this segment and cite the appropriate code in ACK01.

Example
If Unit or Basis for Measurement Code (PO1-03) is present, then Quantity Ordered (PO1-02) is required
If either Product/Service ID Qualifier (PO1-06) or Product/Service ID (PO1-07) is present, then the other is required
If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other is required
If either Product/Service ID Qualifier (PO1-10) or Product/Service ID (PO1-11) is present, then the other is required
If either Product/Service ID Qualifier (PO1-12) or Product/Service ID (PO1-13) is present, then the other is required
If either Product/Service ID Qualifier (PO1-14) or Product/Service ID (PO1-15) is present, then the other is required
If either Product/Service ID Qualifier (PO1-16) or Product/Service ID (PO1-17) is present, then the other is required
PO1-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • PO101 is the line item identification.
Usage notes

Cite the same PO101 line item number as contained in the 850 transaction set.

PO1-02
330
Quantity Ordered
Optional
Decimal number (R)
Min 1Max 15

Quantity ordered

Usage notes

Use to identify the quantity accepted by the selling party. If the total quantity ordered is accepted, cite the quantity that was shown in the 850 transaction set.

PO1-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

Usage notes

Use to identify the unit of measure applicable to the quantity cited in PO102. If the unit of measure that was shown in the 850 transaction set is accepted, cite that unit of measure.

PO1-04
212
Unit Price
Optional
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

PO1-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Usage notes
  1. Cite the appropriate code to identify the corrected line item information when different from that contained in the 850 transaction set.

  2. PO106/PO107 is optional for use if the line item was correctly identified in the 850 transaction set; the PO101 is adequate identification in this circumstance.

  3. Use the LIN segment for the identification of manufacturers and associated part numbers.

F1
Catalog Number
FS
National Stock Number
HI
HIBC (Health Care Industry Bar Code)
IB
International Standard Book Number (ISBN)
MF
Manufacturer
MG
Manufacturer's Part Number
N4
National Drug Code in 5-4-2 Format
ND
National Drug Code (NDC)
PD
Part Number Description

Use to indicate the noun nomenclature of the item.

PQ
Product ID Attribute Code

Use to indicate the UII Unique Item Identifier.

SV
Service Rendered
UK
U.P.C./EAN Shipping Container Code (1-2-5-5-1)
UX
Universal Product Number
VC
Vendor's (Seller's) Catalog Number
VP
Vendor's (Seller's) Part Number
ZZ
Mutually Defined
PO1-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

PO1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

PO1-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-12
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

PO1-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-14
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

PO1-15
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-16
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

PO1-17
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK Loop
OptionalMax 104
ACK
270
Detail > PO1 Loop > ACK Loop > ACK

Line Item Acknowledgment

RequiredMax use 1

To acknowledge the ordered quantities and specify the ready date for a specific line item

Usage notes

Use this segment when BAK02 is code AC to provide information related to the line item identified in PO101. If a line item is rejected, cite the appropriate code in ACK01.

Example
If either Quantity (ACK-02) or Unit or Basis for Measurement Code (ACK-03) is present, then the other is required
If Date/Time Qualifier (ACK-04) is present, then Date (ACK-05) is required
ACK-01
668
Line Item Status Code
Required
Identifier (ID)

Code specifying the action taken by the seller on a line item requested by the buyer

AA
Item Accepted – Order Forwarded to alternate supplier location. Item shipped to GSA Depot Burlington
AC
Item Accepted and Shipped

Cite code 011 in ACK04 and the actual shipping date in ACK05.

AR
Item Accepted and released for shipment. Item shipped to Tracy, CA
DR
Item Accepted. Item shipped to GSA Depot Sharpe
IA
Item Accepted

Item Shipped

IB
Item Backordered

Cite code 068 in ACK04 and the projected shipping date in ACK05.Backordered

IC
Item Accepted. Items shipped to New Cumberland, PA
ID
Item Deleted
IP
Item Accepted - Price Changed
IQ
Item Accepted - Quantity Changed
IR
Item Rejected

Use this code only when a codes R1-R8 do not apply. Item cancelled.

IS
Item Accepted - Substitution Made
R1
Item Rejected, Not a Contract Item
R2
Item Rejected, Invalid Item Product Number
R3
Item Rejected, Invalid Unit of Issue
R4
Item Rejected, Contract Item not Available
R5
Item Rejected, Reorder Item as a Just in Time (JIT) Order
R6
Item Rejected, Reorder Item as an Extended Delivery Order (EDO)
R7
Item Rejected, Reorder Item as a Drop Shipment
R8
Item Rejected, Reorder Item as a Surge Order
SP
Item Accepted. Item has been reshipped.
ACK-02
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

ACK-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

ACK-04
374
Date/Time Qualifier
Optional
Identifier (ID)

Code specifying type of date or time, or both date and time

011
Shipped
068
Current Schedule Ship
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

ACK Loop end
N9 Loop
OptionalMax 1000
N9
350
Detail > PO1 Loop > N9 Loop > N9

Reference Identification

RequiredMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Usage notes

This segment is used only within the Department of Defense Prime Vendor program.

Example
At least one of Reference Identification (N9-02) or Free-form Description (N9-03) is required
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

2I
Tracking Number
IL
Internal Order Number– Requisition Number
RQ
Purchase Requisition Number
TG
Transportation Control Number (TCN)
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

Tracking number

N9-03
369
Free-form Description
Optional
String (AN)
Min 1Max 45

Free-form descriptive text

Usage notes

Mode of transportation/carrier name

N9 Loop end
PO1 Loop end
Detail end

Summary

CTT Loop
RequiredMax 1
CTT
010
Summary > CTT Loop > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

  • The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

Usage notes

Use to identify the total number of PO1 segments contained in this transaction set.

CTT-02
347
Hash Total
Optional
Decimal number (R)
Min 1Max 10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

## Example:
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.

1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.

Usage notes

Use to identify the sum of the quantities (PO102) for all PO1 segments.

CTT Loop end
SE
030
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample

ISA*00* *00* *01*0001111119 *ZZ*GSAADV *190417*0452*U*00401*000000011*0*T*>
GS*PR*0001111119*GSAADV*20190417*0452*11*X*004010
ST*855*0011
BAK*00*AC*47QZWA99D000M*20190306*47QDCC19M999Z*26291999-180000000***20190307
N1*BY*DEPARTMENT OF VETERANS AFFAIRS*1*012966339
N1*SE*ABC TECH*1*000111119
PO1*1*1*PK*1.63**MG*UNVZZ70000***VP*UNVZZ70011*MF*OFFICE PRODUCTS INC
ACK*IA*1*PK*011*20190403
N9*2I*1122334455*FEDEX Tracking number
PO1*2*1*PK*3.27**MG*UNV99999***VP*UNV999990*MF*OFFICE PRODUCTS INC
ACK*IB*1*PK*068*20190403
PO1*3*1*BX*28.39**MG*UNV00005***VP*UNV00005*MF*MANUFACTURING CO.
ACK*IR*1*BX
PO1*4*1*BX*28.39**MG*UNV00055***VP*UNV00055*MF*MANUFACTURING CO.
ACK*IR*1*BX
CTT*4*4
SE*15*0011
GE*1*11
IEA*1*000000011

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.