Work orders that authorize every hour billed
Large clients approve work through work orders with their own dates and budgets. Doktally bills each hour under the right one, shows what is used and left, and splits a month between them.
The problem
An enterprise client does not pay for hours, it pays for hours under a work order: WO-A for the backend, WO-B for the frontend, each with its own validity and an approved number of hours. Their accounts payable rejects an invoice that does not name the work order or goes over its budget.
How Doktally solves it
- Work orders per client, for one project or all of them, valid for their own dates or the contract's term, with an optional authorized number of hours or amount. Rates still come from the project or contract.
- Usage at a glance: billed plus on drafts, against what was authorized, with what is left or over, and a warning near the limit and when an invoice would exceed it.
- Allocation rules split a month across work orders by percentage or by fixed hours. With a 60/40 rule, 100 hours become 60 on WO-A and 40 on WO-B.
- Required work orders: if the client requires one, an invoice with hours that have none cannot be issued.
- Named on the invoice: each line says "WO-A: Backend Development"; the name is copied when the draft is made, so a later rename never changes an issued invoice.

The result
Invoices pass the client's approval the first time, and nobody finds out from a rejected invoice that a work order ran out.
Technologies
Work orders, Billing, Spring Boot
- Published: 2026-11-19
- Project: Doktally — Invoicing, time billing and VAT for small businesses
- Case study