Do you have any question about this error?
Message type: E = Error
Message class: EK - IS-U Accounts Receivable and Payable
Message number: 382
Message text: Entry of tax account not permitted
G/L account &v1& is a tax account. This entry is not permitted.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Enter a G/L account that is not a tax account.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message EK382 ("Entry of tax account not permitted") typically occurs when there is an issue with the configuration of tax accounts in the system. This error can arise during various transactions, such as when trying to post an invoice or create a purchase order that involves tax calculations.
Cause:
- Incorrect Tax Account Configuration: The tax account specified in the transaction may not be allowed for the type of transaction being processed.
- Account Assignment Issues: The account assignment for the tax code may not be correctly set up in the financial accounting (FI) or controlling (CO) modules.
- Tax Code Settings: The tax code used in the transaction may not be properly configured or may not correspond to a valid tax account.
- Document Type Restrictions: Certain document types may have restrictions on which accounts can be used for tax postings.
Solution:
Check Tax Account Configuration:
- Go to the transaction code OB40 (for tax codes) and verify that the tax codes are correctly assigned to the appropriate tax accounts.
- Ensure that the tax accounts are set up in the chart of accounts and are active.
Review Account Assignment:
- Check the account assignment in the transaction to ensure that the correct accounts are being used.
- Make sure that the account type (e.g., expense, revenue) is compatible with the tax account being referenced.
Validate Tax Code Settings:
- Use transaction code FTXP to review the settings for the tax code in question. Ensure that it is configured correctly and that the tax account is valid.
Check Document Type Settings:
- Review the settings for the document type being used in the transaction. Ensure that it allows for the posting of tax accounts.
Consult with Finance Team:
- If you are unsure about the configuration, consult with your finance or SAP configuration team to ensure that the tax accounts and codes are set up correctly.
Testing:
- After making any changes, perform a test transaction to ensure that the error no longer occurs.
Related Information:
Transaction Codes:
SAP Notes: Check for any relevant SAP Notes that may address specific issues related to tax account postings.
Documentation: Review SAP documentation on tax configuration and account assignment for further insights.
By following these steps, you should be able to identify and resolve the EK382 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
EK381 Tax determination code with quantity reference not uniquely determined
What causes this issue? The system cannot find a unique entry for the primary t...
EK380 Deactivating loan &
Self-Explanatory Message Since SAP believes that this specific error message is ...
EK383 Installment plan &1 deactivated in dunning run &2 &3
What causes this issue? A dunning note for installment plan &V1& was re...
EK384 &1 disconnection orders created for disconnection document &2
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.