Account mapping in the Tripletex integration

Account mapping in the Tripletex integration

This article explains how account mapping works when invoices and vouchers are exported from Telaris to Tripletex.

Account mapping determines which account is used for the postings in Tripletex, and is the basis for both bookkeeping and VAT handling.

TABLE OF CONTENTS

• Account mapping in the Tripletex integration
• Introduction to account mapping
• Overview of account mapping
  • Product classes control the account
  • No manual mapping table
  • Zero-VAT account (nullvataccount)
  • Partner account
  • Purchaseaccount for negative lines
  • How the account is used in Tripletex
• Troubleshooting

Introduction to account mapping

When invoices, credit notes, and vouchers are exported from Telaris to Tripletex, each posting must be booked on the correct account.

Account mapping is about how Telaris determines which account to use on each line.

In the Tripletex integration, there is no separate mapping table between the systems. Instead, the same account number is used in both systems.

This means:

• Telaris chooses the account number

• Tripletex must have the same account in the chart of accounts

• Tripletex uses the account's VAT type and accounting setup

Tip: If an export fails with «Konto X ble ikke funnet», it is almost always because the account number is missing in Tripletex.

Overview of account mapping

Account mapping is mainly controlled by product classes and various account setups in Telaris.

Product classes control the account

The most common account source in Telaris is the product class.

Each product class can have its own accounts for different types of bookkeeping.

When an invoice line is exported, Telaris first sees which product class the product belongs to. Then the account set on the product class is used.

Typical accounts on a product class:

• Sales account

• Zero-VAT account

• Purchase account (purchaseaccount)

• Partner account

The account number chosen must exist with the same number in Tripletex.

Guide: Product classes

NOTE: The product class normally determines which account is used on export to Tripletex.

No manual mapping table

The Tripletex integration does not use a separate mapping table between Telaris and Tripletex.

Instead, the mapping works like this:

1. Telaris chooses an account number

2. The Tripletex chart of accounts is looked up

3. The same account number is used in Tripletex
   
   

Example:

• The product class uses account 3000

• Telaris exports account number 3000

• Tripletex finds account 3000 in the chart of accounts

• The posting is booked on account 3000
  
  

If the account does not exist in Tripletex, the export stops with an error.

Guide: Chart of accounts

Important: The account numbers in Telaris and Tripletex must match. There is no automatic translation between accounts.

Zero-VAT account (nullvataccount)

Product classes can have a separate account for lines without VAT.

This is often callednullvataccountor zero-VAT account.

When an invoice line has 0% VAT, this account is used instead of the normal sales account.

This means that:

• 0% lines are booked on the correct account

• Tripletex uses the correct VAT type for VAT-exempt sales

Example:

• Normal sales use account 3000

• 0% VAT uses account 3100

Both accounts must exist in Tripletex.

NOTE: The zero-VAT account is used automatically when the VAT percentage on the line is 0.

Partner account

Some setups use separate accounts for factoring or partner-based invoicing.

In such cases, the product class can use a separate partner account instead of the default sales account.

This is typically used when:

• Invoices are handled via a factoring partner

• Different partners should be booked separately

• The bookkeeping requires separate accounts per partner
  
  

The partner account otherwise works the same way as normal accounts:

• The account number must exist in Tripletex

• The account's VAT type controls the VAT handling

Purchaseaccount for negative lines

Some product classes are configured so that negative sales lines are treated as a purchase instead of negative sales.

Then the account used ispurchaseaccount.

This happens when:

• The line has a negative quantity or a negative amount

• The product class has "reverse negative sales as purchase" enabled

Instead of the sales account, the purchase account on the product class is then used.

This is often used for:

• Returns

• Corrections

• Special accounting rules

NOTE: Purchaseaccount is only used when the product class is set up to treat negative sales as purchases.

How the account is used in Tripletex

When the correct account is chosen in Telaris, the account is used in Tripletex for:

• Bookkeeping

• VAT handling

• Accounting reporting

• General ledger
  
  

Tripletex uses the account's setup and VAT type automatically.

This means a wrong account affects not only the accounts but also the VAT handling.

Tip: For accounting errors, you should always check both the account number and the VAT type on the account in Tripletex.

Troubleshooting

Common errors related to account mapping:

• «Konto X ble ikke funnet»– the account number does not exist in Tripletex

• Wrong VAT on the posting– the account in Tripletex has the wrong VAT type

• 0% lines are booked incorrectly– nullvataccount is missing or points to the wrong account in the product class in Telaris

• Negative lines are booked incorrectly– purchaseaccount or reversenegativesalesaspurchase is incorrectly configured
  
  

When troubleshooting, you should check:

• The product class in Telaris

• The account number used

• The account exists in Tripletex

• The VAT type on the account in Tripletex
  
  

In short:

• The product class determines the account

• The same account must exist in Tripletex

• There is no mapping table

• The account in Tripletex controls the VAT handling
  
  

Tip: Most account errors are due to either a missing account in Tripletex or the wrong account on the product class in Telaris.

Guide: Product classes