Add more configurable options with Chargeback / GL Codes.

Description

Customer needs more flexibility with chargeback / GL codes.

Current Workflow

• Booking Type Mapping:

  • Chargeback / GL codes are triggered based on booking type.

  • However, Services/Add-ons are visible for all bookings.

  • Users can select a booking type that doesn’t require codes but still add chargeable Services/Add-ons—bypassing code requirement.

• Resource Type Mapping:

  • Can trigger Chargeback / GL Code only if a chargeable item is added.

  • This is based on Add-On Resource Types, not booking type.

  • Configuration requires selecting codes per Resource Type.

  • For example, if Catering is configured for both Chargeback and GL Code, both are requested, even if only one is needed.

Proposed Workflow

• Option 1: Restrict Services/Add-ons by Booking Type.

  • Only show Services/Add-ons for specific booking types.

  • Similar to how Services/Add-ons are restricted by Interface Type.

• Option 2: Enhance Booking Type Mapping:

  • Add setting: “Only request Chargeback / GL Code if Add-on has a cost.”

  • If enabled:

    • System checks if Add-on has a cost.

    • Then prompts for the appropriate code (Chargeback or GL), based on what’s ticked.

    • If Add-on has no cost, no code is requested—same as current Resource Type Mapping behaviour.

Business Reason:

• Ensures users cannot bypass code requirements by selecting a booking type that doesn’t trigger them.

• Provides flexibility in determining which code (Chargeback or GL) should be applied based on booking context.