This guide explains what information is included in a Worklog360 invoice and how each field is populated from Jira, budgets, and rate configuration.
Understanding these fields helps ensure invoices are accurate, defensible, and easy to reconcile.
Invoice header fields
These fields identify the invoice and the parties involved.
Invoice Number
A unique identifier for the invoice.
-
Can be generated automatically (incremented)
-
Used for tracking, accounting, and reconciliation
Customer Name
The client being invoiced.
-
Pulled from the Client linked to the budget
-
Appears on the invoice header
Invoice Date
The date the invoice is issued.
-
Usually the creation or finalization date
-
Used for accounting and reporting
Due Date
The payment due date.
-
Calculated based on your payment terms
-
Clearly indicates when payment is expected
Invoice line item fields
These fields describe what is being billed.
Item Name
The name of the billed item.
-
Can represent:
-
A user
-
An issue
-
A worklog group
-
-
Depends on the selected invoice granularity
Description
Additional details about the billed work.
-
May include:
-
Jira issue keys
-
Work descriptions
-
Date ranges
-
-
Helps clients understand what they are paying for
Qty (Hours)
The number of billable hours being invoiced.
-
Based on billable hours, not total logged time
-
Non-billable hours are excluded
Rate (€/hr)
The billable rate applied to the hours.
-
Comes from:
-
Role-based rates
-
User-specific rates
-
Project or client overrides
-
-
Displayed per invoice line item
Tax Name
The tax applied to the invoice line.
-
Defined in your tax configuration
-
Can vary by client or invoice
-
Optional, depending on your setup
Amount
The calculated line item total.
-
Formula:
Qty (Hours) × Rate (+ tax, if applicable) -
Rolled up into the invoice total
Where invoice data comes from
Invoice fields are populated from:
-
Clients (customer details)
-
Budgets (scope and time period)
-
Worklogs (hours)
-
Rates (billable rates)
-
Tax configuration (tax name and rules)
📌 All data is traceable back to Jira worklogs.
What is not included
-
Non-billable hours
-
Worklogs outside the budget period
-
Worklogs already marked as invoiced
This prevents double billing and keeps invoices clean.
Why this structure matters
-
Clear, auditable invoices
-
Easy reconciliation with Jira and accounting systems
-
Transparency for clients
-
Confidence for finance teams