ANSI X12 transaction set 240
Connect ANSI X12 240 package status updates with UPS and your ERP, WMS or 3PL.
Tirnav helps logistics and finance teams automate EDI 240 workflows with partner-specific mapping, testing and exception handling. Receive package status updates and map package identifiers and reported events into your order-management, warehouse or customer-service workflow.
Message overview
EDI 240 is the ANSI X12 Motor Carrier Package Status Transaction Set. It communicates carrier package status information so businesses can associate updates with package records in their operational systems.
Typical message flow
Implementation workflow
Review the carrier implementation guide, X12 version and business requirements for EDI 240.
Agree connectivity, sender and receiver identifiers, and test data with the trading partner.
Receive package status updates and map package identifiers and reported events into your order-management, warehouse or customer-service workflow.
Validate required fields, qualifiers, references and business rules against the agreed implementation guide.
Test accepted and rejected messages, duplicate handling and acknowledgement requirements.
Launch with transaction monitoring, actionable alerts and controlled reprocessing.
X12 reference
Segment requirements vary by trading partner and implementation guide. These are common examples, not a universal requirement list.
| Segment | Business meaning | Implementation notes |
|---|---|---|
| ISA / GS | Control headers | Identify the interchange sender, receiver and functional group using the agreed partner identifiers. |
| ST / SE | Transaction envelope | Identify the 240 transaction set and validate its control number and segment count. |
| B1 | Beginning segment | Identifies the motor carrier shipment information, shipment reference and transaction purpose. |
| N1 / N2 / N3 / N4 | Party and location | Identifies shipment parties and locations such as shipper, consignee, carrier and other transportation-related parties. |
| G62 | Date and time | Communicates shipment, pickup, delivery or other transportation-related dates and times. |
| L11 | Reference information | Carries shipment, order, booking, bill of lading, customer and other reference numbers. |
| MS3 | Interline information | Identifies participating carriers and transportation responsibilities when interline movement is involved. |
| S5 | Stop-off details | Identifies shipment stops and communicates stop sequence and related transportation information. |
| N1 / N3 / N4 | Stop party and address | Provides the name, address and location details associated with a shipment stop. |
| L5 | Commodity information | Identifies the commodity being transported and provides shipment-level commodity descriptions. |
| L0 | Line-item quantities | Communicates shipped quantities, packaging information, weights and units of measure. |
| L1 | Freight charges | Provides freight rates, charges, allowances and other transportation pricing information when required. |
| L3 | Shipment totals | Provides shipment-level totals such as weight, quantity, volume and freight charges. |
| SE / GE / IEA | Control trailers | Close the transaction, functional group and interchange with control counts and matching references. |
Mapping and operations
Tirnav transforms the partner message into the format required by your ERP, WMS, OMS, 3PL or custom application while applying partner-specific business rules.
Exception handling
Detect rejected, malformed or incomplete messages.
Diagnose source data, mapping or business-rule failures.
Resolve the issue with the right owner and correction.
Reprocess safely while preserving transaction history.
Trading partners
Related transaction sets
EDI 240 is the ANSI X12 Motor Carrier Package Status Transaction Set. It is used to communicate package-level status information and associate shipment events with package records.
An EDI 240 can include package identifiers, shipment references, carrier information, status details, dates, times and other package-level information required by the trading partner.
UPS supports EDI 240 for motor carrier package status information under applicable carrier requirements. Tirnav can map the UPS-specific EDI 240 structure and integrate package status data with your business systems.
Tirnav receives package status messages, validates the EDI data and maps package identifiers, shipment references and status events into your ERP, WMS, order-management or customer-service systems.
EDI 240 is used for motor carrier package status information, while EDI 214 is used for transportation carrier shipment status. The appropriate transaction depends on the carrier and its implementation requirements.
Implementation typically requires the carrier's implementation guide, X12 version, sample EDI files, connectivity details, package and status mapping requirements, and destination-system field mappings.
Yes. Depending on the carrier's connectivity and transmission requirements, EDI 240 messages can be received and processed automatically so package status updates can flow into operational and customer-service systems.
Tirnav validates incoming EDI 240 transactions and identifies issues such as missing package identifiers, invalid values or mapping errors. Failed messages can be reviewed, corrected and reprocessed.
Explore our latest thoughts on technology and business.
Learn how automotive EDI helps Indian OEMs and suppliers automate forecasts, purchase orders, ASN, invoices, ERP integration and supplier collaboration.
A practical plan to convert UB-04 claim data into HIPAA-compliant X12 837I, submit to a clearinghouse or payer, and track 999/277CA acknowledgments - with realistic timeline and cost.
Confused about how to start with EDI? We break down the three paths: SaaS Fulfilment Portals (like SPS Commerce Web), Integrated EDI (ERP Automation), and building your own In-House system.
Skip the backlog. Connect directly with our architects to discuss your business goals, technical challenges, and digital transformation roadmap.