The Amadeus ES, ESD, and ESX commands help you manage PNR security. Use ES to create security agreements, ESD to display them, and ESX to cancel them.
Amadeus ES, ESD, and ESX Commands
ES is the Amadeus GDS command used to create security agreements for an individual PNR.
ESD is the Amadeus GDS command used to display the security agreements associated with an individual PNR.
ESX is the Amadeus GDS command used to cancel security agreements associated with an individual PNR.
Category: PNR Security.
Key Takeaways
- ES creates security agreements for an individual PNR.
- ESD displays the security agreements currently associated with a PNR.
- ESX cancels security agreements and removes the related access permissions.
- Use ES to grant or restrict access to another office, multiple offices, or a specific IATA number.
- Use ESD before making any security change to see what is already in place.
- Use ESX when the restriction is no longer needed and its removal is authorised.
- Use RT to retrieve the PNR before managing its security.
- Use RH to review security-related changes in the PNR history.
- These commands are essential for corporate bookings, VIP travel, confidential fares, and joint office handling.
Every PNR contains sensitive information. Passenger names, passport details, contact numbers, ticket records, and frequently negotiated fares all sit inside a single booking, and not every agent or office should be able to see them. Amadeus handles this through security agreements — rules that define exactly who can view, modify, or manage a specific PNR.
The Amadeus ES, ESD, and ESX commands are the core tools for PNR security. ES creates the agreements, ESD displays what is already in place, and ESX cancels the agreements when they are no longer needed.
This guide explains what each command does, the syntax for each variation, and when it should be used. You can also explore our training modules to learn more. You can further review Amadeus commands to master additional entries.
ES vs ESD vs ESX: Quick Comparison
The practical rule: always run ESD first to see the current security structure. Then use ES to create or manage agreements when authorised. Use ESX to remove restrictions when they are no longer needed.
Amadeus ES Command: Create Security Agreements
Create a security agreement with a specific office:
ESPARWL21**-B
This creates a security agreement with the office identified in the entry. Use it when the PNR is being handled together with a partner office or a branch, and that office needs access to the booking.
Create security agreements for multiple offices in one entry:
ESPARWL21**-B,***WL2***-R
This creates security agreements for several offices at the same time, each separated by a comma. It is useful when a booking is shared between multiple branches or departments and every one of them needs access.
Create a security agreement for a specific IATA number:
ES/I20239951-B
This creates a security agreement tied to the specified IATA number rather than to an individual office. Use it when access should be granted at agency level rather than per office location — for example in corporate contracts or joint ventures.
Amadeus ESD Command: Display Security Agreements
Enter the command on its own while the PNR is retrieved:
ESD
This displays the security agreements currently associated with the PNR, showing the offices, IATA numbers, or profiles that have access to the booking.
The ESD display shows:
- Access agreements — the offices or user profiles permitted to view or modify the PNR.
- IATA numbers — the agency or office identifiers linked to the security agreement.
- Other offices — partner offices or branch locations with whom the booking is shared.
- Restrictions in place — any additional rules that limit access to the record.
Reviewing this display before making changes prevents mistakes — for example, cancelling an agreement that is still required by another office, or assuming a PNR is restricted when it is not.
Amadeus ESX Command: Cancel Security Agreements
Enter the command on its own while the PNR is retrieved:
ESX
This cancels the security agreements associated with the PNR and removes the access permissions that were set by those agreements.
Once the agreements are cancelled, the PNR returns to the standard office-level access rules. Agents whose access was restricted by the agreement can view and modify the booking again, according to their normal profile permissions.
Use ESX when a PNR no longer requires restricted access, when a booking is being transferred, or when a security agreement was created in error.
When to Use ES, ESD, and ESX
Use ES when you need to grant or restrict access to an individual PNR for another office or IATA number. Use ESD when you need to view the existing security agreements for an individual PNR. Use ESX when you need to cancel the existing security agreements for an individual PNR. Typical scenarios include:
- Restricting a corporate or VIP booking to authorised offices only.
- Sharing a PNR with a partner office or branch for joint handling.
- Allowing a specific IATA number to access a booking made under a corporate agreement.
- Protecting a booking that contains confidential fares or negotiated rates.
- Giving another office access so they can issue the ticket or handle a refund.
- Verifying which offices or profiles currently have access to a PNR.
- Reviewing the security structure before cancelling agreements with ESX.
- Investigating access problems when an agent cannot retrieve or update a PNR.
- Transferring a booking between offices and removing the original security restrictions.
- Closing a booking at the end of a project or contract that required security agreements.
- Correcting a PNR that was accidentally placed under a security agreement.
- Removing outdated restrictions after a change in office policy or client requirements.
How ES, ESD, and ESX Fit Into Your PNR Security Workflow
A typical PNR security session using ES, ESD, and ESX might look like this:
- Retrieve the PNR with RT.
- Enter
ESDto display the security agreements on the PNR. - Review the offices, IATA numbers, and profiles that appear in the display.
- Confirm with your supervisor which offices or IATA numbers should have access.
- Enter the ES entry with the appropriate office or IATA number.
- End the transaction to save the security agreement.
- Verify the agreement by displaying it again with ESD.
- To remove the agreement later, use
ESX. - End the transaction to save the change.
- Review the change in the PNR history with RH if required.
ES, ESD, and ESX vs Other Security Commands
- ES → creates security agreements for an individual PNR.
- ESD → displays the security agreements currently associated with a PNR.
- ESX → cancels the security agreements on an individual PNR.
- RP → changes the responsible office and related office assignments.
- RT → retrieves the PNR before managing its security.
- RH → displays the PNR history, including security-related changes.
The distinction matters: ES creates, ESD displays, and ESX cancels. Together they form the complete PNR security toolkit in Amadeus.
Important: Creating a security agreement restricts who can access the PNR. Once the agreement is saved, only the offices or IATA numbers listed — plus the responsible office — can retrieve or update the booking. Always confirm the correct entries before saving, and check with your supervisor if you are unsure.
Cancelling security agreements opens the PNR to standard office access rules. Before using ESX, confirm that the removal is authorised — particularly for corporate, VIP, or confidential bookings where the restriction may still be required by policy or by the client.
Security agreements are recorded in the PNR history. Use RH to see when the agreement was created or cancelled and by whom.
Frequently Asked Questions
What does ES do in Amadeus?
ES creates security agreements for an individual PNR, controlling which offices or IATA numbers can access or modify the booking.
What does ESD do in Amadeus?
ESD displays the security agreements associated with an individual PNR, including access agreements with other offices or IATA numbers.
What does ESX do in Amadeus?
ESX cancels the security agreements associated with an individual PNR, removing the related access permissions.
How do I check the current security agreements?
Use ESD to display the security agreements on the PNR before making changes.
How do I create an agreement for multiple offices?
Separate the office entries with commas, for example ESPARWL21**-B,***WL2***-R.
How do I create an agreement for an IATA number?
Use the format ES/I20239951-B, replacing the IATA number with your own.
How do I remove a security agreement?
Use ESX to cancel the security agreements on the PNR. Confirm the change is authorised before doing so.
Does ESD change anything on the PNR?
No. ESD only displays the security information. To cancel agreements, use ESX.
Does ESX affect the itinerary or passengers?
No. ESX only removes the security agreements and access restrictions. The itinerary, passengers, and ticket data remain unchanged.
Can I restore a security agreement after using ESX?
Not in a single step. Recreating a security agreement requires the appropriate security commands and permissions. Handle ESX carefully and only after confirming it is authorised.
Official Amadeus reference:
For official product information and agent documentation, visit the Amadeus Selling Platform or the Amadeus Service Hub.
Amadeus ES, ESD, and ESX Commands: Final Overview
The Amadeus ES, ESD, and ESX commands are the core tools for PNR security. Use ESPARWL21**-B to grant access to a single office, ESPARWL21**-B,***WL2***-R to share a booking with multiple offices, and ES/I20239951-B to grant access at agency level using an IATA number.
Use ESD to view the security agreements currently associated with a PNR, including access agreements with other offices and IATA numbers. It is the correct first step before managing security with ES or cancelling agreements with ESX.
Use ESX to remove the access restrictions that were set through security agreements, returning the booking to standard office-level permissions. Always check the existing security structure with ESD before creating an agreement, confirm the correct office or IATA number, and remember that you can remove the agreement later with ESX.
Paired with RP for responsible office changes and RH for PNR history, the ES, ESD, and ESX commands complete your PNR security toolkit and keep every booking protected according to your office’s policy.
Read also: Amadeus QE Command: QE, QER & QES Queue Management Guide · Amadeus RTQ Command: Display PNR Queue Placements · Amadeus QU Command: Redisplay Queue Message Without Removing It