Field notes › Running the business
Why the roster and the invoice should never disagree
Most invoice disputes in labour hire aren't really about money. They're about memory. The client's site manager remembers sending two people home at lunch on the Wednesday, your office remembers a full crew for the full week, and the invoice lands in the middle of that argument. Nobody is lying. Two people are working from different records, and the invoice is the first document that forces them to compare.
Where the disagreement starts
Trace a disputed invoice back and you usually find a change that happened on site and never made it to the office. A supervisor asked for an extra labourer on the spot and the leading hand rang someone he knew. A night shift got cut short because a crane was down. A worker was swapped out mid-swing, and the replacement's name only ever existed in a text message.
Each change made sense at the time. The problem is that it lived in one person's phone, and by the end of the month that person has moved on to three other jobs. When the invoice arrives, the client checks it against their recollection, or their gate log, or their own spreadsheet, and the lines don't match.
Bigger clients make this worse in a quiet way. The person who approves the invoice is often not the person who ran the shift. Accounts payable has no idea what happened on the Wednesday, so anything that doesn't match gets held until someone can explain it, and your cash waits in that queue.
Booked, worked and billed are different records
It helps to be clear about what each record is for. The roster says who was booked, where and on which dates. Timesheets or site dockets say who actually worked and for how long. The invoice turns that into money. Trouble starts when the roster is treated as a rough plan everyone knows is out of date, because then the worked record has nothing solid to be checked against.
Keep the roster honest and it becomes the spine the other two hang off. If the roster says Tuesday to Friday for four people and the dockets show five people on the Thursday, that gap is a question you can ask the same week, while everyone still remembers. If the roster was never updated, every docket looks equally plausible and you have nothing to argue from.
Mustr sits on the booking side of that picture. It doesn't do timesheets, payroll exports or invoicing yet; those are on the public roadmap. What it does is keep one roster that the office and the client both look at, with an audit trail of who changed what, and when. Where rates are switched on, admins see bill, pay and margin on each shift, which gives whoever raises the invoice something to check against. Workers and clients never see the dollar figures.
Capture the change on the day it happens
The habit that prevents most disputes is updating the roster when the change happens, not when someone gets around to it. That sounds obvious. In practice it means making the update quick enough that a rosterer does it from the car park, and making it one person's job rather than everyone's.
It also means treating a client's on-site request as a request, not a done deal. If a supervisor wants an extra person tomorrow, the answer can still be yes, but the extra shift goes on the roster before the person turns up. When the request is written down first, you have the record before the argument instead of after it.
Clients who can see their own roster help more than you'd expect. In Mustr each client site has its own logins, sees only its own roster and raises shift requests through its portal. Clients are told when a request is crewed, with names, and when a shift changes, with the previous details shown next to the new. A client who got that notice on the Wednesday is far less likely to be surprised by the invoice a few weeks later.
Sign-off habits that stop the argument early
Don't wait for the invoice to find out whether the client agrees with you. Get agreement in small pieces while the work is fresh.
- Agree with each client who on their side confirms the crew, and get that person's name in writing.
- Send a short confirmation of who was booked, by date, before anything is invoiced.
- Ask site supervisors to sign dockets on the day rather than in a pile at the end of the swing.
- Put any variation, like an extra person or a shift cut short, in writing the same day, even if it's a two-line email.
None of this needs to be heavy. A client who has confirmed the crew week after week rarely disputes the next invoice, and when a dispute does come up you're arguing about one shift instead of a month of recollections.
There's an internal payoff as well. Once the roster is trusted, your accounts person stops chasing rosterers for the real story behind every line, and rosterers stop keeping private notes to cover themselves.
There's more on what a client sees and can do on the client portal page, or you can book a demo and follow a change from the shift through to the client's notice.