Confluence template for generating invoice with automated numbering

Question

Hi,

tl'dr: I want to create invoice template in confluence that automatically generate invoice number.

long version:

I create orders for my customers in confluence. For that I have created a template in confluence namely "Time and Material" for example.

Every time I create a new invoice, I have to write a unique serial number on invoice. I would like to build a template that generate a unique serial number automatically when I create a new invoice.

Furthermore, It would also be great if everytime I edit an invoice, it can generate version number of that particular invoice.

Has someone done that before or know how to do that?

Would appreciate any kind of input from community.

Thanks and regards,

Aron Gombas _Midori_ · Answer

We are developing a PDF exporter app for Jira Cloud which exports PDF documents from super-customizable templates.

In fact, we are using this app to generate our own invoices, quotes and business documents, so what I outlined above is exactly what we did with great success! It even has a template to generate invoices from Jira worklogs and Tempo worklogs (in case you charge your customer primarily for time):

It generates the document from the up-to-date issue data when you generate the invoice and downloads the PDF file to your computer. Very easy to use.

I encourage you to try to implement it with Jira custom fields, Insight objects, etc.

(If you were on Data Center, we have a free companion app to implement time-saver automations.)

Ubaid Eusuf Zai · Answer

Hi @Aron Gombas Could you elaborate please? We need to be able to download the invoices as PDF document and send it to customer.

Aron Gombas · Answer

Isn't Jira a better fit to manage invoices that are rather structured in nature? I mean where are well-defined fields like "customer name", "invoice address", etc.

Confluence is a better fit for unstructured data.

In Jira, you could use the issue key ("FOO-123") or only the "number part" of the issue key ("123") as invoice ID. And you could model customers as Insight objects, so it is easier to manage CRM like data.