Failed to export into MS Business Central. Dimensions already exist.

Prev Next
This content is currently unavailable in Dutch. You are viewing the default (English) version.

Error message

Dimensions already exist. Please ensure no default dimensions have effect on that expense in MS Business Central.

Affected ERP integrations

  • MS Business Central

Cause

This error occurs when default dimensions are automatically applied in MS Business Central, creating a conflict with the dimensions Payhawk is attempting to set based on the expense's custom fields. This automatic population can happen due to:

  • Dimensions set on the Vendor: Your accounting system might automatically assign dimensions to purchase documents based on the vendor's setup.

  • Dimensions set on the G/L Account: Similarly, default dimensions might be configured directly on the General Ledger account being used for the expense.

Solution

You can resolve this issue in the following ways:

  • Remove dimensions from the Vendor record.

    1. Log in to your MS Business Central account.

    2. Navigate to the Vendor card that is linked to the expense owner or the transaction.

    3. Review the Dimensions setup for that vendor.

    4. Remove any default dimensions that are automatically populating and causing a conflict.

    5. Save the changes to the vendor record.

      Vendor card displaying details for Fabrikam, Inc., including dimensions and general information.

  • Remove dimensions from the G/L Account.

    1. Log in to your MS Business Central account.

    2. Identify the G/L Account associated with the expense that is failing to export.

    3. Navigate to the settings or details of that specific G/L Account.

    4. Review its Dimensions settings and remove any default dimensions that are automatically populating.

    5. Save the changes to the G/L Account.

      G/L Account Card displaying income from securities and dimensions for transaction analysis.

After performing either or both of the above options, return to the Payhawk portal and try to export the expense again. Payhawk must be able to set the dimensions based on the expense's custom fields without conflict.