Keeping financial systems aligned should not feel like a full-time job. The Tripletex and Qondor integration is built to remove manual work, reduce errors, and give you confidence that your project finances are always up to date.

This article explains why the integration matters, how data flows between the systems, and what you need to set it up successfully.

When invoicing, payments, and project costs live in separate systems, it is easy to lose oversight. This integration brings everything together.

Customer invoices, booking invoices, and card payment invoices created in Qondor automatically appear in Tripletex. There is no manual data entry, which means fewer mistakes and more time saved.

Qondor is the master system for projects and customers. When data is synced, Tripletex is created or updated based on what exists in Qondor. Both systems stay aligned without extra effort.

Supplier costs and sales revenue registered in Tripletex sync back to Qondor. Your project profit and loss overview stays accurate throughout the project lifecycle.

Payment status flows from Tripletex back to Qondor, ensuring dashboards and reports always show current figures.

The integration consists of two main sync flows:

📌 Note: Invoice sync and Cost/Sales sync are two separate integrations that can be enabled independently.

When an invoice is processed in Qondor, the following data is sent to Tripletex:

📌 Note: Invoice sync typically runs every few minutes, depending on your configuration.

This scheduled sync pulls financial data from Tripletex into Qondor, giving project managers a complete financial picture without manual data entry.

For a supplier invoice to sync as an Actual cost in Qondor:

Data synced to Qondor costs:

💡 Tip: If a supplier invoice covers multiple projects, split the posting lines—each will sync to its respective project.

For a customer invoice to sync as Actual sales in Qondor:

Data synced to Qondor Sale:

The Cost and Sales sync runs on a configurable schedule (typically daily). It looks back over a defined period to catch any new or updated invoices.

⚠️ Note: Only projects that exist in both Qondor and Tripletex (with matching project numbers) will have costs and sales synced.

The integration uses External Reference fields in Qondor to maintain links between systems:

📌 Note: When an entity is created in Tripletex, its ID is stored in Qondor's External Reference field. On subsequent syncs, this ID is used to update the existing record rather than creating duplicates.

💡 Tip: If you need to manually link a Qondor customer to an existing Tripletex customer, you can set the External Reference field in Qondor to the Tripletex customer ID.

The integration supports the following Qondor invoice types:

When an invoice is processed, the integration automatically:

When is the project created?

When an order or invoice is created in Tripletex, the following fields are mapped from Qondor:

Contact persons are matched using the following logic:

📌 Note: If no matching contact is found in Tripletex, the order is created without a linked contact person. The integration will separately attempt to create or update the contact person in Tripletex based on the Qondor contact person data.

The Invoice Comment field in Tripletex is automatically populated with:

{Invoice Reference} / {Contact Person Name}

This ensures the booker's full name always appears on the invoice, even when the invoice address is set to a company name.

Examples:

When creating customers in Tripletex, the integration validates the delivery method (EHF, e-invoice, etc.). If validation fails:

For company customers:

For individual customers:

⚠️ Note: This fallback behaviour prevents sync failures when customers are not registered for electronic invoicing.

The integration supports several configuration choices:

💡 Tip: Contact your Qondor CSM to adjust these settings for your specific needs.

❗ Norwegian customers only

The integration currently supports Norwegian companies and addresses.

❗ Project-based invoicing

All invoices must be linked to a project in Qondor.

❗ Customer matching rules

Customers are matched by organisation number first, then email. Clean data is essential to avoid duplicates.

❗ Duplicate organisation numbers

Multiple customers in Qondor with the same organisation number can cause sync errors. Ensure customer data is cleaned and de-duplicated before enabling the integration.

❗ Department not supported

The integration does not currently support setting department on orders based on team in Qondor. All orders are created without department assignment.

❗ Products are not synced

Products are not transferred from Qondor to Tripletex. Use article mapping to link Qondor articles to existing Tripletex products or VAT types instead.

❗ Contact person selection

The integration selects the first matching contact person by email. If multiple contacts share the same email address, the first one returned by Tripletex is used.

If you are ready to simplify invoicing and gain full financial visibility across projects, contact your Qondor CSM to get started. They will guide you through setup and ensure everything runs smoothly from day one.