Jira is where the work is tracked. Invoice Office is where it gets billed. For any team working to tickets, the gap between those two is filled by somebody totting up issues at the end of the month — which is slow, and reliably an undercount.
Where to set it up
Connectors are configured under Settings → Integration connectors. Open the Jira connector, enter your Atlassian username, API token and Jira address, and enable it with the switch. Then add the connector’s Webhook url to Jira as a webhook, so worklogs reach your timesheet as they are logged.
The Jira help article walks through every step, including the webhook events to tick in Jira.
Why connect issue tracking to billing
- Billable work stops being invisible. Time recorded against a ticket is time you can charge for; time nobody transferred is time you wrote off without deciding to.
- The invoice matches the work. A customer querying a line can be shown the tickets behind it, which ends most billing disputes quickly.
- Less month-end reconstruction, which is where undercounting happens.
Worth deciding before you connect
- What is billable. Not every ticket is chargeable, and the rule needs to be explicit before it is automated.
- How the work maps to a project. Invoice Office bills hours against projects and tasks, so agreeing how your Jira structure corresponds to that is the step that determines whether the output is usable.
- Who checks it. Automation is best treated as a first draft of the invoice, not the final one — at least until you have seen a few come through correctly.
For help with your specific configuration, contact us.