How To Fix MN456 - G/L account & in company code & does not allow posting w/o tax code


SAP Error Message - Details

  • Message type: E = Error

  • Message class: MN - Message class for subsequent settlement (Purchasing)

  • Message number: 456

  • Message text: G/L account & in company code & does not allow posting w/o tax code

  • Show details Hide details
  • What causes this issue?

    It must always be possible to make postings without using a
    <GL:tax_code>tax code</> for <GL:G/L_account>G/L accounts</> to which
    rebate income or provisions for accrued rebate income from
    <DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent settlement</> are
    posted (postings of provisions for accrued income are not subject to
    tax).
    Therefore, the indicator "Posting without tax allowed" must be set for
    G/L account &V1& in <GL:company_code>company code</> &V2&.
    However, this is not the case.

    System Response

    Settlement accounting is not possible.

    How to fix this error?

    Please set the indicator or change the account determination (other G/L
    account).

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message MN456 - G/L account & in company code & does not allow posting w/o tax code ?

    The SAP error message MN456 indicates that a General Ledger (G/L) account in a specific company code does not allow postings without a tax code. This typically occurs when you attempt to post a transaction that requires a tax code, but the system is configured to enforce tax code requirements for that particular G/L account.

    Cause:

    1. G/L Account Configuration: The G/L account in question is set up in such a way that it mandates a tax code for postings. This is often the case for accounts that are related to sales, purchases, or any transactions that are subject to taxation.
    2. Company Code Settings: The company code settings may also enforce tax code requirements for certain types of transactions.
    3. Transaction Type: The type of transaction you are trying to post may inherently require a tax code (e.g., sales invoices, purchase invoices).

    Solution:

    To resolve this error, you can take the following steps:

    1. Check G/L Account Settings:

      • Go to the G/L account master data (transaction code FS00).
      • Verify the settings for the G/L account in question. Check the "Tax" tab to see if the account is set to require a tax code.
      • If necessary, adjust the settings to allow postings without a tax code, but be cautious as this may have implications for tax reporting.
    2. Provide a Tax Code:

      • When posting the transaction, ensure that you include a valid tax code that corresponds to the nature of the transaction. This is often the simplest solution if the account is meant to require a tax code.
    3. Review Company Code Configuration:

      • Check the company code settings related to tax configuration (transaction code OBY6).
      • Ensure that the tax settings align with your business requirements and that they are correctly configured.
    4. Consult with Finance Team:

      • If you are unsure about changing G/L account settings or tax configurations, consult with your finance or accounting team to ensure compliance with tax regulations.
    5. Transaction Type Review:

      • If the transaction type you are using does not require a tax code, consider using a different transaction type that aligns with your posting requirements.

    Related Information:

    • Tax Codes: Tax codes in SAP are used to determine the tax amount to be calculated on transactions. They are essential for compliance with tax regulations.
    • G/L Account Master Data: The master data for G/L accounts includes various settings that dictate how the account behaves during postings, including tax-related settings.
    • SAP Documentation: For more detailed information, refer to SAP Help documentation or consult with your SAP support team for guidance specific to your system configuration.

    By following these steps, you should be able to resolve the MN456 error and successfully post your transaction.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant