--- title: "EDI 110 Air Freight Details and Invoice | X12 | Stacksync" description: "EDI 110 is the X12 Air Freight Details and Invoice, used when carrier billing is ready to reconcile. See key segments (B3, B3A, C3) and mapping checks." canonical: https://www.stacksync.com/edi/x12/110-air-freight-details-and-invoice last_modified: 2026-09-29 --- X12 transaction code # EDI 110 Air Freight Details and Invoice (X12 110) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDI 110 is the X12 Air Freight Details and Invoice transaction set, used when carrier billing is ready to reconcile. An air carrier or freight forwarder sends the 110 to its customer, the party billed for the shipment. Standard X12 Code 110 Partner references 5 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 110 at a glance What the 110 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 110 Air Freight Details and Invoice summary** | | | | --- | --- | | Document | X12 110 Air Freight Details and Invoice | | Business record | Air-freight payable | | Who sends it to whom | An air carrier or freight forwarder sends the 110 to its customer, the party billed for the shipment. | | When it is sent | 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. | | Match on | Carrier invoice, air waybill and billing revision | | Partner references | 5 trading partners in this directory | | Related documents | [X12 104 Air Shipment Information](https://www.stacksync.com/edi/x12/104-air-shipment-information) | ### Key segments in an EDI 110 The business segments that appear in at least half of the 14 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send. | Segment | Name | Purpose | Partner references | | --- | --- | --- | --- | | B3 | Beginning Segment for Carrier's Invoice | To transmit basic data relating to the carrier's invoice. | 14 of 14 | | B3A | Invoice Type | To indicate type of invoice and number of shipments. | 14 of 14 | | C3 | Currency | To specify the currency being used in the transaction set. | 14 of 14 | | N1 | Name | To identify a party by type of organization, name, and code. | 14 of 14 | | N3 | Address Information | To specify the location of the named party. | 14 of 14 | | N4 | Geographic Location | To specify the geographic place of the named party. | 14 of 14 | | N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 14 of 14 | | LX | Assigned Number | To reference a line number in a transaction set. | 14 of 14 | | L3 | Total Weight and Charges | To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items. | 14 of 14 | | P1 | Pick-up | To specify the pick-up details including time, date, and equipment. | 14 of 14 | Stacksync connects EDI documents such as the X12 110 to your ERP, CRM and databases with two-way sync. Read the [EDI overview](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/book-a-demo) to walk through your partner guide. 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 decision | Record and matching IDs | What 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. - [X12 104 Air Shipment Information](https://www.stacksync.com/edi/x12/104-air-shipment-information) **air shipment:** air-freight booking is ready for carrier processing. ### 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. ### Related documents and resources - [X12 104 Air Shipment Information](https://www.stacksync.com/edi/x12/104-air-shipment-information) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) 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 ## Find your trading partner for X12 110 5 partners, 14 channels. Choose a channel to inspect its listed document reference and implementation context. - [CTSI-Global](https://www.stacksync.com/edi/ctsi) [Phillips Medisize (via CTSI) (ISA ID: CTSI5383)](https://www.stacksync.com/edi/ctsi/phillips-medisize-via-ctsi-isa-id-ctsi5383/x12-110-air-freight-details-and-invoice) [Molex USA (via CTSI) (ISA ID: CTSI5365)](https://www.stacksync.com/edi/ctsi/molex-usa-via-ctsi-isa-id-ctsi5365/x12-110-air-freight-details-and-invoice) - [Data2Logistics (Toshiba)](https://www.stacksync.com/edi/data2logistics-toshiba) [Data2Logistics (Toshiba)](https://www.stacksync.com/edi/data2logistics-toshiba/data2logistics-toshiba/x12-110-air-freight-details-and-invoice) - [Merck](https://www.stacksync.com/edi/merck) [Merck Global Clinical Supply](https://www.stacksync.com/edi/merck/merck-global-clinical-supply/x12-110-air-freight-details-and-invoice) - [Pfizer Trax](https://www.stacksync.com/edi/pfizer-trax) [Pfizer Trax US](https://www.stacksync.com/edi/pfizer-trax/pfizer-trax-us/x12-110-air-freight-details-and-invoice) - [Q2 Solutions (Quintiles)](https://www.stacksync.com/edi/q2-solutions-quintiles) [Q2 Solutions SSIQUINAR](https://www.stacksync.com/edi/q2-solutions-quintiles/q2-solutions-ssiquinar/x12-110-air-freight-details-and-invoice) [Q2 Solutions SSIQUIN](https://www.stacksync.com/edi/q2-solutions-quintiles/q2-solutions-ssiquin/x12-110-air-freight-details-and-invoice) [Q2 Solutions SSIQUININ](https://www.stacksync.com/edi/q2-solutions-quintiles/q2-solutions-ssiquinin/x12-110-air-freight-details-and-invoice) [Q2 Solutions SSIQUINSG](https://www.stacksync.com/edi/q2-solutions-quintiles/q2-solutions-ssiquinsg/x12-110-air-freight-details-and-invoice) [Q2 Solutions SSIQUINGB](https://www.stacksync.com/edi/q2-solutions-quintiles/q2-solutions-ssiquingb/x12-110-air-freight-details-and-invoice) [Q2 Solutions SSIQUINZA](https://www.stacksync.com/edi/q2-solutions-quintiles/q2-solutions-ssiquinza/x12-110-air-freight-details-and-invoice) [Q2 Solutions SSIQUINEU](https://www.stacksync.com/edi/q2-solutions-quintiles/q2-solutions-ssiquineu/x12-110-air-freight-details-and-invoice) [Q2 Solutions SSIQUINCN](https://www.stacksync.com/edi/q2-solutions-quintiles/q2-solutions-ssiquincn/x12-110-air-freight-details-and-invoice) [Q2 Solutions SSIQUINJP](https://www.stacksync.com/edi/q2-solutions-quintiles/q2-solutions-ssiquinjp/x12-110-air-freight-details-and-invoice) 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 Partner entries with the most listed channels - [Q2 Solutions (Quintiles)](https://www.stacksync.com/edi/q2-solutions-quintiles) - [CTSI-Global](https://www.stacksync.com/edi/ctsi) - [Data2Logistics (Toshiba)](https://www.stacksync.com/edi/data2logistics-toshiba) - [Merck](https://www.stacksync.com/edi/merck) - [Pfizer Trax](https://www.stacksync.com/edi/pfizer-trax) FAQ ## EDI 110 questions ### What is an EDI 110? EDI 110 is the X12 Air Freight Details and Invoice transaction set. Trading partners use it when carrier billing is ready to reconcile. It carries the data for the air-freight payable, and your system matches it on carrier invoice, air waybill and billing revision. ### Who sends an EDI 110 and who receives it? An air carrier or freight forwarder sends the 110 to its customer, the party billed for the shipment. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 110 sent? 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. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 110? Across 14 partner document references listed here, the business segments that appear most often include B3 (Beginning Segment for Carrier's Invoice), B3A (Invoice Type), C3 (Currency), N1 (Name), N3 (Address Information), N4 (Geographic Location). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 110 and EDI 104? The 110 carries the air-freight payable and is used when carrier billing is ready to reconcile. The 104 carries the air shipment and is used when air-freight booking is ready for carrier processing. ### 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. ### 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. ## 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. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)