Tempo and invoicing
Tempo tracks the time. Something still has to write the invoice.
Hours priced to what you actually charge, per client and per role.
Numbered, branded PDF, and an invoice record created in Xero or QuickBooks.
Billable time that never made it onto an invoice, valued before you close the month.
What Tempo actually does
Tempo lets you mark time as billable or non-billable, attribute it to clients through Tempo Accounts, and report on it. Its own invoicing page frames the product as supporting accurate invoicing with time tracking, and says reports can be saved and exported as XLS, CSV and PDF. Its Atlassian Marketplace listing describes governance features that lock periods before they reach payroll or invoicing.
That wording is precise and worth taking at face value. Tempo produces trustworthy time data and hands it off. The invoice is created downstream, by a person with a spreadsheet, or by an accounting system someone re-keys the numbers into.
Where the work actually goes
The export is not the hard part. The hard part is everything after it. Someone has to apply the right rate to the right person on the right project, decide which hours are actually billable this month, group the lines so the client can understand them, calculate tax, assign an invoice number that does not collide with last month, and then type all of it into Xero or QuickBooks without a transcription error.
Done monthly across a handful of clients, that is a recurring day of work that produces no new value and is easy to get subtly wrong.
What Reeve adds
- Pricing: your rate cards, applied per client and per role, rather than an hours column you multiply by hand.
- Review: approve, adjust or exclude billable time in one pass. Reeve never edits your Jira worklogs.
- The invoice itself: a numbered, branded PDF, and a real invoice created in Xero or QuickBooks, not a spreadsheet you re-key.
- Leakage: unbilled billable time shown in dollars, including hours logged to projects nobody mapped to a client.
They are not competitors
We do not think you should replace Tempo with Reeve. Reeve deliberately consumes worklogs and never creates them, because fighting an established timesheet tool helps nobody. Tempo owns time. Reeve owns billing.
One honest caveat: Reeve reads the worklogs stored in Jira. Reading worklogs from Tempo’s own API is on the roadmap and is not shipped yet. If that matters to your setup, say so and we will tell you plainly whether Reeve fits today.
Questions
Does Tempo create client invoices?
No. Tempo tracks billable and non-billable hours and produces reports you can export as XLS, CSV or PDF. Tempo's own marketing describes it as supporting accurate invoicing with time tracking, and its Marketplace listing talks about locking periods before they reach payroll or invoicing. The invoice itself is created somewhere else.
Do I have to stop using Tempo to use Reeve?
No, and most teams should not. Tempo is a strong time tracker. Reeve is the billing layer that turns tracked hours into an invoice. They solve different halves of the same problem.
Does Reeve read worklogs logged through Tempo?
Not yet. Reeve reads the worklogs stored in Jira today. Reading worklogs from Tempo's own API is planned, not shipped. If your team logs time so that it lands in Jira worklogs, Reeve works now. If you rely entirely on Tempo-specific worklog data, wait for that integration or get in touch and we will tell you honestly where it stands.
What does Reeve do that a Tempo report does not?
It prices hours to your rate cards, groups the lines the way your client reads them, applies tax, produces a branded invoice PDF with a real invoice number, and pushes the invoice into Xero or QuickBooks as an actual invoice record. It also shows unbilled time in dollars so work does not quietly go uninvoiced.
Get early access
For agencies who track time in Jira and are tired of building the invoice by hand afterwards.