Error message
G/L account xxx does not allow direct postings in company code xxx. Please update the G/L account settings in SAP S/4HANA.Affected ERP integrations
SAP S/4HANA®
Cause
When exporting an expense, you may encounter an error indicating that direct postings are not allowed for the selected General Ledger (G/L) account.
To protect financial data integrity, SAP S/4HANA marks certain G/L accounts as Post Automatically Only or designates them as Reconciliation Accounts, such as Fixed Assets or Accounts Payable control accounts. This means SAP S/4HANA strictly forbids any external tool or API from throwing a transaction directly into these accounts; instead, they must be updated through specific automated system processes.
If Payhawk attempts to post an expense directly to an account with these restrictions, SAP S/4HANA will reject the export to keep the ledger safe.
Solution
Before making changes in SAP S/4HANA, double-check how the transaction is categorized in Payhawk:
Log in to the Payhawk Web Portal.
Navigate to the Expenses app.
Open the affected expense by clicking on it and look at the assigned category or G/L account code.
Verify if a mistake was made during selection, for example, accidentally picking a fixed asset or system control account instead of a standard expense G/L account, such as travel, team meals, or office supplies.
If the wrong account was chosen, updating it to the correct expense account in Payhawk will resolve the issue immediately.
If the G/L account selection is intentional and your organization requirements dictate that it must accept external data transfers, you will need to adjust the company-specific settings for that account in SAP S/4HANA.
SAP S/4HANA Public Cloud Edition
To resolve the issue in SAP S/4HANA Public Cloud Edition:
Log into your SAP Fiori launchpad and open the Manage G/L Account Master Data app.
Search for the specific G/L account code.
Instead of looking at the General tab, which only shows basic global settings, click on the Company Code Data tab, or scroll down to the bottom section.
Select the specific Company Code row you are trying to export to and open its details.
Enable the Post Automatically Only toggle. If your company policy allows direct postings here, turn this setting off.
Note that if the account's Reconciliation Account Type is active, for example, for Assets, direct external postings are blocked by default. If it cannot be changed, you must update the mapping in Payhawk to use a standard expense account instead.
Save your changes.
SAP S/4HANA Private Cloud Edition
To resolve the issue in SAP S/4HANA Private Cloud Edition:
Run transaction code
FS00(Centrally Maintain G/L Account).Enter the G/L account number and Company Code, then press Enter.
Navigate to the Control Data tab.
Locate the Post automatically only checkbox. If checked, uncheck it to allow direct entries from integrations like Payhawk.
Review the Reconciliation account for acct type field. If it is restricted, direct external postings are fundamentally blocked by SAP S/4HANA design, meaning a different expense account must be chosen in Payhawk.
Click Save to apply the configuration.
Next steps
Once you have corrected the G/L account configuration in SAP S/4HANA or selected a valid expense account in Payhawk, go back to Payhawk and follow the steps:
Log in to the Payhawk Web Portal.
Go to the Expenses app.
Locate the pending expense and click Review to re-try the export.