> For the complete documentation index, see [llms.txt](https://developer.siteminder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.siteminder.com/pmsxchange-api/additional-resources/reservation-delivery-for-unmapped-rates.md).

# Reservation Delivery for Unmapped Rates

Receive every confirmed reservation in your PMS, even when the room type or rate plan has no verified mapping.

## What is Reservation Delivery for Unmapped Rates?

**Reservation Delivery for Unmapped Rates** is a PMS-level feature that delivers confirmed reservations to your PMS even when SiteMinder cannot resolve a verified PMS room type or rate plan mapping. Instead of withholding the reservation or guessing at codes, SiteMinder omits RoomTypeCode and RatePlanCode from the message. This ensures the PMS receives every confirmed booking.

By default, reservations with unmapped rates are not delivered to the PMS, and the property receives an email explaining the delivery failure. When this feature is enabled, SiteMinder delivers these reservations without the unresolved mapping codes.

A reservation can contain an unmapped rate in one of two scenarios:

<table><thead><tr><th width="142.642333984375">Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Unmapped channel rate</strong></td><td>The booking channel rate is not associated with any SiteMinder Room Type / Rate Plan, so there is no PMS mapping to resolve.</td></tr><tr><td><strong>Unmapped PMS rate</strong></td><td>The booking channel rate is mapped to a SiteMinder Room Type / Rate Plan, but that room rate has no PMS room type / rate plan code configured.</td></tr></tbody></table>

#### Benefits

* **Full visibility:** property staff can see on the PMS every confirmed booking, not only those with a resolved mapping.
* **Reduced overbooking exposure:** once your PMS processes the reservation and sends updated availability, inventory no longer stays stale for unmapped bookings.
* **Operational simplicity:** properties manage every reservation in the PMS rather than reconciling an explanatory email.

## How It Works

The reservation is delivered using the standard `OTA_HotelResNotifRQ` structure via [Push](/pmsxchange-api/reference/reservations/push.md) or [Pull](/pmsxchange-api/reference/reservations/pull.md). When a RoomStay contains an unmapped rate, the corresponding code attributes are omitted. The remaining reservation data follows the standard pmsXchange reservation structure.

{% hint style="info" %}
Only the code attributes are omitted. The `RoomType`, `RatePlan` and `RoomRate` elements are always present, and `RatePlan` `@EffectiveDate` and `@ExpireDate` are still sent.
{% endhint %}

{% tabs %}
{% tab title="RoomStay with mapped rate" %}
When a verified PMS mapping exists, `RoomTypeCode` and `RatePlanCode` are included as normal.

{% code expandable="true" %}

```xml
<RoomStays>
    <RoomStay>
        <RoomTypes>
            <RoomType RoomType="Double room" RoomTypeCode="RT001"/>
        </RoomTypes>
        <RatePlans>
            <RatePlan RatePlanCode="BAR" EffectiveDate="2026-12-05" ExpireDate="2026-12-07"/>
        </RatePlans>
        <RoomRates>
            <RoomRate RoomTypeCode="RT001" RatePlanCode="BAR" NumberOfUnits="1">
                <Rates>
                    <Rate UnitMultiplier="2" RateTimeUnit="Day" EffectiveDate="2026-12-05" ExpireDate="2026-12-07">
                        <Total AmountAfterTax="112.76" CurrencyCode="AUD" AmountBeforeTax="100.00"/>
                    </Rate>
                </Rates>
            </RoomRate>
        </RoomRates>
        <!-- ... other elements and attributes have been omitted for brevity ... -->
    </RoomStay>
</RoomStays>
```

{% endcode %}
{% endtab %}

{% tab title="RoomStay with unmapped rate" %}
When no verified PMS mapping exists, `RoomTypeCode` and `RatePlanCode` are omitted.

{% code expandable="true" %}

```xml
<RoomStays>
    <RoomStay>
        <RoomTypes>
            <RoomType RoomType="Double room"/> <!-- RoomTypeCode omitted -->
        </RoomTypes>
        <RatePlans>
            <RatePlan EffectiveDate="2026-12-05" ExpireDate="2026-12-07"/> <!-- RatePlanCode omitted -->
        </RatePlans>
        <RoomRates>
            <RoomRate NumberOfUnits="1"> <!-- RoomTypeCode and RatePlanCode omitted -->
                <Rates>
                    <Rate UnitMultiplier="2" RateTimeUnit="Day" EffectiveDate="2026-12-05" ExpireDate="2026-12-07">
                        <Total AmountAfterTax="112.76" CurrencyCode="AUD" AmountBeforeTax="100.00"/>
                    </Rate>
                </Rates>
            </RoomRate>
        </RoomRates>
        <!-- ... other elements and attributes have been omitted for brevity ... -->
    </RoomStay>
</RoomStays>
```

{% endcode %}
{% endtab %}
{% endtabs %}

## Multiple RoomStays Reservation

The behaviour applies separately per `RoomStay` element. If one room stay in a reservation has a valid mapping and another does not, only the unmapped room stay omits the codes. The mapped room stay is delivered normally.

{% code expandable="true" %}

```xml
<RoomStays>
    <RoomStay> <!-- RoomStay with mapped rate -->
        <RoomTypes>
            <RoomType RoomType="Double room" RoomTypeCode="RT001"/>
        </RoomTypes>
        <RatePlans>
            <RatePlan RatePlanCode="BAR" EffectiveDate="2026-12-05" ExpireDate="2026-12-07"/>
        </RatePlans>
        <RoomRates>
            <RoomRate RoomTypeCode="RT001" RatePlanCode="BAR" NumberOfUnits="1">
                <!-- ... other elements and attributes have been omitted for brevity ... -->
            </RoomRate>
        </RoomRates>
        <!-- ... other elements and attributes have been omitted for brevity ... -->
    </RoomStay>
    <RoomStay> <!-- RoomStay with unmapped rate -->
        <RoomTypes>
            <RoomType RoomType="Double room"/> <!-- RoomTypeCode omitted -->
        </RoomTypes>
        <RatePlans>
            <RatePlan EffectiveDate="2026-12-05" ExpireDate="2026-12-07"/> <!-- RatePlanCode omitted -->
        </RatePlans>
        <RoomRates>
            <RoomRate NumberOfUnits="1"> <!-- RoomTypeCode and RatePlanCode omitted -->
                <!-- ... other elements and attributes have been omitted for brevity ... -->
            </RoomRate>
        </RoomRates>
        <!-- ... other elements and attributes have been omitted for brevity ... -->
    </RoomStay>
</RoomStays>
```

{% endcode %}

## What Your PMS Should Do

SiteMinder delivers the reservation without codes because it cannot know the correct room type or rate plan. Your PMS cannot know either, so the reservation needs to be created, flagged, and then resolved by the property. Follow this sequence for every reservation that arrives with omitted codes.

1. **Create the reservation and confirm delivery:** Create the reservation in the PMS and return `<Success/>` with the PMS reservation ID, as for any other reservation.
2. **Hold it in a clearly flagged state:** Place the reservation in a state that is visibly pending review, such as an unassigned or "needs attention" status. Avoid silently attaching it to a real room type or rate, where the property may not notice it is wrong.
3. **Notify the property:** Alert property staff that the reservation needs a room type and rate plan, and make it easy to find. Once the feature is enabled SiteMinder no longer sends the "PMS notification failed" email for unmapped rates.
4. **Keep availability accurate:** After the property resolves it, send the corresponding `OTA_HotelAvailNotifRQ`, so SiteMinder inventory reflects the booking.

{% hint style="warning" %}
**Do not leave the reservation unresolved.** The booking is confirmed to the guest. If staff are not alerted, it can sit in the PMS with no room assigned and the property can overbook or miss the arrival.
{% endhint %}

## **Feature Enablement**

This feature is enabled at the PMS level and applies to all properties connected through your integration. It cannot be enabled for selected hotels only.&#x20;

To request this feature, contact the Partner Integrations team through [Partner Contacts](https://www.siteminder.com/partners-contact/). Your integration must be re-certified for this behaviour before it can be enabled.&#x20;

{% hint style="success" icon="sparkles" %}

## Still have questions?

Use the <i class="fa-gitbook-assistant">:gitbook-assistant:</i> **Ask** button at the top of the page to chat with our AI assistant — it can help you navigate the guide, understand requirements, and troubleshoot issues.

If you need more support, visit [Integration Support](/integration-support/integration-support.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.siteminder.com/pmsxchange-api/additional-resources/reservation-delivery-for-unmapped-rates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.