Package Posting Rhythms

Note: When a package with an allowance is attached to a rate code and an in-house reservation exists for this rate code (i.e., the package is attached to the reservation via the rate code), the posting rhythm for the package cannot be changed (the Posting Rhythm field will be unavailable).

The package Posting Rhythms screen is accessed when you select the down arrow on the Posting Rhythms field on the Package Codes setup screen. Use this screen to select the posting rhythm for the package you are configuring.

The default selection is Post Every Night. You may make another posting rhythm choice by selecting a different radio button. Some of the selections may open up fields for you to define particular features for that posting rhythm.

Post Every Night – Post this package charge every night of the stay.

Post on Arrival Night – Post this package charge only on arrival night. When a package that has this posting rhythm configured is attached to a reservation and a begin date is specified to be different than the arrival date, the user will be prompted with a message that states, "The package does not have posting rhythm which falls in the date range selected" and the package will not be attached to the reservation.

Post on Every X Nights Starting Night Y - Post this package charge every X nights, beginning the Y night of stay. You are prompted to enter the start night (e.g., night 1, night 2, night 3, etc.) and how often the posting should be repeated.

Example

A reservation arrives on 04/07/07 and is departing on 04/11/07. A posting rhythm has been configured to post the package Every 3 Nights Starting with Night 3.  So according to the configuration and the reservation dates, the package charge would post to the reservation on 04/09/07 because it is based off of the arrival date of 04/07/07.

Post on Certain Nights of the Week – You are prompted to check mark the days of the week to determine the days to post this package charge.

Post on Last Night – Post this package charge on the last night of the stay only.

Post Every Night Except Arrival Night – Post this package charge on all nights of the stay except the arrival night.

Post Every Night Except Last – Post this package charge on all nights of the stay except the last night.

Do not Post on First and Last Night – Post this package charge on all nights of the stay except the first and last nights of the stay.

Custom Posting Schedule (Based on Stay) – This user defined schedule lets you enter a posting rhythm over a 14-day period, starting with the arrival date, by assigning the day (number) within a guest stay for posting this package price. For example, if you check mark boxes 3, 5, and 7, OPERA will post on the third, fifth and seventh day of the stay and will repeat this posting schedule after the 14th day through the remainder of the stay.

Custom Posting Schedule (Based on Night) - This user defined schedule lets you enter a posting rhythm over a 14 day period. The start and end of the posting period is determined as follows:

If the package is attached to a rate code: The period starts with the date when the rate code to which the package is attached becomes effective for the stay. The period ends with the date of the last night for that rate code (or the last night of the stay if the rate code remains in effect until the departure date).

If the package is attached separately to the reservation: The Begin Date specified on the reservation when the package was attached is the start date for the period. The End Date specified on the reservation when the package was attached is the end date for the period. If no Begin Date and/or End Date are specified when the package is attached to the reservation, the Begin Date is assumed to be the arrival date and the End Date is assumed to be the departure date of the reservation, irrespective of when the package is attached to the reservation.

Example 1

Rate code WKEND is set up to include package code CHAMP, which is configured with the Custom Posting Schedule (Based on Night) posting rhythm, with posting on night 1. A reservation for 4 nights has the following rate codes assigned:

01/01/10 Rate code = CORP

01/02/10 Rate code = CORP

01/03/10 Rate code = WKEND

01/04/10 Rate code = WKEND

When the rate code for WKEND posts on 01/03/10, which is the first night for this rate code, OPERA will post the charge for the CHAMP package. However, the package will not post on the nights of 01/01/10, 01/02/10, or 01/04/10.

Example 2

A BKFST package having the Custom Posting Schedule (Based on Night) posting rhythm of 1st night and 3rd night is attached to a reservation arriving on 01/01/10 and departing on 01/06/10.

If no Begin Date or End Date are specified at the time the package is attached to the reservation, the posting period begin date will be assumed to be 01/01/10. The posting period end date will be assumed to be the departure date for the reservation. The package will post on 01/01/10 and on 01/03/10.

If a Begin Date of 01/02/10 is specified when the package is added to the reservation, the posting period begins on 01/02/10 and ends on 01/06/10. The package will post on 01/02/10 and 01/04/10.

Note: If a rate code having a package configured with Custom Posting Schedule (either Based on Stay or Based on Night) is posted to a reservation, the package will post as if it was applicable every night.

Floating Allowance per Stay – Allow the allowance to be consumed at anytime during the guest stay.

The message "The partially consumed package(s) will be charged to the guest account. Are you sure?" appears at check out under the following conditions.

1. Arrival Date is less than or greater than the current business date.

2. Original Departure Date is less than or greater than the current business date.

3. New Departure Date equals the current business date (early check out)

4. A posting was made against the allowance on that business date (doesn't matter if the posting is less than, equal to, or more than the allowance).

This means that if you have an allowance of $20.00 and you post $11.25 from the interface against the allowance, this posting will be removed from the package ledger and posted to the guest ledger. All allowances for that day will also be removed, as if the package was not attached to the reservation.

Example:

1. Reservation is checked in for 3 nights on a rate code that has a floating allowance package attached.

2. After check in, a posting is made against the allowance (partial or full).

3. Run a night audit.

4. Go to Cashiering>Billing>Post fully against the allowance.

5. Perform an early departure. It is intentional that the message appears as we will be converting any postings against the allowance to the guest ledger, irrespective of whether the allowance was fully or partially consumed.

Note: If a reservation includes multiple rate codes over the course of the stay, and one of the rate codes has a package with a floating allowance per stay, the allowances are not automatically created by OPERA when the reservation transitions to the rate code with the package. Floating allowance per stay is always considered for application to the full stay and such allowances will only be created automatically on the day of arrival.

Ticket Posting - Available when the TIK interface is running and the package has been selected as a Ticket Package, this option will post this package immediately when a successful response is received back from the ticketing vendor.