id int64 0 199 | golden_business_rule stringlengths 89 4.82k | finetuned_prediction stringlengths 1 4.57k | finetuned_meteor float64 0 0.87 | finetuned_bertscore_p float64 -0.62 0.72 | finetuned_bertscore_r float64 -0.29 0.66 | finetuned_bertscore_f1 float64 -0.36 0.68 |
|---|---|---|---|---|---|---|
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**, ... | - Each booking's monthly income report must include separate sections for accommodation income, addon income, expense income, and investor income.
- Each section must display the income, expense, and profit amounts for accommodation, addons, and expenses.
- Each section must include a profit amount calculation for acco... | 0.131535 | -0.267148 | -0.120596 | -0.193059 |
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 bookings with a valid access for the current user may be extended.
- A booking may not be extended if it is scheduled for cancellation or has been canceled.
- A booking may not be extended if it is a no-show booking.
- A booking may not be extended if it has already been extended once.
- A booking may not be ext... | 0.22186 | 0.307397 | -0.084636 | 0.105213 |
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:... | - A booking may only be split if it is not finalised and not already split.
- A booking may not be split if the split date falls within the booking's arrival date or departure date.
- A booking may not be split if the number of nights is less than 2.
- A booking may not be split if it has been split at least once.
- A ... | 0.185752 | 0.301575 | -0.041651 | 0.125562 |
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 ... | - Each staff member must have a unique email address.
- Each staff member must be assigned at least one role.
- Each staff member must have a related user associated.
- Each staff member must belong to their organization.
- Each staff member must have a password set.
- Each staff member must have a team assigned.
- Eac... | 0.125783 | 0.209649 | -0.210578 | -0.007782 |
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... | - Each rate rule that applies to only one rate plan must have a currency specified and must not be applied to all rate plans.
- If a rate rule specifies a change in rates (either as a fixed amount or a fixed percentage), the currency must be specified.
- If a rate rule does not apply to all rate plans and specifies a c... | 0.285819 | 0.372541 | 0.141268 | 0.255535 |
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... | - Each PayPal integration must be associated with an organization.
- Each PayPal integration must specify the environment (sandbox or live) for its access credentials.
- Each PayPal integration must include the client secret and client ID as required credentials.
- Each PayPal integration must be identified by its type... | 0.26752 | 0.315162 | 0.116291 | 0.21508 |
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... | - Each tax schema must have a rate assigned to it.
- Each customer invoice must have its bank account information and payment method shown on the invoice set according to the corresponding settings.
- Each investor must be checked to determine if they have a custom integration gateway associated with their landlord. | 0.316384 | 0.356344 | 0.096676 | 0.2245 |
7 | This snippet includes only technical behavior and implementation details; no business rules apply.
| - Each Financial Message Queue that is completed must be processed to create nightly detail tax components.
- Only Financial Message Queues with valid and active identifiers may be processed for nightly detail tax component creation. | 0.115607 | -0.055725 | 0.0136 | -0.019646 |
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... | - An expense excel file cannot be deleted if any of its lines have been transferred.
- An expense excel file cannot be processed if any of its lines have an error or warning state.
- The status of an expense excel file must reflect its current processing state, including whether it is ready for transfer, processing, co... | 0.298387 | 0.321456 | 0.156897 | 0.239102 |
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 Rules
## Rate Rule Application and Job Generation Rules
1. Each rate plan may have one or more rate rules applied to it.
2. Each rate rule must be applied to the correct scope (e.g., channel manager, direct booking).
3. Each rate rule must be applied to the correct organization and, if appli... | 0.255041 | 0.03384 | -0.133235 | -0.049423 |
10 | # Agency Uniqueness Rules
- No two agencies may share the same Name.
- No two agencies may share the same Code.
| - Each agency must have a unique name and code combination.
- An agency cannot be created if another agency with the same name or code already exists. | 0.345254 | 0.280095 | 0.261871 | 0.272151 |
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... | - An LTSA order must be created for each parcel identifier (PID).
- The access token must be obtained from LTSA before processing any PID.
- The title summary information for a PID must be retrieved using the access token.
- An order must be created in LTSA for each PID, specifying the title number and land title distr... | 0.279605 | 0.295048 | 0.077728 | 0.185403 |
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, ... | - Each notification must have a status indicating its current state (Accepted, Pending, Cancelled, Failed, Completed, Not Found).
- When a notification's status is not standard (i.e., it is not Accepted, Pending, Cancelled, Failed, Completed, or Not Found), the notification's status must not be updated.
- Each notifica... | 0.254348 | -0.10215 | -0.062366 | -0.08058 |
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... | - Each property must be accessible through a search or map view.
- Only properties that have been published may be viewed in the map or property detail pages.
- Each property must have its own unique identifier when displayed.
- Only the owner of a property may view its details.
- Users must be redirected to the canoni... | 0.328662 | 0.211778 | 0.128982 | 0.171391 |
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... | - Similar properties must be identified based on the property's location and category.
- If a property belongs to a neighborhood, similar properties must be found within the same neighborhood.
- If a property belongs to a district, similar properties must be found within the same district.
- If a property does not belo... | 0.288104 | 0.375411 | 0.164953 | 0.269239 |
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... | - Only users who are not already registered may register.
- Users must agree to the terms and conditions before registration.
- Passwords must be at least 10 characters long.
- Registration must include an email confirmation link. | 0.342455 | 0.427848 | 0.104151 | 0.262156 |
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.
... | - Each property must be associated with a valid owner.
- A channel manager may connect a property to one or more channels.
- A channel manager may disconnect a property from one or more channels.
- Each unit type must be associated with a property.
- Each unit type must be associated with a unit type property.
- Each r... | 0.224113 | -0.19319 | -0.064295 | -0.127768 |
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... | - Each expense line must have a valid expense date.
- Each expense line must have a valid start date (default to the first day of the month).
- Each expense line must have a valid end date (default to the last day of the month).
- Each expense line must be associated with a supplier if a supplier name is provided and n... | 0.182771 | 0.35354 | 0.027243 | 0.186515 |
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... | - Each property that is active and belongs to the current organization must be considered when configuring the occupancy rate calendar.
- The calendar must be grouped by city and must only include properties that are viewable for the current organization.
- Each city that meets the above criteria must be a child of the... | 0.293172 | 0.435159 | 0.356729 | 0.396636 |
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... | - Each company detail fill must include the organization's name, birth date, city, country, postal code, region, and website address.
- Each company detail fill must include the contact information for the organization's representative, including first name, last name, email, phone, city, country, postal code, region, ... | 0.404781 | 0.411756 | 0.259728 | 0.335723 |
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... | - Each guest notification configuration must be restricted to notifications associated with the current organization.
- Each favorite automated message must be restricted to archived messages and must be associated with the current organization.
- Only users with the necessary permissions may view or manage guest notif... | 0.321851 | 0.262544 | 0.176648 | 0.220504 |
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... | - Each customer invoice must be associated with a booking.
- Only users with appropriate permissions may view or edit a customer invoice.
- A customer invoice may only be deleted if it is in a non-complete state.
- The bank account information and payment method shown on an invoice may be customized for each invoice.
-... | 0.162862 | 0.427552 | 0.095958 | 0.257666 |
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 Secrets and Account IDs
## Secret Key Rules
- The Stripe secret key for an organization must be determined based on the following criteria:
- If the organization is not the one with ID 66, the secret key must be StripePartnershipController::STRIPE_SECRET_KEY.
- If the integr... | 0.456527 | 0.075417 | 0.276204 | 0.175185 |
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... | - Each booking's task date must be updated to reflect its current and previous dates.
- When a booking is canceled, all relevant tasks must be recalculated.
- When a booking is uncanceled, all relevant tasks must be recalculated.
- When the arrival or departure date of a booking is changed, all relevant tasks must be r... | 0.495042 | 0.581491 | 0.427315 | 0.504114 |
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.* | - A property unit must be selected when creating or selecting a property.
- The selection of a property unit is required and cannot be disabled.
- No new property units may be created when selecting a property unit. | 0.201993 | 0.165861 | 0.010325 | 0.088369 |
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... | - Each booking income report must include the booking ID, booking number, channel name, and channel logo.
- Each booking income report must include the number of guests, total nights, nights in month, accommodation price, discount, accommodation total, and monthly accommodation total.
- Each booking income report must ... | 0.305435 | 0.404947 | 0.106405 | 0.252593 |
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
## Booking and Guest Rules
- Each automated message must include conditions for bookings, guests, and properties.
- Each condition must specify the type of condition (e.g., number of nights, arrival date, etc.).
- Each condition must specify the operator and value for ... | 0.350534 | 0.306769 | 0.271193 | 0.290075 |
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.* | - Each rental booking must be associated with a valid brand.
- Each rental booking must be assigned to a valid channel rate log.
- Each rental booking must be linked to the correct organization.
- Each rental booking must be linked to the correct location.
- Each rental booking must be linked to the correct availabilit... | 0.056306 | -0.1698 | -0.089279 | -0.128039 |
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... | - Each booking order line breakdown must be associated with a booking.
- Each booking order line breakdown must not be an add-on (i.e., it must have an "addon" field set to false).
- Breakdowns must be grouped by batch code and ID for reporting purposes.
- Only breakdowns belonging to the same booking and not linked to... | 0.247172 | 0.165284 | -0.002835 | 0.081307 |
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... | - Each message sent via the Rentals United Messaging API must include a message body.
- Each message sent via the Rentals United Messaging API may include one or more attachments.
- Each message sent via the Rentals United Messaging API must be associated with a booking.
- Each message sent via the Rentals United Messa... | 0.411832 | 0.153329 | 0.143441 | 0.149764 |
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, ... | - Each Key Place Profile must be associated with an owner when created.
- Only users with the appropriate permissions may view or edit a Key Place Profile.
- A new Key Place Profile may only be created if all required information is valid and the submission is complete.
- A Key Place Profile may be updated by an author... | 0.370528 | 0.507279 | 0.326409 | 0.416262 |
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.
| - Each payment or refund must have a unique identifier.
- The total number of payments or refunds must be known.
- The number of items per page must be known.
- The current page and last page must be known.
- The total number of items must be known. | 0.416392 | 0.362349 | 0.263948 | 0.313802 |
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... | - Each booking must include its booking status, including any canceled or scheduled statuses.
- Each booking must include its total price in breakdown, including the currency and amount.
- Each booking must include its security deposit, including the currency and amount.
- Each booking must include its check-in and che... | 0.240643 | -0.02245 | -0.013483 | -0.016317 |
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... | - Each property connected to Google must have its transaction data sent to Google.
- The transaction data must be sent for properties that are currently active and connected to Google.
- The transaction data must be sent for the following contents: property, promotions, and taxes/fees. | 0.299639 | 0.462966 | 0.150101 | 0.302992 |
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**
... | - Each booking must be associated with a unit type.
- Each booking must have a valid start date and an end date.
- Each booking must be associated with the correct organization.
- Each booking must have a booking status.
- Each booking must be included in the result if its booking date falls within the specified range. | 0.124164 | 0.357508 | -0.153486 | 0.090518 |
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... | - Each property must have a unique identifier.
- The description of a property must be provided and must not be empty.
- The number of active units for a property must be updated to reflect the actual count of active units.
- The authentication for a property must be determined by the associated owner's authentication,... | 0.23325 | 0.391541 | 0.027565 | 0.204401 |
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... | - Each availability must be calculated for a property that is active.
- Each availability must be calculated within a specified date range.
- Each availability must only consider unit types that have a valid rate plan and are associated with the property.
- Each availability must only consider unit types where the maxi... | 0.380983 | 0.332863 | 0.278239 | 0.306536 |
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
## Revenue and Profit Calculation Rules
- Each nightly detail report must calculate the total revenue and total profit based on the applicable currency and organization settings.
- If the default currency is not defined for the organization, the calculation must use the defau... | 0.304579 | 0.367282 | 0.18554 | 0.276001 |
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... | - Each booking must be created with an arrival date, a departure date, an accommodation price, and a booking status.
- Each booking must be associated with a property, a unit type, a unit, and a rate plan.
- Each booking must specify the number of adult, child, and infant guests.
- Each booking must include a channel c... | 0.170001 | 0.399666 | 0.017163 | 0.202591 |
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... | - Property unit synchronization with Staah Su is only enabled for properties that have a Su enabled, a valid Staah ID, and a Su Staah ID configured.
- When a property unit is deactivated and synchronization with Staah Su is enabled, Staah Su must be used to update the status of the property unit.
- If Staah Su is unabl... | 0.284499 | 0.317758 | 0.295766 | 0.307865 |
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.
| - Each new message, email body, SMS send, or SMS receive must be associated with a valid record in the system.
- When a new message, email body, SMS send, or SMS receive is created or updated, the relevant business rules must be applied.
- Each new contact created as a result of a message, email body, SMS send, or SMS ... | 0.380704 | 0.089743 | 0.28927 | 0.188889 |
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... | - No business rules are defined for the payment retrieval operations described. The code performs technical data filtering and does not implement any business policy or domain logic. | 0.053448 | 0.05874 | -0.265854 | -0.107215 |
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
## 1. Batch Expense Processing
- When a batch expense is processed, all associated bookings must be allocated costs according to the specified allocation strategy.
## 2. Booking Allocation
- Each booking must be allocated costs based on the following strategies:
- If the bo... | 0.277893 | 0.24085 | 0.167208 | 0.205057 |
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. | - Each unit type must be validated before it can be deleted.
- Only valid unit types may be deleted.
- When a unit type is deleted, any associated errors must be recorded and the deletion process must fail if validation is not acceptable. | 0.462131 | 0.564652 | 0.482576 | 0.524078 |
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 ... | - When authenticating with Xero, the system must provide the authentication URL.
- When a user denies access to their Xero account, the system must display an error message indicating the reason for the denial.
- When a connection to Xero is successfully deleted, the system must display a success message indicating tha... | 0.182371 | 0.186072 | 0.29535 | 0.24137 |
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 ... | - Each booking must have a valid booking ID.
- If a booking exists, its associated bedding configuration must be retrieved and its contents must be extracted.
- If a booking does not exist, the unit type's bed configuration must be used as the bedding configuration.
- A new bedding configuration for a booking may be se... | 0.389871 | 0.482286 | 0.396258 | 0.439837 |
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... | - Each unit type rate log must have an owner.
- Each unit type rate log must have a list of associated rate log lines.
- Each rate log line must inherit the override rate rules from its parent unit type rate log if the parent exists.
- When adding a new rate log line to a unit type rate log, the line must inherit the o... | 0.534808 | 0.391484 | 0.378206 | 0.385836 |
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... | - Each review must be associated with the booking it is related to.
- If a review does not have a property, unit type, or unit assigned, it must be set to inherit the values from the associated booking.
- Only users with the Booking Engine admin role may assign reviews to an organization other than the one associated w... | 0.31302 | 0.410478 | 0.192951 | 0.300589 |
48 | # Business Rules for Accounting Schema Defaults
- The default accounting schema **cannot be deleted**. | - A default accounting schema cannot be removed.
- Each accounting schema default must be removed only if it is not the default schema. | 0.394805 | 0.409939 | 0.30463 | 0.357803 |
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 ... | - A booking may be early checked out.
- The new departure date for an early checkout must be later than the old departure date.
- The booking must be associated with a specific departure date. | 0.456805 | 0.577896 | 0.33049 | 0.45224 |
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 Assignment Rules
- Each tax rate must be associated with one or more rate plans.
- If a tax rate is deleted, all associated rate plans must also be deleted.
## Rate Plan Availability Rules
- Each organization must have at least one available rate plan for a given c... | 0.297736 | 0.500868 | 0.361804 | 0.431357 |
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 Rules
## Cancellation Policy Condition Rules
- The cancellation policy condition must be based on the following criteria:
- The number of minutes after booking
- The number of minutes before check-in
## Cancellation Policy Action Rules
- The cancellation policy actio... | 0.319864 | 0.02755 | 0.159874 | 0.094319 |
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... | - When a booking's check-in type is KeySafe or Code Entry, the access code must be set to the code associated with that type, unless the booking has a key safe code override.
- When a booking's check-in type is KeySafe or Code Entry, and the unit has key sets, the access code must be set to the unit's key safe code.
- ... | 0.294691 | 0.39766 | 0.076872 | 0.233532 |
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 ... | - Each room whose bed configuration has not been converted must have its bed configuration converted.
- The conversion process must not persist or flush the database if the dry run option is enabled. | 0.238603 | 0.37391 | 0.326416 | 0.351111 |
54 | # Business Rules for Rentals United Synchronization and Dictionary Management
- No dictionary item may be deleted while it is assigned to another entity.
| - Each Rentals United dictionary must be synchronized with its corresponding definition.
- Only dictionaries that are subscribed for synchronization may be updated.
- Any dictionary item that is removed from the dictionary must be marked as removed in the database.
- Any dictionary item that is no longer present in the... | 0.10799 | -0.500916 | 0.144332 | -0.198209 |
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 ... | - Each booking must have a valid booking order associated with it.
- Each payment made for a booking must be linked to the corresponding booking order.
- The payment method for a booking must be specified and valid.
- A payment must be successful and have a valid payment status.
- If a payment fails, the payment record... | 0.212529 | 0.24969 | -0.028437 | 0.108238 |
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... | - Only payments of type "OK" (PaymentState::PAYMENT_STATE_OK) and not of type "Channel Pay" (PaymentType::PAYMENT_TYPE_CHANNEL_PAY) or "OTA Credit" (PaymentType::PAYMENT_TYPE_OTA_CREDIT) may be considered for cancellation penalty payments.
- Only booking order lines associated with bookings where the payment state is "... | 0.244387 | -0.071047 | -0.001357 | -0.034764 |
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... | - Each cost element must be associated with a specific organization.
- Each cost element must have a name.
- Each cost element must be identified by its name within the context of its associated organization.
- Each cost element must not be classified as a refund.
- Each cost element must not be classified as an expens... | 0.16065 | 0.160868 | -0.153654 | 0.000219 |
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. | - A property must be selected or provided when creating or selecting an inline property.
- The arrival date, departure date, and availability must be provided or selected when creating or selecting an inline property.
- The property must be linked to the correct booking. | 0.215085 | 0.043092 | 0.005599 | 0.025859 |
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 Query Generation
## 1. Category Join Rules
- Each booking must be joined to the following categories based on its conditions:
- **Channel**: If the condition is for channel, the booking must be joined to the channel table.
- **Booking Order**: If the condition is for payment or securit... | 0.112245 | -0.517158 | -0.034837 | -0.286374 |
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.
| - A booking must be created for each Booking Request that is assigned to the Rentals Unit channel manager.
- When a Booking Request is assigned to the SU channel manager, a booking must be created by transferring the Booking Order from the SU XML Data.
- Only bookings created by the Rentals Unit or SU channel managers ... | 0.3653 | 0.182271 | 0.276848 | 0.230381 |
61 | # Sync History Business Rules
No business rules in this set; all items are technical implementation. | - Each sync history record must have a unique identifier.
- Each sync history record may optionally specify the method used, the URI of the request, the request header, the request body, the status code, the response body, and a response ID.
- Each sync history record may optionally specify the timestamp when it was se... | 0.105601 | -0.17466 | -0.022109 | -0.097797 |
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... | - Each check-in ready setting must include guest information, terms and conditions, guest verification, payment method, security deposit amount, and any other relevant details.
- When adding check-in ready settings for a booking, the system must update the check-in ready settings for all current and future bookings in ... | 0.282422 | 0.420106 | 0.20631 | 0.312146 |
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... | - Each booking split must have the same property, unit type, and unit as the original booking.
- The arrival date of the split booking must be the same as the split date.
- The departure date of the split booking must be the same as the original booking's departure date.
- The arrival time of the split booking must be ... | 0.339127 | 0.327425 | 0.145502 | 0.236103 |
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
## Booking Creation Constraints
1. A booking must have a valid booking date and a valid departure date.
2. If a booking is linked to a unit or a unit type, the corresponding unit or unit type must exist.
3. A booking cannot be created if it is already checked out (i.e., its booki... | 0.24595 | 0.14026 | 0.079021 | 0.1109 |
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 date may be changed.
- The booking's departure date may be changed.
- The new arrival date must be specified when the arrival date is changed.
- The new departure date must be specified when the departure date is changed.
- The old arrival date must be specified when the arrival date is changed.... | 0.257896 | 0.239934 | 0.066263 | 0.152991 |
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... | - Each automated message notification must be created or updated based on the following criteria:
1. If the notification is to be updated, only those notifications that correspond to an existing automated message must be processed.
2. If the notification is to be created, all notifications, regardless of their ... | 0.294175 | 0.260292 | 0.231013 | 0.246836 |
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. | - Each channel must have a code.
- Each channel may have a description.
- Each channel must specify whether deposit handling is included.
- Each channel may be configured to collect from the channel.
- Each channel may be configured to collect from the hotel.
- Each channel must have a name alias model.
- Each channel ... | 0.376845 | 0.426712 | 0.263189 | 0.344747 |
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. Default Fee
The default fee for all rentals is **$0**.
## 2. Fee Mapping by Inclusion
Fees may be mapped to a specific category based on inclusion criteria. The following categories are defined:
- **Breakfast**
- **Cleaning**
- **Community**
- **Linen**
- **Management**
- **Pet*... | 0.145858 | -0.391571 | 0.005314 | -0.199471 |
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... | - Each property must have at least one associated unit type.
- Each unit type must be linked to at least one upsell from that property.
- Each upsell assigned to a unit type must include the correct purchase price and sales price for that unit type. | 0.230359 | 0.347586 | 0.169746 | 0.258346 |
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 Widget
## Deposit Capture and Finalization Constraints
1. A booking may only proceed to finalization if all associated deposits have been authorized.
2. If a deposit is guaranteed by a channel, the booking may proceed to finalization only if it is also authorized.
3. If a dep... | 0.430788 | 0.406998 | 0.372114 | 0.39049 |
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 ... | - Each deal collection must include a unique identifier for each deal.
- The total number of deals in each collection must be known.
- The number of deals per page and the total number of deals must be known when dealing with paginated collections.
- When dealing with collections that are not paginated, the total numbe... | 0.382773 | 0.472257 | 0.348948 | 0.410847 |
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 | - Each deal template line must include the following fields:
1. Cost element
2. Charge to
3. Profit host percent
4. Profit investor percent | 0.573529 | 0.623713 | 0.474455 | 0.5488 |
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 export must apply only to specified API endpoints.
- The filename for CSV exports must include a unique timestamp.
- CSV exports must be served as both CSV and XLSX file types. | 0.095886 | 0.313371 | -0.076678 | 0.112255 |
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,... | - A rate log must be created for each nightly rate plan associated with a unit type.
- Each rate log must be defined by a start date, an end date, and must use the same currency and value as specified for that rate plan.
- Each rate log must include minimum and maximum stay values, if provided.
- Each rate log must be ... | 0.416755 | 0.198798 | 0.204803 | 0.203096 |
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... | - Each payment must be associated with the correct first name and last name from the booking's guest information.
- Each payment must be assigned a postcode, city, country, region, and address based on the guest's address details or default settings.
- If the guest's address does not provide a postal code, the city and... | 0.251409 | 0.228771 | -0.197273 | 0.008186 |
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 ... | - Each guest booking must be associated with a valid guest record.
- Only bookings linked to the specified guest may be retrieved.
- Bookings may be filtered by a search term, which must match the booking code or name. | 0.354473 | 0.534543 | 0.354894 | 0.44412 |
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... | - Each guest must be associated with an organization.
- Each guest must have a valid email address, name, and surname.
- Each guest must have a valid phone number, including the correct country code.
- Each guest must have a valid address and zip code.
- Each guest must be created or found based on the provided email, ... | 0.25702 | 0.241064 | -0.015229 | 0.111105 |
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... | - Each booking must be linked to a property, unit type, channel, check-in type, or booking status as specified by the user.
- When resolving conflicts for bookings, any applicable linked fields (property, unit type, channel, check-in type, or booking status) must be updated to match the user-specified values. | 0.403957 | 0.403369 | 0.349507 | 0.377313 |
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:
... | - Each booking must have its OTA commission recalculated when a corresponding channel deal is updated.
- The OTA commission for a booking must be set to the channel commission value if the channel deal is active or not archived.
- If a channel deal is not active or not archived, the OTA commission for a booking must be... | 0.378437 | 0.481228 | 0.296451 | 0.388228 |
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 ... | - Each booking must have a unique identifier (ID).
- Each booking must have an arrival date and a departure date.
- Each booking must have an arrival time and a departure time.
- Each booking must have a number of nights.
- Each booking must have a unit type.
- Each booking must have a check-in type.
- Each booking mus... | 0.199322 | -0.112453 | -0.106164 | -0.107508 |
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... | - Each unit type rate must be associated with its rate plan.
- The owner and organization of each unit type rate must be set to the same values as the rate plan to which it is associated. | 0.401839 | 0.448773 | 0.311218 | 0.380111 |
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.
| - Each booking must have its access code protected by a key safe code override if specified.
- Each booking must be assigned an auto addon if it includes an arrival time or a departure time. | 0.046012 | 0.026501 | 0.043255 | 0.036432 |
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 and Promotion Operations
## Booking Rules
- Each booking must have an arrival date and a departure date.
- Each booking must have a guest associated with it.
- Each booking must have a property associated with it.
- Each booking must have a unit associated with it.
- Each booking must have... | 0.302125 | 0.147518 | 0.222896 | 0.186255 |
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
## Payment State and Type Rules
- Each payment must have one of the following payment states: OK, Pending, Not Authed, Rejected, Malformed, Invalid, Error, 3D Auth, Void.
- Each payment must have one of the following payment types: Bank Transfer, Cash, PDQ, Virtual Credit Card, ... | 0.492399 | -0.068475 | 0.477273 | 0.191239 |
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. | - Each payment term condition must have a name and a description.
- Each payment term condition may be added or removed as needed.
- Payment term conditions must be associated with a specific payment term. | 0.385094 | 0.330436 | 0.304745 | 0.318667 |
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. | - Each account name provided must correspond to an existing Google Hotel account.
- Only accounts that are active and have an updated XML file within the last 15 minutes may be synchronized.
- Any accounts that are not active or have an updated XML file more than 15 minutes ago must be requeued for synchronization.
- E... | 0.189678 | -0.046357 | 0.06157 | 0.008633 |
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 ... | - Each parking type must have a name, a description, and must be associated with the current user's organization and the user who created it.
- Each parking type must be owned by the user who created it. | 0.275088 | 0.323264 | 0.132442 | 0.227343 |
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... | - Each booking must have a corresponding payment model associated with it.
- The payment model for a booking must be linked to its booking order.
- The payment model for a booking must use the client key provided by the organization.
- A payment must be saved only if the payment intent is successful.
- A payment must n... | 0.202836 | -0.079079 | -0.059415 | -0.067529 |
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... | - Only bookings for which the user has permission to edit may have their dates changed.
- The arrival date and departure date for a booking must be determined from the booking or its associated date change model.
- If an arrival time is set for the booking, it must be associated with the booking; otherwise, it must def... | 0.308041 | 0.305504 | 0.182776 | 0.24464 |
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... | - Each tax fee must be associated with a rate plan.
- Each tax fee must specify the type, basis, and period of application.
- Each tax fee must specify the amount to be charged.
- Each tax fee may have a minimum length of stay and a maximum length of stay.
- Each tax fee may include an additional rate add-on. | 0.199929 | 0.366603 | 0.081803 | 0.221533 |
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... | - A property may be in a draft state and may require redirection to its creation wizard if it is in draft.
- The list of available amenities for a property must include all amenities associated with that property.
- If a property has multiple brands, the list of brands must include all brands associated with that prope... | 0.41618 | 0.305203 | 0.219794 | 0.263344 |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 9