Troubleshooting - invoice is not exported to Tripletex

Troubleshooting - invoice is not exported to Tripletex

Find the cause when an invoice is not exported from Telaris to Tripletex.

TABLE OF CONTENTS

• Troubleshooting - invoice is not exported to Tripletex
• Introduction to troubleshooting invoice export
• Troubleshooting walkthrough
  • Check 1 - is the invoice in an export batch?
  • Check 2 - is the batch exported?
  • Check 3 - is the invoice already exported?
  • Check 4 - does the customer exist in Tripletex?
  • Check 5 - is the product and account setup correct?
  • Check 6 - is VAT correctly configured in Tripletex?
  • Check 7 - is the integration in an error state?
• Error messages

Introduction

Invoices are not sent individually directly to Tripletex. They are part of an export batch in Accounting export, and are sent to Tripletex when the batch is exported.

When invoice export fails, it is usually due to a missing link, wrong account setup, wrong VAT setup in Tripletex, or the integration being unable to communicate with the Tripletex API.

Tip: Always start in the export batch. It shows the status per posting and is the best place to find the cause of the error.

Troubleshooting walkthrough

Go through the points below in order.

Guide: Batch transfer

Check 1 - is the invoice in an export batch?

The invoice must be included in an export batch before it can be sent to Tripletex.

If the invoice is not in a batch:

• Check that the invoice is created and ready for accounting export
• Check that batch closing has been run
• Check that the invoice is not outside the accounting period being exported

Check 2 - is the batch exported?

Even if the invoice is in a batch, it is not sent to Tripletex until the batch is exported. An exported batch shows the status "100%"

Check the status of the batch:

• Ventende
• Eksportert
• Feilet
  
  

If the batch has failed, look at the error message on the relevant posting.

Check 3 - is the invoice already exported?

Telaris checks whether the invoice already has an integration reference to Tripletex.

This is often an edge case in that it rarely happens.

If the invoice is already exported:

• It is not exported again
• The Tripletex voucher number is stored as a reference

NOTE: To export an invoice again, the integration reference must be removed and the batch reset. This should only be done by a system administrator.

Check 4 - does the customer exist in Tripletex?

On export, Telaris looks up the customer in Tripletex. If the customer is missing, the system tries to create the customer automatically.

If this fails, check:

• That the customer has the necessary information in Telaris
• That the customer number or organisation number does not create a conflict (duplicates, shown in the integration log)
• That the Tripletex integration has valid access

Check 5 - is the product and account setup correct?

Each invoice line is mapped to a product and an account in Tripletex.

The account is taken from the product class in Telaris and looked up in Tripletex based on account number.

Check:

• That the product has the correct product class
• That the product class has the correct account number
• That the account number exists in Tripletex's chart of accounts

Guide: Chart of accountsGuide: Product classes

NOTE: There is no manual mapping table for accounts. The account numbers in Telaris and Tripletex must match.

Check 6 - is VAT correctly configured in Tripletex?

Telaris does not send the VAT rate or VAT code directly to Tripletex.

VAT is inherited from the VAT type configured on the account in Tripletex.

Therefore check:

• That the correct account is used
• That the account in Tripletex has the correct VAT type
• That any zero-VAT account exists and has the correct VAT setup

Guide: VAT code - Override default account allocation

NOTE: Wrong VAT on the invoice is usually due to the wrong VAT type on the account in Tripletex.

Check 7 - is the integration in an error state?

If the Tripletex API integration has had repeated authentication errors or API errors, it can be set into an error state.

Check:

• That the Employee Token is valid
• That the integration does not show error state
• That the Tripletex API responds
• That the API limit is not reached

To see a detailed error message, go to:

Innstillinger → Integrasjonsinnstillinger → Tripletex API

Contact Telaris support if the integration is in an error state.

Error messages

«Account X was not found in [integration name]»

The account number from the product class does not exist in Tripletex's chart of accounts.

Solution:Add the account in Tripletex, or change the account number on the product class in Telaris.

«Invoice is not found»

The posting refers to an invoice that does not exist in Telaris.

Solution:Check the contents of the batch and whether the invoice has been deleted or changed.

Invoice already exported

The invoice already has an integration reference to Tripletex.

Solution:No action is needed if the invoice is already in Tripletex.

«The integration authentication was unsuccessful»

The Employee Token or Testing Token is wrong or expired.

Solution:Check the tokens in the integration settings and in Tripletex.

«The Integration is in error state»

The integration is disabled after repeated errors.

Solution:Check the log, fix the error, and reactivate the integration.

«Integration returned with too many requests»

The Tripletex API limit is reached.

Solution:Wait and try again later.

«The customer number/supplier number is already in use»

The customer/supplier is not linked correctly between Telaris and Tripletex.

Solution:Look up the customer/supplier in Tripletex and see which customer number the customer belongs to. Contact Telaris support or see the guide.

NOTE: The error message in the export batch is usually the best source for the correct cause.