A stack of crew invoices after the show
The show finished last week. Twenty-odd freelancers now send invoices: some as PDFs, some in the body of an email, some through an invoicing app. Each one lists days, a day rate, sometimes a half day, overtime past a certain hour, mileage, parking, a meal, kit they brought. One lists four days when you think they did three. One uses a higher day rate than you agreed. Two forgot the event name.
Your bookkeeper asks the production manager about each one. The production manager is on the next build and answers from memory. Freelancers wait to be paid and start chasing.
Why checking crew invoices is slow
Every invoice is a small puzzle, and the pieces are in different places: the booking, the agreed rate, the call sheet, the actual hours, the overtime rules.
- Crew invoice in different formats and with different levels of detail.
- Agreed rates and overtime rules differ by role and sometimes by person.
- Hours actually worked are rarely recorded, so overtime is hard to check.
- Expenses rules (mileage, parking, meals) are not written down consistently.
- The person who can check is always on the next job.
Why it matters beyond the money
Overpayments add up quietly across a season. Underpayments or slow payments damage your reputation with freelancers, who talk to each other and choose who to work for when the calendar is busy. Disputes about hours are awkward when there is no record, and the production manager ends up choosing between a relationship and the budget.
There is a finance cost as well. When invoices are not coded to an event and a role, the event's labour cost is only known once someone sorts them, so the event budget shows crew as a single guess until long after the show. Kit hire charged on a crew invoice may duplicate kit you also hired from a supplier, and nobody spots it because the two invoices are checked by different people at different times.
Year end brings its own version of the problem, when your accountant asks for a breakdown of freelance costs and someone has to rebuild it from a year of PDFs.
Invoice checks against the booking
- Each confirmed booking holds the role, dates, agreed day rate and overtime rule, and the expenses policy for that event.
- Hours are recorded on site when crew check in and out, or entered by the crew chief at the end of each day.
- Invoices arrive in an accounts inbox or through your accounts package, and an extraction step reads days, rates, overtime, and expenses lines.
- Each line is compared with the booking and recorded hours: days worked, rate, overtime past the agreed point, expenses against the policy.
- Matching invoices are marked ready to approve in your accounts package, such as Xero or QuickBooks.
- Differences are sent to the production manager as a short list with the evidence: the booking, the hours, the policy line.
- Freelancers can see the status of their invoice through their crew link, so they do not need to chase.
| Invoice line | Booking says | Recorded | Result |
|---|---|---|---|
| Four show days | Three show days | Three days | Query |
| Day rate | Agreed rate | N/A | Higher than agreed: query |
| Overtime | After agreed hour | Late finish on day two | Matches |
| Mileage | Per event policy | N/A | Matches |
After the show, invoices mostly check themselves
Most crew invoices match the booking and the hours, and go straight into the payment run. The production manager receives three queries on their phone, each with the evidence, and resolves them in minutes. Freelancers get paid in your normal cycle and can see where their invoice is. Over a season, you also see which rates and overtime rules cause most queries, and can make them clearer in the next booking.
Does this match your crew invoicing?
- Crew invoices are checked against call sheets and memory.
- Actual hours are not recorded on site.
- Overtime and expenses rules are unclear or inconsistent.
- Freelancers chase you for payment status.
- The production manager is the bottleneck for approving invoices.