How does your team handle client invoicing from Jira worklogs? Looking for honest feedback

Hi All,

Another option could be the app we have built. The worklog attributes feature help to extract billing hours easily.

Worklogs Time Tracking in Jira & Timesheets

With this add-on, you can easily -

• Prepare your reports based on Project/Sprint/Issue Type/Assignees/Authors and various other filters
• Create user wise time reports in real time by grouping & categorizing data with aggregation
• Group your data to build more meaningful reports
• Enter Time Spent for multiple issues from Time sheet screen. With Calendar view and Board view
• CSV Export
• Dashboard gadget
• Add and use custom attributes to worklogs (like organization, billable status, work type, cost center, etc.) and create reports based on those attributes.

Disclaimer : I am part of the dev team

Update: I ended up building a solution to this exact problem — WorklogPDF (worklogpdf.com.au).

It connects to Jira via OAuth, pulls worklogs for a selected project and date range, lets you set hourly rates per team member, and generates a clean PDF invoice. Takes about 30 seconds end to end.

For context: the main tools in this space (Tempo, Clerk Invoices) are excellent but priced per Atlassian user. If you're a small agency where one person does all the invoicing, WorklogPDF charges a flat $19/month regardless of how many people are in your Jira instance.

Free tier available (3 invoices/month) if you want to try before committing to anything. Would appreciate feedback from anyone in a similar situation.

Hi, @Justin Lo 

Many of our customers use Clerk Invoices app to close exactly this gap between Jira worklogs and client invoices.

Disclosure: I'm a maker of the app.

We at Midori use our own app to produce invoices from Jira Cloud with great success.

Replies:

1. We generate a professional PDF format invoice using our own invoice template (similar to these samples). We use Tempo worklogs, but our approach would also work with the built-in Jira worklogs.
2. There is really not much pain. It doesn't require manual work. There is a Jira work item that represents the project, and when it moves to a specific status, an automation flow starts which will generate the PDF and send it to the customer. (Each customer is managed using JSM, so that we manage their email addresses, post addresses, VAT ID, etc. centrally.)
3. PDF. (And it seems that this is exactly what they expect.)
4. Those are also logged to the "main" Jira work item. (We use Tempo custom work attributes to categorize worklogs, and everything else, but "Non-billable" goes to the invoice.)
5. We don't have any problem to fix with it. It is fast, efficient, and makes our customers happy.

I hope this helps.