Verify via the Amadeus Flight Order Management API that the order requires a change fee before issuing an EMD-S; retrieve the applicable penalty amount from the fare rules (CAT16).
In Amadeus cryptic or via the Amadeus Orders API, create a Miscellaneous Services Order (MSR) entry in the PNR specifying the service code (e.g., SRVC code for rebooking fee), the amount, and the form of payment.
Issue the EMD-S via the Amadeus ticketing command or API call; note the 13-digit EMD document number in your records — it begins with the airline's IATA numeric code.
Associate the EMD-S with the reissued ticket in your records; the EMD-S is a standalone document and is not directly coupon-linked, but must be referenced in the exchange transaction.
For refunds of the fee, void the EMD-S within the BSP void window (typically same day); after the void window, initiate a refund via the BSP or ARC refund application citing the EMD document number.
Reconcile the EMD-S issuance against BSP/ARC settlement files; EMD-S documents appear as separate line items distinct from ticket coupons.
Known gotchas
EMD-S documents have their own validity period — typically one year from issuance; expired EMDs cannot be refunded through normal channels and require airline direct resolution.
Not all GDS connections support EMD-S issuance via REST API — Amadeus cryptic commands may be required for some EMD types depending on your configuration and the airline's GDS profile.
EMD-S settlement through BSP follows a separate billing cycle from tickets; failure to account for EMDs in reconciliation leads to BSP debit memos.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp