I set out this morning to write something genuinely boring. A practical guide on automating invoicing. Convert the quote, stop re-typing the client's details, let reminders go out on their own. I have written around the edges of this before, about becoming my own bookkeeper and about the invoice I almost did not send, so I thought I knew the shape of it.
It took about forty minutes to find something that changed how I think about the whole exercise.
The habit that caught it
I did not start in a search engine. I have stopped doing that, for reasons I wrote about yesterday. I downloaded the actual guide and read the chapter.
Two things came out of it quickly. The first is that issuing a tax invoice is not a courtesy, it is an obligation with a deadline: twenty one days from the supply. The second is the sentence I did not expect, which says in plain words that failing to issue tax invoices is a contravention of the Act and that vendors will be guilty of an offence.
I have thought of late invoicing as a cash flow problem for my entire working life. It is also, apparently, an offence. Nobody has ever mentioned that to me.
Then the part that actually stopped me
Further in, there is a rule about when a supply is treated as having happened. It is the earlier of two events: the invoice being issued, or payment being received.
Sit with that for a second, because I had to.
The invoice going out is what starts the tax. Not the money arriving. Issue the invoice, and the VAT on it belongs to that tax period whether or not the client has paid you a cent.
Which means the thing I was about to recommend, cheerfully, to every reader of the other post, has a consequence I had not thought about. Automate your invoicing well and invoices go out faster and more reliably than before. Some of them cross into an earlier tax period than they would have. You declare sooner. You may hand over the VAT before the client has paid.
That is not a reason to keep doing it by hand. It is a reason to know what you are changing. But it took me from writing a productivity tip to writing something with a warning in it, and the only reason I found it is that I opened a file I did not strictly need to open.
The founder tax
Here is the thing I actually want to say, and the reason today felt different from a normal research day.
When you work for someone else, those are two different people's jobs. Someone decides to speed up invoicing because the process is slow. Someone else, in finance, knows what that does to the VAT position. They may never speak. The system works anyway, because both bases are covered by somebody.
On your own, that handoff does not exist. It is the same decision, made once, by you, and there is no second person whose job it is to notice the other half. Speeding up invoicing is an operations decision and a tax decision simultaneously. Nobody sends you the memo, because you are the person who would have written it.
That is the founder tax. Not the money. The fact that every improvement arrives with a second consequence attached, in a field you have no training in, and the only way to find out is to go looking for something you do not yet know exists.
It is a strange thing to be responsible for. You cannot research everything. You cannot open every guide before every decision. So you develop a rough sense of which changes are likely to have a hidden second half, and you check those. I am getting better at it, mostly by being wrong.
Why I keep writing these
Someone asked me recently why I publish compliance guides when I sell automation. The honest answer is not marketing strategy.
It is that writing the guide is how I find out what I am responsible for.
I did not know about the twenty one days until I had to explain it to someone else. I did not know that issuing the invoice starts the tax until I sat down to tell people how to issue invoices faster. Explaining something forces a completeness that reading it never does. You can read a chapter and absorb the gist. You cannot write the sentence "here is when you must do this" without going and checking exactly when.
When I stopped shipping features and started reading the law I framed it as a marketing decision that turned into an education. Today was the clearest version of that yet. The post is for whoever reads it. The reading was for me.
What I am doing about it
Nothing clever. Two small things.
I am adding a question to how I evaluate any process change in my own business: what does this touch that I am not thinking about. Not a general instruction to be careful, which never works. A specific prompt at a specific moment.
And I am going to keep opening the document. It has now paid for itself three times in one week, which is more than most of my habits manage.
The version of me who started this would have written the invoicing post in an hour from general knowledge. It would have been fine. It would have been wrong in a way nobody would have caught, including me.