Documentation

Worklog Invoices for Jira

What it does

Worklog Invoices turns time logged in Jira into invoices. It reads worklogs, applies your rates, and produces a document you can print or hand to your accounting system. It never writes anything back to Jira.

First run

  1. Apps → Invoices → Settings: fill in your issuer details and upload a logo if you want one on the printed invoice.
  2. Clients: add a client with its code, currency, billing email and tax details.
  3. Rates: set what an hour costs.

How rates are resolved

Four levels, most specific wins: assignee on a project → assignee → project → client. That mirrors how agencies actually price: a senior on one account is not the same rate as the same senior elsewhere.

Issuing an invoice

  1. Pick a client and a period, then Preview. You see every line that will be billed before anything is committed.
  2. Run the pre-flight audit. It reads the draft the way a careful colleague would and points at what looks wrong: a worklog logged to the wrong client, a suspicious round number, an entry far outside the period.
  3. Issue. The invoice gets a number and becomes immutable.

A worklog can never be claimed by two invoices. Once an invoice is issued, the time it covers is locked to it. Voiding the invoice releases that time again, so a mistake costs one click, not a reconciliation.

Getting the data out

Print to PDF from the invoice page, or export to CSV for your accounting software. The printed invoice renders in ten languages, chosen per client — the interface language and the invoice language are separate settings on purpose.

Without an active subscription

New invoices cannot be created and settings cannot be changed. Everything already issued stays readable, printable and exportable. An invoice is a primary document, and you are entitled to last year's paperwork whatever happened to your subscription.

Something missing here?

Write to support@avakode.com. Questions that arrive twice get added to this page.