A complete guide to the RM* command in Amadeus โ how to add a remark specifically intended for the back-office system through the Amadeus Interface Record.
Not every remark in a PNR is meant for the airline. Some information is intended for your own agency โ accounting references, internal codes, invoice notes, or instructions that must reach the back-office system. If this information is added with a standard remark entry, it travels with the PNR but may not be transmitted correctly to the back-office platform. The RM* command solves this. It allows you to enter a remark specifically intended for processing or transmission to the back-office system through the Amadeus Interface Record. This guide explains what RM* does, its syntax, and when it should be used.
What Does the RM* Command Do?
RM* is the Amadeus GDS command used to add a remark for the back-office system through the Amadeus Interface Record.
Category: PNR Elements.
It allows you to enter a remark specifically intended for processing or transmission to the back-office system.
The asterisk is the key detail. A standard RM entry adds a general remark to the PNR. An RM* entry adds a remark that is flagged for the Amadeus Interface Record โ the data feed that transmits PNR information from Amadeus to your agencyโs back-office accounting or reporting system.
Syntax & Example
Add an Interface Record remark for the back-office system:
RM*THIS IS THE REMARK FOR THE BACK OFFICE SYSTEMThis adds a remark that is specifically intended for the back-office system. The free-flow text after the asterisk is the information that will be transmitted through the Amadeus Interface Record.
The remark is stored in the PNR and also sent to the back-office system, so accounting staff can see the reference without having to retrieve the booking in Amadeus.
When to Use RM*
Use RM* when you need to add information that should be transferred to the back-office system as an Interface Record remark. Typical scenarios include:
- Adding an invoice reference or internal accounting code to a booking.
- Recording a purchase order number that must reach the accounts team.
- Flagging a booking for special handling by the back-office staff.
- Noting the cost centre or department for a corporate trip.
- Adding an internal reference for a group booking or tour operator contract.
- Sending accounting instructions that must be visible in the reporting system.
- Recording settlement notes or reconciliation references for the finance team.
How RM* Fits Into Your PNR Management Workflow
A typical session using RM* might look like this:
- Retrieve the PNR with RT and confirm the booking details.
- Identify the information that needs to reach the back-office system โ invoice references, internal codes, or accounting notes.
- Enter the RM* entry with the required free-flow text.
- End the transaction so the remark is saved and included in the Interface Record.
- Verify the remark appears correctly by redisplaying the PNR.
- Confirm with the back-office team that the remark was received in their system.
- If the remark needs to be corrected, use XE to delete the element and re-enter it correctly.
How RM* Relates to Other Remark and PNR Commands
- RM โ adds a general remark to the PNR.
- RM* โ adds a remark for the back-office system through the Amadeus Interface Record.
- XE โ deletes a remark or any other PNR element.
- RH โ displays the PNR history, including remarks added and removed.
- OP โ creates an option element for follow-up actions.
- AM and AB โ add mailing and billing address elements to the PNR.
The distinction matters: RM is for general remarks inside the PNR, while RM* is specifically for remarks that must be transmitted to the back-office system through the Amadeus Interface Record.
Important: RM* is not a substitute for RM. Use RM* only when the remark is genuinely intended for the back-office system. Adding unnecessary RM* elements can flood the Interface Record with irrelevant data and complicate accounting and reporting.
Because the remark is transmitted to a third system, always verify the text before entering it. A wrong invoice number or reference will be carried into the back-office records and may need manual correction later.
Frequently Asked Questions
What does RM* do in Amadeus?
RM* adds a remark to the PNR for the back-office system through the Amadeus Interface Record.
How is RM* different from RM?
RM adds a general remark. RM* flags the remark for transmission to the back-office system through the Interface Record.
What is the Amadeus Interface Record?
It is the data feed that transmits PNR information from Amadeus to your agencyโs back-office system for accounting and reporting purposes.
Can I add multiple RM* remarks to the same PNR?
Yes. Each RM* entry creates its own remark element. Add only the remarks that are genuinely needed by the back-office system.
How do I correct a wrong RM* remark?
Delete the element with XE and re-enter the corrected remark with RM*. Confirm with the back-office team that the correction reached their system.
Conclusion
The RM* command is the Interface Record remark tool in Amadeus. Use RM*THIS IS THE REMARK FOR THE BACK OFFICE SYSTEM to add information that must reach your agencyโs back-office platform for accounting, reporting, or reconciliation. It is the correct entry for invoice references, internal codes, purchase order numbers, and any other data that belongs in the finance system rather than just inside the PNR. Always distinguish between a general remark with RM and an Interface Record remark with RM* โ using the wrong entry either sends unnecessary data to the back office or leaves important references stranded in the PNR. Paired with XE to correct mistakes and RH to review the PNR history, RM* completes your remark toolkit and keeps every bookingโs accounting data flowing to the right place.
Focus Keywords
- RM* command
- Amadeus RM*
- back-office remark Amadeus
- Amadeus Interface Record
- Interface Record remark
- RM command
- PNR remark Amadeus
- accounting remark PNR
- Amadeus back office
- PNR elements
