IATA RP 1745: Baggage Information Messages – The Common Data Language of the Global Baggage Journey

Introduction

Modern baggage handling depends on continuous, machine-readable communication. A bag checked in Tokyo must be understood by the sorter in Dubai and the reconciliation system in London without proprietary translation. When systems cannot exchange unambiguous event data, sortation fails, reconciliation breaks down and mishandling rates rise.

IATA Recommended Practice 1745 supplies the missing common language. It defines the formats, data elements and sequencing rules for the full family of baggage information messages used beyond the simplest interline exchanges. By prescribing how every bag—identified by its unique 10-digit license-plate number—is reported at each operational milestone, RP 1745 enables automated sortation, passenger–bag reconciliation, interline handovers and auditable tracking across airlines, ground handlers and airports.

Origin and Evolution

RP 1745 was developed under the IATA Passenger Services Conference to support the license-plate tagging concept established by Resolution 740. It first appeared in the PSC Resolutions Manual around 2010; the designation PSC(31)1745 indicates adoption at the 31st Passenger Services Conference. The full text was included in the 38th Edition of the Manual (published 1 June 2018) and continues to be maintained in subsequent editions (the Manual having reached its 45th edition by 2025).

As member-controlled intellectual property, the practice is updated only by formal PSC vote, usually after technical working-group review. Notable amendments have refined the “.J” processing-information element, extended data-element codes, introduced new exception codes such as UNAR (unaccompanied) in 2020, and added location codes to the “.D” element in the 2024–25 cycle. A companion practice, RP 1745a (Automated Baggage Handling), was introduced in 2022 to address modern automated environments while remaining compatible with the core RP 1745 message set.

Purpose and Scope

The purpose of RP 1745 is to ensure that baggage event data can be exchanged reliably between any compliant Departure Control System (DCS) and any compliant Baggage Handling System (BHS). It covers the complete suite of Type-B baggage information messages required for automated handling and reconciliation, including:

• Baggage Source Message (BSM) – original check-in data.
• Baggage Processed Message (BPM) – sortation or processing actions.
• Baggage Transfer Message (BTM) – interline handover data.
• Baggage Unload Message (BUM) – unloading events.
• Baggage Not Seen Message (BNS) – alerts that an expected bag is missing.
• Baggage Control Message (BCM) – special instructions (hold, scan reminders, etc.).
• Baggage Manifest Message (BMM) – post-sortation flight manifest.
• Baggage Request (BRQ) – requests for information or reconciliation actions.

Each message follows a fixed sequence of data elements defined in the RP 1745 data dictionary, guaranteeing that any receiving system can parse the information without custom mapping.

Technical Structure

Every RP 1745 message is constructed from a standardized set of data elements. Core fields include:

• Bag-tag number (the 10-digit license plate).
• Flight designator and date.
• Status and processing codes.
• Location codes (the “.D” element).
• Exception codes (the “.E” element).
• Timestamps.
• Passenger-related and routing information where required.

A typical BSM, for example, carries passenger name, bag tag, flight, date, weight and routing data generated at check-in. A BPM reports the subsequent sortation action; a BTM conveys the same bag’s details to a connecting carrier.

Messages may be transmitted over traditional Type-B networks or modern data links. Addressing and transmission rules are further detailed in the IATA Systems and Communications Reference. While some carriers are adopting XML-based baggage schemas, the RP 1745 Type-B formats remain the interoperability baseline and continue to be carried or translated in hybrid environments.

Implementation Guidelines

Successful implementation requires that both the airline DCS and the airport or handler BHS apply the definitions, formats and specifications set out in RP 1745. Typical steps include:

1. Ensuring every interline bag carries a 10-digit license-plate tag in accordance with Resolution 740.
2. Configuring the DCS to generate the appropriate RP 1745 message (BSM at bag drop, BTM at transfer, etc.) at each defined event.
3. Configuring the BHS to consume those messages in real time or near-real time, using the data to drive sortation, issue alerts (BNS) or enforce reconciliation rules.
4. Agreeing with interline partners that only the standard code tables will be used; bilateral proprietary codes are discouraged.
5. Aligning message exchange with the four mandatory tracking points required by Resolution 753 (acceptance, loading, transfer and arrival).

The IATA Baggage Reference Manual and Airport Handling Manual supply operational mapping examples and technical implementation notes. Office Function Designators (OFDs) defined in the RP text govern message routing between systems.

Operational Workflow

1. At check-in or bag drop the DCS creates a BSM containing the license-plate number and flight data and transmits it to the local BHS.
2. As the bag moves through sortation the BHS generates BPMs reporting each processing action.
3. At interline transfer a BTM carries the bag’s current status to the receiving carrier’s systems.
4. Loading or unloading events trigger BUMs; any expected bag that fails to appear generates a BNS.
5. Special instructions (hold, priority, security) are conveyed by BCMs.
6. After sortation a BMM may list all bags assigned to a flight.
7. Reconciliation or information requests are handled via BRQs.
8. The complete sequence of time-stamped messages forms the electronic journey record used for tracking, claims investigation and audit.

Benefits for Airlines and Airports

Standardized messaging delivers measurable operational and commercial returns:

• Interoperability – New interline partnerships or system upgrades require no proprietary interface design; every compliant system already understands the RP 1745 vocabulary.
• Efficiency – Automated sortation and reconciliation become possible only when event data arrive in a predictable format. Carriers report faster flight readiness, lower mishandling rates and reduced recovery costs.
• Auditability and compliance – Time-stamped messages create a complete electronic trail that satisfies Resolution 753 tracking audits, interline service-level agreements and internal quality programmes.
• Analytics – Aggregated message data reveal dwell times, transfer success rates and recurring exception patterns, enabling targeted process improvements.
• Passenger service – Faster identification and reunification of mishandled bags improve the overall travel experience and protect airline reputation.

Auditability and Compliance

RP 1745 messages are the primary evidence examined during IATA baggage-tracking certification. Auditors select sample flights and verify that the correct messages were generated and transmitted at each of the four mandatory touchpoints (acceptance, loading, transfer, arrival). Missing BSMs, absent BPMs at transfer, or unexplained gaps that should have produced a BNS are recorded as non-conformities. The same message archive supports root-cause analysis of individual mishandling incidents and provides objective data for interline prorating and regulatory reporting.

Relationship to Other IATA Standards

RP 1745 is the messaging backbone that operationalizes several related standards:

• Resolution 740 – supplies the 10-digit license-plate number carried in every message.
• Resolution 753 – mandates the four tracking points whose events are reported via RP 1745 messages.
• RP 1740 series – governs tag media and print quality so that the license plate remains scannable and therefore reportable.
• RP 1745a – extends the framework into fully automated baggage-handling environments.
• RP 1743e – irregularity codes may appear inside the exception or special-information elements of RP 1745 messages.
• Local rules under RP 1744 and Resolution 744 – determine when and where particular messages are triggered at a given airport.

Real-World Use Cases

• A green-field hub installs a high-speed sorter that natively consumes BSMs and BPMs; self-service bag-drop units generate the initial BSM, and the sorter routes every bag without manual intervention.
• A Baggage Reconciliation System receives RP 1745 messages from multiple carriers’ DCS platforms and prevents a bag from being loaded if the corresponding passenger has not boarded.
• At an alliance hub a delivering carrier transmits a BTM; the receiving carrier’s BHS parses it according to RP 1745 rules and continues automated handling without re-keying.
• An expected bag fails to appear at the aircraft-side loader; a BNS is generated automatically, triggering an immediate search and preventing a “not seen” mishandling from becoming a permanent loss.
• Electronic bag tags and RFID readers capture the license-plate number and populate the corresponding RP 1745 message fields, feeding the same messaging infrastructure used by conventional barcode systems.

Industry Challenges

Legacy systems may still generate incomplete or non-standard message content, requiring translation layers. High-volume transfer banks can generate message bursts that stress older Type-B networks. Consistent population of optional but operationally valuable fields (location codes, precise exception codes) depends on disciplined configuration and training. Hybrid environments that mix Type-B and emerging XML schemas must maintain bidirectional mapping to preserve end-to-end visibility.

Future Outlook

RP 1745 continues to evolve through the normal PSC amendment cycle. Recent additions of location and exception codes demonstrate ongoing adaptation to operational needs. The parallel development of RP 1745a and XML schemas indicates a gradual modernization path, yet the core Type-B message set remains the interoperability foundation for the foreseeable future. As tracking mandates tighten and passenger expectations for real-time bag status rise, the quality and completeness of RP 1745 messaging will remain central to both compliance and service quality.

Amendment Status

RP 1745 was adopted at the 31st Passenger Services Conference and has been maintained through successive editions of the PSC Resolutions Manual. Substantive updates—including refinements to processing elements, new exception codes (2020) and expanded location codes (2024–25)—are recorded in the manual’s amendment history. The practice remains current; any further changes will continue to follow formal PSC voting and publication procedures.

Key Takeaways

• RP 1745 defines the standard formats and data elements for the full suite of Type-B baggage information messages.
• Core messages include BSM, BPM, BTM, BUM, BNS, BCM, BMM and BRQ.
• Every message centres on the 10-digit license-plate tag and carries standardized location, status, exception and timestamp fields.
• The practice was adopted around 2010 (PSC 31) and continues to be refined through PSC amendments.
• Implementation requires coordinated configuration of airline DCS and airport/handler BHS platforms.
• Messages provide the electronic evidence required for Resolution 753 tracking audits.
• Benefits include system interoperability, automated sortation, lower mishandling rates, full audit trails and actionable analytics.
• The standard underpins interline handovers, baggage reconciliation and exception management worldwide.
• It works in concert with Resolution 740, Resolution 753, the RP 1740 series and RP 1745a.
• Ongoing evolution of codes and the emergence of complementary XML schemas keep the framework relevant while preserving backward compatibility.

Conclusion

RP 1745 is the invisible infrastructure that makes modern baggage handling possible. By giving every system a shared vocabulary for reporting the life of a bag, it turns isolated check-in, sortation and transfer events into a continuous, auditable journey record. Airlines and airports that implement it fully gain not only operational efficiency and regulatory compliance but also the data foundation required for continuous improvement and superior passenger service. In an industry that moves bags across hundreds of systems and dozens of borders every day, that common language remains indispensable.