Tribe's Uniconta integration connects your CRM directly to a cloud-based ERP system widely used across the Nordics, allowing your customer, supplier, contact, product, and invoice data to stay aligned between both platforms. Rather than managing data in two separate systems, the integration keeps records consistent and up to date automatically. By following this guide, you will learn how to connect Uniconta to Tribe, configure which data to sync, and understand how the integration behaves on an ongoing basis.
Table of Contents
What Does the Uniconta Integration Do?
Prerequisites
How Do I Set Up the Uniconta Integration?
What Data is Synchronised?
Troubleshooting
Quick Summary
What Does the Uniconta Integration Do?
The Uniconta connector supports three different types of synchronisations:
Contact synchronisation
Organisation and Supplier Synchronisation
Product synchronisation
Invoice synchronisation
Contact Synchronisation
Contacts (Organization Customers, Suppliers, Persons) are synchronised in both directions. Contacts must be linked to a customer (Debtor) in Uniconta — contacts without a parent customer, or whose parent has not yet synced, are skipped.
Organisation and Supplier Synchronisation
When the integration is activated, organisations and suppliers from Uniconta are automatically loaded into Tribe during the initial synchronisation. After that, new records and changes to existing ones are kept up to date in both directions in real time.
Product Synchronisation
Products sync one-way from Uniconta into Tribe in real time. Uniconta is the source of truth for product data — changes made to products in Tribe are not pushed back to Uniconta. Stock levels are updated daily at 05:00.
Invoice Synchronisation
Invoices are synchronised in both directions. Changes made in Tribe are sent to Uniconta in near real time, while invoices from Uniconta are pulled into Tribe approximately every hour. Invoice payment status is updated daily at 03:00 and is only from Uniconta to Tribe.
Did you know? Once an invoice has been posted in Uniconta, its lines become read-only. Only header fields such as Date and Payment Term can still be updated after posting.
Prerequisites
Before setting up the integration, ensure the following are in place in both systems.
In Uniconta create or identify a user account with the User type set to Server. This is required for API access.
Make sure to have a dedicated account to use for the Uniconta x Tribe integration. If the same user account is used across multiple integrations, API tokens may overwrite each other, causing authentication conflicts.In Uniconta assign the Reseller role to that user. This role is required specifically to enable invoice synchronisation.
Ensure that VAT codes and Units are mapped
How Do I Set Up the Uniconta Integration?
Before starting, make sure your Uniconta account is using the Server user type.
Step-by-step instructions:
Install the Uniconta integration from the Marketplace.
Click Uniconta.
Click Activate.
Enter your Uniconta username and password, then click Login.
Select your Uniconta company from the dropdown list.
Click Save to confirm the connection.
Enable each entity type you want to sync: Customers, Suppliers, Contacts, Products, and Invoices.
Map your Uniconta VAT codes to the corresponding Tribe VAT groups.
Review and confirm the Unit mappings. Common units are pre-mapped automatically; adjust or add any custom mappings as needed.
Click Start Initial Import to run the first full import of all enabled entities.
Note: VAT codes must be mapped before running the initial import — products with unmapped VAT codes will be skipped during the sync. The Reseller role in Uniconta is also required to enable invoice synchronisation.
What Data is Synchronised?
Uniconta Entity | Tribe Entity | Tribe → Uniconta | Uniconta → Tribe |
Customers | Organisation Customers | Yes | Yes |
Suppliers | Organisation Suppliers | Yes | Yes |
Contacts | Person Contacts | Yes | Yes |
Products | Products | No | Yes |
Stock Level | Product Stock Position | No | Yes (daily at 05:00 am) |
Invoices | Invoices | Yes | Yes (synced every hour) |
Invoice Payment Status | Invoice Phase (Paid) | No | Yes (daily at 03:00 am) |
Troubleshooting
Products are not syncing
Check that all Uniconta VAT codes have been mapped to the corresponding Tribe VAT groups. Products with unmapped VAT codes are skipped during the sync. Revisit the VAT mapping in your connector settings.
Contacts are missing after the initial import
Contacts must be linked to a customer (Debtor) in Uniconta. Orphan contacts, or contacts whose parent customer has not yet synced, are skipped.
Invoice lines cannot be edited
Once an invoice has been posted in Uniconta, its lines become read-only. Only header fields such as Date and Payment Term can be updated after posting. If changes to invoice lines are needed, they must be made before the invoice is posted in Uniconta.
Invoice generation fails
This is a known issue with the Uniconta API for certain companies. If invoice generation consistently fails, contact Tribe support for further assistance.
Stock levels or invoice payment status are not up to date
These fields do not sync in real time. Stock levels update daily at 05:00 am and invoice payment status updates daily at 03:00 am. If the data appears outdated outside of these windows, verify your connector is still active and connected.
Note: Uniconta applies a limit of 5,000 API calls per user per day. Large initial imports or high-volume environments may approach this limit. If syncing stalls unexpectedly, this may be the cause. Contact Tribe support if the issue persists.
Quick Summary
The Uniconta integration connects Tribe to a cloud ERP system used widely across the Nordics, synchronising customers, suppliers, contacts, products, and invoices between the two platforms. Setup involves activating the connector from the Marketplace, providing your Uniconta credentials, enabling the relevant entity types, and running an initial import. Once active, most data syncs automatically in real time or on a scheduled basis, keeping both systems consistent without manual effort.