Set Cleaner Pay Rates

Cleaner rates determine how completed work is valued for staff invoices. Configure the most specific rule needed and verify the result on a sample job before invoicing a full period.

What you will accomplish

By the end of this guide, you will be able to complete a cleaner pay rate from the correct CleanOver screen, understand the important checks before saving, and verify that the result is visible to the people who use it next.

Before you begin

• Know whether the rule applies to a worker, company, unit, job type, subtype, or holiday.
• Confirm the amount, currency, and effective dates with the approved pay schedule.
• Sign in to the Admin workspace and confirm you are in the correct business context.
• Use real operational dates and the property’s local timezone when the workflow includes time.

Step 1: Open Rates

Go to Cleaner Invoices > Rates. Review existing worker, group, unit, and holiday rules before creating another one.

Expected result: You understand which rule currently supplies the amount.

Step 2: Choose the correct scope

Select the cleaner or group and narrow by unit or job subtype only when their pay differs from the default.

Expected result: The new rule is no broader than necessary.

Step 3: Enter the amount

Set the flat amount or supported calculation values using the business currency. Check decimal placement carefully.

Expected result: The stored amount matches the approved rate.

Step 4: Set effective dates

Use start and end dates when the rate is seasonal, temporary, or part of a scheduled increase.

Expected result: Past and future work receive the intended rule.

Step 5: Handle holiday rules separately

Use Holiday Rates for date-specific premiums instead of replacing the normal base rate.

Expected result: Normal days keep their original pay amount.

Step 6: Save and inspect precedence

After saving, review overlapping specific and default rules. More specific rules may override broader ones.

Expected result: Only one intended calculation wins for the sample job.

Step 7: Verify in Jobs to Invoice

Open a completed sample job in the invoice report and confirm the displayed cleaner amount.

Expected result: The report uses the new rate.

Step 8: Protect generated invoices

Remember that already generated invoices keep snapshots. Refresh a draft or follow the approved void-and-regenerate process when a historical correction is required.

Expected result: Rate maintenance does not silently rewrite accounting history.

How to confirm the workflow is complete

• Refresh the destination list or calendar and confirm the saved record appears only once.
• Check the unit, date, status, owner or assignee, and any linked record before leaving the page.
• Open the next downstream view mentioned in the guide and confirm it shows the same information.
• Record an internal note when the action corrects historical data or changes another person’s responsibility.

Common issues and what to do

The expected record is missing

Clear old filters, check the date and business context, then search by the most specific identifier available. If the data comes from a connected provider, check connection and mapping status before recreating it manually.

A button is disabled

Look for a required field, incomplete checklist item, missing permission, locked lifecycle status, or unresolved linked task. Complete the highlighted requirement instead of trying to bypass it.

The page shows different information after refresh

Another user or integration may have updated the record. Compare timestamps and the source system, then apply the correction in the system that owns the data.

You are unsure whether to continue

Stop before cancelling, overwriting, revoking, or issuing a financial document. Ask the workflow owner to confirm the intended outcome and add that decision to the internal record.

Best practices

• Use clear names that make sense to a new team member without extra context.
• Prefer the smallest safe scope for bulk actions, filters, permissions, and date ranges.
• Keep guest-facing communication separate from internal diagnostic notes.
• Verify a high-risk change in a second view before considering it finished.
• Update the source configuration when the same correction is needed repeatedly.