Events - 1.47.0

This SMS will be the same as the one configured in Tables > Brand Setup > Reservation SMS.

In order to enable this feature for a specific Brand, it must be enabled in Tables > Brand Setup > Booking Components:

Manual Payments will only be available for provisional or confirmed bookings in the future with an outstanding balance.

 

Permissions

Permissions to use this feature will be set in Events Admin, under Payments, on a Estate, Brand or Site level, and disabled by default.

Logging a Manual Payment

If a site has the permission enabled there will be an option to 'log a manual payment' in the booking section of the host app:

This will open a form with the following fields:

• Payment Type (Mandatory field)

• Payment Value (Read Only)

• Payment Date (Mandatory field, the date the payment was received)

• Reference Number (Mandatory Field)

• Comment Box (Free Text)

Only 100% of the remaining value of Deposit and Prepayment can be logged.

 

Refunding a Manual Payment

In the Events Host app, a manual payment can be refunded in the payments section of the booking via 'view all payments':

All payments & refunds will sync to Aztec, update the guest portal and trigger any current communication functionality.

An example of the prompt is below:

If Yes is selected, the booking rule change will be saved and update all existing and future bookings.

If No is selected, the booking rule change will be saved and only affect bookings created after the change.

Until the bulk booking update is complete, no further updates can be made to the edited booking rule.

As the update is running, it will be displayed in Events Admin as such:

Please be aware that only changes to the booking rule actions, as listed below, will be applied to existing bookings:

• Changing a deposit or pre-authorisation amount;

• Changing a deposit, pre-order, pre-payment or pre-authorisation due date;

• Adding a new action / requirement;

• Removing an action / requirement.

Updates to booking rule conditions, i.e. changing or adding a menu, will not be applied to existing bookings.

Changes to bookings caused by a booking rule update, will be logged in the booking history:

Previously the Events Admin would have had to re-select the outlet.

If any changes have been made and not saved, this will trigger a warning to the user:

No changes have been made to the actual functionality.