Recommended Practice 1719 (Passenger Services Conference, IATA) is the industry recommended practice that standardises the Passenger Final Sales Message (PFS). The PFS is a Type B teletype message generated at the completion of check-in (typically at flight close-out / CCF) that reports final sales and passenger-status information from the departure-control system back to the airline’s reservations and inventory systems. It appears in the Passenger Services Conference Resolutions Manual (PSCRM) as the first of the 1719-series messages (followed by FTL, PRL, ETL, TPL and ASL).
Origin, Status, and Relationship to Other Standards
The PFS was developed to close the information loop between the airport check-in environment and the central reservations/inventory systems. Before automated close-out messaging, final boarded figures, no-shows and go-shows were often communicated by telephone or ad-hoc telex. The PFS provides a structured, machine-readable summary that allows reservations systems to update inventory, revenue accounting and post-flight statistics.
It is closely related to the other messages in the 1719 family:
- 1719a Frequent Traveller List (FTL)
- 1719b Passenger Reconcile List (PRL)
- 1719c Electronic Ticket List (ETL)
- 1719d Ticketless Product List (TPL)
- 1719e Additional Service List (ASL)
All of these messages share the same post-check-in / flight-close timing and Type B infrastructure. The PFS itself focuses on final sales and passenger-status reconciliation rather than on special-service, frequent-flyer or ticket-detail data.
The practice is Type B (recommended) and of indefinite duration. Modern DCS and reservations systems continue to generate and consume the PFS (or equivalent structured close-out data) even when richer XML or API interfaces are also in use.
Purpose and Scope
The purpose of the PFS is to advise the airline’s reservations and inventory systems of the final passenger and sales outcome of a flight after check-in has been completed. Typical information carried includes:
- Numeric summary of passengers who travelled, broken down by class or compartment.
- Lists of passengers who appeared on the Passenger Name List (PNL) but did not travel (no-shows).
- Lists of passengers who travelled but did not appear on the original PNL (go-shows / NOREC – no-record).
- Other status categories defined by the airline (for example standby passengers who boarded, or specific inventory adjustments).
Scope is limited to the final sales and passenger-status picture for the flight (or flight segment) as recorded by the DCS at close-out. It does not replace revenue-accounting messages or full ticket-image feeds; it provides the operational “what actually flew” snapshot needed by reservations and inventory control.
Technical Structure and Message Content
The PFS follows standard IATA Type B conventions (addressing, communications reference, message identifier “PFS”, multi-part handling where required, and an end indicator).
Typical content structure (as implemented in major DCS platforms):
- Header / Flight identification – airline, flight number, date, origin station.
- Numeric portion – counts of passengers who travelled, usually by class or by master/equivalent class group.
Example form:MIA 27/012/030/002indicating 27Y + 12M + 30K + 2G (or similar class mapping). - Exception lists – named passengers falling into defined categories, most commonly:
- NOREC / go-show (travelled but not on the original PNL).
- NOSHOW (on the PNL but did not travel).
- Other airline-defined status groups.
- End element.
The exact set of status categories and the level of name detail are determined by airline configuration tables within the DCS. The message is addressed to a reservations printer PID or processing address designated by the airline (or handling company) when the carrier is set up in the system; an alternate address may be specified in the flight’s schedule/CSM.
Implementation in Airline Operations
Generation trigger
The PFS is produced automatically by the DCS at the completion of check-in (commonly the CCF – Check-in Complete / Flight Close event). It is therefore one of the last passenger messages sent for the flight.
Recipients
- Primary: airline reservations / inventory system address.
- Secondary: any additional addresses configured for the carrier or for a specific flight (for example a host airline’s central office when a flight is handled by a ground handler).
Operational use
- Inventory systems use the numeric counts and no-show/go-show lists to finalise the flown inventory picture.
- Revenue management and post-flight analysis systems use the data for load-factor and yield calculations.
- Some airlines feed the PFS into revenue-accounting or interline billing preparation processes.
Ground-handling context
When a flight is handled by a third-party agent, the agent’s DCS still generates the PFS to the operating carrier’s designated reservations address, ensuring the carrier receives a consistent final-sales picture regardless of who performed check-in.
Relationship to Other Close-Out Messages
The PFS is part of a family of post-check-in messages:
| Message | RP | Primary Focus |
|---|---|---|
| PFS | 1719 | Final sales counts + no-show / go-show lists |
| FTL | 1719a | Frequent-traveller / elite passengers |
| PRL | 1719b | Passenger reconciliation data |
| ETL | 1719c | Electronic ticket list |
| TPL | 1719d | Ticketless product list |
| ASL | 1719e | Additional services |
Airlines may elect to receive any combination of these messages according to their system architecture and business needs.
Benefits
- Reservations / Inventory – Timely, structured finalisation of the flown passenger picture; accurate no-show and go-show capture.
- Revenue Management – Reliable post-departure load and class-mix data.
- Ground Handlers – Standard method to report final sales outcome to the operating carrier.
- Industry – Common Type B format that every major DCS can generate and every reservations system can be configured to receive.
Auditability and Compliance
Compliance is demonstrated by:
- Correct generation at flight close-out.
- Accurate numeric counts that match the final boarded passenger figures.
- Correct identification of NOREC and NOSHOW (and any other configured) categories.
- Delivery to the airline-designated reservations address.
- Message logs retained according to airline record-keeping requirements.
Conclusion
Recommended Practice 1719 – Passenger Final Sales Message (PFS) provides the standardised Type B mechanism for reporting the final passenger and sales outcome of a flight from the departure-control system back to the airline’s reservations and inventory systems. By combining a numeric class summary with explicit lists of no-shows and go-shows, the PFS closes the operational loop between airport check-in and central inventory control. It remains a core member of the 1719-series close-out messages and continues to be generated by modern DCS platforms even as richer data interfaces proliferate.
Sources include the IATA PSCRM listing for RP 1719, operational DCS documentation describing PFS generation and content, related 1719-series message definitions, and industry practice for post-check-in messaging. Full proprietary specifications reside in the Passenger Services Conference Resolutions Manual.
Pixel 4a Review
The Google Pixel 4A currently tops our rank of the greatest Samsung phones available, beating even the pricier iPhone Ultra Max Mega.
So unsurprisingly this is an absolutely fantastic phone. The design isn't massively changed from the previous generation, but most other elements have been upgraded. This is what we call a big boost.
-
Display8.5
-
Performance9
-
Features7
-
Usability8
-
Battery Life10
