X12 212 Motor Carrier Delivery Trailer Manifest
This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Delivery Trailer Manifest Transaction Set (212) for use within the context of an Electronic Data Interchange (EDI) environment.
This transaction set can be used to allow motor carriers to provide consignees or other interested parties with the contents of a trailer, containing multiple shipments, that has been tendered for delivery. It is not to be used to provide the recipient with data relative to a full truckload shipment.
- ~ Segment
- * Element
- > Component
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code identifying the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- TM
- Motor Carrier Delivery Trailer Manifest (212)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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)
Assigned number originated and maintained by the sender
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
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
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 212
- Motor Carrier Delivery Trailer Manifest
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Motor Carrier Delivery Trailer Manifest
To transmit identifying numbers and other basic data relating to the Motor Carrier Delivery Trailer Manifest Transaction Set
Example Data: ATASCACManifestID*20100624~
Standard Carrier Alpha Code
- ATA01 is the Standard Carrier Alpha Code (SCAC) of the carrier that is delivering the trailer.
This should contain the NMFTA registered SCAC code of the carrier who is ultimately responsible for the load and will be billing the customer for the shipment.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- ATA02 is the delivery trailer manifest number assigned by the carrier.
This element should contain the Delivery Trailer Manifest ID that has been assigned by the carrier.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- ATA03 is the date that the delivery trailer manifest was created.
This element should contain the date the carrier created the manifest.
Set Purpose
To allow for positive identification of transaction set purpose
A Replace Manifest/05 that is current and complete, should be sent if freight is added or removed from the trailer after the original manifest has been transmitted to Best Buy. The original manifest ID must be used when the replace manifest is sent.
A Manifest should be cancelled only if the trailer will no longer be arriving at Best Buy for any reason. The original Manifest ID must be transmitted in the document.
Example Data: B2A*00~
Code identifying purpose of transaction set
- 00
- Original
- 01
- Cancellation
- 05
- Replace
This Loop should contain the information for the Best Buy location that the carrier is attempting to deliver the trailer to.
Name
To identify a party by type of organization, name, and code
- Loop 0100 provides the location where the carrier will deliver the trailer.
This segment should contain the information for the Best Buy location that the carrier is attempting to deliver the trailer to.
Example Data: N1STBest Buy RDC709470~
Code identifying an organizational entity, a physical location, property or an individual
This element should always have the qualifier of "ST" used in it to indicate that this is a Ship To Location ID.
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
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.
This element should contain the Unique Location ID that Best Buy has assigned to the location that the carrier is attempting to deliver the trailer to.
There should only be one iteration of the Shipment Status Details Loop/150. It should contain information about the entire delivery, including carrier and trailer information.
Shipment Status Details
To specify the status of a shipment, the reason for that status, the date and time of the status and the date and time of any appointments scheduled.
- The AT7 segment provides the status of all of the shipments on the trailer.
This segment should contain the date and time that the items listed in the manifest are ready to be delivered.
Example Data: AT7AVNS**201006241000*LT~
Code indicating the status of a shipment
- If AT701 is present, AT705 is the date the status occurred. If AT703 is present, AT705 is a date related to an appointment.
- If AT701 is present, AT706 is the time of the status. If AT703 is present, AT706 is the time of the appointment.
This status code should always be "AV" to indicate that the trailer is Available for Delivery.
- AV
- Available for Delivery
Code indicating the reason a shipment status or appointment reason was transmitted
- NS
- Normal Status
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
The date that the event indicated in the AT701 & AT702, occurred should be sent here.
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)
The time that the event indicated in the AT701 & AT702 , occurred should be sent here.
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
- If AT707 is not present then AT706 represents local time of the status.
The time zone code that the event indicated in the AT701 & AT702, occurred should be sent here. Best Buy expects this to be "LT".
- LT
- Local Time
There should be only one iteration of the Equipment or Container and Type Loop/160. It should contain information about the trailer and seal numbers.
Equipment or Container Owner and Type
To specify the owner, the identification number assigned by that owner, and the type of equipment
Example Data: MS2SCAC9876544321*TL~
Standard Carrier Alpha Code
This field must contain the NMFTA registered SCAC of the carrier who is physically moving the shipment(s) and owns the trailer.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
This field must contain the actual ID of the trailer or container that contains the shipment(s) that are being moved.
Code identifying type of equipment used for shipment
- MS203 identifies the type for the equipment specified in MS202.
This field should contain the qualifier that best describes the physical trailer or container length and type attributes.
Seal Numbers
To record seal numbers used and the organization that applied the seals
Any known seal number given to the carrier by the shipper should be listed here and the parties identified who applied the seal. If the seal is broken by another party such as Customs (DOT), the new seal ID should be sent on an update with "CM" qualifier (if it was Customs) sent in the M705.
Example Data: M7Seal1***CM~
Detail
Each iteration of Loop 200 should contain information about a single LTL shipment that a single shipper is shipping to the Best Buy location identified in Loop 100, segment N1 of the header. The details of each individual order within the LTL shipment should be contained in Loop 210 and the details of the shipper of each order should be contained in Loop 220.
Assigned Number
To reference a line number in a transaction set
- Loop 0200 provides the specific details concerning all of the shipments included in the manifest. There will be one iteration of loop 0200 for each shipment contained in the manifest. The most common way to identify the shipments is by the PRO number assigned by the carrier.
Example Data: LX*1~
Number assigned for differentiation within a transaction set
This is the sequential number assigned for differentiation of each iteration of the LX/200 Loop. It should start with 1 and be incremented by 1 for each iteration.
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
There must be at least 2 iterations of the L11 segment in each LX loop. One must contain the Bill of lading and the other must contain the carrier PRO/Load/Tracking ID.
In cases where Best Buy is paying for the freight charges a third iteration of the L11 must be present as well. This third iteration must contain the Best Buy TMS load ID/Carrier Move Number. (The Best Buy TMS Load ID may also be referred to as the CID (Unique Consignee ID) or SID (Unique Shipper ID) from VICS).
Example Data:
Typical L11 where Best Buy is not paying the freight charges for a particular shipment.
L11BOLID12345BM~ - indicates the Bill of Lading ID
L11CarrierPROID123CN~ - indicates the Carrier PRO/Load/Tracking ID
Typical L11 where Best Buy is paying the freight charges for a particular shipment.
L11BOLID54321BM~ - indicates the Bill of Lading ID
L11CarrierPROID321CN~ indicates the Carrier PRO/Load/Tracking ID
L111234567BN~ - indicates the Best Buy TMS Load/Carrier Move ID.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
If the value in L1102 is "BN", the value to be entered in this L1101 element, can also be pulled from the 204 Load tender that Best Buy would have transmitted to the carrier. It is located in the B204 element of the 204.
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
This qualifier must be used to identify that the value sent in the L1101 is the Bill of lading ID.
- BN
- Booking Number
This qualifier must be used to identify that the information in the L1101 element is the Best Buy TMS Load/Carrier Move ID (also known as CID (Unique Consignee ID) or SID (Unique Shipper ID) from VICS or should be noted on the BOL in a special instructions field.).
This can also be pulled from the 204 Load tender that Best Buy would have transmitted to the carrier as well. It is located in the B204 element of the 204.
- CN
- Carrier's Reference Number (PRO/Invoice)
This qualifier must be used to identify that the information in the L1101 element is the Carrier's PRO/Load/Tracking ID for the shipment.
The values in this OID Loop/210 describe each individual order/shipment included in the shipment identified in the current iteration of the LX /200 Loop.
Order Identification Detail
To specify order identification detail
The OID segment will contain all reference numbers that drivers MUST HAVE in order to deliver the shipment to Best Buy.
Example Data: OIDBestBuyPOCTN245L*18000~
Identifying number for Purchase Order assigned by the orderer/purchaser
This element should contain the Best Buy Purchase Order or similar reference number (Transfer ID, RTV (Return to Vendor Authorization number) #, etc) that has been assigned to all or some of the logistical shipping/handling units on the shipment. If a 204 Load Tender was received for this shipment from Best Buy the OID02 element from the 204 Load Tender should be mapped here.
Code for packaging form of the lading quantity
This must be the qualifier that defines the type of Logistical shipping/handling units that are being moved on the shipment under the Reference ID indicated in the OID02. In all cases the qualifier must be "CTN". If a 204 Load Tender was received for this shipment from Best
Buy the OID04 element from the 204 Load Tender can be mapped here.
- CTN
- Carton
Numeric value of quantity
This is the actual numerical quantity of the Logistical shipping/handling units being moved on the Shipment. If Best Buy has provided a 204 Load Tender for this shipment then the OID05 from the 204 Load Tender should be mapped here.
Code specifying the weight unit
This should be the qualifier that defines the type of weight units used for the Logistical shipping/handling units that are being moved on the shipment under the Reference ID indicated in the OID02. In almost all cases the qualifier should be "L" for Pounds or "K" for kilograms. If Best Buy has provided a 204 Load Tender for this shipment then the OID06 from the 204 Load Tender should be mapped here.
- K
- Kilograms
- L
- Pounds
Numeric value of weight
This is the actual numerical weight of the Logistical shipping/handling units being moved on the Shipment. If Best Buy has provided a 204 Load Tender for this shipment then the OID07 from the 204 Load Tender should be mapped here.
The values in this Name loop/220 identify the shipper of the shipment identified in the current iteration of the LX loop/200. Since there can be only one shipper of a shipment, there must be only one iteration of this loop.
Name
To identify a party by type of organization, name, and code
- Loop 0220 shall only be used to provide the identification of the shipper if the carrier has not provided that information in a previous shipment status message.
This segment identifies the shipper of the shipment identified in the current iteration of the LX 200/loop.
Example Data: N1SFShippers name93Shippers unique Loc ID~
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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.
If the shipping charges are being paid by Best Buy and a 204 Load Tender was received by the carrier for the shipment indicated within the 212 Carrier Delivery Trailer Manifest message, the N104 element should be filled with the ID from the N104 Element of the corresponding EDI 204 Load Tender for the appropriate type of location type indicated in the N101. Otherwise the N104 element should contain the identifier assigned by the facility/location shipping the product.
Geographic Location
To specify the geographic place of the named party
This segment identifies the origin location of the shipment identified in the current iteration of the LX loop/200.
Example Data: N4CityNameSt99999USA~
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
This must be the name of the actual City that the location indicated in the N1 segment is located within/by.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
This must be the code of the state or province that the location indicated in the N1 segment is located within/by.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
This must be the postal code for the location that is indicated in the N1 segment is located within.
Code identifying the country
This must be the Country code for the location that is indicated in the N1 segment is located within.
The values in this Name loop/220 identify the shipper of the shipment identified in the current iteration of the LX loop/200. Since there can be only one shipper of a shipment, there must be only one iteration of this loop.
Name
To identify a party by type of organization, name, and code
- Loop 0220 shall only be used to provide the identification of the shipper if the carrier has not provided that information in a previous shipment status message.
This segment identifies the shipper of the shipment identified in the current iteration of the LX 200/loop.
Code identifying an organizational entity, a physical location, property or an individual
- SH
- Shipper
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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.
If the shipping charges are being paid by Best Buy and a 204 Load Tender was received by the carrier for the shipment indicated within the 212 Carrier Delivery Trailer Manifest message, the N104 element should be filled with the ID from the N104 Element of the corresponding EDI 204 Load Tender for the appropriate type of location type indicated in the N101. Otherwise the N104 element should contain the identifier assigned by the facility/location shipping the product.
Geographic Location
To specify the geographic place of the named party
This segment identifies the origin location of the shipment identified in the current iteration of the LX loop/200.
Example Data: N4CityNameSt99999USA~
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
This must be the name of the actual City that the location indicated in the N1 segment is located within/by.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
This must be the code of the state or province that the location indicated in the N1 segment is located within/by.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
This must be the postal code for the location that is indicated in the N1 segment is located within.
Code identifying the country
This must be the Country code for the location that is indicated in the N1 segment is located within.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
212 Cancel Manifest
ATA*SCAC*MANIFESTID1*20100902~
B2A*01~
N1*ST*BEST BUY RDC70*94*70~
AT7*AV*NS***20100902*1525*LT~
MS2*SCAC*9876544321*TL~
M7*Seal1****CM~
LX*1~
L11*BOLID12345*BM~
L11*CarrierPROID123*CN~
OID**ABCDEF**CTN*245*L*3800~
OID**LSEGAB**CTN*21*L*2162~
N1*SH*Shippers name*93*Shipper-01~
N4*Bellevue*WA*98004*US~
LX*2~
L11* CMV0000001*BM~
L11*CarrierPROID321*CN~
L11*CMV0000001*BN~
OID**FEDCBA**CTN*120*L*10570~
N1*SH*Widget Inc*93*WIDGE-01~
N4*Los Angeles*CA*90001*US~
LX*3~
L11*76543210987654321*BM~
L11*CarrierPROID789*CN~
OID**EMPLEH**CTN*154*L*1253~
OID**FEVAHI**CTN*336*L*2003~
OID**YLLANI**CTN*14*L*210~
OID**YMTSOL**CTN*56*L*3498~
OID**YTINAS**CTN*34*L*4206~
N1*SH*Arkham Mulysa Industries*93*Shipper-01~
N4*New York*NY*10011*US~
LX*4~
L11* CMV0000020*BM~
L11*CarrierPROID987*CN~
L11*CMV0000020*BN~
OID**AARRGH**CTN*5*L*1800~
OID**MEWOOO**CTN*17*L*980~
OID**WOLFIE**CTN*32*L*565~
N1*SH*Johns Gizmo’s*93*BBYLoadATID-01~
N4*Chicago*IL*60601*US~
LX*5~
L11*12345678901234567*BM~
L11*CarrierPROID684*CN~
OID**NAMTAB**CTN*24*L*1080~
OID**SNIBOR**CTN*45*L*800~
OID**SREKOJ**CTN*25*L*1000~
N1*SH*Wayne Enterprises*93*WAYNE01~
N4*New York*NY*10003*US~
SE*49*0001~
212 Original Manifest
ATA*SCAC*MANIFESTID1*20100902~
B2A*00~
N1*ST*BEST BUY RDC70*94*70~
AT7*AV*NS***20100902*1525*LT~
MS2*SCAC*9876544321*TL~
M7*Seal1****CM~
LX*1~
L11*BOLID12345*BM~
L11*CarrierPROID123*CN~
OID**ABCDEF**CTN*245*L*3800~
N1*SH*Shippers name*93*Shipper-01~
N4*Bellevue*WA*98004*US~
LX*2~
L11* CMV0000001*BM~
L11*CarrierPROID321*CN~
L11*CMV0000001*BN~
OID**FEDCBA**CTN*120*L*10570~
N1*SH*Widget Inc*93*WIDGE-01~
N4*Los Angeles*CA*90001*US~
LX*3~
L11*76543210987654321*BM~
L11*CarrierPROID789*CN~
OID**EMPLEH**CTN*154*L*1253~
OID**FEVAHI**CTN*336*L*2003~
OID**YLLANI**CTN*14*L*210~
OID**YMTSOL**CTN*56*L*3498~
OID**YTINAS**CTN*34*L*4206~
N1*SH*Arkham Mulysa Industries*93*Shipper-01~
N4*New York*NY*10011*US~
LX*4~
L11* CMV0000020*BM~
L11*CarrierPROID987*CN~
L11*CMV0000020*BN~
OID**AARRGH**CTN*5*L*1800~
OID**MEWOOO**CTN*17*L*980~
OID**WOLFIE**CTN*32*L*565~
OID**BAGELS**CTN*21*L*2162~
N1*SH*Johns Gizmo’s*93*BBYLoadATID-01~
N4*Chicago*IL*60601*US~
LX*5~
L11*12345678901234567*BM~
L11*CarrierPROID684*CN~
OID**NAMTAB**CTN*24*L*1080~
OID**SNIBOR**CTN*45*L*800~
OID**SREKOJ**CTN*25*L*1000~
N1*SH*Wayne Enterprises*93*WAYNE01~
N4*New York*NY*10003*US~
LX*6~
L11*281-0000001*BM~
L11*CarrierPROID264*CN~
L11*CMV0000281*BN~
OID**999999**CTN*15*L*120~
N1*SH*Best Buy Richfield*93*281~
N4*Richfield*MN*55423*US~
SE*56*0001~
212 Replacement Manifest
ATA*SCAC*MANIFESTID1*20100902~
B2A*05~
N1*ST*BEST BUY RDC70*94*70~
AT7*AV*NS***20100902*1525*LT~
MS2*SCAC*9876544321*TL~
M7*Seal1****CM~
LX*1~
L11*BOLID12345*BM~
L11*CarrierPROID123*CN~
OID**ABCDEF**CTN*245*L*3800~
OID**LSEGAB**CTN*21*L*2162~
N1*SH*Shippers name*93*Shipper-01~
N4*Bellevue*WA*98004*US~
LX*2~
L11* CMV0000001*BM~
L11*CarrierPROID321*CN~
L11*CMV0000001*BN~
OID**FEDCBA**CTN*120*L*10570~
N1*SH*Widget Inc*93*WIDGE-01~
N4*Los Angeles*CA*90001*US~
LX*3~
L11*76543210987654321*BM~
L11*CarrierPROID789*CN~
OID**EMPLEH**CTN*154*L*1253~
OID**FEVAHI**CTN*336*L*2003~
OID**YLLANI**CTN*14*L*210~
OID**YMTSOL**CTN*56*L*3498~
OID**YTINAS**CTN*34*L*4206~
N1*SH*Arkham Mulysa Industries*93*Shipper-01~
N4*New York*NY*10011*US~
LX*4~
L11* CMV0000020*BM~
L11*CarrierPROID987*CN~
L11*CMV0000020*BN~
OID**AARRGH**CTN*5*L*1800~
OID**MEWOOO**CTN*17*L*980~
OID**WOLFIE**CTN*32*L*565~
N1*SH*Johns Gizmo’s*93*BBYLoadATID-01~
N4*Chicago*IL*60601*US~
LX*5~
L11*12345678901234567*BM~
L11*CarrierPROID684*CN~
OID**NAMTAB**CTN*24*L*1080~
OID**SNIBOR**CTN*45*L*800~
OID**SREKOJ**CTN*25*L*1000~
N1*SH*Wayne Enterprises*93*WAYNE01~
N4*New York*NY*10003*US~
SE*49*0001~
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.