How to invoice Jira worklogs in Fiken

By Kayabyte · Updated 11 November 2026

Short answer: Fiken doesn’t read Jira, and Jira has no invoice. The manual route is to export the worklogs for the month, sum the billable hours per customer and type the lines into a Fiken invoice draft. Fakturer: Invoice Jira Worklogs in Fiken, in Atlassian Marketplace review and not yet available, does that step for you: it maps Jira work to Fiken customers with an hourly rate and creates the draft, which you check and send in Fiken.

Consultancies and agencies that log time in Jira usually bill by the hour. At the end of the month someone has to turn worklogs into invoice lines. This guide shows how to do it by hand, what to watch for, and when it is worth automating.

Step 1: decide what is billable

Before you count hours, agree on what goes on the invoice:

Which work belongs to which customer. A project per customer is easiest. If one project serves several customers, use an epic, a component or a custom field such as “Client”, so a JQL query can pick out one customer’s work.
What is not billable. Internal meetings, rework and warranty fixes. Jira has no billable flag on worklogs; the usual options are a label on the work item or a tag in the worklog comment. See How to track billable and non-billable hours in Jira.
The rate. One hourly rate per customer, or different rates for some people (for example a senior consultant).
Rounding. Per worklog, per line or per invoice, to a quarter or half hour. Write it down and use the same rule every month.

Step 2: get the hours for the period

Jira’s work item export gives the total time spent on each item, not the time logged in a given month. For a monthly invoice you need the worklogs themselves, with their dates. How to export Jira worklogs to Excel or CSV shows a free script and the API calls.

Filter the worklogs on their own start date, not the work item’s dates: a work item created in September can have hours logged in October, and those belong on October’s invoice.

Step 3: build the invoice lines

In a spreadsheet, group the hours the way the customer wants to see them:

One line per work item: “PLAT-12 Payment form, 7.5 h”. The most common choice; customers can check each item.
One line per person: useful when people have different rates.
One line per day, or one summary line for retainers.

Multiply hours by the rate, and check the total against the hours you logged.

Step 4: create the draft in Fiken

In Fiken, go to Salg, create a new invoice, choose the customer and add the lines with quantity (hours), unit price and VAT. Save it as a draft (fakturautkast) if someone else should check it before it is sent. Put the customer’s order number in Deres referanse if they need one.

Step 5: don’t bill the same hours twice

This is where the manual route goes wrong. People log time late, so October’s export run on 2 November misses hours logged on 5 November for 31 October. Next month, those hours fall outside November’s dates and are never billed, or someone widens the dates and bills hours that were already on October’s invoice.

Keep a record of which worklogs went on which invoice: the worklog ID is the only stable key. A spreadsheet with one row per invoiced worklog works, but it has to be kept up to date by hand.

Automating it with the Fiken API

Fiken has an open API, and invoice drafts can be created through it. The company needs Fiken’s API module (an additional service in Fiken), and an integration made by a third party has to use Fiken’s OAuth sign-in rather than a personal API token.

Fakturer: Invoice Jira Worklogs in Fiken

Fakturer is the app I make for this. It runs inside Jira Cloud:

Mappings: a Jira admin maps a project, epic or any JQL to a Fiken customer, with an hourly rate, other rates for some people, an optional product and a reference such as an order number.
Preview: pick a period and see the billable hours per customer, after leaving out non-billable labels, a worklog tag and worklogs already on a draft. Rounding is per line, to a minute, quarter or half hour.
Lines: one per work item, person or day, or a single summary line.
Draft: one click creates an invoice draft in Fiken. Fakturer never sends, books or deletes invoices; you send it from Fiken.
No double billing: every worklog on a draft is recorded. If you delete a draft in Fiken, release its worklogs in Fakturer and they can be invoiced again.

Fiken asks each person who creates drafts to connect their own Fiken user once. Fakturer is in Atlassian Marketplace review and not yet available to install.

FAQ

Does Fiken have a Jira integration? Not of its own. Hours from Jira have to be exported and typed in, or sent through Fiken’s API by an app.

Can I invoice Jira hours per work item in Fiken? Yes: one invoice line per work item, with the key and summary as the line text, is the usual layout.

What do I need in Fiken to use an integration? Fiken’s API module for the company, and a Fiken user with access to that company.

How do I stop hours being billed twice? Record the IDs of the worklogs on each invoice and leave them out of the next month’s hours. Fakturer does this for you.

Jira and Atlassian are trademarks of Atlassian. Fiken is a trademark of Fiken AS. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian or Fiken.