Why you should approve every invoice before it is sent

Drafting is not approving

It is easy to blur three different actions: preparing an invoice, deciding it is right, and sending it to a customer. They carry different risks. Preparing is harmless. Approving is where you take responsibility. Sending is the point of no return, because the customer now has a document you cannot quietly take back.

What a good approval step looks like

• You see the finished document. The PDF the customer will receive, not a summary of it.
• The numbers are checked by software, not hope. Totals and tax are calculated, not typed from memory.
• Changes are visible. If something was edited after you looked, you see it again.
• Sending is its own button. Approving does not send, and a request for a draft is never read as permission.

Why this matters more with assistants

Assistants are fast, and speed is the problem when a mistake is hard to reverse. A sensible assistant proposes, shows the result and waits. It does not report something as sent or paid unless that really happened, and it does not do arithmetic it cannot show its work for.

How Invo.tax handles it

Every Invo.tax invoice follows the same path: a draft you can read, a PDF preview, your approval, then saving and sending as separate actions. Reminders and thank-you emails stay off until you switch them on for a particular invoice, and the final reminder asks you first. It is slower than blind automation by about ten seconds, which is the point.