Kayabyte

How to invoice Jira worklogs in Fortnox

By Kayabyte · Updated 12 November 2026

Short answer: Fortnox has its own time reporting (Tid) and invoicing, but it doesn’t read Jira worklogs. If your team logs time in Jira, you either log the hours twice, or export them from Jira and type the rows into a Fortnox invoice each month. Fakturer for Fortnox, a Jira app, creates the invoice from Jira worklogs, not booked, so you check it first (see below); the manual steps here work without it.

Option 1: log hours in Fortnox as well

Fortnox Tid lets people report time against customers and projects and invoice it. If people also log time in Jira for the team’s own use, every hour is entered twice, and the two never quite agree. It works for small teams; it is the first thing people want to stop doing.

Option 2: export from Jira, invoice in Fortnox

  1. Decide what is billable: which Jira work belongs to which customer (a project, an epic, a component or a “Client” field), what is not billable (a label or a worklog comment tag, see How to track billable and non-billable hours in Jira), the rates and the rounding.
  2. Get the worklogs for the period. Jira’s work item export gives total time per item, not the hours logged in a month. How to export Jira worklogs to Excel or CSV shows how to get each worklog with its date.
  3. Group the hours per work item, per person or per day, and multiply by the rate.
  4. Create a customer invoice in Fortnox with one row per invoice line: an article (for example your hourly service), a description, the delivered quantity in hours and the price. Fortnox keeps an invoice unbooked until you book it.
  5. Check, book and send the invoice in Fortnox.
  6. Record which worklogs you invoiced, by worklog ID, so late-logged hours are neither missed nor billed twice.

Automating it with the Fortnox API

Fortnox has an open API (version 3). Integrations use OAuth 2.0: the integration is registered in Fortnox’s developer portal, and a Fortnox user allows it for their company with the scopes it needs (for invoices: invoice, customer and article). The company needs the invoicing (Kundfaktura) licence. An invoice created through the API is not booked, so it can be checked before it is booked and sent.

A Jira app for Fortnox

We make Fakturer for Fortnox, a Jira Cloud app that turns billable worklogs into Fortnox invoices:

The app is in review at the Atlassian Marketplace. Using another system? There is also Fakturer for Tripletex, Fakturer for Fiken and Fakturer for PowerOffice Go.

FAQ

Does Fortnox import hours from Jira? Not on its own. Hours have to be reported in Fortnox, typed in from an export, or sent through the Fortnox API by an app.

Is the invoice sent to my customer? No. An invoice created through the API is not booked and not sent until you do it in Fortnox.

Which licence does the company need? Fortnox’s invoicing licence (Kundfaktura).

How do I stop hours being billed twice? Keep the IDs of invoiced worklogs and leave them out next month. Fakturer does this for you.

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