id int64 0 199 | golden_business_rule stringlengths 89 4.82k | finetuned_prediction stringlengths 38 4.11k | finetuned_meteor float64 0.08 0.95 | finetuned_bertscore_p float64 -0.53 0.87 | finetuned_bertscore_r float64 -0.21 0.89 | finetuned_bertscore_f1 float64 -0.24 0.88 |
|---|---|---|---|---|---|---|
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 Booking Income Report
## Accommodation and Channel Totals
- The total amount for an accommodation booking must be calculated as the sum of the accommodation price and any channel promotions, discounts, and addons.
- The total channel amount for a booking must include the sum of the channel... | 0.219951 | -0.069591 | 0.063799 | -0.002163 |
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... | # Business Rules for Booking Extension
1. Each booking extension must be authorized by the user with edit access to the booking.
2. A booking with a status of **Scheduled for Cancellation** or **Canceled** cannot be extended.
3. A booking with a status of **No Show** cannot be extended.
4. A booking that has already b... | 0.25687 | 0.342537 | 0.115275 | 0.227657 |
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. **Each Booking May Only Be Split Once**
- A Booking that has already been split cannot be split again.
2. **Booking Must Not Be Finalized Before Splitting**
- A finalised Booking cannot be split.
3. **Booking Must Have At Least Two Nights**
- A Booking with fewer than t... | 0.31291 | 0.104003 | 0.171529 | 0.138943 |
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 new staff member must have a unique email address.
- A staff member cannot be created if another user already exists with the same email address, including landlords, suppliers, or any other user type associated with the organization.
- Each staff m... | 0.333583 | 0.253431 | 0.113715 | 0.183944 |
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 for Non-Universal Rate Rules
- If a Rate Rule is not applied to all rate plans and specifies a currency, the currency must match the currency of at least one associated rate plan.
## Rule 2: Currency Requirement for Fixed Rate Changes
... | 0.336917 | 0.562555 | 0.476329 | 0.519881 |
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
## Integration Setup and Configuration
1. A PayPal integration must be associated with an organization.
2. A PayPal integration must have a PayPal client ID and a PayPal client secret.
3. The PayPal client secret must be defined for each integration.
4. The PayPal client ID may... | 0.302811 | 0.241046 | 0.122682 | 0.182507 |
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 assigned to it.
## Investor Custom Gateway Rules
- A deal must be identified as having a custom investor gateway integration only if it is linked to a landlord and meets the criteria for a custom gateway.
## ... | 0.431589 | 0.418347 | 0.405811 | 0.413027 |
7 | This snippet includes only technical behavior and implementation details; no business rules apply.
| - Each Financial Message Queue must have a status indicating it is completed before it may be processed further.
- Only Financial Message Queues with a completed status may be processed as nightly detail tax components.
- Each nightly detail tax component creation must be associated with a valid Financial Message Queue... | 0.078947 | -0.168737 | -0.053546 | -0.110019 |
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. Transfer Eligibility
- An expense Excel file may only be transferred if no records within the file have an error state of "TRANSFERRED".
## 2. Validation for Transfer
- An expense Excel file may only be transferred if at least one record within the file has an error... | 0.395627 | 0.250404 | 0.338712 | 0.295333 |
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 Rules
1. Each rate plan may have multiple rate rules applied to it.
2. Only active rate rules may be considered for application.
3. A rate rule may only be applied if it is not disabled.
## Rate Rule Calculation Rules
4. The calcu... | 0.264484 | 0.069078 | 0.044999 | 0.058541 |
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.
- Each agency must have a unique code.
- An agency cannot be created if another agency with the same name or code already exists. | 0.337066 | 0.311261 | 0.243461 | 0.278313 |
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
## Access Token and Authentication
- An access token must be obtained from LTSA before any title summary or order processing can occur.
## Title Summary Retrieval
- Each parcel identifier (PID) must be associated with a title summary before an order may be created for that P... | 0.430484 | 0.302832 | 0.272471 | 0.288764 |
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.
- Accepted: The notification has been accepted.
- Pending: The notification is awaiting processing.
- Cancelled: The notification has been cancelled.
- Failed: The notification... | 0.397043 | 0.212453 | 0.205255 | 0.210137 |
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 Viewing and Access Rules
## Property Access Rules
- Only the owner of a property may view that property.
## Property Display Rules
- Each property must be accessible via its unique identifier.
- Each property must be displayed with its number of photos included.
- A back button must be provided for each pr... | 0.400382 | 0.409209 | 0.312399 | 0.361398 |
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 Recommendations
## 1. Eligibility
- Similar property recommendations must only be available if the similarity module is enabled.
- Similarity recommendations cannot include the current property itself.
## 2. Area-Based Recommendations
- If a property belongs to a neighborhood, si... | 0.331706 | 0.260625 | 0.265736 | 0.264377 |
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字符长.
- Only authenticated users may proceed with registration. | 0.313083 | 0.173647 | 0.176323 | 0.176325 |
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 Management
## Property Synchronization Rules
- A property may be synchronized with the channel manager using a valid property identifier.
- Synchronization must be successful if the operation is performed without errors.
- If synchronization fails, an error message mus... | 0.383256 | 0.418863 | 0.300764 | 0.360193 |
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. Expense Data Preparation
- Each expense line must have a valid date for the expense date.
- Each expense line must have a valid date for the start date.
- Each expense line must have a valid date for the end date.
- If a supplier name is provided for an expense line, the syste... | 0.370207 | 0.374482 | 0.333381 | 0.354901 |
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 within the current organization that are active may be included in the rate calendar navigation.
2. The rate calendar must be linked to each property's city, displaying a calendar only for properties located in each city.
3. Each property's rate calendar... | 0.511427 | 0.565227 | 0.507271 | 0.536848 |
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 Fill Company Details Normalization
1. Each fill company details request must include the following information:
- Company name: The organization's name must be displayed as the company name.
- Company website address: The organization's website address must be displayed if available.
-... | 0.312309 | -0.165208 | 0.135324 | -0.017868 |
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
- Only notifications associated with favorite guest notifications from the organization may be sent as part of a notification operation.
- Only notifications that are marked as favorites and not archived may be sent as part of a notification operation. | 0.404889 | 0.530385 | 0.416796 | 0.473848 |
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
## General Rules
- Only authorized users may view or process customer invoices.
- A customer invoice may only be deleted if it is in a non-complete state.
## Invoice Creation Rules
- Each customer invoice must be created from its associated booking.
- If a booking does... | 0.256764 | 0.445333 | 0.274805 | 0.359734 |
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 organization's ID:
- If the organization's ID is not 66, the secret key must be Stripe.
- If the organization's ID is 66, the secret key must be Stripe tes... | 0.469248 | 0.315581 | 0.341662 | 0.32968 |
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 Task Scheduling
## 1. Booking Task Scheduling on Booking Creation
- Each new booking must have its previous and current booking task dates updated when it is created.
## 2. Booking Task Scheduling on Booking Cancellation
- When a booking is canceled, all associated tasks must be recalcula... | 0.445982 | 0.262858 | 0.440135 | 0.35107 |
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
- No business rules are defined at the business policy level for property unit selection in this component.
- All logic pertains to user interface configuration and presentation details.
- No business rules are applicable.
- The form configuration specifies presentati... | 0.240275 | -0.450776 | 0.3567 | -0.078612 |
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
## Booking Information
- Each booking income export must include the following information for each booking:
- Booking ID
- Booking Number
- Guest
- Property Name
- Unit Type Name
- Unit Name
- Arrival Date
- Departure Date
- Booking ... | 0.369981 | 0.179848 | 0.237187 | 0.209645 |
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 Trigger Rules
## 1. Condition Generation
- Each automated message must allow the addition of conditions to define its triggering criteria.
- When new conditions are added to an automated message, corresponding conditions must be created and persisted for each booking that matches... | 0.191583 | -0.531789 | 0.09723 | -0.236219 |
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 Manager
- Each Rentals United manager must be associated with a brand, channel rate logs, configuration, entity manager, location assignment, message bus, multi-organization service, availability log, Rentals United service, translator, and ticketing system.
- Each Rentals United ma... | 0.201381 | -0.109742 | 0.14411 | 0.015539 |
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 Breakdowns
1. Only breakdowns associated with addons for the specified booking are considered.
2. Only breakdowns whose date range falls within the specified date range are considered.
3. Only breakdowns with no main line for the given booking and date range are considered.
4. O... | 0.270722 | 0.20386 | 0.042671 | 0.123404 |
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 Push Normalization
- Each message sent via the Messaging API must include its message ID.
- Each message sent via the Messaging API must be associated with the correct booking and channel information.
- When attachments are present in a message, their names and content must be includ... | 0.485382 | 0.506643 | 0.438741 | 0.473334 |
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 it is created.
- Only users with the appropriate view permission may access a key place profile.
- Only users with the appropriate edit permission may update a key place profile.
- Each key place profile must be... | 0.412432 | 0.583851 | 0.450087 | 0.516932 |
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
1. Each payment collection must include metadata containing a unique identifier.
2. When payment data is paginated, metadata must include the total number of items, the current page, the last page, and the number of items per page.
3. For non-paginated data, metadata... | 0.533846 | 0.337692 | 0.510063 | 0.423433 |
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 Data Normalization
## General Rules
- All relevant booking data must be included in the normalized output.
- Security deposits and additional charges must be distinguished and included appropriately.
- Each booking must be associated with its guest, property, unit, and channel.
## Specifi... | 0.241603 | -0.159074 | 0.068868 | -0.046052 |
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 property on Google that is currently active must be processed to send its transaction data to Google.
2. The transaction data to be sent must include:
- The property identifier
- The account identifier
- The following property contents: p... | 0.372251 | 0.281198 | 0.219922 | 0.251596 |
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
## Access Rules
- Access to booking retrieval must be granted only if the user has valid access rights.
- If access is denied, the response must indicate the reason for denial.
## Required Information
- The request must include a listing identifier.
- The request must include a ... | 0.298475 | 0.423709 | 0.100898 | 0.25849 |
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 must be assigned a unique identifier that includes a prefix indicating whether it is a hub or a non-hub property, followed by an identifier and an identifier suffix.
- Each property's description must be extracted and included in the normalization process.
- ... | 0.307723 | 0.330989 | 0.14499 | 0.237554 |
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 Retrieval
1. Each property must have availability data within a specified date range.
2. Availability data must only include unit types whose property is active and whose rate plan is associated with an origin limit booking engine.
3. Availability data must be filtered by dat... | 0.224808 | 0.24706 | 0.228204 | 0.238853 |
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
## General Rules
- Each nightly detail report must be generated for the selected organization and its properties.
- Each report must include revenue, profit, occupancy, average daily rate (ADR), and room rate per available room (RevPAR) for the selected period.
## Revenue an... | 0.346782 | 0.395382 | 0.210709 | 0.302549 |
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 and Details
- Each booking must be created with a valid arrival date and departure date.
- The booking must be associated with an accommodation price and tax.
- The booking must specify the channel commission, if applicable.
- The booking must... | 0.394761 | 0.41074 | 0.296795 | 0.354202 |
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
- Property unit SU synchronization is only enabled for properties that have a supported SU service configuration and a configured SU service for the unit type.
- SU synchronization must not proceed if the requested unit type does not support SU integration.
- S... | 0.280137 | 0.364993 | 0.287024 | 0.326813 |
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 Unified Inbox Message Processing
- Each new message (including messages of types such as API messages, body text, SMS sends, or SMS receives) must be recorded and associated with the appropriate context or destination.
- When a new message is created, a contact record may be required to be establi... | 0.429485 | 0.209693 | 0.453179 | 0.329718 |
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. Unallocated Payments and State Mismatch
- Payments that have a three-dimensional state of "OK" and were created within the past six months must include all payments where payment allocation is not assigned.
- Mismatches between the booking order's co... | 0.354109 | 0.343709 | 0.240153 | 0.292567 |
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 created, all related bookings must be identified and their associated bill cost allocations must be created.
- Each booking’s bill cost allocation must be linked to the correct batch expense and must not be excluded from... | 0.34827 | 0.314269 | 0.255707 | 0.285985 |
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 Deletion
1. Each unit type must exist and be identifiable before deletion.
2. Deletion of a unit type must only proceed if all required validations are satisfied.
3. Any errors encountered during deletion must be recorded and the process must not complete until all issues are addressed. | 0.398002 | 0.454501 | 0.550418 | 0.502848 |
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
## Authentication and Authorization
1. **Authentication URL Retrieval**
- The system must provide a link to retrieve the authentication URL for Xero application authentication.
2. **Authorization Code Handling**
- When the authorization code is provided and the... | 0.254701 | -0.051634 | 0.367426 | 0.150667 |
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 a defined bedding configuration.
2. The bedding configuration for a booking must be based on the booking’s unit type or must include a default bedding configuration if the booking has no bedding configu... | 0.540645 | 0.628138 | 0.621494 | 0.625423 |
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 an owner.
- Each unit type rate log must have an identifier (ID).
- Each unit type rate log must have a state indicating whether rate rules are being overridden.
- Each unit type rate log must include one or more log line models.
- Each log li... | 0.509415 | 0.413851 | 0.442094 | 0.428865 |
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
## Rule 1: Review Origin and Organization Assignment
- When a review is created, the origin of the review must be set to **Website** if the logged-in user is a Booking Engine administrator.
- When a review is created, the organization of the review must be set to the organization ... | 0.521385 | 0.315111 | 0.340506 | 0.32887 |
48 | # Business Rules for Accounting Schema Defaults
- The default accounting schema **cannot be deleted**. | # Business Rules for Accounting Schema Default Removal
1. A default accounting schema cannot be removed.
2. Any removal of an accounting schema must not proceed if the schema is designated as the default.
3. Removal of an accounting schema must be authorized according to applicable permissions. | 0.525834 | 0.348251 | 0.505174 | 0.426501 |
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 being affected, the new departure date, and the old departure date.
- The departure date for the affected booking must be updated to the new departure date specified in the event. | 0.496635 | 0.599361 | 0.530217 | 0.565277 |
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 Plan Application and Management
## Tax Rate Plan Rules
1. Each tax rate may be associated with one or more rate plans.
2. A tax rate must not be applied if it is not associated with any available rate plans.
## Rate Plan Rules
1. A rate plan must only be selected if at least one applic... | 0.385995 | 0.301016 | 0.333539 | 0.318337 |
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. The cancellation policy human rule must apply to all applicable terms.
2. The rule must determine the condition and action for each term based on its defined criteria.
3. The rule must include the atomic cancellation fee for each applicable fee type, including non... | 0.364113 | 0.358276 | 0.368633 | 0.364484 |
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 Departure Date Changes
## Check-In Type and Access Code Assignment
1. When a booking’s check-in type is either a key-safe or code-entry check-in, the access code must be set according to the following precedence:
- If an override code is not available, the access code mus... | 0.29656 | 0.289809 | 0.234011 | 0.262958 |
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
1. Each room whose bed configuration has not been converted must be processed for bed configuration conversion.
2. The bed configuration of a room must be converted only if the current status is not completed.
3. Conversion of bed configuration must not occur durin... | 0.38988 | 0.51866 | 0.523952 | 0.522083 |
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 Dictionary Synchronization
1. **Dictionary Synchronization Policy**
- All Rentals United dictionaries subscribed to for synchronization must be synchronized regularly.
- Synchronization must ensure that all items in a dictionary are properly tracked and synchronized.
2.... | 0.154369 | -0.391699 | 0.305679 | -0.066113 |
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 VCC Payment
1. Each booking must have a corresponding booking order.
2. A payment must be associated with its respective booking order.
3. The payment process must use the organization and investor deal service client key for integration.
4. Each payment must be linked to the corr... | 0.189136 | -0.265281 | -0.077532 | -0.171345 |
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 for Cancellation Penalty and Channel Payments
## 1. Cancellation Penalty Payments
- Only payments of type "OK" (i.e., without a "threeDState" of "ok") and not of type "Channel Pay" or "OTA Credit" should be considered for booking cancellation penalty allocations.
- Payments rela... | 0.473509 | 0.318713 | 0.357686 | 0.339204 |
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. Each cost element must be associated with a specific organization.
2. Each cost element must have a name.
3. Only cost elements belonging to the specified organization and with the name matching the requested name may be retrieved or identified.
4. Accommodation cost ele... | 0.281981 | 0.168629 | 0.058647 | 0.114477 |
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
- The property field is required when using inline property selection for a booking.
- The arrival and departure dates must be provided when selecting a property for a booking.
- The availability status must be included for the selected property.
- The booking... | 0.220118 | 0.011375 | 0.11452 | 0.063941 |
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 Booking Queries
## 1. Organization and User Scope
- Only bookings belonging to the specified organization may be included in queries.
- Queries may be filtered by user scope, including only bookings accessible to the current user.
## 2. Joining Tables
- When querying bookings, all relevan... | 0.199201 | -0.228564 | 0.060907 | -0.086372 |
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
- Each booking request must be processed according to the assigned channel manager.
- If the channel manager is Rentals Unit, the booking must be processed using the built-in system.
- If the channel manager is Su, the booking must be processed by transferring da... | 0.385964 | 0.257884 | 0.491556 | 0.373174 |
61 | # Sync History Business Rules
No business rules in this set; all items are technical implementation. | # Business Rules for Rental Synchronization History
- Each synchronization operation must have a unique identifier.
- Each synchronization operation must specify the method used for the request.
- Each synchronization operation may include request headers or request bodies; these may be omitted if not applicable.
- Ea... | 0.14961 | -0.209047 | 0.142101 | -0.038065 |
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 booking must have its own check-in ready settings, including details such as brand, guest information, terms and conditions, guest verification, payment method, and security deposit.
- Each check-in ready setting must be sav... | 0.329494 | 0.366054 | 0.273898 | 0.320675 |
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 Creation
- A booking may be split into multiple bookings based on a specified split date and time.
- Each split booking must inherit the source booking’s properties, including property, unit type, unit, collection type, brand, creation source, and tax.
- The split... | 0.491308 | 0.381848 | 0.393467 | 0.388647 |
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
## General Rules
- Each booking must have a valid arrival and departure date.
- Each booking must be associated with a unit or a unit type.
- If a booking is linked to a guest, the guest must exist.
## Booking Creation Rules
- A new booking must be created for each guest.
- When ... | 0.246699 | 0.24155 | 0.045595 | 0.143072 |
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... | # Business Rules for Booking Arrival and Departure Date Changes
1. Each booking change involving arrival or departure dates must specify the new arrival and departure dates.
2. Each booking change must also specify the original arrival and departure dates.
3. The arrival and departure dates recorded for a booking must... | 0.362914 | 0.617255 | 0.475337 | 0.546113 |
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 must be created or updated based on the following criteria:
- If the notification is an update:
- Only if an automated message with the input exists, must the system attempt to create or update each notification associat... | 0.383885 | -0.015355 | 0.251072 | 0.115791 |
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 Configuration
- Each channel must have a code.
- Each channel may have a description.
- Each channel must specify whether deposit handling is enabled or disabled.
- Each channel may be configured to collect from the channel.
- Each channel may be configured to collect from the hotel.
- Eac... | 0.4519 | 0.428068 | 0.464736 | 0.44724 |
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 system must assign a default fee of **0** to any fee that does not have a specific fee value defined.
2. **Inclusion-Based Fees**: Any fee that is explicitly defined by inclusion must take precedence over other fee mappings.
3. **Exhaustive Fee Mapping**: Any fe... | 0.270649 | -0.133309 | 0.15033 | 0.006066 |
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
1. Each property must have at least one associated unit type.
2. If a property has multiple upsells, each upsell must be linked to the property’s unit types, with the association including both the unit type and the corresponding upsell details.
3. When lin... | 0.422108 | 0.449226 | 0.350103 | 0.400178 |
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 Rules
1. A booking may be finalized only if all required deposits have been captured.
2. When a booking is finalized, the final status must be updated accordingly.
3. The finalization process may proceed to the next step only if all necessary deposits ... | 0.346426 | 0.430241 | 0.381192 | 0.406568 |
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 Collection Metadata
1. Each deal collection must include a unique identifier in its metadata.
2. The total number of items in the deal collection must be included in its metadata.
3. The metadata must specify the current page, last page, and items per page if the collection is paginated.
4. I... | 0.777584 | 0.751049 | 0.733772 | 0.742815 |
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 line must include the following fields:
- Cost Element
- Charge to
- Profit Host Percent
- Investor Percent | 0.662132 | 0.673559 | 0.606899 | 0.640613 |
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
The following rules define which types of API responses may be exported as CSV files:
1. **Guest Data Grid:** CSV exports are allowed for all guest-related data grids.
2. **Corporation Data Grid:** CSV exports are allowed for all corporation-related data grids.
3. **Newslett... | 0.164081 | -0.151915 | -0.091252 | -0.11995 |
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
1. Each rate log must be associated with a unit type.
2. Each rate log must specify a start date and an end date.
3. If a price is provided for a rate log, it must be a valid numerical value.
4. If a currency code is provided for a rate log, it must be specified.
5. If a min... | 0.381364 | 0.234676 | 0.308319 | 0.272423 |
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 first name and last name.
2. Each payment must include the guest's postcode, city, country, and region.
3. If the guest's address provides a street and postal code, these details must be... | 0.237286 | -0.077732 | -0.129205 | -0.101814 |
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 may be included in the booking list.
2. If the guest is not specified, all available bookings must be included, regardless of the guest’s association.
3. Bookings may be filtered by partial booking code matching a search term. | 0.375576 | 0.478069 | 0.449053 | 0.464393 |
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 Provision
- Each guest must be identified using an email address, name, and surname if available.
- If an email or name/surname is not provided, the guest’s phone number must be used to identify them.
- The guest’s phone number must match the country code specified when the guest is created.... | 0.365014 | 0.429076 | 0.281778 | 0.355447 |
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
1. Each resolved conflict mass action must process all selected bookings according to their identifiers.
2. For each selected booking, the system must update the following booking properties based on the provided values:
- Property: If a property identifier is provi... | 0.431247 | 0.039684 | 0.355839 | 0.194211 |
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 by Channel Deal
1. The channel commission for a booking must be calculated based on the applicable channel deal.
2. If the channel deal is not archived or is eligible, the channel commission for the booking must be calculated as follows:
- The channel total for t... | 0.455784 | 0.303908 | 0.383807 | 0.344624 |
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, arrival and departure times, number of nights, unit, unit type, check-in type, accommodation price, tax, booking status, deposit amount, and booking purpose may be changed during booking preparati... | 0.376032 | 0.240395 | 0.2501 | 0.24647 |
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 Ownership and Organization
## Ownership Rules
- Each unit type rate must inherit its owner and organization from its associated rate plan.
- If a unit type rate does not have an assigned owner or organization, it must be set to match the owner and organization of its associated rate... | 0.765264 | 0.550524 | 0.578586 | 0.565227 |
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 Data Normalization
## Access Code Rules
- If an access code is provided for a booking, the key safe code override flag must be set to true.
## Booking Time Rules
- If an arrival or departure time is provided for a booking, the auto addon flag must be set to true. | 0.156695 | 0.150236 | 0.262685 | 0.207138 |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 27