---
title: "SAP house bank missing on G/L for Administrators - Payhawk Help Center"
slug: "failed-to-export-into-sap-s-4hana-missing-house-bank-entry-for-g-l-account"
description: "Resolve SAP S/4HANA export errors by ensuring proper House Bank links for G/L accounts. Follow our guide for quick fixes and integration tips."
updated: 2026-10-27T15:14:17Z
published: 2026-10-27T15:14:17Z
canonical: "payhawk.com/failed-to-export-into-sap-s-4hana-missing-house-bank-entry-for-g-l-account"
---

> ## 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 SAP S/4HANA. House bank is not assigned to G/L account.

## Error message

```plaintext
House bank [ID] is not assigned to G/L account [code]. Please check bank account settings on S/4HANA.
```

## Affected ERP integrations

- SAP S/4HANA®

## Cause

When exporting an expense, you may hit a roadblock stating that an entry is required in the House bank field for a specific General Ledger (G/L) account.

In SAP S/4HANA, a **House Bank** represents a bank account that your company owns. Certain G/L accounts, specifically those used for bank transactions, cash, or clearing accounts, are configured to strictly require a House Bank and Account ID link whenever a transaction is posted. If Payhawk tries to send an expense to one of these accounts, but SAP S/4HANA detects that the House Bank link is missing or not designated properly in the transaction details, the export will fail.

## Solution

Before modifying your SAP S/4HANA configuration, verify how the transaction is being categorized.

Ensure that the G/L account mapped to this specific expense is the correct bank or clearing account. If a wrong G/L account was selected by mistake, updating the mapping in Payhawk may resolve the issue immediately.

If the G/L account mapping is correct, the integration or the account itself needs to be adjusted in SAP S/4HANA so it knows which House Bank to associate with the transaction.

### SAP S/4HANA Public Cloud Edition

To resolve the issue in SAP S/4HANA Public Cloud Edition:

1. Open the **Manage Bank Accounts** app from your Fiori launchpad.
2. Locate the bank account associated with the G/L account mentioned in the error.
3. Go to the **Connectivity Path** tab and ensure that the G/L account is properly linked to the House Bank and House Bank Account ID.

Alternatively, if this G/L account does not require a house bank for external data transfers, open the **Manage G/L Account Master Data** app, check the account's Field Status Group, and ensure the House Bank field is set to optional rather than mandatory.

### SAP S/4HANA Private Cloud Edition

To resolve the issue in SAP S/4HANA Private Cloud Edition:

1. Go to transaction code `FS00` (Centrally Maintain G/L Account) and enter the G/L account code.
2. Under the **Create/bank/interest** tab, check the **Field status group**. If the field status group forces the House Bank as a required entry, you may need to adjust the group configuration via transaction `OBC4` to make it optional for API postings.
3. If the account must be tied to a House Bank, use transaction `FI12` (House Banks) or the NetWeaver Business Client (NWBC) **Bank Account Management** to ensure the G/L account is correctly assigned to your House Bank and Account ID.

### Next steps

Once the House Bank connection is updated or the field requirement is relaxed in SAP S/4HANA, go back to Payhawk and follow the steps:

1. Log in to the [Payhawk Web Portal](https://portal.payhawk.com).
2. Go to **Spend**.
3. Locate the pending expense and click **Review** to re-try the export.