This article explains why RMS shows the error "The Owner Account Is Not The Same On The Departure Date As It Is On The Arrival Date" when a reservation on an owned Area is saved, and how to resolve it.
Overview
RMS shows this error after the text "Save Res:" when you save a reservation on an owned Area and the owner account on the arrival date is not the owner account on the last night of the stay. A common trigger is extending the Depart Date of a Long Term reservation past the end of an owner contract or past a change of ownership. The error is fixable by correcting the owner contract dates or by ending the reservation at the changeover date.
Applies to: properties using Owner Accounting, for reservations on an Area that has an owner contract.
Before you begin, you need:
- The reservation's Arrive Date and the new Depart Date.
- User access to view the Area's owner contracts, and, for Cause 1, the Allow Users to Modify Owner Contract Tab function on your Security Profile.
How RMS Checks the Owner Account on the Departure Date
When a reservation is saved, RMS compares two things: the owner account on the owner contract that covers the arrival date, and the owner account on the owner contract that covers the last night of the stay. The last night is the day before the Depart Date.
The check compares owner accounts, not owner names or contract numbers. A date with no owner contract counts as having no owner account, so an Area with a gap in its contract dates can also cause the error.
The same check runs when a reservation is moved to another Area or imported, because both of these save the reservation. It does not run at check-out.
Important! The check does not look at charges, receipts or payments. The error is not caused by owner income having been paid out.
Quick Checks
The Owners tab of the Area lists every owner contract, so open it before changing anything.
- In the side menu of RMS, go to Setup > Category/Area.
- Edit the Category that the Area belongs to.
- Select the Room tab, then edit the Area.
- Select Owner Accounting, then the Owners tab.
- Note the From Date, To Date and Acc No of each owner contract. Acc No is the owner account.
Then compare those dates with the reservation's Arrive Date and the day before its Depart Date. If the two dates fall under different contracts with different Acc No values, or one of them has no contract, RMS shows the error. The terms on your screens may differ from this article, for example Room in place of Area.
Possible Causes
Cause 1: The Owner Contract Ends Before the Last Night
The owner contract covering the arrival date has a To Date earlier than the new last night, so the last night has no owner account.
Fix:
- Open the Owners tab for the Area, as shown in Quick Checks.
- Edit the owner contract.
- Change the To date to a date on or after the new last night.
- Select Save/Exit.
- Save the reservation again.
Please Note! Changing the To date may need the Daily Password. Your Primary System Admin logs a Service Request to obtain it. See Daily Password.
Tip! Owner contracts are normally set with a To Date far in the future, for example the year 2126, so that long reservations do not outlast the contract.
Cause 2: The Stay Crosses a Change of Ownership
The new last night falls under the next owner's contract, which has a different owner account, so the reservation can no longer sit under both owners. This includes extending a reservation that arrived under a previous owner into the new owner's contract.
On the changeover date, RMS treats the reservation dates as follows:
- A reservation departing on the new contract's From Date saves, because its last night is the previous day.
- A reservation departing one night later than that fails.
- A reservation arriving on the new contract's From Date saves.
Fix:
- Keep the existing reservation ending on the changeover date, which is the new owner contract's From Date.
- Create a new reservation for the same guest arriving on the new owner contract's From Date.
- On a Long Term reservation, add a Repeat Charge to the new reservation with its own Starting On date.
Please Note! Reservations that cross a settlement date can also be split in two so that each owner receives the correct income. See Record a change of ownership.
Cause 3: A New Contract for the Same Owner
RMS normally gives each later owner contract its own owner account, even when the owner is the same person. A reservation that crosses from one contract to the next can therefore fail even though the owner has not changed.
Fix:
- Where the owner has not changed, extend the To date of the existing contract instead of adding a new contract.
- Where a new contract is needed, end the reservation at the changeover date and create a new reservation, as in Cause 2.
Cause 4: The Reservation Is Moved to a Different Area
RMS checks the owner contracts of the Area the reservation will have after the save, so moving a reservation to an Area whose owner contract does not cover the stay produces the same error.
Fix:
- Open the Owners tab of the new Area, as shown in Quick Checks.
- Check that one owner contract covers the Arrive Date through the last night.
- If the contract ends too early, change its To date as in Cause 1, or choose an Area whose contract covers the stay.
Similar Errors That Are Not This Check
Three other RMS messages relate to owner income that has already been paid, and each comes from a separate check with a different cause:
- "Cannot Be Voided as it has already been paid out", shown when a date change would void a charge already paid to the owner.
- "Cannot Move a Booking After The Owner Income Has Been Disbursed", shown when moving a reservation to another Area.
- "Cannot Reinstate Booking After The Owner Income Has Been Disbursed", shown when unconfirming a departed reservation.
If you see one of these messages, contact RMS Support.
Still Not Working?
If the error continues after working through the causes above, contact RMS Support and include: the property name, the reservation number, the Arrive and Depart dates, the From and To dates of each owner contract on the Area, and a screenshot of the error.
Comments
0 comments
Please sign in to leave a comment.