Package Allowance Consumption for No Post Reservations

Note: When the application parameter mentioned in this help topic is active, this functionality does NOT reference the value defined for the Postings option on the IFC Postings Tab.

When the Cashiering>CONSUME ALLOWANCE WHEN NOPOST OR POST STAY FLAG application parameter is set to Y and when an In House reservation has the No Post check box selected for it that has a package allowance available for consumption, then postings from an interface, or manually from a user, is posted against the package allowance transaction code. Thus, allowing for the package allowance consumption to occur.

Package allowance consumption for No Post, In House reservations can occur only up to the allowance balance when postings are from an interface. Should this occur where the posting from the interface exceeds the total allowance amount, the posting will not take place and allowance will not be consumed. But if the postings are manually completed by a user and the allowance consumption goes over the allowance balance, then an Overage will be generated.

For Example

Interface Posting
A package attached to a No Post reservation has an allowance of 25.00 and a transaction is made from the interface for 35.00. The transaction of 35.00 will not be posted to the No Post reservation as it exceeds the allowance of 25.00.

Manual Posting
A package attached to a No Post reservation has an allowance of 25.00 and a transaction is manually entered by a user for 35.00. The transaction of 35.00 will be posted to the No Post reservation that will consume the 25.00 allowance and create an overage of 10.00.

There will be no prompt / question for user regarding posting to a No Post reservation and posting against allowance. Since the parameter is active, OPERA will always attempt to first consume the allowance.

Note: When an interface posting consists of multiple transactions that refer to multiple transaction codes in OPERA, in order for OPERA to accept the entire check/set of transactions and post against allowance for a reservation with No Post flag, each of the individual transaction codes must have an allowance in OPERA or setup as alternates for the transaction code that has the allowance. If the total of all the postings from interface on one check exceeds the available allowance, OPERA will reject the entire posting from interface even if one of the transaction codes has an allowance. So essentially this will behave as all or none process where OPERA will accept the entire check/set of transaction from interface and consume allowance or reject an entire check as no Overage can be posted to a reservation with No Post flag when posting is from an Interface.