id int64 0 199 | golden_business_rule stringlengths 89 4.82k | finetuned_prediction stringlengths 1 4.54k | finetuned_meteor float64 0 0.96 | finetuned_bertscore_p float64 -0.43 0.84 | finetuned_bertscore_r float64 -0.32 0.85 | finetuned_bertscore_f1 float64 -0.25 0.83 |
|---|---|---|---|---|---|---|
0 | # Business Rules: Monthly Profit Report
## Rule 1: Monthly Report Frequency
The Monthly Profit Report must be generated for each calendar month.
## Rule 2: Report Scope Based on Contract
- If a **contract exists** for a unit, the Monthly Profit Report **must be calculated per contract**.
- If **no contract exists**, ... | # Business Rules for Monthly Profit Report
## Accommodation and Channel Revenue Rules
- The total revenue for a booking must include the accommodation total, channel addons, and revenue from bookings, excluding discounts and transaction costs.
- The total revenue for a booking must be calculated as the accommodation t... | 0.209616 | -0.105955 | 0.052054 | -0.026548 |
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 must exist and be accessible for the current user.
2. A booking cannot be extended if it is scheduled for cancellation or has been canceled.
3. A booking cannot be extended if it has already been extended.
4. A booking cannot be extended if it is in the "No Show" ... | 0.239986 | 0.3587 | -0.045307 | 0.150056 |
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 must be finalizable before it can be split.
2. A booking cannot be split if it is already finalised.
3. A booking cannot be split if another split has already been performed.
4. The number of nights in a booking must be at least 2 to be split.
5. The split date must f... | 0.245746 | 0.309539 | 0.025091 | 0.164704 |
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 within the same organization.
- Each staff member must be assigned at least one role, and at least one of the following roles must be included: Housekeeper, Check-in Staff, Office Staff (Financial), or Office Staff (No Finance).
- Each staff member’s schedule must be... | 0.171142 | 0.223239 | -0.117873 | 0.048391 |
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
- Each rate rule that specifies a currency and is not universal must have its currency matched to the currency of at least one associated rate plan.
- If a rate rule’s currency does not match the currency of... | 0.484716 | 0.410686 | 0.49857 | 0.455158 |
5 | # Payment and Contact Integration Business Rules
- Each contact must be linked to its corresponding staff member.
- Each PayPal integration must include a client secret.
- Each PayPal integration must include a client ID.
- When a deal requires a custom gateway deposit, the landlord’s primary integration must se... | # Business Rules for PayPal Integration
1. Each organization must have a PayPal integration associated with it.
2. The PayPal integration for an organization must be defined at the organization level or at the highest possible integration level within the organization.
3. The PayPal integration must be identified by i... | 0.300181 | 0.227864 | 0.114869 | 0.172086 |
6 | # Business Rules
## Contact Rules
- Each contact must be linked to its corresponding staff member.
## Tax Rules
- Each Tax Schema must have a defined rate; if no rate exists, the rate must be considered 0.
## Deal Rules
- Each deal with a custom investor gateway must be associated with that investor.
## Custo... | # Business Rules for Finance and Accounting
## Tax Rate Rules
- Each tax schema must have a defined tax rate.
## Investor Custom Gateway Rules
- A deal must exist only if an investor has a custom gateway integration for the landlord.
## Invoice Print Setting Rules
- Each customer invoice must have its bank account i... | 0.367159 | 0.438958 | 0.358906 | 0.399607 |
7 | This snippet includes only technical behavior and implementation details; no business rules apply.
| - Each Financial Message Queue (FMQ) must only be processed if it is not already completed.
- Each valid Financial Message Queue ID must correspond to an active and non-completed Financial Message Queue before processing may proceed. | 0.085227 | -0.188438 | -0.029516 | -0.108478 |
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. Record Deletion and Transfer
- An expense Excel record may not be deleted if any previous record for that record is marked as "transferred".
## 2. Record Transfer and Processing
- An expense Excel record may not be transferred if any previous record for that record ... | 0.419399 | 0.227983 | 0.287971 | 0.259011 |
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
## 1. Rate Rule Activation and Deactivation
- Each rate rule must have a priority assigned to determine its order of activation.
- Only rate rules with a positive priority may be activated.
## 2. Rate Rule Application and Deletion
- Each rate rule application must be associated with a ... | 0.226273 | 0.24697 | 0.017323 | 0.130953 |
10 | # Agency Uniqueness Rules
- No two agencies may share the same Name.
- No two agencies may share the same Code.
| # Agency Creation Business Rules
- Each agency must have a unique name and code in the system.
- An attempt to create an agency with a name or code that already exists must result in a conflict error. | 0.352612 | 0.304477 | 0.404063 | 0.354853 |
11 | # LTSA Business Rules
## 1. Title Summary Rules
- A Title Summary may only be retrieved for a valid Parcel Identifier (PID).
## 2. Title Order Rules
- Each Title Order must be based on a Title Summary issued by LTSA.
- Each Title Order must include the Title Number provided by LTSA.
- Each Title Order must incl... | # Business Rules for LTSA Order Processing
The following rules define the business processes and requirements for initiating and completing an LTSA order.
1. **Access Token Requirement**
- An access token is required to authenticate and interact with the LTSA system.
2. **Title Summary Retrieval**
- Each LTSA ... | 0.381227 | 0.256161 | 0.338368 | 0.298085 |
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 Processing
## Notification Status Rules
- Each notification must have a status indicating its current state.
- Accepted notifications must be in Accepted status.
- Pending notifications must be in Pending status.
- Cancelled notifications must be in Cancelled status.
- Failed notifica... | 0.424533 | 0.252113 | 0.239024 | 0.246786 |
13 | # Property Business Rules
## Property Access and Visibility
- Users may only view a property if they are the owner or have been explicitly granted viewing rights.
- Only properties marked as published may be made visible to users.
## Property Information
- Each property must display the total number of associated... | # Property Search and Viewing Business Rules
## Search Rules
- Only properties that match the search criteria may be displayed in the search results.
## Map View Rules
- Only published properties may be displayed in the map view.
## Property Detail Rules
- Each property must be accessible through a unique identifier... | 0.496496 | 0.376764 | 0.352796 | 0.365784 |
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 and Scope
- Similar property recommendations must be available only if the similarity module is enabled.
- Similarity searches must consider properties within the same neighborhood, district, or both.
## 2. Area Consideration
- If a property belo... | 0.36745 | 0.2177 | 0.273997 | 0.246922 |
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" setting 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 register. | 0.30767 | 0.224219 | 0.175313 | 0.200949 |
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 and Rate Plan Management
## Property Synchronization Rules
- A property may be synchronized with the channel manager using a valid property identifier.
## Channel Connection Rules
- A channel manager connection may be established for a property using a valid property identifier.
## Unit ... | 0.260909 | 0.40176 | 0.189447 | 0.294592 |
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 be assigned an initial expense date. If the expense date is missing, it must be set to the current date.
- Each expense line must be assigned an initial from date. If the from date is missing, it must be set to the first day of... | 0.389065 | 0.497886 | 0.400119 | 0.449453 |
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 Property Rate Calendar Navigation
1. Only properties belonging to the current organization may be included in the property rate calendar.
2. Only properties that are active may be included in the property rate calendar.
3. Properties may be grouped by city for navigation in the rate calendar.
4. E... | 0.506822 | 0.641548 | 0.482254 | 0.561457 |
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
The following rules define the business processes and requirements for populating company details in the rental management system.
1. **Company Name and Name:**
- The company name must be consistent with the organization's name.
- If the organization does not have a nam... | 0.48039 | 0.101651 | 0.372538 | 0.234799 |
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 Configuration
1. Only notifications marked as favorites and belonging to the current organization may be selected for processing.
2. Automated messages may be selected for processing only if they are marked as favorites and not archived, and belong to the current organization.
3. No o... | 0.643964 | 0.508705 | 0.469195 | 0.489708 |
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... | - Only invoices associated with bookings that have been processed may have their status set to "Draft".
- When a customer invoice is deleted, its Xero invoice status must be set to the default or to the status it had before deletion.
- When a customer invoice is re-generated from a reference booking, the invoice must b... | 0.170265 | 0.317569 | 0.078913 | 0.196769 |
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.39136 | 0.265865 | 0.228169 | 0.248171 |
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
## Booking Task Scheduling Rules
1. **Booking Task Date Update**
- When a booking is created, the task dates for all related bookings must be updated to reflect the new booking date.
2. **Cancellation and Rescheduling Rules**
- When a booking is canceled, all associ... | 0.494111 | 0.252783 | 0.433793 | 0.34281 |
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 this component.
- All logic pertains to user interface configuration and presentation details.
- No business rules apply to property unit selection in this context.
- All statements relate to form config... | 0.244272 | -0.392931 | 0.240957 | -0.094864 |
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 Rules
- Each booking income export must include the following booking details:
- Booking ID
- Booking Number
- Channel Name
- Channel Logo
## Guest Information Rules
- Each booking income export must include the following guest information... | 0.391663 | 0.219279 | 0.166198 | 0.193912 |
26 | # Business Rules for Automated Message Trigger Rules
## Condition Assignment and Management
- When updating automated message trigger rules, all existing conditions associated with the message must be removed before assigning new conditions.
- Each automated message may have multiple conditions and timing rules assign... | # Business Rules for Automated Message Triggering
## 1. Condition Generation
- Each automated message must allow the addition of conditions based on various criteria such as number of nights, arrival/departure dates, booking status, and guest attributes.
## 2. Operator and Variable Rules
- Each condition must sp... | 0.349588 | 0.069907 | 0.197718 | 0.134418 |
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 rental must be associated with its respective brand.
- Each Rentals United rental must be linked to its associated channel rates.
- Each Rentals United rental must be linked to its related availability logs.
- Each Rentals United rental must be linked t... | 0.133508 | -0.210516 | 0.08606 | -0.065001 |
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. Addon Breakdowns
- Each breakdown for an add-on must be associated with a booking order line that includes an add-on.
## 2. Breakdowns Between Date Range
- Each breakdown for an add-on between a specified start date and end date must be associated with a bookin... | 0.310396 | -0.191689 | 0.248368 | 0.02019 |
29 | # Business Rules for Messaging API Push Normalization
- Only message line entities may be processed for outgoing messages.
- Each outgoing message must include the response content in the message body.
- If a message includes attachments, each attachment must include its file name and the file content encoded in b... | # Business Rules for Messaging API Message Processing
- Each message sent via the Messaging API must include its response message.
- Each message sent via the Messaging API must specify the associated booking if available.
- Each message sent via the Messaging API must specify the associated channel if available.
- Ea... | 0.471503 | 0.374382 | 0.410865 | 0.393548 |
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 be owned by its owner, unless it is the first profile created.
- Each new key place profile must be saved with its owner set to the current organization user.
- Each key place profile may be created and saved through a user interface.
- Ea... | 0.379025 | 0.531568 | 0.401316 | 0.466522 |
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 the payment collection is paginated, metadata must include the total number of items, the current page, the last page, and the number of items per page.
3. For non-paginated coll... | 0.562182 | 0.349451 | 0.535215 | 0.441641 |
32 | # Business Rules For Booking Normalizer
## Guest Rules
- Each booking must calculate total guests as the sum of adult guests and child guests.
- Each lead guest must meet the property’s minimum age requirement.
- No guest may be accepted when the guest is below the minimum allowed age.
- Each booking must require docu... | # Business Rules for Booking Normalization
The following rules define the business requirements and constraints for booking normalization.
1. **Booking Normalization by Status**
- When a booking is canceled, its details must be normalized to reflect the canceled status.
2. **Booking Normalization by Payment and S... | 0.177269 | -0.211608 | -0.038579 | -0.124815 |
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-on-Google property must be sent transactional data to Google for its properties, promotions, and taxes/fees.
2. Only authenticated users with appropriate roles may perform property transaction data synchronization to Google.
3. Command scheduling is ... | 0.267418 | 0.466405 | 0.198006 | 0.329871 |
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 end date.
- Each booking must belong to the same organization as the listing.
- Each booking must be identified by a unique identifier. | 0.089431 | 0.313781 | -0.209513 | 0.039956 |
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 owner identifier based on its associated rental unit owner.
- Each property must use the owner identifier assigned by its rental unit owner as the identifier for the property.
- Each property must be assigned a location identifie... | 0.240083 | 0.045788 | -0.02643 | 0.011023 |
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 availability must be calculated based on the following criteria:
- The availability period must fall within the range specified by "after" and "before" dates.
- The property must have an active unit type.
- The unit type's maximum capacity ... | 0.329771 | 0.133141 | 0.233349 | 0.184084 |
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 Reports
## 1. Organization Currency and Default Currency
- Each nightly detail report must use the organization's default currency as the reference currency.
- If the organization does not have a default currency, the report must use the currency code of the organization's default c... | 0.33393 | 0.446213 | 0.23547 | 0.339807 |
38 | # Business Rules for Booking Creation and Order Management
## 1. Booking Creation and Assignment
- Each booking must be associated with a property, unit type, and, if applicable, a specific unit.
- The booking must record arrival and departure dates and times, guest counts (adults, children, infants), and booking stat... | # Business Rules for Booking Creation and Management
## 1. Booking Creation Requirements
- Each booking must be associated with an arrival date and a departure date.
- The booking must specify an arrival time and a departure time.
- The booking must include an accommodation price.
- The booking must be linked to a pro... | 0.397695 | 0.354175 | 0.259726 | 0.30765 |
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-Sync
- Su-Sync is only enabled for property units whose associated property is enabled and has a valid Su-STAah ID.
- Su-Sync may only be performed if Su-STAah connection is not already established for the property unit. | 0.13326 | 0.318773 | 0.133218 | 0.225584 |
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, body, SMS send, or SMS receive must be associated with a valid source identifier.
- Each new message, body, SMS send, or SMS receive must be attributed to the correct recipient.
- Each new message, body, SMS send, or SMS receive must be linked t... | 0.378861 | 0.04017 | 0.381096 | 0.206285 |
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 Payment Processing
## 1. Payment Allocation and State
- Payments with a three-state status of "OK" and an allocation ID of zero must be considered.
- Only payments created within the last six months are included if they meet the three-state condition and booking order is not null.
## 2. Guest Mis... | 0.373403 | 0.33973 | 0.32433 | 0.333103 |
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
- Each batch expense must be associated with a bill ID.
## 2. Booking and Unit Allocation
- A bill may be allocated to one or more property units or a property.
- The allocation method for a bill must be determined by the bill's level and alloca... | 0.278362 | 0.257742 | 0.159221 | 0.209294 |
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
- Each unit type must exist and be identifiable before it can be deleted.
- Deleting a unit type must not proceed if the deletion is not acceptable according to validation rules.
- Upon successful deletion, any associated data must be validated and removed as required. | 0.5425 | 0.565319 | 0.657226 | 0.611526 |
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 Rules
- Only authorized users may access Xero authentication procedures.
- If access is denied due to an error, the user must be informed of the access denial.
## Integration Connection Rules
- Each organization must have a correspo... | 0.317296 | 0.229142 | 0.458413 | 0.342363 |
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
## 1. Booking Bedding Configuration Retrieval
- The bedding configuration for a booking must include all rooms in the booking, along with their room type, room ID, label, and assigned beds.
- If the booking has a bedding configuration, it must be retrieved and present... | 0.526364 | 0.391448 | 0.546008 | 0.468491 |
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 may be set to override rate rules.
- Each unit type rate log must have its own set of rate rules.
- Each unit type rate log may include one or more rate log lines.
- When adding a rate log line to a unit typ... | 0.675764 | 0.502733 | 0.50652 | 0.505431 |
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 Assignment and Origin
## Review Assignment Rules
- Each review associated with a booking must be linked to the same property and unit as the booking.
- If a review does not have a property or unit assigned, it must be set to match the booking’s property and unit.
## Review Origin Rules
- W... | 0.502636 | 0.403283 | 0.270741 | 0.337255 |
48 | # Business Rules for Accounting Schema Defaults
- The default accounting schema **cannot be deleted**. | - A default accounting schema cannot be removed. | 0.376884 | 0.705798 | 0.306913 | 0.499851 |
49 | # Business Rules for Booking Early Checkout
## Early Checkout Rules
- Each early checkout event must be associated with a specific booking.
- An early checkout event must record both the original departure date and the new (earlier) departure date.
- The new departure date must be earlier than the original departure ... | # Business Rules for Booking Early Checkout
- Each booking early checkout event must record the booking, the new departure date, and the old departure date.
- The departure date for the affected booking must be updated to the new departure date specified in the event. | 0.488731 | 0.617287 | 0.525726 | 0.571821 |
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
## 1. Tax Rate Plan Assignment
- A tax rate may be assigned to one or more rate plans.
- If no rate plans are available for a tax rate, the tax rate must be assigned to an empty list of rate plans.
## 2. Rate Plan Removal
- A tax rate may be removed from one or more rate plans... | 0.493701 | 0.362732 | 0.311989 | 0.338314 |
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 must apply only if the check-in date is within the specified period.
## Cancellation Policy Action Rules
- The cancellation fee must be calculated based on the following factors:
- Non-refundable ... | 0.381708 | -0.02653 | 0.234113 | 0.101889 |
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 Check-Out Processing
## Check-In Type and Access Code Assignment
1. When a booking’s check-in type is either KeySafe or Code Entry, the access code must be set to the code associated with that check-in type, unless an override code is specified.
2. For bookings with a Check-I... | 0.228259 | 0.424181 | 0.203013 | 0.312381 |
53 | # Business Rules for Bedding Configuration Conversion
1. Each room's bedding configuration must be converted according to the defined conversion process.
2. The conversion process must be applicable to all rooms that have not yet completed the bedding configuration conversion.
3. The conversion process may be limited ... | # Business Rules for Bedding Configuration Conversion
- Each room without a completed bedding configuration conversion status must be processed for bedding configuration conversion.
- The bedding configuration for each eligible room must be converted.
- The system must perform a final flush after each successful conve... | 0.38153 | 0.490408 | 0.468618 | 0.480336 |
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 Synchronization
1. **Dictionary Synchronization Rules:**
- All Rentals United dictionaries subscribed to for synchronization must be synchronized regularly.
- If a dictionary fails to sync, its last synchronization timestamp must be updated to reflect the latest attempt.
... | 0.261121 | -0.256145 | 0.348041 | 0.02922 |
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 Worldpay Payment by CVV
1. Each worldpay payment must be associated with the correct booking.
2. The booking must exist before a worldpay payment can be processed.
3. The worldpay client key for a booking must be determined by organization and investor deal.
4. Worldpay integration for a booking m... | 0.273142 | 0.183814 | 0.011226 | 0.097504 |
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
## 1. Cancellation Penalty Payments
- Only payments of type "OK" (Payment State: PAYMENT_STATE_OK) and not of type "Channel Pay" or "OTA Credit" may be considered for booking cancellation penalty payments.
## 2. OTCredit Payments
- Only payments of type "OTA Credit" (Payment Ty... | 0.354412 | 0.488453 | 0.388303 | 0.438822 |
57 | # Business Rules for Cost Element Management
## Uniqueness and Identification
- Each cost element within an organization must have a unique combination of name and category.
- No two cost elements in the same organization may share the same name and category, except when validating the current record being updated... | # Business Rules for Cost Element Management
## 1. Cost Element Naming and Identification
- Each cost element must have a unique name within its organization.
## 2. Cost Element Classification and Filtering
- Cost elements belonging to a specific organization and category must be retrievable by both organization and ... | 0.287268 | 0.319397 | 0.117711 | 0.217849 |
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
- No business rules are defined at the business policy level for this form type.
- All logic must be implemented at the technical or implementation level.
- No business rules apply to this form.
- All functionality must be implemented in technical code, ... | 0.345204 | 0.160544 | 0.355875 | 0.257585 |
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. Organization and Date Restrictions
- Only bookings belonging to the specified organization may be included in queries.
- Only bookings created after the current date may be included in queries if the restriction is enabled.
## 2. Join Categories
- When generating a ... | 0.155039 | -0.132801 | 0.067079 | -0.033212 |
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-Managed Bookings
- Each booking request must be processed according to the assigned channel manager.
- When a booking is assigned to the Rentals Unit channel manager, the booking must be created directly by the system.
- When a booking is assigned to the Su channel manager, the booking mus... | 0.433281 | 0.248891 | 0.42392 | 0.336037 |
61 | # Sync History Business Rules
No business rules in this set; all items are technical implementation. | # Business Rules for Sync History
- Each sync history record must have a unique identifier.
- Each sync history record may include the following metadata:
- Method of the sync request
- URI of the sync request
- Request header
- Request body
- Status code
- Response body
- Response ID
- Timestamp when ... | 0.176925 | -0.17179 | 0.135782 | -0.021145 |
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 check-in ready settings defined for all relevant brands and guests.
## 2. Guest Information and Verification
- Each check-in ready setting must include guest information and verification details.
- Eac... | 0.297465 | 0.373823 | 0.221481 | 0.297683 |
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
- Each split booking must inherit the properties (property, unit type, unit, brand, collection type, tax, creation source) from the original booking.
- The split booking must have an arrival date and a booking date set to the current date.
- The arrival t... | 0.428331 | 0.3489 | 0.303175 | 0.327032 |
64 | # Business Rules for Booking Creation and Update
## Booking Status and Access Rules
1. **Locked Bookings:** A booking that is finalized or locked cannot be edited or updated.
2. **Cancelled Bookings:** If a booking is cancelled, its status must be set to "Cancelled".
## Date and Time Rules
3. **Arrival and Departure ... | # Business Rules for Booking Creation
## 1. Guest Association
- If a guest is specified for the booking, the booking must be linked to that guest.
- The guest associated with a booking must be the one specified when creating the booking.
## 2. Booking Date and Time
- The arrival date and departure date of the booking... | 0.21539 | 0.258997 | 0.042181 | 0.149657 |
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
- Each booking change to the arrival or departure date must specify both the new arrival date and the new departure date.
- Each booking change must specify the corresponding old arrival and old departure dates.
- The arrival and departure dates must only... | 0.486852 | 0.64673 | 0.536002 | 0.591474 |
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 Message Notifications
## Notification Creation and Updating Rules
1. When updating a notification:
- Only notifications associated with existing automated messages and bookings must be considered for update.
- Each eligible notification must be linked to its corresponding automa... | 0.484332 | 0.2169 | 0.362077 | 0.289639 |
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
1. Each channel must have a code.
2. The channel must specify whether deposit handling is included.
3. The channel may be configured to collect from the customer or the hotel.
4. The channel must have a name and a name alias.
5. The commission type for the channel must be def... | 0.427714 | 0.437522 | 0.360146 | 0.399529 |
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 mapping defined.
2. **Inclusion Mapping**: Fees may be mapped based on inclusion criteria. If a fee matches an inclusion criterion, the corresponding fee value must be used.
3. **... | 0.310084 | 0.031816 | 0.262697 | 0.14603 |
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 linked to a unit type must have its purchase price set to the purchase price of the upsell.
- Each upsell linked to a unit type must have its sales price set to the sales... | 0.389426 | 0.45328 | 0.269722 | 0.360947 |
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
## 1. Booking Finalization Eligibility
- A booking may only be finalized if it is eligible for finalization according to the current status and settings.
## 2. Deposit Capture and Authorization
- A deposit capture form may only be submitted if the booking has at least one dep... | 0.435336 | 0.272393 | 0.382196 | 0.327818 |
71 | # Business Rules for Deal Collection Metadata Normalization
1. Each deal collection response must include a unique identifier representing the collection.
2. If the deal collection is paginated, the response must include metadata specifying the total number of items, current page, last page, and items per page.
3. If ... | # Business Rules for Deal Meta Normalization
- Each deal collection must include a unique identifier in its metadata.
- When dealing with paginated results, the metadata must include the total number of items, the current page, the last page, and the number of items per page.
- For non-paginated results, the metadata ... | 0.608036 | 0.683898 | 0.641652 | 0.663243 |
72 | # Deal Template Line Service Rules
1. Each deal template must include one or more service lines.
2. Each service line must include the following fields:
- Cost Element
- Charge To
- Profit Host Percent
- Profit Investor Percent | # Business Rules for Deal Template Line Service Collection
- Each deal template must include one or more service line records.
- Each service line record must include the following fields:
- Cost Element
- Charge to
- Profit Host Percent
- Profit Investor Percent | 0.89588 | 0.72318 | 0.769959 | 0.746886 |
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 File Generation
The following business rules define which types of API responses will be exported as CSV files:
1. **Guest Data**: CSV files must be generated for all requests to the guest data API.
2. **Company Data**: CSV files must be generated for all requests to the company data API.
3. ... | 0.238366 | -0.222548 | -0.060036 | -0.140809 |
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 Rate Synchronization
1. Each rate synchronization must require at least one of the following parameters: unit type ID, from date, and to date.
2. The from date and to date must be valid dates in the UTC timezone.
3. If a price is provided, it must be a numeric value and a currency code must be... | 0.442292 | 0.234439 | 0.367509 | 0.301268 |
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 in Payments
1. Each payment associated with a booking must include the guest's first name and last name.
2. The payment address must use the guest's address details if available; otherwise, it must default to the organization's address.
3. The payment postcode, city... | 0.275371 | 0.344939 | -0.035841 | 0.148803 |
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 list.
2. If the guest is not specified, all bookings must be included in the list.
3. Bookings may be filtered by a search term; only bookings whose booking code contains the search term (case-insensitiv... | 0.351003 | 0.45494 | 0.424443 | 0.440558 |
77 | # Business Rules for Guest Creation and Lookup
## Rule 1: Guest Identification
- A guest must be identified using available customer information, including email, name, surname, phone number, address, and zip code.
## Rule 2: Country Code Resolution
- The country code for a guest must be determined based on the provi... | # Business Rules for Guest Provisioning
- Each guest must be provisioned using the correct country code based on the provided country identifier.
- Each guest must be provisioned only if a valid country code is available for the provided country identifier.
- Each guest must be provisioned using the provided email, na... | 0.324442 | 0.379257 | 0.240423 | 0.310041 |
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 selected booking must be associated with the specified property, unit type, unit, channel, check-in type, or booking status as defined by the user.
2. The resolved booking properties, unit type, unit, channel, check-in type, and booking status must be applied t... | 0.54669 | 0.466705 | 0.513902 | 0.49103 |
79 | # Business Rules for Channel Deal Commission Calculation
## Channel Commission Rules
- For each booking associated with a channel deal, the channel commission must be recalculated whenever required.
- If a channel deal is active (not archived), the channel commission for a booking must be calculated as the sum of:
... | # Business Rules for Channel Commission Calculation
## 1. Commission Eligibility
- A channel commission may only be calculated for a booking if the associated channel deal is not archived.
## 2. Commission Calculation
- The channel commission for a booking must be calculated as follows:
- Calculate the total chan... | 0.381668 | 0.361871 | 0.355823 | 0.359887 |
80 | # Business Rules for Booking Entity Preparation
## Booking Timing
- Each change to arrival date, departure date, arrival time, departure time, or number of nights must be detected and processed.
## Accommodation Details
- Each change to the assigned unit, assigned unit type, check-in type, or rate plan must be ... | # Business Rules for Booking Entity Preparation
## 1. Data Consistency and Update Rules
- The arrival and departure dates, as well as the arrival and departure times, must be updated when they differ between an old and a new booking entity.
- The number of nights must be updated when it differs between an old and a ne... | 0.370652 | -0.059347 | 0.114996 | 0.027879 |
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 Synchronization
## 1. Ownership and Organization Assignment
- Each newly inserted Unit Type Rate must inherit its owner and organization from its associated Rate Plan.
- Each updated Unit Type Rate must check if the current owner or organization is missing; if so, it must set its ow... | 0.630609 | 0.589115 | 0.624344 | 0.607313 |
82 | # Business Rules for Booking Normalization
There are no business rules defined at the business policy level in this section. All logic pertains to form configuration and user interface behavior.
| # Business Rules for Booking Normalization
## 1. Key Safe Code and Arrival/Departure Time
- When a booking data includes an access code or arrival/departure time, the system must automatically enable the corresponding auto-adding feature.
## 2. Booking Summary and Details
- Only bookings for which summary access is a... | 0.119332 | -0.122333 | 0.220789 | 0.044885 |
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
## Promotion Application and Detail Rules
- A promotion application must be identified by its unique ID.
- The total price and discount for a promotion application must be calculated based on the promotion’s base price, including any applicable discounts and taxes.... | 0.306409 | 0.399829 | 0.23406 | 0.316745 |
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 states: OK, Pending, Not Authed, Rejected, Malformed, Invalid, Error, 3D Auth, Void.
- Each payment must have one of the following types: Bank Transfer, Cash, PDQ, Virtual Credit Card, PayPal, Online G... | 0.538137 | 0.401428 | 0.524511 | 0.463144 |
85 | # Payment Term Condition Business Rules
1. A payment term may include one or more payment term conditions.
2. Payment term conditions are optional; a payment term can exist without any conditions. | # Business Rules for Payment Term Conditions
- Each payment term condition must have a valid description.
- Each payment term condition may be added or removed as needed. | 0.417567 | 0.420264 | 0.456331 | 0.439151 |
86 | # Business Rules for Google Hotel Account XML Synchronization
There are no business rules defined at the business policy level in this section. All logic pertains to form configuration and user interface behavior. | # Business Rules for Google Feeding
There are no business rules in this code segment; all statements describe technical system behavior related to message processing and system operations. | 0.423466 | 0.507754 | 0.494693 | 0.502025 |
87 | # Business Rules for Parking Type Definitions
## 1. Standard Parking Types
The following parking types must be defined and available in the system:
- Street Parking
- Free Street Parking
- Underground Parking
- Driveway Parking
- Secure Parking
- Valet Parking
## 2. Ownership and Organization Assignment
Each parking ... | # Business Rules for Parking Types
- Each parking type must be associated with the same owner and organization.
- Each parking type must be created by the same user.
- Each parking type must have a name and a description. | 0.339324 | 0.497132 | 0.283165 | 0.388989 |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 9