How it works

Which time is billed

For each active mapping, Fakturer finds the work items its JQL matches that have time logged in the period, and reads their worklogs. A worklog counts when the day it was logged for falls inside the period.

A worklog is left out when: - it is already on an invoice (see below), - its work item, or the work item directly above it, has one of the non-billable labels, - its comment contains the non-billable tag, if you set one, - nobody has an hourly rate for it (neither the mapping nor a personal rate).

The preview shows how many worklogs were left out and why.

When mappings overlap

A work item belongs to the first active mapping in the list whose JQL matches it, so it is never billed to two customers.

Rows and amounts

Worklogs are grouped into rows by work item, person or day, or into one summary line. A line always has one hourly rate; when people with different rates worked on the same work item, it becomes one line per rate and names the people.

Hours are rounded per line if you choose rounding: to the nearest step (half rounds up) or always up. Amounts are hours times the rate, rounded to whole øre or cents per line. Fortnox calculates VAT from the article or account and the invoice total.

Never billed twice

When you create an invoice, Fakturer first records every worklog on it. If two people try to bill the same worklogs at the same time, only one invoice is created. If Fortnox refuses it, the worklogs are freed again; if Fortnox doesn’t answer, they stay reserved until you check. Each invoice carries Fakturer’s own reference (external invoice reference 1), so you can find it in Fortnox. Later previews leave recorded worklogs out.

A worklog stays recorded even if its time is changed in Jira afterwards; extra time added to a billed worklog is not billed. Log the extra time as a new worklog instead.

If you delete an invoice in Fortnox before it is booked, a Jira admin can release its worklogs from History → Deleted in Fortnox? so they appear in the next preview.

What Fakturer creates

• Fortnox: a customer invoice that is not booked, with the customer, the invoice date you pick, a due date, the customer’s currency, “your reference” made of your reference and the period, and one row per group: description (up to 50 characters), hours, the hourly rate, and the article or sales account. Book and send it in Fortnox.

Fakturer never books, sends, credits or deletes anything in Fortnox.

Limits

• One preview reads at most 3,000 work items per mapping; the preview says when a mapping was cut short. Use a shorter period or narrower JQL.
• Previews are kept for 14 days, and an invoice can only be created from a preview less than a day old.

What Fakturer stores

Settings, mappings, previews for 14 days, the IDs of billed worklogs and a history of invoices. Fortnox sign-ins are held by Atlassian’s Forge platform. It does not store worklog comments. Data goes only to the Fortnox company you connect. See the privacy policy.