---
title: "Business Central dimension for Administrators - Payhawk Help Center"
slug: "failed-to-export-into-ms-business-central-a-dimension-value-used-is-the-expense-does-not-exist"
description: "Fix the MS Business Central export error for a dimension value that no longer exists. Check the custom fields on the expense and choose valid, active values."
updated: 2026-10-27T15:08:46Z
published: 2026-10-27T15:08:46Z
canonical: "payhawk.com/failed-to-export-into-ms-business-central-a-dimension-value-used-is-the-expense-does-not-exist"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://payhawk.com/help/llms.txt
> Use this file to discover all available pages before exploring further.

# Failed to export into MS Business Central. A dimension value used is the expense does not exist.

## Error message

```plaintext
A dimension value used is the expense does not exist. Please make sure that all dimension values are valid in MS Business Central.
```

## Affected ERP integrations

- MS Business Central

## Cause

This error occurs when the expense contains a custom field (dimension) value that no longer exists in MS Business Central. The dimension value may have been deleted, deactivated, or renamed in MS Business Central after it was originally selected in Payhawk.

## Solution

To resolve this issue:

1. In the [Payhawk Web Portal](https://portal.payhawk.com), go to **Spend**.
2. Click on the expense that failed to export to open its details view. To find it quickly, filter by **Export status** and select **Failed**.
3. Check all custom fields (dimensions) in the expense and note the selected values.
4. Log in to your MS Business Central account and verify that each dimension value used in the expense exists and is active. If any dimension value is missing or invalid in MS Business Central, return to Payhawk and update the expense with a valid dimension value.
5. Click on **Save** and try to export the expense again.

> [!TIP]
> Regularly synchronize your custom fields between Payhawk and MS Business Central to avoid mismatches caused by deleted or modified dimension values.