Skip to main content
All CollectionsAccountants & admins: Processing & exporting spendAccounting integration guidesDATEV
Troubleshooting: An Expense Account is not allowed to have more digits than the length of accounts set in DATEV
Troubleshooting: An Expense Account is not allowed to have more digits than the length of accounts set in DATEV
Support avatar
Written by Support
Updated over a year ago

Error message: An Expense Account is not allowed to have more digits than the length of accounts set in DATEV

Problem:

An Expense Account is not allowed to have more digits than the length of digits set by a DATEV account set in DATEV.

The Expense Account length is defined in DATEV Unternehmen Online settings. DATEV does not allow more digits than the defined expense account length. Accounts with fewer digits are allowed (for example, asset accounts have one digit less than the defined account length).

Solution:

DATEV and Moss’s expense accounts need to be the same length.

  1. Go to DATEV and

  2. Update the expense account length

  3. Follow the steps below, to learn how to do it.

Example:

The merchant and the amount in the error message indicate the affected transaction causing the error.

Steps:

  1. The Account Length is defined in DATEV Unternehmen Online

  2. Anwendungen”

  3. “Stammdaten”

  4. “Unternehmensangaben”

  5. “Grunddaten Rechnungswesen”

The setting is synced to Moss “Accounting” → “Accounting-Integrations”

After updating the account length in DATEV Unternehmen Online, DATEV needs to be disconnected and reconnected to update the value in Moss. Validation always works against this value imported to Moss.

The expense account which is assigned to a transaction is validated - please keep in mind that old and already deleted accounts can be assigned - usually they are marked orange in the side panel when opening the transaction

It might be that the account has been set inactive or deleted in the meantime and replaced by the correct account. This screenshot shows the transaction side panel when a transaction has been deleted or set inactive. DATEV validation still uses the values of this inactive account.

Did this answer your question?