Skip to content
X12 EDI

Pfizer Trax X12 110 Air Freight Details and Invoice

X12 110 (Air Freight Details and Invoice) is the EDI transaction exchanged between Pfizer Trax (Pfizer Trax US) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
24
Loops
4
X12 110
All partners ↗

Transaction context

Where 110 Air Freight Details and Invoice fits on Pfizer Trax US

Pfizer Trax channels
1 of 1

1 of Pfizer Trax's 1 channel carries 110

Trading partners
5

partners across the Stacksync network trade 110

Channels
14

channels network-wide carry 110

The 110 is the air carrier's invoice for transportation and other charges on air shipments. It covers original invoices, past due billings, balance due bills, and revisions, carrying freight charges, fuel and security surcharges, shipment weights, origin and destination detail, and party information. Customers require it to reconcile freight invoices against shipments and manage transportation spend in accounts payable. An air carrier or freight forwarder sends the 110 to its customer, the party billed for the shipment.

When it fires: The carrier's billing system rates a completed air shipment and issues the invoice, or generates a revision, balance due bill, or past due billing on an existing one.

Common 110 rejection causes
  • Conditional pairing violations in the L1 rate and charges segment: a freight rate transmitted without its rate/value qualifier, or the reverse, fails syntax validation.
  • Charge totals in the mandatory L3 total weight and charges segment that do not reconcile with the line-item charges.
  • Invoice header problems in the B3 segment, such as duplicate or malformed invoice numbers, which break the customer's accounts payable matching.
  • Payment terms in the ITD segment that are incomplete or internally inconsistent, so discounts and due dates cannot be applied automatically.

Specification summary

X12 110 Air Freight Details and Invoice at the element level

The X12 110 specification defines 44 segments carrying 278 data elements, 72 of which are mandatory.

Segments
44
Data elements
278
Mandatory elements
72
Segments with mandatory elements
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
Full segment guideline — 24 segments 4 loops · X12 110 Air Freight Details and Invoice
ISA Interchange Control Header 16 elements

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

GS Functional Group Header 8 elements

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

ST Transaction Set Header 2 elements

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

B3 Beginning Segment for Carrier's Invoice 14 elements

To transmit basic data relating to the carrier's invoice

B3A Invoice Type 2 elements

To indicate type of invoice and number of shipments

ITD Terms of Sale/Deferred Terms of Sale 15 elements

To specify terms of sale

N1 Loop Repeat: 3
N1 Name 6 elements

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

N2 Additional Name Information 2 elements

To specify additional names or those longer than 35 characters in length

N3 Address Information 2 elements

To specify the location of the named party

N4 Geographic Location 6 elements

To specify the geographic place of the named party

N9 Reference Identification 12 elements

To transmit identifying information as specified by the Reference Identification Qualifier

LX Loop Repeat: 9,999
LX Assigned Number 1 element

To reference a line number in a transaction set

L3 Total Weight and Charges 15 elements

To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

SE Transaction Set Trailer 2 elements

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

PER Administrative Communications Contact 9 elements

To identify a person or office to whom administrative communications should be directed

P1 Pick-up 7 elements

To specify the pick-up details including time, date, and equipment

R1 Route Information (Air) 13 elements

To specify airline and airport routing sequences

POD Proof of Delivery 3 elements

To provide proof of delivery

L5 Loop Repeat: 4
L5 Description, Marks and Numbers 10 elements

To specify the line item in terms of description, quantity, packaging, and marks and numbers

L0 Line Item - Quantity and Weight 15 elements

To specify quantity, weight, volume, and type of service for a line item including applicable \"quantity/rate-as\" data

L10 Weight 3 elements

To transmit weight information

SL1 Tariff Reference 9 elements

To reference details of the tariff used to arrive at applicable rates or charges for customer-requested service

L1 Loop Repeat: 30
L1 Rate and Charges 21 elements

To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements

C3 Currency 4 elements

To specify the currency being used in the transaction set

Pfizer Trax Pfizer Trax US EDI 110 FAQ

Common questions about 110 Air Freight Details and Invoice on the Pfizer Trax US channel.

What is X12 110 Air Freight Details and Invoice?
X12 110 (Air Freight Details and Invoice) is the EDI transaction set used to exchange air freight details and invoice data. Pfizer Trax's Pfizer Trax US channel requires it from trading partners.
Does Pfizer Trax Pfizer Trax US require 110 for trading partners?
Yes, Pfizer Trax (Pfizer Trax US) supports X12 110 Air Freight Details and Invoice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Pfizer Trax 110 with Stacksync?
Most companies go live with Pfizer Trax 110 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.

Ready to automate your Pfizer Trax EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.