Guides · Operations & Billing

Manday billing explained: how labor camps actually bill worker accommodation

Commercial camp operators in the GCC bill their clients per manday: one worker accommodated for one day. It sounds trivially simple, and that simplicity is exactly why so many operators run it in Excel — until the volume, the rate tiers, and the mid-month movements turn month-end into a reconciliation project. This guide walks through how manday billing works and where it breaks.

The billing model

A camp houses workers belonging to one or more client companies. Each client has a contract that defines rates, usually varying by:

• Room type — a bed in a 6-man room bills less than a bed in a 2-man room or a private room.
• Client tier — negotiated rates differ per client, sometimes per project.
• Services included — accommodation only, or accommodation plus catering, laundry, and transport.
• Overflow — beds occupied above the contracted block, often at a different rate. This is the most commonly unbilled revenue in the industry.

The month's invoice for a client is, in principle: for every worker of theirs, for every day, the rate of the room type they occupied that day. The complexity is entirely in the words that day — workers arrive mid-month, transfer between rooms, move between camps, and check out early.

Why spreadsheets get it wrong

Occupancy history, not occupancy snapshots

A spreadsheet holds who is in which room now. Billing needs who was in which room on each day of the month. Reconstructing that history from a snapshot plus memory is where errors enter — a transfer logged three days late is billed at the wrong room rate for three days, for that client, silently.

Disputes with no evidence

When a client questions an invoice line, the operator needs a room-by-room, day-by-day breakdown for that worker. If producing it takes a day of Excel archaeology, disputes drag, payments stall, and relationships strain.

The overflow leak

Project surges push camps past contracted capacity. Informally logged overflow workers frequently never reach the invoice at all — occupied beds that earn nothing.

What automated manday billing changes

The structural fix is to derive billing from operations instead of reconstructing it afterwards. When check-ins, transfers, and checkouts are recorded as they happen:

• Every occupied bed-day generates a manday at the correct client and room-type rate, automatically.
• Month-end is a review, not a rebuild — the numbers already exist, grouped by client, camp, and room type.
• Any invoice line expands into an audit-ready day-by-day breakdown in one click, which is what ends disputes.
• Overflow is tracked as its own billable category instead of leaking.
• The invoice generates directly from the billing data — in Saudi Arabia, with the ZATCA-required QR code attached.

This is the core of what Bydexo CMS automates, and the difference is measurable: check-in-driven billing with per-client rates is the reason operators report near-zero billing errors after leaving spreadsheets. For a feature-by-feature view against Excel and legacy tools, see the comparison table.