id int64 0 199 | golden_business_rule stringlengths 89 4.82k | finetuned_prediction stringlengths 107 4.51k | finetuned_meteor float64 0.04 0.96 | finetuned_bertscore_p float64 -1.04 0.92 | finetuned_bertscore_r float64 -0.28 0.89 | finetuned_bertscore_f1 float64 -0.62 0.9 |
|---|---|---|---|---|---|---|
0 | # Business Rules: Monthly Profit Report
## Rule 1: Monthly Report Frequency
The Monthly Profit Report must be generated for each calendar month.
## Rule 2: Report Scope Based on Contract
- If a **contract exists** for a unit, the Monthly Profit Report **must be calculated per contract**.
- If **no contract exists**, ... | # Business Rules for Monthly Profit Report
## Accommodation and Channel Revenue Rules
- The accommodation price for a booking must be calculated as the sum of the accommodation price value and any channel promotions or discounts applied to the booking.
- The channel total for a booking must be calculated as the sum of... | 0.207249 | -0.221511 | -0.05284 | -0.136804 |
1 | # Business Rules: Booking Extension
## Rule 1: Split Bookings
A booking that has been **split** must **not be extended**.
## Rule 2: Cancellation Status
A booking with status **"Cancelled"** or **"Scheduled for Cancellation"** must **not be extended**.
## Rule 3: No-Show Status
A booking with status **"No Show"** mu... | - Only one booking may be extended at a time for a given unit and date range.
- A booking cannot be extended if it is scheduled for cancellation or has been canceled.
- A booking cannot be extended if it has already been extended to a different date.
- A booking cannot be extended if it is a no-show booking.
- A bookin... | 0.157427 | 0.287047 | -0.174511 | 0.047137 |
2 | # Business Rules: Booking Splitting
## Rule 1: Split Date Validity
The split date must be selected and must fall after the booking's check-in date and before its check-out date.
## Rule 2: Required Fields for Splitting
When splitting a booking, the following must be selected:
- Property
- Unit Type
- Unit
## Rule 3:... | # Business Rules for Booking Split
## 1. Eligibility and Permissions
- No user may split a Booking if they do not have access to it.
## 2. Splitting Conditions
- A Booking may only be split if it is not finalised.
- A Booking may only be split if the split date is between the booking’s arrival and departure dates, ex... | 0.287219 | 0.292679 | 0.211484 | 0.252978 |
3 | # Business Rules: User and Staff Management
## Rule 1: Unique Email Address
A user's email address must be unique across all users, landlords (owners), and suppliers (companies). Duplicate emails are not allowed.
## Rule 2: Valid Role Assignment
Each role assigned to a staff member must match a valid role defined in ... | # Business Rules for Staff Creation
## User Registration Rules
- Each staff member must have a unique email address.
- A staff member may only be created if there is no existing user registered under that email address.
## User Authentication and API Keys
- Each user must have at least one associated API key.
- When ... | 0.243831 | 0.321227 | 0.011449 | 0.16299 |
4 | # Business Rules: Rate Rule Currency Validation
## Rule 1: Currency Matching for Rate Plans
If a rate rule applies to specific rate plans and includes a currency, the currency must match the currency of each associated rate plan.
## Rule 2: Currency Requirement for Fixed Amount Adjustment
A currency must be specified... | # Business Rules for Rate Rule Currency Validation
## Rule 1: Currency Consistency per Rate Plan
- If a Rate Rule specifies a currency and is not applied to all rate plans, the currency of each associated rate plan must match the currency specified in the Rate Rule.
## Rule 2: Currency Requirement for Fixed Rate Chan... | 0.381545 | 0.550264 | 0.496929 | 0.524239 |
5 | # Payment and Contact Integration Business Rules
- Each contact must be linked to its corresponding staff member.
- Each PayPal integration must include a client secret.
- Each PayPal integration must include a client ID.
- When a deal requires a custom gateway deposit, the landlord’s primary integration must se... | # Business Rules for PayPal Integration
1. A PayPal integration must be associated with the organization it serves.
2. The PayPal integration must use PayPal’s test environment if the integration is configured to use a test environment.
3. The PayPal integration must use PayPal’s live environment if the integration is... | 0.374025 | 0.180901 | 0.168082 | 0.175825 |
6 | # Business Rules
## Contact Rules
- Each contact must be linked to its corresponding staff member.
## Tax Rules
- Each Tax Schema must have a defined rate; if no rate exists, the rate must be considered 0.
## Deal Rules
- Each deal with a custom investor gateway must be associated with that investor.
## Custo... | # Business Rules for Finance and Accounting
## Tax Rate Rules
- Each tax schema must have a defined tax rate.
## Investor Custom Gateway Rules
- Only invoices associated with an investor who has a custom integration gateway may be selected for review.
## Invoice Print Setting Rules
- Each customer invoice must have ... | 0.366427 | 0.442261 | 0.360148 | 0.401861 |
7 | This snippet includes only technical behavior and implementation details; no business rules apply.
| # Business Rules for Nightly Detail Tax Component Creation
- Only nightly tax detail component creation processes may be triggered when a financial message queue is active and contains at least one valid financial message queue identifier.
- A nightly tax detail component may only be created if the corresponding finan... | 0.219788 | -0.103538 | 0.068615 | -0.017308 |
8 | # Expense Excel Business Rules
## Deletion and Transfer Restrictions
- No Expense Excel record may be deleted if it contains any lines in the "Transferred" state.
- No Expense Excel record may be transferred if it contains any lines in the "Error" or "Warning" state.
- No Expense Excel record may be transferred if... | # Business Rules for Expense Excel Processing
## 1. Line Deletion and Transfer
- An expense Excel file may only be transferred if none of its lines have an "Transferred" error state.
## 2. Line Processing and Status
- An expense Excel file may only be processed if at least one of its lines has an "OK" error state or ... | 0.455028 | 0.225674 | 0.3696 | 0.297793 |
9 | # Rate Rule Business Rules
## 1. Priority
- Each rate rule must be applied according to its assigned priority, with higher-priority rules applied before lower-priority rules.
- Only rate rules that are not disabled may be applied.
## 2. Rate Rule Actions
- Each rate rule that changes a rate must adjust the price ... | # Business Rules for Rate Rule Calculations and Applications
## Rate Rule Application Priorities
Each rate rule must have a defined priority order. When rate rules are updated, the system must re-prioritize all rate rules according to their defined priorities.
## Rate Rule Activation
A rate rule may only be activated... | 0.27048 | 0.090532 | -0.048276 | 0.021745 |
10 | # Agency Uniqueness Rules
- No two agencies may share the same Name.
- No two agencies may share the same Code.
| # Agency Creation Business Rules
- Each agency must have a unique name and code in the system.
- An attempt to create an agency with a name or code that already exists must result in a conflict error. | 0.352612 | 0.304477 | 0.404063 | 0.354853 |
11 | # LTSA Business Rules
## 1. Title Summary Rules
- A Title Summary may only be retrieved for a valid Parcel Identifier (PID).
## 2. Title Order Rules
- Each Title Order must be based on a Title Summary issued by LTSA.
- Each Title Order must include the Title Number provided by LTSA.
- Each Title Order must incl... | # Business Rules for LTSA Order Processing
- An LTSA order must be created for each parcel using the appropriate title number and land title district code.
- The order must include all necessary information as per LTSA guidelines, including the parcel identifier, title number, land title district code, and any require... | 0.25172 | 0.280678 | 0.165467 | 0.22369 |
12 | # Notification Update Rules
- Each CHES status must correspond to one valid notification status.
- A notification’s status must not be updated if the CHES status is unrecognized.
- Notifications in Pending or Accepted status may be updated with new status from CHES.
- Notifications in final statuses (Cancelled, ... | # Business Rules for Notification Management
## Notification Status Rules
- Each notification must have a status indicating its current state.
- The status of a notification must be updated according to the corresponding status defined in the notification system.
## Notification Processing Rules
- All notifications i... | 0.451193 | 0.283196 | 0.212207 | 0.24868 |
13 | # Property Business Rules
## Property Access and Visibility
- Users may only view a property if they are the owner or have been explicitly granted viewing rights.
- Only properties marked as published may be made visible to users.
## Property Information
- Each property must display the total number of associated... | # Property Search and Viewing Business Rules
- Only properties belonging to the current user may be viewed or searched for by users with appropriate permissions.
- Each property must have its own unique URL, and users may redirect to the canonical URL of a property.
- Users may browse published properties only if they... | 0.407415 | 0.342111 | 0.279791 | 0.311884 |
14 | # Similar Properties Business Rules
- Similar properties may only be suggested if the feature is enabled.
- Similar properties should be identified primarily within the same neighborhood as the current property, when applicable.
- If no similar properties exist in the same neighborhood, similar properties should b... | # Business Rules for Similar Property Retrieval
- Similar property retrieval is only available when the module is enabled.
- When a property has no matching results within its assigned area (small or large), the system must search across all areas where the property could be located.
- Similar property retrieval is li... | 0.268001 | 0.304336 | 0.207457 | 0.256652 |
15 | # User Registration Business Rules
- Existing users may not register again.
- User registration is only allowed when registration is enabled.
- A successfully registered user must have a profile created and linked to their account.
- A successfully registered user must receive a confirmation email.
- A usernam... | # Business Rules for User Registration
- Only users with the "Anyone Can Register" option enabled may register.
- Users must agree to the terms and conditions before registering.
- Passwords must be at least 10 characters long and不得超过4096字符长.
- Each user must create a profile upon registration. | 0.36346 | 0.190706 | 0.190212 | 0.191774 |
16 | # Business Rules for Channel Manager Integration
## Property and Unit Type Synchronization
- Each property may be synchronized with the channel manager to establish or update its external representation.
- Each unit type may be synchronized with the channel manager to establish or update its external representation.
... | # Business Rules for Channel Manager and Property Synchronization
There are no business rules in the provided code segments; all statements describe technical implementation details for property and channel management without defining any business policies or domain rules. | 0.03832 | 0.114872 | -0.265596 | -0.08106 |
17 | # Business Rules for Expense Excel Import and Transfer
## 1. Expense Excel Processing Workflow
- An expense Excel file must be validated before processing.
- The status of an expense Excel file must be set to "PROCESSING" during transfer and updated to "OK" upon successful completion.
## 2. Expense Line Date Defaults... | # Business Rules for Expense Import
## 1. Required Information
- Each expense line must have a valid date.
- Each expense line must have a start date.
- Each expense line must have an end date.
## 2. Supplier Assignment
- Each expense line must be assigned to a supplier.
- If a supplier cannot be found for a ... | 0.304581 | 0.333742 | 0.267937 | 0.301768 |
18 | # Business Rules for Occupancy Rate Calendar Navigation
1. Only active properties belonging to the current organization must be considered when generating occupancy rate calendar navigation options.
2. Each city with at least one eligible property must be represented as a selectable option in the occupancy rate calend... | # Business Rules for Rate Calendar Navigation
1. Only properties that are active must be included in the rate calendar navigation.
2. Only properties belonging to the current organization may be displayed in the navigation.
3. Each property's navigation entry must be grouped by city.
4. Each property's navigation entr... | 0.513043 | 0.637642 | 0.503893 | 0.570651 |
19 | # Business Rules for Company Details Submission
1. The company name, address, city, postal code, region, and country must be provided for each organization.
2. The company’s contact information must include a valid email address and phone number.
3. The company’s website address must be included if available; otherwis... | # Business Rules for Company Details Filling
- Each company detail fill must be associated with the correct user. | 0.071855 | 0.402276 | -0.144058 | 0.115799 |
20 | # Business Rules for Sending Notifications
## Property Selection Rules
- Only properties marked as favorites within the current organization may be selected for notification purposes.
## Automated Message Selection Rules
- Only automated messages that are marked as favorites, not archived, and belong to the current o... | # Business Rules for Notification Sending
*No business rules are defined for this section. The provided code only contains configuration and presentation logic for notification items.* | 0.140351 | 0.080882 | 0.045385 | 0.064592 |
21 | # Business Rules for Customer Invoice Management
## Access and Authorization Rules
1. A user must have appropriate permissions to view or download a customer invoice.
2. A user must have appropriate permissions to post a customer invoice to Xero.
3. Only authorized users may void a customer invoice from Xero.
## Invo... | # Business Rules for Customer Invoice Processing
## Invoice Generation and Downloading
- Each customer invoice must be generated for every booking associated with it, even if the invoice lines are empty.
- Only users with the appropriate view permission may download customer invoices.
## Invoice Voiding and Re-Genera... | 0.266576 | 0.353858 | 0.240175 | 0.297539 |
22 | # Business Rules for Stripe Configuration
## 1. Stripe Secret Key Usage
- Organizations with a Stripe integration must use the appropriate secret key based on whether the integration is for production or testing.
- If no specific integration is provided, the organization must use its default Stripe configuration.
... | # Business Rules for Stripe Integration Secret and Publishable Key Retrieval
## Secret Key Rules
- The Stripe secret key must be retrieved for the organization if the integration is associated with Stripe and:
- The integration has a valid Stripe account (including both live and test accounts);
- The organization ... | 0.395677 | 0.12009 | 0.251561 | 0.186309 |
23 | # Business Rules for Booking Task Management
- When a booking is inserted, the dates of tasks related to both the previous and current bookings must be updated accordingly.
- When a booking is canceled, all tasks associated with that booking must be recalculated. If the booking was an extension of another booking, tas... | # Business Rules for Booking Tasks
## 1. Booking Task Synchronization
- When a booking is **updated**, the previous and current booking task dates must be synchronized.
## 2. Booking Task Recalculation on Cancellation
- When a booking is **canceled**, all relevant tasks must be recalculated for the booking and its ex... | 0.56628 | 0.231013 | 0.455273 | 0.341837 |
24 | # Business Rules for Property Unit Selection
*No business rules are defined for Property Unit Selection in this code. The implementation only concerns technical configuration and user interface behavior.* | # Business Rules for Property Unit Selection
- Only property units may be selected as options in the property unit list. | 0.300685 | 0.356787 | 0.186291 | 0.271325 |
25 | # Business Rules for Booking Income Report Export
The following rules define the required data elements and structure for each exported booking income report record.
## Booking and Channel Information
- Each booking income report record must include the booking ID and booking number.
- Each record must specify the c... | # Business Rules for Booking Income Grid Export
- Each booking income record must specify the booking ID, booking number, and related booking details including guest information, property name, unit name, arrival date, departure date, booking status, number of guests, total nights, and accommodation price.
- Each book... | 0.381016 | 0.409237 | 0.199489 | 0.303393 |
26 | # Business Rules for Automated Message Trigger Rules
## Condition Assignment and Management
- When updating automated message trigger rules, all existing conditions associated with the message must be removed before assigning new conditions.
- Each automated message may have multiple conditions and timing rules assign... | # Business Rules for Automated Message Triggering
## 1. Condition Generation
- Each automated message must allow users to define one or more conditions that must be met for a notification to be sent.
## 2. Condition Types
- Users must be able to specify conditions of various types, including:
- Specific dates ... | 0.155851 | -0.310923 | 0.033133 | -0.143197 |
27 | # Business Rules for Rentals United Manager
*No explicit business rules are defined at the business policy level in this section. All logic pertains to form structure, field requirements, and presentation details.* | # Business Rules for Rentals United Management
- Each rental booking must be associated with a valid brand and channel rate log.
- Each availability log entry must be linked to a specific location and time period.
- Each rate log entry must include the relevant channel and its associated charges.
- Each location assig... | 0.270005 | -0.041214 | 0.155358 | 0.056676 |
28 | # Business Rules for Booking Order Line Breakdowns
## 1. Addon Line Classification
- Each booking order line breakdown must be classified as either an addon line or a main line based on whether it includes an addon.
## 2. Date Range Relevance
- Addon breakdowns must correspond to the relevant date range for the... | # Business Rules for Booking Order Line Breakdown
1. Only breakdowns associated with add-ons for the specified booking may be retrieved.
2. Only breakdowns with a date range falling within the requested period may be retrieved.
3. Only breakdowns with the main line not linked to a date may be retrieved for a given boo... | 0.345036 | 0.161892 | 0.036916 | 0.10009 |
29 | # Business Rules for Messaging API Push Normalization
- Only message line entities may be processed for outgoing messages.
- Each outgoing message must include the response content in the message body.
- If a message includes attachments, each attachment must include its file name and the file content encoded in b... | # Business Rules for Messaging API Message Normalization
- Each messaging API message must be identified by its unique message ID.
- Each messaging API message must include its body as the message content.
- Each messaging API message may include one or more attachments. Each attachment must include a name and its con... | 0.495901 | 0.438972 | 0.486657 | 0.463583 |
30 | # Business Rules for Key Place Profile Management
## Ownership Rules
- Each new Key Place Profile must have an assigned owner.
- The owner of a newly created Key Place Profile must be the current organization user at the time of creation.
## Access Control Rules
- Users must have the appropriate permissions to view, ... | # Business Rules for Key Place Profile Management
- Each key place profile must have an owner assigned when created.
- When a key place profile is updated and all required fields are valid, the system must save and redirect to the detailed view of the profile.
- A new key place profile may be created through a widget ... | 0.342023 | 0.429967 | 0.373645 | 0.402628 |
31 | # Business Rules for Payment Collection Metadata
- All payment and refund collections must include metadata that uniquely identifies each collection.
- The metadata must indicate the total number of items in the collection.
| # Business Rules for Payment Metadata Normalization
- Each payment collection must include metadata containing a unique identifier.
- When the payment collection is paginated, metadata must include the total number of items, the current page, the last page, and the number of items per page.
- For non-paginated collect... | 0.61755 | 0.414456 | 0.640426 | 0.52588 |
32 | # Business Rules For Booking Normalizer
## Guest Rules
- Each booking must calculate total guests as the sum of adult guests and child guests.
- Each lead guest must meet the property’s minimum age requirement.
- No guest may be accepted when the guest is below the minimum allowed age.
- Each booking must require docu... | # Business Rules for Booking Normalization
The following rules define the business requirements and constraints for booking normalization:
1. **Security Deposit and Integration**
- The security deposit status and link must be available only when the booking integration is active.
2. **Guest Information**
- The... | 0.212397 | -0.088469 | 0.05248 | -0.017346 |
33 | # Business Rules for Sending Transaction Data to Google
## Execution Rules
- The transaction data synchronization process must only run if the application URL is set to "https://hub.zeevou.com".
- The process must not run concurrently; only one instance may execute at a time.
## Data Transmission Rules
- For each Goo... | # Business Rules for Sending Transaction Data to Google
1. Each live hotel account connected to Google must have its transaction data sent to Google.
2. For each eligible hotel account, the transaction data must be sent to Google using the appropriate contents (property, promotions, taxes, and fees).
3. Each message s... | 0.290736 | 0.495237 | 0.221291 | 0.355762 |
34 | # Business Rules for Booking Retrieval via PriceLab Service
## 1. Access Control
- Only users with valid credentials (username and API key) may retrieve booking data.
## 2. Mandatory Parameters
- The following parameters are required to retrieve bookings:
- **listing_id** (unit type identifier)
- **start_date**
... | # Business Rules for Booking Retrieval
1. Each booking must be associated with a booking date, number of nights, total cost, status, and currency.
2. Only bookings dated within the specified start and end dates may be retrieved.
3. Only bookings for the requested unit type may be retrieved.
4. Only bookings belonging ... | 0.244855 | 0.369492 | -0.109365 | 0.120165 |
35 | # Business Rules for Property Normalization
## Ownership and Identification Rules
- Each property must have an owner assigned, and the owner's unique identifier must be retrievable.
- Each property must have a location assigned, and the location's unique identifier must be retrievable.
## Unit and Rate Plan Rules
- T... | # Business Rules for Property Normalization
- Each property's description must be extracted and included in its normalized form.
- Each property's owner must be assigned using the owner defined in the property's associated brand.
- Each property's location must be assigned using the location assigned to the property's... | 0.240659 | 0.396106 | 0.086378 | 0.237842 |
36 | # Business Rules for Property Availability
- Each property must be identified and exist before availability can be determined.
- Availability data must be provided only for dates that are valid and within the specified range.
- The number of guests must not exceed the maximum capacity defined for each unit type.
- Onl... | # Business Rules for Property Availability
1. Availability must be calculated for dates within the specified range.
2. Availability must only include units that are active and have an orgin limit booking engine.
3. Availability must not exceed the maximum capacity of the unit.
4. Availability must meet the minimum num... | 0.327236 | 0.359747 | 0.274367 | 0.317818 |
37 | # Business Rules for Nightly Detail Financial and Occupancy Reporting
## 1. Currency Determination
- All financial metrics in nightly detail reports must be calculated and displayed using the property's default currency.
- If a property's default currency is not set, the organization's default currency must be used.... | # Business Rules for Nightly Detail Report
## 1. Organization and Currency Configuration
- Each organization must have a default currency assigned.
- If no default currency is found for an organization, the currency must be set to the organization's default currency.
## 2. Revenue Calculation
- Revenue must be calcul... | 0.30515 | 0.50055 | 0.287237 | 0.392743 |
38 | # Business Rules for Booking Creation and Order Management
## 1. Booking Creation and Assignment
- Each booking must be associated with a property, unit type, and, if applicable, a specific unit.
- The booking must record arrival and departure dates and times, guest counts (adults, children, infants), and booking stat... | # Business Rules for Booking Creation and Management
## 1. Booking Creation Requirements
- Each booking must be associated with an arrival date and a departure date.
- Each booking must specify an arrival time and a departure time.
- Each booking must include an accommodation price and a tax amount.
- Each booking ma... | 0.392135 | 0.400074 | 0.341816 | 0.371806 |
39 | # Business Rules for Property Unit SU Synchronization
1. A property unit can only be disconnected from the SU system if the property is SU-enabled and both the property and unit type have valid SU Staah IDs.
2. If a property unit is disconnected, its status must be updated to "Deactivated" in the SU system.
3. If a pr... | # Business Rules for Property Unit SU Synchronization
- If a property unit is to be deactivated and the associated property unit type has SU enabled for the organization, the system must attempt to disconnect the property unit from SU channels.
- If SU connection is not possible due to an existing SU map, the deact... | 0.306301 | 0.459503 | 0.327323 | 0.393577 |
40 | # Business Rules for Message Insertion and Update
- Each newly created message must be included in the communication processing workflow.
- Each updated sent SMS message must remain included in the communication processing workflow.
| # Business Rules for Message Processing
- Each new message insertion must be processed as a scheduled action.
- Each update to a message must be processed as a scheduled action only if it is a SendSms update.
- Each newly created conversation must be associated with the correct contact.
- Each new email address or pho... | 0.540378 | 0.335355 | 0.474642 | 0.405062 |
41 | # Business Rules for Payment Records
## Unallocated Payments
- Only payments created within the last six months may be considered for unallocated payment review.
- Only payments with a 3D state of "OK" may be considered for unallocated payment review.
- Only payments that are linked to a booking order may be consider... | # Business Rules for Unallocated Payments and Guest Mismatches
1. All payments with a three-state status of "OK" and a booking order must be considered for payments that are not allocated.
2. Payments must not be included if they involve a guest who does not match the booking order's specified guest.
3. Payments must ... | 0.258376 | 0.258334 | 0.150583 | 0.205185 |
42 | # Business Rules for Bill Cost Allocation
## General Allocation Rules
1. Each bill cost allocation must be linked to its corresponding bill, organization, owner, and property unit.
2. If a bill is associated with a booking, the cost allocation must also reference that booking and its investor deal.
3. If no investor d... | # Business Rules for Bill Cost Allocation
## Booking and Cost Allocation Rules
1. Each batch expense associated with a bill must be allocated to the appropriate bookings in accordance with the bill’s defined allocation strategy.
2. For each booking involved in a batch expense, the cost allocation must be determined b... | 0.26647 | 0.360286 | 0.213546 | 0.287042 |
43 | # Business Rules for Unit Type Deletion
- A unit type must be validated for removal before it can be deleted.
- If a unit type cannot be removed due to business constraints, the deletion must be rejected with an appropriate error message. | # Business Rules for Unit Type Management
- No business rules are defined at the business policy level in this section. All logic pertains to form configuration, data binding, or presentation details. | 0.208972 | 0.235205 | 0.217466 | 0.227577 |
44 | # Business Rules for Xero Application Integration
1. Only organizations without an existing Xero integration may create a new integration.
2. Each organization may disconnect its Xero integration at any time.
3. No organization may have more than one active Xero integration.
4. Each organization must have its Xero ... | # Business Rules for Xero Application Integration
- Each Xero integration must be associated with a valid authentication code.
- Each Xero integration must be linked to the correct organization.
- Users may disconnect their Xero integration from the system by deleting the corresponding connection.
- The status of each... | 0.418284 | 0.47332 | 0.481189 | 0.478101 |
45 | # Business Rules for Booking Bedding Configuration
## Booking Bedding Configuration Rules
1. Each booking must have a bedding configuration that can be retrieved using the booking ID.
2. If a booking does not have a specific bedding configuration, the default bedding configuration of the associated unit type must be ... | # Business Rules for Booking Bedding Configuration
## Booking Bedding Configuration Rules
1. Each booking must have an associated bedding configuration.
2. The bedding configuration for a booking must be a structured representation containing information about each room type, its ID, label, and list of beds.
3. If a ... | 0.61552 | 0.644865 | 0.657482 | 0.651733 |
46 | # Business Rules for Unit Type Rate
- Each Unit Type Rate must have an owner.
- When the "override rate rules" setting is enabled or disabled for a Unit Type Rate, the same setting must be applied to all of its rate lines.
- Each rate line added to a Unit Type Rate must inherit the current "override rate rules" setti... | # Business Rules for Unit Type Rate Log
- Each unit type rate log must have a list of associated rate log lines.
- Each rate log line added to a unit type rate log must be associated with that unit type rate log.
- When an override rate rules flag is set for a unit type rate log, all associated rate log lines must als... | 0.622615 | 0.417862 | 0.495811 | 0.457439 |
47 | # Business Rules for Review Creation
## 1. Review Property and Unit Assignment
- When a Review is created and linked to a Booking, the Review must inherit the Property, Unit Type, and Unit from the associated Booking if these fields are not already set.
## 2. Review Origin and Organization Assignment for Booking Eng... | # Business Rules for Review Creation
## Review Association Rules
- Each review must be linked to a booking.
- Each review must be linked to a property.
- Each review must be linked to a unit.
## Origin and Organization Rules
- When a review is created as a booking engine operation, the review must have the origin set... | 0.486637 | 0.395993 | 0.393668 | 0.395814 |
48 | # Business Rules for Accounting Schema Defaults
- The default accounting schema **cannot be deleted**. | # Business Rules for Accounting Schema Default Removal
- A default accounting schema cannot be removed; removal actions must only target non-default schemas.
- All removal operations must comply with applicable permissions and error handling. | 0.645712 | 0.335761 | 0.567414 | 0.449997 |
49 | # Business Rules for Booking Early Checkout
## Early Checkout Rules
- Each early checkout event must be associated with a specific booking.
- An early checkout event must record both the original departure date and the new (earlier) departure date.
- The new departure date must be earlier than the original departure ... | # Business Rules for Booking Early Checkout
- Each booking early checkout event must record the booking, the new departure date, and the old departure date.
- The departure date for the booking must be updated to the new departure date when an early checkout occurs. | 0.52788 | 0.66747 | 0.55834 | 0.612996 |
50 | # Business Rules for Tax Rate Management
## Tax Rate Application Rules
- A tax rate may only be applied to rate plans that exist and are valid.
- When applying a tax rate, only valid and existing rate plans must be associated with the tax rate.
## Tax Rate Deletion and Archiving Rules
- If any bookings exist that are... | # Business Rules for Tax Rate Management
## Tax Rate Plan Rules
- Each tax rate may have one or more associated Staah Rate Plans.
- A tax rate may have one or more associated Tax Components.
- When a tax rate is deleted or archived, all associated Tax Components and Staah Rate Plans must be removed from the system.
#... | 0.464027 | 0.355379 | 0.340913 | 0.349195 |
51 | # Business Rules for Cancellation Policy Terms
1. Each cancellation policy term must define the time intervals after booking and before check-in during which cancellation actions apply.
2. The cancellation conditions must be expressed as combinations of time intervals after booking and before check-in.
3. The cancella... | # Business Rules for Cancellation Policy Human Rule
1. Each cancellation policy term must define a condition and an action.
2. The action for a cancellation policy term must specify whether the cancellation is without cost or with cost.
3. The action for a cancellation policy term must include the cost amount, if appl... | 0.255017 | -0.060965 | 0.064006 | 0.002356 |
52 | # Business Rules for Booking Event Processing
## 1. Check-In Type Handling
- When a booking's check-in type is set to **Keysafe** or **Code Entry**, an access code must be assigned to the booking.
- When a booking's check-in type is set to **KeyNest**, and the associated unit has available key sets, a key set assignme... | # Business Rules for Booking Check-In and Cancellation
## 1. Check-In Type and Access Code Assignment
- When a booking's check-in type is **KeySafe** or **Code Entry**, the access code must be set according to the following precedence:
- If an override code is not set, the access code must match the code assigned b... | 0.4061 | 0.436769 | 0.357262 | 0.397698 |
53 | # Business Rules for Bedding Configuration Conversion
1. Each room's bedding configuration must be converted according to the defined conversion process.
2. The conversion process must be applicable to all rooms that have not yet completed the bedding configuration conversion.
3. The conversion process may be limited ... | # Business Rules for Bedding Configuration Conversion
- Each room not yet converted based on its bedding configuration must be converted.
- Conversion must be performed for the specified list of room IDs or all rooms without bed configuration if no room IDs are provided.
- If the operation is executed in dry-run mode,... | 0.487147 | 0.429255 | 0.553062 | 0.491283 |
54 | # Business Rules for Rentals United Synchronization and Dictionary Management
- No dictionary item may be deleted while it is assigned to another entity.
| # Business Rules for Rentals United Data Synchronization
## 1. Dictionary Synchronization Rules
- All Rentals United dictionaries that are subscribed to for synchronization must be synchronized regularly.
## 2. Item Removal and Synchronization Rules
- When a dictionary item is removed from a dictionary, it must ... | 0.210925 | -0.246268 | 0.373451 | 0.04595 |
55 | # Business Rules for Worldpay CVC Payment Processing
## Booking Validation Rules
- A payment may be processed only if the associated booking exists.
- If the booking does not exist, the payment process must be terminated immediately.
## Token Requirement Rules
- A payment requires a valid payment token.
- If ... | # Business Rules for Booking Worldpay Payment via CVV
1. Each booking worldpay payment must be associated with the correct booking and booking order.
2. The worldpay payment token must be provided when initiating the payment.
3. A successful worldpay payment must result in the creation of a new payment record for the ... | 0.255288 | 0.158007 | -0.003492 | 0.077454 |
56 | # Business Rules for Payment Allocation Retrieval
## 1. Cancellation Penalty Payment Allocation
- Only payments with a type other than "Channel Payment" or "OTA Credit" and with a 3D state of "OK" may be considered as allocated payments for cancellation penalty for a booking.
## 2. OTA Credit Payment Allocation
- Onl... | # Business Rules for Payment Allocation and Cancellation
## 1. Cancellation Penalty Payments
- Only payments of type **Channel Pay** or **OTA Credit** are excluded from cancellation penalty payment allocations.
- Only payments with a three-digit state of **OK** are included in cancellation penalty payment allocations.... | 0.2821 | 0.363918 | 0.275694 | 0.320539 |
57 | # Business Rules for Cost Element Management
## Uniqueness and Identification
- Each cost element within an organization must have a unique combination of name and category.
- No two cost elements in the same organization may share the same name and category, except when validating the current record being updated... | # Business Rules for Cost Element Management
1. Cost elements must be associated with a specific organization.
2. A cost element’s name must uniquely identify it within its organization.
3. Each cost element must be categorized and categorized types include: expense, refund, payment, accommodation, and management fee.... | 0.241391 | 0.243342 | 0.016041 | 0.128553 |
58 | # Business Rules for Create or Select Inline Property Aware
This component does not define any business rules. All logic pertains to form configuration and user interface presentation. | # Business Rules for Inline Property Selection and Booking
- A property must be selected when creating or selecting a booking inline. | 0.303218 | 0.288684 | 0.216667 | 0.253638 |
59 | # Business Rules for Automated Message Query Generation
*No explicit business rules are defined at the business policy level in this section. All logic pertains to form structure, field requirements, and presentation details.* | # Business Rules for Booking and Guest Queries
## 1. Data Joining Rules
- Each booking must be joined to the relevant categories defined by the user.
- Categories to be joined include:
- Channel information
- Booking order information
- Booking warning information
- Guest information
- Corporation informatio... | 0.166341 | -0.228443 | 0.04976 | -0.091552 |
60 | # Business Rules for Channel Manager Booking Conversion
- Only booking requests from approved channels may be converted to bookings.
- No booking request from an unapproved channel may be converted to a booking.
| # Business Rules for Channel Manager Booking Processing
- A booking may be accepted from the Su channel only if a corresponding booking order exists for the booking request.
- The acceptance of a booking from Su must involve transferring the booking data according to the Su-specific order. | 0.512036 | 0.383839 | 0.522644 | 0.453241 |
61 | # Sync History Business Rules
No business rules in this set; all items are technical implementation. | # Business Rules for Sync History
- Each sync history record must have a unique identifier.
- Each sync history record may optionally include the sync method, URI, request header, request body, status code, response body, response ID, and sending timestamp.
- Each sync history record may be associated with an organiza... | 0.228175 | -0.095067 | 0.172393 | 0.036642 |
62 | # Business Rules for Check-In Ready Settings and Booking Deposit Management
## Check-In Ready Settings
1. Each brand or organization may define check-in ready settings, including guest information requirements, terms and conditions, guest verification, payment, and security deposit policies.
2. When check-in ready se... | # Business Rules for Check-In Ready Settings
## 1. Check-In Ready Setting Configuration
- Each organization must have check-in ready settings configured for all current and future bookings.
- Each booking must be associated with its respective check-in ready settings.
## 2. Check-In Ready Settings Saving
- When check... | 0.355094 | 0.310685 | 0.261331 | 0.28705 |
63 | # Business Rules for Booking Splitting
## Rule 1: Booking Split Creation
When a booking is split, a new booking must be created with its own property, unit type, unit, arrival date, and booking date, while retaining the brand and collection type of the original booking.
## Rule 2: Split Reference Linking
The new spli... | # Business Rules for Booking Split
## 1. Booking Split Requirements
- Each split booking must inherit all properties from the original booking, including property, unit type, unit, arrival date, booking date, collection type, tax, brand, creation source, and number of nights.
- The arrival and departure times for the... | 0.348185 | 0.287324 | 0.202128 | 0.245601 |
64 | # Business Rules for Booking Creation and Update
## Booking Status and Access Rules
1. **Locked Bookings:** A booking that is finalized or locked cannot be edited or updated.
2. **Cancelled Bookings:** If a booking is cancelled, its status must be set to "Cancelled".
## Date and Time Rules
3. **Arrival and Departure ... | # Business Rules for Booking Creation
## 1. Guest Association
- Each booking must be associated with a guest. If no guest is specified, the booking must be linked to the default guest.
## 2. Booking Date and Unit/Type Assignment
- The arrival date and departure date for a booking must be set if provided in the bookin... | 0.275765 | 0.211152 | 0.048176 | 0.129765 |
65 | # Business Rules for Booking Arrival and Departure Date Changes
## Rule 1: Tracking Booking Date Changes
- Any change to a booking’s arrival or departure date must record both the new and previous arrival and departure dates.
## Rule 2: Booking Association
- Each arrival or departure date change must be associated wi... | - The booking's arrival and departure dates may be changed.
- The new arrival date must be specified when a change to the arrival date occurs.
- The new departure date must be specified when a change to the departure date occurs.
- The old arrival date must be specified when a change to the arrival date occurs.
- The o... | 0.279253 | 0.311606 | 0.157242 | 0.234513 |
66 | # Business Rules for Automated Notification Creation and Update
## Notification Update Rules
- When an update is requested, each relevant guest notification must be revised based on the latest booking and automated message information.
- If a guest notification is valid after revision, a new notification must be creat... | # Business Rules for Automated Notification Processing
1. Each automated notification created or updated must correspond to a valid booking or organization.
2. If a notification is **updated**, only notifications linked to the same booking or organization, and previously valid for that booking or organization, may be ... | 0.208448 | 0.335617 | 0.28097 | 0.309274 |
67 | # Business Rules for Channel Management
- A channel must have a unique code.
- Deposit handling must be specified for each channel (either "Yes" or "No").
- Commission type must be specified for each channel (either "PRE" or "POST").
- A channel must have at least one name alias defined. | # Business Rules for Channel Definition
- Each channel must have a code.
- Each channel may have a description.
- Each channel must indicate whether deposit handling is enabled or disabled.
- Each channel may be configured to collect from the hotel.
- Each channel may be configured to connect to the channel.
- Each ch... | 0.420339 | 0.424935 | 0.477391 | 0.451929 |
68 | # Business Rules for Fee Mapping
- Each fee type must be assigned an internal fee code according to the predefined fee-type mapping.
- When a fee type does not match the predefined mapping, the fee code must be assigned based on recognized keywords in the fee name.
- When a fee type does not match by type or keywo... | # Business Rules for Fee Mapping
1. No business rule may be expressed in natural language.
2. All decisions must be based on explicit, explicit, implicit, implicit, explicit, implicit, implicit, implicit, implicit, implicit, implicit, implicit, implicit, implicit, implicit, implicit, implicit, implicit, implicit, impl... | 0.068588 | -1.03738 | -0.107499 | -0.619331 |
69 | # Business Rules for Property Upsell Migration
## 1. Upsell Assignment
- Each property’s upsells must be assigned to all of its unit types.
- Each unit type must remove all previously assigned upsells before new assignments.
## 2. Upsell Pricing
- The purchase price for each unit type upsell must match the original u... | # Business Rules for Migrating Property Upsells to Unit Types
- Each property must have at least one associated unit type.
- When a property has one or more upsells, each upsell must be linked to the property’s corresponding unit type with a valid purchase and sales price.
- The sales price of each unit type linked fr... | 0.418776 | 0.486585 | 0.396573 | 0.442108 |
70 | # Business Rules for Booking Finalization
## Booking Finalization Steps
1. A booking may only proceed to finalization if it meets all required finalization conditions.
2. If a booking is eligible for finalization, the process must display a confirmation message to the user.
3. If there are authorized booking deposits ... | # Business Rules for Booking Finalization
## Booking Finalization Steps and Rules
1. **Initial Step (0):**
- A booking may only proceed to the next step if it is eligible for finalization.
2. **Deposit Capture Step (1):**
- If the booking has authorized deposits, the next step must be to capture those deposits... | 0.361619 | 0.096277 | 0.345442 | 0.219125 |
71 | # Business Rules for Deal Collection Metadata Normalization
1. Each deal collection response must include a unique identifier representing the collection.
2. If the deal collection is paginated, the response must include metadata specifying the total number of items, current page, last page, and items per page.
3. If ... | # Business Rules for Deal Meta Normalization
- Each deal collection must include a unique identifier in its metadata.
- Each deal collection must specify the total number of items, the current page, the last page, and the number of items per page in its metadata.
- When a deal collection is paginated, its metadata mus... | 0.618756 | 0.613235 | 0.611042 | 0.612769 |
72 | # Deal Template Line Service Rules
1. Each deal template must include one or more service lines.
2. Each service line must include the following fields:
- Cost Element
- Charge To
- Profit Host Percent
- Profit Investor Percent | # Business Rules for Deal Template Line Service Collection
- Each deal template must include one or more service collection lines.
- Each service collection line must include the following fields:
- Cost Element
- Charge to
- Profit Host Percent
- Profit Investor Percent | 0.899323 | 0.723377 | 0.760985 | 0.742539 |
73 | # Business Rules for CSV and Spreadsheet Data Export
## Export Eligibility Rules
- Data export in CSV or spreadsheet format is permitted only for specific data types, including guests, companies, newsletter subscribers, suppliers, bookings, refunds, payments, invoices, expenses, staff, accounts, accounting schemas, pa... | # Business Rules for CSV Response Handling
1. **File Naming**: When a response is in CSV format, the file name must include the current date and a unique prefix indicating the resource type.
2. **Data Extraction**: Only the first element of an array may be extracted when reading a CSV response.
3. **Response Format**:... | 0.176787 | 0.203109 | -0.006454 | 0.09761 |
74 | # Business Rules for Rate Log Submission
- Each rate update request must include a valid unit type identifier.
- Each rate update request must include a valid start date.
- Each rate update request must include a valid end date.
- Each start date and end date must be a valid calendar date.
- If a price is provided,... | # Business Rules for Unit Type Rate Logging
- Each unit type rate log must be associated with a valid unit type.
- Each unit type rate log must be linked to a start date and an end date.
- Each unit type rate log must have its override rate rules set to false.
- Each unit type rate log must be linked to the corre... | 0.378336 | 0.399218 | 0.462434 | 0.431566 |
75 | # Business Rules for Setting Customer Specifications
## 1. Customer Name
1. The customer’s first and last name must be taken from the guest’s first and last name.
## 2. Address Fields (Fallback Logic)
For each of the following fields — address line 1, address line 2, postal code, city, country, and region — the... | # Business Rules for Setting Customer Specifications for Payments
1. Each payment associated with a booking must include the guest's address information.
2. If the guest provides a street address, it must be used as the primary address; if not, the organization's address must be used as the primary address.
3. If the ... | 0.305757 | 0.216142 | -0.081036 | 0.064655 |
76 | # Business Rules for Guest Booking List
- The guest booking list must be retrieved only if a valid guest identifier is provided.
- The booking list may include bookings where the guest is the main guest, the person who booked, a related guest, or the person who placed the booking order.
- Users may filter the booking ... | # Business Rules for Guest Booking List
1. Only bookings associated with the specified guest are included in the booking list.
2. If the guest is not specified, all bookings must be included in the list.
3. Bookings must be filtered by booking code if a search term is provided; only bookings matching the search term m... | 0.46005 | 0.330843 | 0.460945 | 0.396086 |
77 | # Business Rules for Guest Creation and Lookup
## Rule 1: Guest Identification
- A guest must be identified using available customer information, including email, name, surname, phone number, address, and zip code.
## Rule 2: Country Code Resolution
- The country code for a guest must be determined based on the provi... | # Business Rules for Guest Provisioning
- Each guest must be assigned a country code based on the customer's country of residence.
- Each guest's phone number must be validated and formatted according to the country code before a guest record can be created.
- Each guest record must be created using the customer's pro... | 0.264968 | 0.537256 | 0.275996 | 0.404395 |
78 | # Business Rules for Booking Conflict Resolution
1. When resolving booking conflicts in bulk, each selected booking must have its property, unit type, unit, channel, check-in type, and booking status updated according to the specified resolution parameters.
2. A unit may only be assigned to a booking if the unit is ac... | # Business Rules for Resolve Conflict Mass Action
- Each booking that is being resolved must be linked to the correct property, unit type, channel, check-in type, and booking status.
- Only bookings that are explicitly linked to a property, unit type, channel, check-in type, or booking status may have their associated... | 0.477974 | 0.414716 | 0.46315 | 0.439736 |
79 | # Business Rules for Channel Deal Commission Calculation
## Channel Commission Rules
- For each booking associated with a channel deal, the channel commission must be recalculated whenever required.
- If a channel deal is active (not archived), the channel commission for a booking must be calculated as the sum of:
... | # Business Rules for Channel Commission Calculation
## 1. Channel Commission Eligibility
- A channel commission may only be calculated for a booking if the associated channel deal is active or not archived.
## 2. Commission Calculation Requirements
- The channel commission for a booking must be calculated as follows:... | 0.415731 | 0.316717 | 0.36554 | 0.342087 |
80 | # Business Rules for Booking Entity Preparation
## Booking Timing
- Each change to arrival date, departure date, arrival time, departure time, or number of nights must be detected and processed.
## Accommodation Details
- Each change to the assigned unit, assigned unit type, check-in type, or rate plan must be ... | # Business Rules for Booking Entity Preparation
## 1. Data Consistency and Update Rules
- The arrival and departure dates, as well as the arrival and departure times, must be updated if any three of the following changes occur:
- Arrival or departure date
- Arrival or departure time
- Departure or departur... | 0.365527 | -0.025636 | 0.213456 | 0.092551 |
81 | # Business Rules for Unit Type Rate Management
## Ownership and Organization Assignment
- Each new Unit Type Rate must be assigned the same owner as its associated Rate Plan.
- Each new Unit Type Rate must be assigned to the same organization as its associated Rate Plan.
- If an updated Unit Type Rate does not have a... | # Business Rules for Unit Type Rate Management
## Ownership and Organization Assignment Rules
1. Each newly created Unit Type Rate must inherit its owner and organization from its associated Rate Plan.
2. If a Unit Type Rate does not explicitly specify an owner or organization, it must be assigned the same values as ... | 0.768259 | 0.597947 | 0.677541 | 0.638051 |
82 | # Business Rules for Booking Normalization
There are no business rules defined at the business policy level in this section. All logic pertains to form configuration and user interface behavior.
| # Business Rules for Booking Normalization
1. When a booking is loaded, any key safe code override must be applied.
2. When a booking is loaded, any automatic addon must be activated if arrival or departure times are provided. | 0.135135 | 0.242264 | 0.27826 | 0.261403 |
83 | # Business Rules for Booking Management (AjaxController)
## Promotion and Voucher Rules
- Each promotion application must be applied to a booking using the booking’s rate plan, channel, dates, and guest history to determine the discount and total price.
- Each voucher code must be validated for the current organizatio... | # Business Rules for Booking Check-In Status
## Check-In Time Rules
- Each booking must have an assigned check-in time upon save.
- The check-in time for a booking must be set to match the specified check-in timestamp.
## Booking Status Rules
- A booking may only be checked in if its arrival time is set.
- The ... | 0.140607 | 0.311259 | 0.030195 | 0.168206 |
84 | # Business Rules for Payment Actions and Listing
## Payment State Rules
- Only the following payment states may be used: OK, Pending, Not Authorized, Rejected, Malformed, Invalid, Error, 3D Authentication Required, and Void.
## Payment Type Rules
- Only the following payment types may be used: Bank Transfer, Ca... | # Business Rules for Payment Management
The following rules define the business behaviors and constraints related to payment processing:
1. Each payment must have a unique identifier.
2. Each payment must specify the amount, currency, and an amount value with its currency.
3. Each payment must include a date and time... | 0.362623 | 0.088988 | 0.077251 | 0.084602 |
85 | # Payment Term Condition Business Rules
1. A payment term may include one or more payment term conditions.
2. Payment term conditions are optional; a payment term can exist without any conditions. | # Business Rules for Payment Term Condition Collection
- Each payment term condition collection must include one or more payment term conditions.
- Payment term conditions in the collection must be independently managed (allowing addition, deletion, etc.). | 0.541285 | 0.365313 | 0.494922 | 0.430265 |
86 | # Business Rules for Google Hotel Account XML Synchronization
There are no business rules defined at the business policy level in this section. All logic pertains to form configuration and user interface behavior. | # Business Rules for Google Feeding Processing
1. Each account name provided must correspond to an existing Google Hotel account.
2. Only accounts whose data has not been recently synced must be attempted to be synchronized.
3. The system must ensure that only valid and active accounts are processed for synchronizatio... | 0.21503 | -0.011978 | 0.197052 | 0.091847 |
87 | # Business Rules for Parking Type Definitions
## 1. Standard Parking Types
The following parking types must be defined and available in the system:
- Street Parking
- Free Street Parking
- Underground Parking
- Driveway Parking
- Secure Parking
- Valet Parking
## 2. Ownership and Organization Assignment
Each parking ... | # Business Rules for Parking Types
- Each parking type must be associated with the correct owner and organization.
- Each parking type must have a name and a description.
- Supported parking types include: Street Parking, Free Street Parking, Underground Parking, Driveway Parking, Secure Parking, and Valet Parking. | 0.449391 | 0.499651 | 0.401203 | 0.450869 |
88 | # Business Rules for Stripe Payment and Deposit Processing
## Booking Payment Rules
1. A payment may only be processed for an existing booking.
2. If a payment token is not provided, the payment process must not proceed.
3. When a payment is successfully processed through Stripe, the guest’s card details must be save... | # Business Rules for Stripe Payment and Credit Card Processing
## Booking Payments and Credits
- Each booking payment must use the booking’s published Stripe client key and be associated with the correct booking order.
- Each booking credit must use the booking’s published Stripe client key and be associated with the... | 0.289954 | 0.343549 | 0.188647 | 0.266136 |
89 | # Business Rules for Booking Date Change
## 1. Authorization
- Only users with edit permissions for a booking may change its dates or unit.
## 2. Unit Availability
- The selected unit for the new booking dates must be available; if not, the unit will be set to null.
## 3. Accommodation Price Update
- If the user req... | # Business Rules for Booking Date Modification
1. Only users with edit permission may modify a booking date.
2. The arrival and departure dates for a booking must be based on the selected dates and the booking’s check-in and check-out times, respectively.
3. If the booking’s arrival or departure time is not specified,... | 0.439888 | 0.324476 | 0.276735 | 0.301632 |
90 | # Business Rules for Google Tax Fee Model
1. A tax or fee must be defined with a specific type, which can be either **amount** or **percent**.
2. The tax or fee must be applied on a defined basis, which can be either **per person** or **per room**.
3. The tax or fee must be applied for a specified period, which can be... | # Business Rules for Google Tax Fee Model
- Each tax fee must be associated with a specific rate plan.
- Each tax fee must specify its type (amount or percent).
- Each tax fee must specify its basis (room or person).
- Each tax fee must specify its period (night or stay).
- Each tax fee must have an amount.
- Each tax... | 0.318975 | 0.436868 | 0.234652 | 0.334898 |
91 | # Business Rules for Property Viewing
## 1. Draft Properties
- A property that is in draft status must redirect to the property creation wizard before it can be viewed.
## 2. Amenities Display
- If a property has one or more amenities, their names must be listed and separated by commas.
## 3. Brand Display
- If a pr... | # Business Rules for Property View
1. A property may only be viewed if it is not in draft mode.
2. The available amenities for a property must be displayed when they exist.
3. The amenities for a property must be listed in a comma-separated string when available.
4. If a property has multiple brands, all brands must b... | 0.347775 | 0.411005 | 0.267087 | 0.339136 |
92 | # Business Rules for Migrating Single-Unit Amenities to Property Level
## 1. Eligibility and Scope
- Only properties that are active and configured as single-unit properties are eligible for amenity migration.
- The migration applies only to active units within eligible properties.
## 2. Amenity Migration
- All extra... | # Business Rules for Migrating Single Unit Amenities to Property Level
1. Each active property that is identified as a single unit property must have all its active units’ extra amenities migrated to the property level.
2. Only the unit type associated with the active, active unit must be considered when migrating ame... | 0.311163 | 0.544657 | 0.327251 | 0.434669 |
93 | # Bed Size Management Business Rules
- Only users with view permission may access bed size information.
- Only users with create permission may add a new bed size.
- Only users with edit permission may update an existing bed size.
- Each new or updated bed size must be valid before it is saved. | # Bed Size Management Business Rules
- Only users with view permission may access bed size records.
- Only users with create permission may add new bed sizes.
- Only users with edit permission may update existing bed sizes.
- Each bed size must be validated before it is created or updated. | 0.910073 | 0.919208 | 0.889225 | 0.904333 |
94 | # Channel Management Business Rules
1. Each channel must be created using the designated creation process.
2. Only users with the appropriate permissions may create, view, or edit channels.
3. After a channel is created, an associated channel deal must be defined.
4. All changes to a channel must be saved and persiste... | # Business Rules for Channel Application
1. Each channel must be created with valid information.
2. After a channel is created, the user must define an associated Channel Deal.
3. Only users with the appropriate create or edit permissions may perform actions related to channels. | 0.53886 | 0.707774 | 0.632742 | 0.670541 |
95 | # Business Rules for Property Meta Normalization
- Property collections may include or exclude metadata based on the provided context attributes.
- When metadata is included, each property collection must provide a unique identifier in the metadata.
- If the property collection is paginated, the metadata must include ... | # Business Rules for Property Collection Normalization
1. Each property collection must include metadata containing a unique identifier.
2. When the collection is paginated, metadata must include the total number of items, the current page, the last page, and the number of items per page.
3. When the collection is not... | 0.675922 | 0.656478 | 0.609154 | 0.633312 |
96 | # Business Rules for Property Data Persistence and Removal
## Mid-Stay Housekeeping Rules
- If the mid-stay housekeeping frequency is overridden and a new frequency is provided, the mid-stay housekeeping period for the property must be updated.
## Property Removal Rules
- A property cannot be removed if it has any fu... | # Business Rules for Property Data Persistence
1. Each property must have its own unique record in the system.
2. A property cannot be removed if it still has any of the following:
- Future bookings
- Past bookings
- Mapped rate plans
- Expenses associated with any units
3. If a property has any of the... | 0.410458 | 0.185969 | 0.318517 | 0.252616 |
97 | # Business Rules for Availability Logging and Overbooking
## Overbooking Detection and Notification
1. **Overbooking Identification**
- Each new availability log entry with a negative availability value must be identified as an overbooking.
2. **Overbooking Notification**
- A notification must be generated for... | # Business Rules for Overbooking Notifications
1. If an availability log records a negative availability value, a notification must be created for that log.
2. When multiple overbookings occur, a notification must be sent for each overbooking, and the overbooked logs must be cleared.
3. The notification for overbookin... | 0.422257 | 0.426978 | 0.337547 | 0.382889 |
98 | # Business Rules for Payment Integration Configuration
## Integration Type Rules
- Each payment integration type must have a unique name and description.
- Each payment integration type must be assigned an owner.
- Each payment integration type must be associated with an organization.
## Integration Parameter Rules
-... | # Business Rules for Payment Integration Configuration
- Each payment integration must be associated with an organization.
- Each payment integration must have an owner and an assigned organization.
- Each payment integration must have at least one integration parameter, including at least one key and label pair.
- In... | 0.412109 | 0.549424 | 0.51324 | 0.532033 |
99 | # Business Rules for Chart of Accounts List
## Account Listing Rules
1. Each account list must include only accounts belonging to the specified organization.
2. Each account in the list must display its identifier, name, code, type, and description.
3. The account list must support export in both CSV and XLSX formats... | # Business Rules for Account Listing
1. Only accounts belonging to the specified organization may be included in the list.
2. Each account in the list must provide its unique identifier, name, code, type, and description.
3. The resulting list of accounts must include all necessary information for each account. | 0.568238 | 0.698264 | 0.583165 | 0.640703 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.