<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Gaiya365 Notes]]></title><description><![CDATA[Gaiya365 Notes]]></description><link>https://gaiya365.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 23 Oct 2026 13:46:02 GMT</lastBuildDate><atom:link href="https://gaiya365.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How to Make an Invoice That Holds Up, for Free (US, UK and EU Checklist)]]></title><description><![CDATA[I build small browser tools, and one of them is an invoice generator. The most common question I get about it isn't about the tool at all. It's "is this a…]]></description><link>https://gaiya365.hashnode.dev/how-to-make-an-invoice-that-holds-up-for-free-us-uk-and-eu-checklist</link><guid isPermaLink="true">https://gaiya365.hashnode.dev/how-to-make-an-invoice-that-holds-up-for-free-us-uk-and-eu-checklist</guid><category><![CDATA[Freelancing]]></category><category><![CDATA[Small business]]></category><category><![CDATA[invoicing]]></category><category><![CDATA[tax]]></category><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[Gary Gao]]></dc:creator><pubDate>Mon, 19 Oct 2026 10:28:15 GMT</pubDate><content:encoded><![CDATA[<p>I build small browser tools, and one of them is an invoice generator. The most common question I get about it isn't about the tool at all. It's "is this a <em>proper</em> invoice?" People want to know whether a PDF they made in five minutes will be accepted by a client's accounts team, or hold up if a tax office ever asks.</p>
<p>The short answer: an invoice is "proper" because of what's written on it, not because of the software that made it. A Word document, a spreadsheet and a $40-a-month app all produce equally valid invoices if the right fields are there. So here's the checklist I wish I'd had when I sent my first one.</p>
<p>This is general information, not legal or tax advice. Rules change, and your country, state and business type matter. When in doubt, check your tax authority's own page (I link the main ones below) or ask an accountant.</p>
<h2>The fields almost everyone needs</h2>
<p>Whatever country you're in, an invoice someone can actually pay and file has:</p>
<ol>
<li><strong>The word "Invoice"</strong> at the top. It sounds silly, but a document titled "Statement" or with no title can get routed to the wrong place in a client's finance team.</li>
<li><strong>A unique invoice number.</strong> Each invoice gets its own number, and you never reuse one. Sequential is safest (<code>2026-001</code>, <code>2026-002</code>…). Gaps raise questions in some countries, so don't skip numbers for vanity.</li>
<li><strong>The date you issued it.</strong></li>
<li><strong>Your legal name or business name, and your address.</strong> If you trade under a name that isn't your legal name, put both.</li>
<li><strong>The client's name and address.</strong> Use their legal entity name, not just the name of the person you talk to. "Acme Outdoor Co." beats "Sarah from marketing".</li>
<li><strong>What you supplied.</strong> A description specific enough that someone who wasn't on the project understands it: "Website redesign, phase 1, as per quote Q-114" rather than "Services".</li>
<li><strong>Quantity and unit price for each line</strong>, and the line total.</li>
<li><strong>The total amount due</strong>, with the currency written out or clearly symbolised (USD, GBP, EUR). If you work internationally, "$" alone is ambiguous.</li>
<li><strong>Payment terms and a due date.</strong> "Net 14" or "Due 2 November 2026".</li>
<li><strong>How to pay you.</strong> Bank details, a payment link, or both.</li>
</ol>
<p>If you only do these ten things, you're already ahead of most first invoices I've seen.</p>
<h2>United States</h2>
<p>There is no single federal invoice format in the US. What the IRS cares about is that you can back up the income and expenses on your return, so your invoices are part of your records. In practice that means the ten fields above, plus:</p>
<ul>
<li><strong>Sales tax, if it applies.</strong> Sales tax is set by states (and sometimes cities), not federally. Many services aren't taxable in many states, but some are, and physical goods usually are. If you charge it, show it as a separate line with the rate.</li>
<li><strong>Keep copies.</strong> The IRS's general guidance is to keep records for at least three years after you file, longer in some situations. A folder of PDFs named by invoice number is fine.</li>
</ul>
<p>Things people often think belong on an invoice but don't: your Social Security number (never put it there) and a W-9. If a US client needs your taxpayer details for a 1099, they'll ask for a W-9 separately. Sending it securely and separately is better than printing tax IDs on every invoice.</p>
<p>Official reading: <a href="https://www.irs.gov/businesses/small-businesses-self-employed/recordkeeping">IRS: Recordkeeping for small businesses</a>.</p>
<h2>United Kingdom</h2>
<p>The UK is more specific, and it depends on whether you're VAT-registered.</p>
<p><strong>Every UK invoice</strong>, according to GOV.UK, must include a unique identification number, your business name, address and contact information, the customer's name and address, a clear description of what you're charging for, the date the goods or service were provided (the supply date), the date of the invoice, the amounts charged, VAT if applicable, and the total owed. If you aren't VAT-registered, you can't charge VAT, so leave it off.</p>
<p><strong>Sole traders</strong> also need their own name next to any business name, and if you trade under a business name, an address where legal documents can be delivered to you.</p>
<p><strong>Limited companies</strong> must use the full company name exactly as it appears on the certificate of incorporation. If you list directors on the invoice, you have to list all of them, so it is simpler to list none.</p>
<p><strong>If you're VAT-registered</strong> and your customer is too, you need a full VAT invoice. It adds your VAT registration number, the time of supply (tax point) if it differs from the invoice date, and for each line the unit price, quantity, VAT rate and amount excluding VAT, followed by the total excluding VAT and the total VAT. Show any discount.</p>
<p>Official reading: <a href="https://www.gov.uk/invoicing-and-taking-payment-from-customers">GOV.UK: Invoicing and taking payment from customers</a> and <a href="https://www.gov.uk/guidance/record-keeping-for-vat-notice-70021">GOV.UK: Record keeping for VAT (Notice 700/21)</a>.</p>
<h2>European Union</h2>
<p>EU VAT invoices follow Article 226 of the VAT Directive, which each country implements in its own law. The common core is close to the UK VAT list: sequential number, issue date, supplier and customer names and addresses, supplier VAT number, the customer's VAT number for cross-border B2B, quantity and nature of goods or extent of services, the supply date if different, taxable amount per rate, the VAT rate, VAT payable, and the unit price excluding VAT.</p>
<p>Two EU cases that trip up freelancers:</p>
<ul>
<li><strong>Reverse charge.</strong> If you sell services B2B to a business in another EU country, you usually don't charge VAT; the customer accounts for it. The invoice should show both VAT numbers and a note such as "Reverse charge". Countries have their own preferred wording, so check yours.</li>
<li><strong>Language and currency.</strong> Some countries have rules about the language of the invoice or require the VAT amount in their local currency. If you invoice in a foreign currency, check.</li>
</ul>
<p>Official reading: <a href="https://europa.eu/youreurope/business/taxation/vat/invoicing-rules/index_en.htm">Your Europe: Invoicing rules</a>.</p>
<h2>Mistakes that get invoices bounced</h2>
<p>From my own invoices and from people who've emailed me:</p>
<ul>
<li><strong>No PO number.</strong> Larger clients often won't pay without their purchase order number on the invoice. Ask for it before you send. Add it as a line under the client's address.</li>
<li><strong>Wrong legal entity.</strong> Billing "Acme" when the contract is with "Acme Holdings Ltd" means accounts payable sends it back.</li>
<li><strong>Totals that don't add up.</strong> If you calculate tax per line and round each one, you can end up a cent away from the total the client's system calculates. Rounding once per tax rate on the subtotal is the usual approach, and it's what most accounting software expects.</li>
<li><strong>Editing an invoice after sending it.</strong> Don't change a sent invoice. Issue a credit note for the old one and a new invoice with a new number. That keeps your numbering clean.</li>
<li><strong>No due date.</strong> "Payable on receipt" is legal but in practice gets you paid last. A specific date gets you paid sooner.</li>
</ul>
<h2>Making one for free</h2>
<p>You don't need paid software for this. Three options that work:</p>
<p><strong>A spreadsheet.</strong> Make a template once with the fields above, then "Save as" for each new invoice. The risk is formulas: test your totals with awkward numbers like 12.5 hours at $85.</p>
<p><strong>A plain HTML template.</strong> If you're comfortable with a bit of code, an HTML page with a print stylesheet prints to a clean PDF from any browser. I published the template I use as open source, with the totals done in integer cents so rounding is predictable.</p>
<p><strong>A browser generator.</strong> If you just want to fill in fields and download a PDF, I made a <a href="https://invoice.gaiya365.com/">free invoice generator</a> that runs entirely in your browser. Nothing you type is uploaded, there's no account, and the free PDFs are unlimited. (Full disclosure: it's my tool. There's an optional one-time Pro upgrade that removes a small footer line, but the free version has every field on this list.)</p>
<p>Whichever you use, run through the checklist before you hit send. It takes thirty seconds and saves the awkward "can you reissue this?" email two weeks later.</p>
<h2>A copy-paste checklist</h2>
<pre><code>[ ] "Invoice" title
[ ] Unique, sequential invoice number
[ ] Issue date (and supply date if different)
[ ] My legal/business name and address
[ ] Client's legal entity name and address
[ ] Client PO number (if they use them)
[ ] Clear description per line, quantity, unit price, line total
[ ] Tax shown separately with rate (if I charge tax)
[ ] My tax/VAT number (if registered)
[ ] Client's VAT number + reverse charge note (EU/UK cross-border B2B)
[ ] Total due with currency code
[ ] Due date and payment terms
[ ] How to pay me
[ ] Full registered company name (UK/EU companies)
</code></pre>
<hr />
<p><em>Gary builds small, privacy-first browser tools at <a href="https://gaiya365.com/">Gaiya365</a>.</em></p>
]]></content:encoded></item></channel></rss>