Skip to content

X12 transaction code

X12 110 Air Freight Details And Invoice

X12 110 Air Freight Details And Invoice: explore its business purpose, mapping identifiers, validation tests and 5 partner references across 14 listed channels.

Standard
X12
Code
110
Partner references
5

Implementation guide

X12 110 mapping and validation

X12 110 Air Freight Details And Invoice is used when carrier billing is ready to reconcile. Preserve carrier invoice, air waybill and billing revision so the air-freight payable in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record air-freight payable

carrier invoice, air waybill and billing revision

  • Define which combination of carrier invoice, air waybill and billing revision identifies one business record, its lines and any later revision.
Update the receiving system Processing the air-freight payable

ID assigned by the receiving system and processing result

  • Resend one invoice and verify that accounts payable creates only one liability.
  • Reconcile revised freight charges against the earlier bill instead of adding a second invoice.
Check the processing result Processing status for the air-freight payable

Original document reference and matching response

  • Reconcile the air-freight payable with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when carrier billing is ready to reconcile. Name the operational owner of the air-freight payable and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map carrier invoice, air waybill and billing revision. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic air-freight payable data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful air-freight payable processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 110 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic air-freight payable data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out air-freight payable without processing it twice.

Document structure

X12 110 Air Freight Details And Invoice at the element level

The X12 110 reference contains 44 segment entries and 278 data elements; 72 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
44
Data elements
278
Mandatory elements
72
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
B3 14 5
B3A 2 1
C2 7 3
C3 4 1
N1 6 1
N2 2 1
N3 2 1
N9 6 1
PER 9 1
LX 1 1
Key identifiers in 110
  • Invoice Number
  • Shipment Method of Payment
  • Date
  • Net Amount Due
  • Standard Carrier Alpha Code
  • Transaction Type Code
  • Bank Client Code
  • Identification Code Qualifier

Catalog breakdown

Where X12 110 Air Freight Details And Invoice appears in this catalog

The largest groups of classified 110 catalog entries are in healthcare & pharma and logistics & transport.

By industry

  • healthcare & pharma 11 channels
  • logistics & transport 3 channels

By network

  • CTSI 2 channels

FAQ

X12 110 questions

What is X12 110 Air Freight Details And Invoice used for?

110 is used when carrier billing is ready to reconcile. It carries information for the air-freight payable. Match it to your business system using carrier invoice, air waybill and billing revision.

Which partners list X12 110?

The directory on this page links 5 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

What should I map for X12 110?

Start with carrier invoice, air waybill and billing revision and the target air-freight payable. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 110 error handling?

Resend one invoice and verify that accounts payable creates only one liability. Reconcile revised freight charges against the earlier bill instead of adding a second invoice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 110 relate to other EDI messages?

X12 104 Air Shipment Information is a related document linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 110 and 104?

110 is used when carrier billing is ready to reconcile. 104 is used when air-freight booking is ready for carrier processing. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.