Bill from the milestone, not from a message
Most month-end disagreements between delivery and finance come from one figure being typed twice. Here is how an invoice can start from the milestone instead.
Ask a finance team why an invoice went out late and the answer is usually a conversation. Delivery finished the work on the 12th. Finance heard about it on the 20th, asked for the amount, got a number in a message and typed it into the invoice.
Nobody in that chain was careless. Each step made sense on its own. The trouble is that the milestone, the amount and the invoice are three separate records, and a person has to carry the figure from one to the next.
Start from the approved milestone
In Kora, an invoice request begins from a project milestone that is approved and ready to bill. The client and the amount are already on the milestone, so whoever raises the request does not enter them. They can only ask for what delivery has already signed off.
Keep asking, approving and issuing apart
Requesting, approving and issuing an invoice are separate permissions. A project manager can ask for an invoice without being able to issue one. A reviewer can approve the request, or query it with a question when something looks wrong. A request raised by mistake can be withdrawn until an invoice has been issued.
Issuing is the only step that assigns an invoice number. Until then nothing has gone to the client, so there is nothing to cancel.
Three checks at month-end
- Every approved milestone has an invoice request, or a reason it does not.
- Every request is approved, queried or withdrawn. None are waiting unread.
- The invoices issued this month match the milestones approved this month.
When those three agree, the month-end conversation between delivery and finance is a short one.
See billing