If the booking is paid at the front end (the web) using retail basket processes, the sale is sent to the Business Central back end using the standard Commerce flow of web basket sales using the Customer Sales Order mechanism.
The sale would be assigned through the Customer Order Header and Customer Order Lines tables in Business Central, and the Activity Reservation will be assigned the payment status Fully Paid, and the transaction type Web. The transaction number would be the Customer Order Document ID, and it can be viewed (drill-down) from the Activity Reservation card. The Customer Order is then normally posted either to a sales invoice or a POS sale (depending on the e-commerce settings in Business Central). The order, however, does not need to be posted to be valid as a payment confirmation. This is because the Bookings module is subscribing to the insert of Customer Order lines to trigger the payment validation. The Customer Order Lines have a field, Order Reference, which will contain the Activity Reservation No. when the line is a charge for an activity reservation.
Eventually, the customer order entries will be transferred to Posted Customer Order by the standard posting processes, which will create the relevant revenue and other G/L entries.
IMPORTANT: When the web front end assigns the Activity Number (Booking reference) to the basket lines to be passed to Business Centrall (Commerce) as Order Reference, the Activity No. value will be prefixed with “ACT:”. This allows the payment confirmation mechanism in the Bookings module to identify the Order Reference correctly as an Activity No. value. In the future, other prefix settings will be used to differentiate transaction types.