technology
Invoice Ninja: prepare, review, then send
- Preparing an invoice and sending it are separate actions.
- Invoice Ninja keeps client details, line items, documents and status in one billing system.
- An API can remove repeated entry while keeping a deliberate review before anything reaches the client.
You finish the work, then open an old invoice to copy the layout. Change the client, the description, the date, the reference. Read it again because one leftover detail would make the document wrong.
For the studio, Invoice Ninja provides the billing records behind that document. I added a command-line wrapper around its API so I can prepare invoices and retrieve their PDFs from the terminal. The useful part is the separation between preparing the record and deciding to send it.
Keep the record behind the PDF
Invoice Ninja lets you create invoices against a client, enter line items, preview the PDF and send it to selected contacts. The invoice also has a status and linked payment information. These are documented product capabilities .
That gives you somewhere to answer the next question. Which document did we prepare? Who should receive it? Did we mark it sent because we delivered it elsewhere, or did we ask the billing system to email it?
The studio’s wrapper exposes separate operations to create an invoice, download its PDF, mark it as sent and send an email. Marking a record as sent does not send the email. That distinction matters when another tool or person handles delivery.
I want those operations to stay separate. A successful API request tells me that one operation completed. It doesn’t tell me that the recipient received, read or paid the invoice.
Put the review where it can catch a mistake
For a client implementation, I would use a workflow like this:
| Step | Work the software can do | Check before moving on |
|---|---|---|
| Prepare | Create the client-linked invoice from agreed inputs | Recipient, currency, scope and reference |
| Render | Generate the PDF | Read the document the client will see |
| Send | Email the approved document or record delivery elsewhere | Confirm the intended delivery method and recipients |
| Reconcile | Keep payment information against the invoice | Check the payment evidence before recording it |
This is an example workflow, not a claim that these steps run unattended.
The step I wouldn’t remove is opening the finished PDF. A correct data record can still produce a cramped description, an awkward page break or missing context. Treat it like checking the plate before it leaves the kitchen: the preparation happened elsewhere, but this is what the customer receives.
Choose which repetition to remove
Invoice Ninja also supports quotes that convert into invoices . For work that starts with an agreed quote, that gives you a way to carry the document’s details forward. You still review changes in scope before billing.
The studio’s project used a self-hosted Docker setup. Hosting is a separate responsibility from invoice preparation: someone needs to maintain the application, its data, PDF generation and email configuration. Invoice Ninja provides self-hosting documentation for those pieces. It takes maintenance time, even when the software fits the job.
I’d start a billing automation with one repeated task, such as turning approved inputs into a reviewable invoice. Once that works, you can decide whether quotes, recurring work or another connection belongs in the next step.
Show me the steps between finishing work and sending the invoice . We can identify the repeated entry worth removing and keep the approval where you need it.
Interested in this?
Learn about Technology →