Establish the traveler's hotel loyalty program memberships by storing program codes and member numbers in your traveler profile system or in the Concur Travel Profile API
When constructing a hotel booking request via your GDS or hotel API, include the loyalty program code and member number in the designated loyalty fields of the reservation payload
After booking confirmation, retrieve the folio or booking confirmation and verify that the loyalty number appears on the reservation to reduce the incidence of points not posting
Ingest the post-stay hotel folio via OCR or e-folio feed to extract room-rate, tax, and incidental line items; match these against the pre-authorized hold amount to detect additional charges
Log the loyalty program, member number, and stay dates in your expense management system so that finance teams can audit whether corporate-negotiated rates are being combined with personal loyalty redemptions contrary to policy
Flag stays at hotels outside the preferred program or where the loyalty number was not attached, and surface these to the travel manager for program compliance reporting
Known gotchas
Hotel chains frequently update loyalty program codes and tier structures; maintain a versioned reference table of program codes rather than relying on static strings that may become invalid after a program rebrand or merger
Many corporate rate agreements prohibit stacking personal loyalty point earning with negotiated room rates; verify your company's rate agreement terms before allowing the loyalty number to be applied automatically
E-folio delivery from hotel properties to expense platforms is inconsistent even within the same chain; have a fallback path for manual folio upload for properties that do not support electronic folio transmission
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