Choosing an integration
What each Temponia integration is for, what it moves, and in which direction.
Last updated 15 August 2026
Temponia connects to three kinds of system, and each one solves a different problem. An issue tracker, so people can log hours where the work is described. An accounting package, so invoices raised from tracked time end up in your books without being typed twice. A calendar, so meetings become time entries instead of being reconstructed from memory at the end of the week.
They are independent. Connecting Xero changes nothing about Jira, and a calendar connection belongs to one person rather than to the company.
What each one does
| Integration | What it is for | What moves, and which way |
|---|---|---|
| Jira | Tracking time on Jira issues | Time tracked in Jira creates Temponia entries; Temponia writes worklogs back |
| Xero | Accounting and invoicing | Contacts and users come in, invoices go out, statuses come back |
| Zoho Books | Accounting and invoicing | Contacts and users come in, invoices go out, statuses come back |
| QuickBooks | Accounting and invoicing | Customers come in, invoices go out, statuses come back |
| Calendar sync | Turning meetings into entries | Events are read only; Temponia never writes to your calendar |
One accounting integration at a time
Xero, Zoho Invoice, Zoho Books and QuickBooks all fill the same role, so Temponia allows one of them at once. As soon as one is connected the others disappear from the Add an integration list, and QuickBooks answers with "Only one integration can be active at a time" if you start its authorisation anyway. To move from one package to another, delete the current integration first.
Jira and calendars are counted separately. An accounting integration, Jira and a calendar connection can all be live together.
What the accounting integrations share
Whichever package you use, the shape is the same.
- Contacts come in. Import your existing customers so a client exists once on each side and invoices land on the right record. You map by hand first, then synchronise, which is what stops duplicates appearing.
- Invoices go out. You assemble the invoice in Temponia from tracked hours and expenses, then export it. Nothing is pushed automatically, and raw timesheet entries are never sent to the accounting package.
- Statuses come back. Sync with the package on the invoice overview re-reads the invoices you exported and updates them in Temponia, so an invoice paid in your accounting system shows as paid here.
Building and exporting invoices needs the Invoicing module switched on. Importing contacts and users works without it.
Calendars are read only
The calendar integration reads your agenda and shows it next to your timesheet so you can drag a meeting across and turn it into an entry. It only ever reads. Temponia does not create, move or delete calendar events, and it does not put your tracked time on your calendar.
Who sets this up
Everything except Jira and personal calendars is managed from Integrations under the Account menu, which only a company owner or an admin can open.
- Calendar connections are made by each person on their own Settings page. There is one exception: an admin can add an organisation-wide Office 365 connection from Integrations, and everyone then links their own Microsoft account to it.
- Jira is installed from the Atlassian Marketplace by a Jira administrator, and confirmed inside Temponia by an owner or admin. It is not in the Add an integration list.
If the integration you want is not in the list, check whether you already have an accounting integration connected, and check that you are signed in as an owner or admin. See roles and permissions for who holds which rights.
Build your own
If we do not integrate with a tool you use, the Temponia API is open to everyone. An owner or admin can register a custom OAuth application from the same Integrations page and connect anything you can write code for.