ASSD - Ho(s)tel Management Software PMS 3

 

General dates for the house are fixed here. Parts can also be defined in the Guest Database individually.

 

 

Days for Confirmation: Days (on from the issuing date) until a booking contract should be sent back by the future guest.

 

Days Prepayment 1/2/3: Days before arrival: positive numbers, Days on from the issuing date: negative numbers!

 

After each alteration, the amount is newly calculated by the system. This was intended for a complete payment before arrival. Instead of a "Y", a number for calculation of the prepayment can now be entered in field "regcode" in the settings. If the date is closer than the entered number of days before arrival, a prepayment is not necessary. If the date is closer than 14+x days before the next prepayment, it is also been removed. This way, it is avoided that more payments have to be made directly after each other for multi-level systems. If a prepayment of 0% has been stored in the Reference Data, the system automatically calculates the prepayment per person via a fixed amount (article) which can be stored in the meal plan (only prepayment 1 and 2).

 

Prepayment 1/2/3 Calculation: Percentage of the invoice sum. Any changes can be made in Reservations.

 

Credit Limit: Not used.

 

Due days: Deadline for the settlement of an open account after departure. For negative numbers, the deadline is calculated on from the invoice date. Instead of the former due days (number) a formula for calculating the due days can now also be used. As usual, a positive result is added to the departure date whereas a negative result is subtracted from the current date (invoice date). Example for the due date on the last day of the month followed by departure:

 

"GOMONTH(DATE(YEAR(s_reser.departure),MONTH(s_reser.departure),1),2)-1-TTOD(s_reser.departure)".

 

NEW PMS3: The reservation is available as $data and the invoice guest as $guest. You can work with the " ? : " operator.

Example: $guest['GUESTCODE'] == '25' ? 18 : 35

Example for field in reservation: $data['s_reser']['RUSER03']

 

Expire Days: Before arrival (allotment/quota Q) and after creation (option O).

 

Cancel Till Days Before Arrival: Days before arrival (only memo box in correspondence).

 

Days Refresh Original Guest Number: Up to the entered days before arrival, the original number of guests and the actual number are recorded equally. After that, the field original number of guests (Reservation Path) remains unchanged. With this option, short-dated aberrations can be recorded statistically.

 

Cancel Till Weeks Before Arrival: Weeks before arrival (only memo box in correspondence).

 

Cancel Fees Day Before Arrival: Scale determining which percentage has to be paid as cancellation fees up to which date before arrival: e.g. 164 days: 30%, 64 days: 50%, 14 days: 80%. This entry helps to calculate up to three date fields in Reservations and can then be printed on the correspondence for the guest.

 

Additional Due Days After Reminder: Proposal for an extension on from the current date after a reminder has been sent (the due date is excluded from the due date control for so long).