X12

Inbound

Merck X12 110 Air Freight Details and Invoice

Merck Global Clinical Supply

The EDI 110 (Air Freight Details and Invoice) document is used by Merck for electronic data interchange. It enables automated processing and compliance with Merck's trading partner requirements.

30segments

5loops

8mandatory

Book a demo

← All Merck transactions

Schema Reference

30 segments · X12 110 Air Freight Details and Invoice

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Interchange Control Standards Identifier

M ID 1-1

ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

B302 Invoice Number

M AN 1-22

B303 Shipment Identification Number

O AN 1-30

B304 Shipment Method of Payment

M ID 2-2

B306 Date

M DT 8-8

B307 Net Amount Due

M N2 1-12

B308 Correction Indicator

O ID 2-2

B309 Delivery Date

C DT 8-8

B310 Date/Time Qualifier

C ID 3-3

B311 Standard Carrier Alpha Code

M ID 2-4

B312 Date

O DT 8-8

B3A01 Transaction Type Code

M ID 2-2

B3A02 Number of Shipments

O N0 1-5

ITD01 Terms Type Code

O ID 2-2

ITD02 Terms Basis Date Code

O ID 1-2

ITD06 Terms Net Due Date

O DT 8-8

ITD07 Terms Net Days

O N0 1-3

N1 Loop Repeat: 3

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N201 Name

M AN 1-60

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

LX Loop Repeat: 9,999

LX01 Assigned Number

M N0 1-6

N1 Loop Repeat: 3

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N201 Name

M AN 1-60

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

PER01 Contact Function Code

M ID 2-2

PER02 Name

O AN 1-60

P101 Pick-up or Delivery Code

O ID 1-2

P102 Pick-up Date

M DT 8-8

P103 Date/Time Qualifier

M ID 3-3

R103 Airport Code

M ID 3-5

R104 Air Carrier Code

M ID 3-3

R105 Airport Code

M ID 3-5

POD01 Date

M DT 8-8

POD02 Time

O TM 4-8

POD03 Name

M AN 1-60

L5 Loop Repeat: 4

L501 Lading Line Item Number

O N0 1-3

L502 Lading Description

O AN 1-50

L505 Packaging Code

O AN 3-5

L001 Lading Line Item Number

O N0 1-3

L002 Billed/Rated-as Quantity

C R 1-11

L003 Billed/Rated-as Qualifier

C ID 2-2

L004 Weight

C R 1-10

L005 Weight Qualifier

C ID 1-2

L008 Lading Quantity

C N0 1-7

L009 Packaging Form Code

C ID 3-3

L011 Weight Unit Code

O ID 1-1

L401 Length

M R 1-8

L402 Width

M R 1-8

L403 Height

M R 1-8

L404 Measurement Unit Qualifier

M ID 1-1

L405 Quantity

O R 1-15

L1001 Weight

M R 1-10

L1002 Weight Qualifier

M ID 1-2

L1003 Weight Unit Code

O ID 1-1

SL101 Service Level Code

M ID 2-2

SL102 Tariff Number

O AN 1-7

SL103 Commodity Code

C AN 1-30

SL106 Service Level Code

O ID 2-2

SL107 Shipment Method of Payment

O ID 2-2

SL108 Data Source Code

O ID 2-2

L1 Loop Repeat: 30

L101 Lading Line Item Number

O N0 1-3

L102 Freight Rate

C R 1-9

L103 Rate/Value Qualifier

C ID 2-2

L104 Charge

C N2 1-12

L108 Special Charge or Allowance Code

O ID 3-3

L112 Special Charge Description

O AN 2-25

C301 Currency Code

M ID 3-3

C302 Exchange Rate

O R 4-10

C303 Currency Code

O ID 3-3

L301 Weight

C R 1-10

L302 Weight Qualifier

C ID 1-2

L305 Charge

O N2 1-12

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating Merck EDI 110

Stacksync validates, transforms, and delivers your 110 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync processes Merck EDI 110 (Air Freight Details and Invoice) documents automatically — syncing data to your system in real time with no manual intervention required.

Merck EDI 110 FAQ

Common questions about 110 Air Freight Details and Invoice transactions with Merck.

What is a Merck EDI 110 Air Freight Details and Invoice?

The Merck EDI 110 Air Freight Details and Invoice is an X12 transaction set used to exchange Air Freight Details and Invoice data electronically between trading partners. As a inbound document, it standardizes the communication of Air Freight Details and Invoice information between Merck and their suppliers, carriers, or partners. Stacksync processes Merck 110 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Merck's requirements in real time.

How does Stacksync automate Merck EDI 110 Air Freight Details and Invoice transactions?

Stacksync handles Merck EDI 110 Air Freight Details and Invoice transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 110 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Merck 110 document meets their specific formatting requirements before transmission or after receipt.

What are common Merck EDI 110 errors and how do I fix them?

Common errors in Merck EDI 110 Air Freight Details and Invoice transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Merck 110 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up Merck EDI 110 with Stacksync?

Most Merck EDI 110 Air Freight Details and Invoice integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Merck's 110 format and your system, running test transactions, and completing Merck's certification process if required. Stacksync includes pre-built mappings for Merck's most common 110 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Merck EDI 110 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Merck EDI 110 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Merck updates their 110 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Merck EDI?