Skip to main content
All CollectionsAccountants & admins: Processing & exporting spendAccounting integration guidesDATEV
Troubleshooting: Supplier Account is not allowed to have more than one digit more than the standard account length set in DATEV
Troubleshooting: Supplier Account is not allowed to have more than one digit more than the standard account length set in DATEV
Support avatar
Written by Support
Updated over a year ago

Error message: Supplier Account is not allowed to have more than one digit more than the standard account length set in DATEV

Problem:

The total number of digits entered in Supplier Accounts does not align with the standard expense account digit length defined in DATEV.

Specifically, a supplier account is not allowed to be longer than the defined account length, plus one digit. In practice, this means that if the expense account length is 4 digits long, the supplier account length must be 5 digits (and so on). Accounts cannot be created if the set limits are not met.

Solution:

The supplier account length in DATEV has to always have one digit more than the defined expense account length

  • if expense account length defined as 4 → Supplier account length is 5

  • if expense account length 5 → Supplier account length is 6

  • And so on…

Example:

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

Steps:

  1. 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).

Notes + Examples:

If supplier accounting is enabled, we validate against the supplier number assigned to the transaction

If supplier accounting is disabled, we validate against the Moss Default Supplier:

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?