Skip to content
Integrations

Connect Tripletex to Uku

Company Admin or Company Owner role on a Team or Elite Uku subscription. You also need a Tripletex login with permission to manage API access — typically an administrator on the Tripletex company.

Tripletex is the right integration for firms in Norway.

Tripletex’s API uses two tokens together:

  • A consumer token identifies the integrating partner (in this case Uku). Uku already holds and manages this — you do not need to provide it.
  • An employee token identifies the user account that data is synced under. You generate this inside Tripletex and paste it into Uku.

Employee tokens have an expiration date that you set when generating them. When the token expires, the connection stops working and you regenerate.

To connect Tripletex to Uku you need an employee token issued by Tripletex. The token is generated inside Tripletex, not in Uku.

  1. Sign in to Tripletex with an administrator account.
  2. Go to Selskap → API-tilgang (Company → API access).
  3. Create a new employee token linked to the user account that should sync data — pick a service or integration user where possible, not a real employee account that might be deactivated.
  4. Set an expiration date appropriate for your firm’s policy. Note the date so you can rotate the token before it expires.
  5. Copy the token value. Tripletex shows the token once at creation.

Path: Settings & Apps → Tripletex

The Tripletex integration must be enabled at the company level before it can be used per client. Enabling does not yet pull data; it just makes the integration available.

  1. Open Settings & Apps in Uku.
  2. Find the Tripletex card in the Integrations section.
  3. Click the card to open the integration dialog.
  4. On the Overview tab, click Enable to turn the integration on. Tripletex now appears as an option in the Integration column of your client list.

After enabling Tripletex, paste the employee token into the integration dialog and pick the matching environment.

  1. In the integration dialog, switch to the Connect (or Settings) tab.
  2. Paste the employee token into the matching field.
  3. Choose the environment:
    • Production for live Tripletex companies.
    • Test if you are connecting a Tripletex sandbox account.
  4. Click Test connection. Tripletex responds with the company name if the token is valid.
  5. Click Save.

If the test connection fails, see Troubleshooting below.

Tripletex syncs both inbound (clients, products, VAT types, work statistics) and outbound (invoice export).

DataDirectionNotes
Clients (Tripletex customers)Tripletex → UkuImported into the Integration column of the client list; matched on contact details.
ProductsTripletex → UkuAvailable when configuring billing products in Uku.
VAT typesTripletex → UkuNorwegian VAT codes; used when sending invoices to Tripletex.
InvoicesUku → TripletexUku invoices can be exported to Tripletex when they are issued.
Work statisticsTripletex → UkuDrives the monthly summary task fields.

Configure summary task settings for Tripletex

Section titled “Configure summary task settings for Tripletex”

Once Tripletex is connected, open the Settings tab in the integration dialog to configure how Uku creates monthly summary tasks for each connected client.

SettingWhat it does
Task titleName used for the auto-generated summary task each month.
TopicWhich topic the summary task is filed under.
RecurrenceAlways monthly.
Import dataWhen in the month data is imported — last work day, last calendar day, or a specific day of the following month (1st–28th).

In the Configure data fields section, map each Tripletex data field to a custom task field in Uku. Common fields exposed by Tripletex include sale entries, purchase entries, bank transactions, and document counts for the period.

For each field you want to track:

  1. Pick the field in the left column.
  2. Select the matching Uku custom task field from the dropdown on the right.
  3. Fields left blank are not imported.
  4. Click Show more to reveal additional less-common fields.
  5. Use New custom field inside the dropdown to create a custom field on the spot if one does not yet exist.
  6. Click Save when done.

Connect each client to its Tripletex customer

Section titled “Connect each client to its Tripletex customer”

Enabling the Tripletex integration only registers it at the company level. Data flows once each Uku client is also linked to its matching Tripletex customer. The full per-client connection workflow is covered in Connect a client to accounting software. The short version:

  1. In the client list, click the Integration column on the client row.
  2. Pick Tripletex from the integration dropdown.
  3. Uku reads the Tripletex customer list using your saved token and lets you pick the matching customer.
  4. Save. From the next scheduled import day onwards, Uku pulls data for that client.

To back-fill historical months immediately after connecting, use Reload data on the integration Settings tab.

To re-import Tripletex data for all connected clients (back-fills the last 12 months and overwrites existing summary task field values):

  1. Open Settings & Apps → Tripletex → Settings.
  2. Click Reload data at the bottom-left of the dialog.
  3. Confirm. Uku processes the reload in the background and notifies you when ready.

Tripletex employee tokens expire on the date you chose at creation. To avoid the integration silently breaking on the expiry date:

  1. A few days before the expiry, generate a new employee token in Selskap → API-tilgang.
  2. In Uku, open Settings & Apps → Tripletex → Connect, paste the new token, click Test connection then Save.
  3. (Optional) Revoke the old token in Tripletex once you have confirmed the new one works.

Test connection fails with an authentication error

Section titled “Test connection fails with an authentication error”

Test connection failures with Tripletex are almost always one of these:

  • The token has expired in Tripletex. Generate a new employee token and paste the new value.
  • The wrong environment (production vs. test) is selected — test tokens will not work against production and vice versa.
  • The token has leading or trailing whitespace. Re-copy directly from Tripletex’s API-tilgang panel.
  • The employee account that owns the token has been deactivated in Tripletex.

Test connection succeeds but no data appears in summary tasks

Section titled “Test connection succeeds but no data appears in summary tasks”

If the Tripletex connection passes the test but no statistics show up in summary tasks, enabling the integration is not enough on its own. You also need to:

  • Connect each client to its Tripletex customer — set the Integration column to Tripletex on the client row.
  • Configure summary task settings on the integration Settings tab (task title, topic, import day, data field mapping).
  • Wait for the next scheduled import day, or trigger Reload data to back-fill the last 12 months.

A previously working Tripletex connection stopped syncing on a specific date

Section titled “A previously working Tripletex connection stopped syncing on a specific date”

A Tripletex connection that stopped on a specific date is almost always a token expiry. Tripletex employee tokens have a fixed expiry date set at creation. Generate a fresh token and paste it into Uku — see Token rotation for Tripletex above.

Wrong Tripletex customer is connected for a Uku client

Section titled “Wrong Tripletex customer is connected for a Uku client”

If the wrong Tripletex customer is connected for a Uku client, fix it in the client list. Click the Integration column for that client and pick the correct Tripletex customer from the dropdown. Then run Reload data to refresh the historical statistics.

If a Tripletex field consistently arrives empty in Uku summary tasks, it is most likely not mapped to a Uku custom task field. Open the integration Settings tab, find the field in Configure data fields, assign a custom field, then click Reload data to back-fill existing months.