Turn Completed Jobs Into a Cleaner Invoice

Create a cleaner invoice from completed jobs, review calculated pay, preview the document, and generate it only when the selected work and totals are correct.

What you will accomplish

By the end of this guide, you will be able to complete a cleaner invoice 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

• Confirm jobs are completed and cleaner rates are configured.
• Know the invoice date range, staff member, billing party, and tax treatment.
• 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 Jobs to Invoice

Go to Cleaner Invoices and open Jobs to Invoice. Start with Ready to invoice when creating a new document.

Expected result: Eligible completed jobs are listed.

Step 2: Choose the date range

Set the service period that contains the jobs. Keep the range within the limit shown by the page and wait for the report to refresh.

Expected result: The list covers the intended billing period.

Step 3: Filter completed work

Use status, job type, unit, and staff filters. Clear old filters if an expected job is missing.

Expected result: Only the cleaner’s intended completed work remains.

Step 4: Review rates and select jobs

Check each amount and select the jobs to include. Do not select a $0 or missing amount until its source rate has been reviewed.

Expected result: The selection count and amounts are correct.

Step 5: Open the invoice draft

Select Create invoice and wait for billing details, selected jobs, and totals to load.

Expected result: The draft contains exactly the selected jobs.

Step 6: Complete billing details

Choose Billed from, verify Bill to, enter tax when applicable, and add a note or adjustment only when needed.

Expected result: The parties and calculation inputs are complete.

Step 7: Preview the invoice

Select Preview invoice and inspect every page, line item, subtotal, adjustment, tax, and total.

Expected result: The rendered document is ready to issue.

Step 8: Generate and verify

Generate the invoice, confirm any warning intentionally, then open Generated Invoices and verify its number, amount, and status.

Expected result: The new invoice is visible once and matches the approved preview.

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.