Most platform work does not need one, until it does

Almost all platform-mediated rating work never involves an invoice. The platform takes the payment, issues its own documentation and pays you a net figure, and your record of the transaction is its payout statement.

Then one buyer asks, and the question is easy if you have a template and awkward if you do not.

When one is actually needed

Four situations, and they are all recognisable in advance.

A buyer paying you directly rather than through a platform, which happens on larger commissions and on anything arranged outside a marketplace. A buyer who is a business and needs the cost documented for their own records. A recurring or staged arrangement where payment follows delivery rather than preceding it. Any job large enough that you would want written terms anyway - contracts for larger jobs covers where that line sits.

Direct payment is the one worth pausing on. An invoice is the paperwork half of a transaction that has also removed the platform's payment protection, and the commission saving being offered is not the whole of the trade.

What one generally contains

Requirements differ by country and by whether you are registered for any sales tax, so treat this as the common core rather than a compliant document. In the UK, for instance, GOV.UK's invoice guidance requires sole traders to show "your name and any business name being used", alongside a unique identification number.

The word invoice, a unique number and the date it was issued. Who is issuing it and who it is for. A description of what was supplied, with the date it was supplied. The amount, the currency, and any tax shown separately if you charge it. Payment terms and how to pay.

The identity line is the one that catches earners in this trade. An invoice generally has to identify the issuer, which can mean a legal name and an address, and that is precisely the disclosure a working alias exists to prevent. There are ordinary answers - a business name, a service address, a company structure - and they all need setting up before the request arrives rather than during it. Anonymity as an earner covers the wider version of that decision, and this is the point at which it stops being theoretical. What personal data ends up sitting in someone else's filing system as a result is worth thinking about in the same sitting, and Ai Penis's privacy material describes the conventions this sector generally works to.

The numbered sequence

Number them sequentially from the first one, with no gaps, and keep every number you issue even if the job is cancelled.

A gap is the thing that gets asked about, because a missing number looks like a hidden transaction. If one is voided, keep it and mark it void rather than deleting it and reusing the number.

Start at one, in a spreadsheet, in the same file where you already log jobs - the records you will wish you kept is the rest of that list. A word processor template and a numbered row is the entire system, and it does not need software.

Keep the sent copy as a file rather than as something you could regenerate. If a payment is later contested, the document you actually sent, with its date, is the evidence; a reconstruction is not, and evidence that actually wins a dispute explains why that distinction decides cases. Retention conventions across this sector are described in Measure My Cock's material on data, and the invoice sequence is the one set of records worth keeping past the point you stop trading.

Buyers commissioning direct work generally expect this paperwork as a matter of course rather than as a favour, which Rate Penis's material on commissioning etiquette describes from their side. For platform-mediated work the equivalent record is the payout statement, and Rate Cock's rewards and payouts page is where its own statements are described. Build the template on a quiet evening. It takes twenty minutes once and never takes twenty minutes again.