The invoice for every payment, without missing a single one
You'll know what detail decides between a full invoice and a simplified one, and how to set up your invoicing software so every payment ends up with its own document and number, without relying on your memory.
By Yodai · Published on September 6, 2026 · Updated on October 12, 2026
Deciding when a full invoice is needed, when a simplified one will do, and which number goes on each is half the job. The other half: if you have to remember it yourself every single time, checking who bought and pulling up the document by hand, you're going to slip up one day: a rushed Friday, a sale made from your phone on the street, ten bookings in a row on a Monday morning.
The question in this lesson isn't which document to send, that was settled back in the first lesson of the course. It's how you make that document come out without depending on your memory. Usually the invoice is handled by a separate invoicing program, apart from the payment gateway you use to get paid: if it knows about every sale, the document comes out on its own; if not, you need a fixed routine to check.
The detail that decides which document applies
One detail decides almost everything: if the customer gives a tax ID and a business name, it's a business or self-employed purchase and a full invoice is required. If they pay without that detail, it's a private customer and, as long as the amount falls within the legal limit for a simplified invoice, that's all they need. You didn't just invent this split, it's the same one you saw at the start of this course. For the document to come out on its own, that detail has to be captured at checkout: in a field on the payment form or your invoicing program, if it has one, or by asking for it yourself before charging.
What's missing is the second half: making sure your invoicing program already has a number series and a delivery method set up for each of those two branches, so the document doesn't have to wait for you to open your computer at night.
- 1Set the detail that decides
In your invoicing program, the tax ID and business name field has to be what opens or closes the full-invoice branch. If it's empty, a simplified invoice goes out, as long as the amount allows it; if it's filled in, a full invoice goes out. You don't decide that by reading the order, the data decides it the moment it's entered. - 2Attach each branch to its own series
The sequential numbering you already set up has to be tied to each document type, not to you. Your program pulls the next number from the right series, you never write a number by hand again. - 3Tie delivery to the payment, not a reminder
If your invoicing program connects with your payment gateway, the document can go out the moment the money is confirmed, not whenever you remember to check the day's list of payments. If they don't connect, that link is the missing piece, and until then, use the fixed check below. - 4Test it before you trust it
Use your program's or gateway's test mode, if they have one, or check the first real sales of each type by hand: one from a private customer, one with a tax ID. Don't charge yourself to test it, a test charge isn't a sale and doesn't need an invoice. Check that two different documents arrive, with the right number, in the customer's inbox and not just yours.
Exceptions don't ride the same conveyor belt
Not every payment is a sale, and you already know that from this course too: a security deposit that gets refunded, or a test charge, doesn't need an invoice. A down payment does: it's part of the price paid upfront and needs its own document. If your automation fires off a tax document blindly every time money comes in, you'll end up generating paperwork you later have to cancel. The automatic-send rule applies only to payments marked as a sale, everything else stays off the conveyor belt, even if it goes through the same gateway.
- It goes out immediately, no gap between the payment and the document
- It doesn't depend on you having free time that day
- The customer gets it before they even ask for it
- You can fix an odd detail before it goes out
- Works fine if you only take a few payments a week
- Every extra payment is one more thing to review
Which one should I pick: If you take payments more than two or three times a week, automate it, every manual step is a gap where something gets forgotten. If your payments are few and you can look them over calmly, checking by hand costs nothing, but once the business grows, that's the first thing that gets skipped when you're busy.
- The tax ID and business name you collect at checkout decide the branch: full invoice or simplified.
- Each path pulls from its own numbering without you ever typing a number by hand.
- The document goes out as soon as the payment is confirmed, if your invoicing program is connected to it; if not, with a fixed check, not whenever you happen to remember.
- Payments that aren't sales, like a security deposit or a test charge, stay out of this automation; a booking deposit doesn't, since it's part of the price.
- You've tested it on every path before calling it good.
- There's one loose end for the next lesson: what to do when someone asks you for an invoice after you've already given them the receipt.