Approve a job before it is invoiced

Plenty of service businesses want somebody to look at a finished visit before it is charged for, especially when the crew added work on site. That check is a status.

Setting it up is one tick on whichever of your own statuses means "done, but not checked yet" (Set up your job statuses). You start with a status called Awaiting approval already marked that way.

What then happens. Moving a job into that status parks it and asks the person who approves. The job says so at the top of its page: This job cannot be invoiced yet, along with This job is waiting for {{names}} to approve it.

While it is parked, the job cannot be invoiced. That refusal is the point: without it the status would be a label rather than a control, and the invoice would go out while somebody believed they were still going to check it.

Approving is Approve this job on the job itself, or from the notification, which links straight to it. After that the job reads Approved. This job can be invoiced. and can be invoiced.

If the total changes, the approval does not carry. Approve a visit at one figure, then tick off another thirty thousand kroner of work as delivered, and it goes back for approval at the new number. Otherwise "get the small version approved, then add to it" would walk straight through.

If nobody is set up to approve, the job invoices as normal rather than getting stuck: This job is waiting for approval, and nobody has been named to give it. Ask an administrator to look at it. A company that has not named an approver should not become unable to bill.

This is the same approval mechanism used for quotes and offers, so the amount thresholds and per-customer rules you have already configured apply here too.