A cleaning invoice arrives after the work has finished, but the information needed to review it should already exist. Which property was serviced? What was the agreed scope? Was extra work authorised? When those details are missing, even a small invoice becomes a chain of messages.
Build the review around the job record, then use Xero for the accounting handover. Xero calls a supplier invoice a bill and supports saving it, submitting it for approval or approving it. The workflow below is an operational model to adapt to your team's permissions and accounting process.
Capture the evidence while the job is open
Record the supplier, property, service date, agreed rate and task reference before service. When the clean is completed, attach the completion record and any approved extras. If a supplier invoices several properties together, keep the individual job references available for each line.
Give the supplier a consistent submission channel. Multiple copies sent to a coordinator, the owner and the accounts team make it harder to identify the authoritative document. Keep the original invoice attached to the review record rather than replacing it with a rewritten version.
Use a small set of review checks
| Check | What the reviewer confirms |
|---|---|
| Supplier and reference | The invoice belongs to the correct supplier and has not already been recorded |
| Service delivered | The property, date and scope match a completed job |
| Amount | Rates and extras match the agreed service record |
| Exceptions | Any disputed line has an owner and a documented resolution |
| Handover | The source document and job references remain available to accounts |
Keep operational sign-off separate from accounting treatment. The coordinator can confirm that a clean occurred; the person responsible for bookkeeping should decide how the bill is coded. Do not ask cleaners to infer internal account codes from an inconsistent property name.
Set approval authority before invoices arrive
Decide who can confirm a standard clean, who can approve an agreed extra and who resolves a disputed line. Those may be different people. If every small variation waits for the portfolio owner, the review queue becomes a bottleneck; if everyone can approve an exception, the agreed rate stops being a control.
| Situation | Suggested decision owner |
|---|---|
| Standard service matches the completed job | Operations coordinator confirms delivery |
| Previously authorised extra appears | Person who approved the extra confirms the record |
| Scope or amount is disputed | Property manager resolves the service question |
| Account coding or payment is uncertain | Accounts team reviews the bill |
This is a model to adapt to your organisation, not a substitute for its financial approval policy. Document the handover point between operational review and the person who has authority to approve the bill in Xero.
Review the difference, not the entire history
When the amount differs from the agreement, identify the line and the reason. Extra linen, additional time or a changed scope should have a record that the reviewer can inspect. If that record is missing, assign the question to the person who authorised the work.
Do not silently net a disputed adjustment against unrelated completed work. Keep the proposed change, supporting evidence and agreed outcome visible in the record. That gives the accounts team a clear document trail and avoids turning an operational disagreement into a reconciliation problem.
Make the Xero handover traceable
Choose a consistent supplier reference and property naming convention. Record which job or group of jobs was sent to Xero and keep the returned bill reference where the operations team can find it. If you use an integration, test this mapping with a small sample before relying on it for a full payment cycle.
A failed or uncertain sync needs investigation before a retry creates another bill. Check whether the first attempt produced a record. Xero documents a duplicate warning when the reference and contact name match an existing bill; keep your own job-to-bill check as well, especially where references are entered differently.
Handle corrections without losing the original trail
A supplier may resend an invoice with a corrected amount or issue a credit after a dispute. Keep the original document, the supplier's replacement or credit and the reason for the change together. Do not edit an approved amount in a separate operations record and leave accounts working from the earlier document.
When a job is cancelled, check whether the supplier had already incurred a cost under your agreement before treating the invoice as an error. Record who confirmed the cancellation terms. The aim is to give both operations and accounts the same explanation for what is payable, without relying on a verbal conversation that disappears before the next payment run.
Distinguish approval from payment
A completed task, an approved supplier invoice and a paid bill are different events. Show them separately so a cleaner asking about payment receives an answer based on the accounting record, rather than an assumption that completion triggered a transfer.
Before a payment run, reconcile approved invoices awaiting handover, bills awaiting resolution and payments already recorded. Give each exception one owner. This is more useful than a shared spreadsheet where several people can mark the same invoice as finished with different meanings.
Start with one payment cycle
- Agree who confirms service, who approves the bill and who handles payment.
- Use one supplier submission channel and retain the source invoice.
- Test a normal bill, an invoice with extras and a duplicate submission.
- Check failed-sync recovery before enabling unattended retries.
- Review unresolved differences before the next payment cycle.
The goal is a short, inspectable path from completed work to an accurate bill. Once the routine checks are consistent, automate the straightforward handovers and reserve review time for the cases that genuinely need a decision.
