Ratelists: Rate rule structure

How rate rules work

Rate rules are built using four key elements: Conditions, Units, Rates, and Components.

To understand how the system calculates pay or charges, think of it as a simple sentence:

"If CONDITION is true, then for each UNIT, apply RATE and call it COMPONENT."

Example: If the profession is STAGEHAND, then for each HOUR WORKED, count 10 EUR and call it BASE.

Condition (The "If")

The condition acts as a gatekeeper using TRUE/FALSE logic. If the condition is met, the system applies the rule; if not, it is skipped.

Staff related: Rating, badge, contract, or profile attributes.
Shift related: Role, profession, shift length, or shift size.

💡Read more about conditions here.

Unit (The "When")

The unit defines exactly which part of the staff member’s time is being calculated.

Worked hours: Based on actual clock-in/out times.
Planned hours: Based on the original schedule.
Flat rate: A fixed amount regardless of time spent.
Overtime: Hours worked specifically beyond the planned schedule.
Custom units: Logic for night hours, weekends, bank holidays, and others.
No rate: For creating a base rule and nesting other rules under it.

💡Read more about units here.

Rate (The "How much")

The specific amount to be paid or charged.

Hourly rate (e.g. 10 per hour)
Flat amount (e.g. 200 per shift)
Percentage (e.g. 10% bonus calculated from the base hourly rate)

💡Read more about rates here.

Component (The "What")

The component labels the amount for wallet records, exports, and PDFs. This ensures a clear breakdown for admins, staff, and clients.

Name: Used for wallet records, PDFs, and exports.
Code: Used for API integrations with accounting and other software.

💡Read more about components here.