3673605 - Duplicate postings after activating the SSCUI 107009 'Intercompany Usage of General Journal Entries functionality'

Activating SSCUI 107009 'Intercompany Usage of General Journal Entries functionality' may lead to duplicate postings in the sub-ledger for the same intercompany transaction.

SAP S/4HANA Cloud Public Edition

The system automatically creates clearing (BUV) lines to balance postings by company code to zero. This occurs through configuration "Automatic Account Determination" (SSCUI ID 100297). The same configuration applies when executing Intercompany (ICO) Billing (4AN), which can result in duplicate entries on the maintained account. This depends on the information provided in the posting via various Apps, including but not limited to:

• Upload General Journal Entries
• Post General Journal Entries
• Verify General Journal Entries (new)

• This behavior results from enabling the SSCUI for Non-Management Accounting postings, which follow a different intercompany clearing account logic. It is important to thoroughly investigate whether the recommended standard Management Accounting transactions can be used, such as 4AN Repostings (e.g., reassigning costs and revenues).
• If the Financial Accounting (FI) journal entries is used instead, ensure the posting includes information on the intercompany clearing lines. If the posting nets to zero by company code (and is recommended by profit center to avoid document split), the automatic account determination for clearing line generation isn't used, and a 'Mgmt Accounting-like' ('CO-like') posting is generated.
  
  

Intercompany Management Accounting postings & subsequent intercompany billing (via 4AN).

• Intercompany Management Accounting postings are normally posted without clearing to payables/receivables as these postings are effected without tax and do not need to comply to transfer pricing guidelines.
• Thus, the clearing of intercompany Management Accounting postings is rather a technical necessity, but can, depending on business and compliance needs, be posted to clearing accounts configured as Non-operative P&L accounts (recommended) or Balance sheet accounts.
  
  

For intercompany, a tax and a legally relevant transaction the intercompany clearing is normally posted as follows:

Intercompany clearing line bears the risk of duplicate entries in case general journal entries are incorporated into 4AN (Intercompany Billing).

Therefore, in case an Intercompany General Journal Entry is posted with automatic clearing account determination, a duplicate entry will be created on the maintained Account from Configuration Automatic Account Determination → SSCUI ID: 100297.

Intercompany Management Accounting postings.

• Intercompany Management Accounting postings are normally posted without clearing to payables/receivables as these postings are effected without tax and do not need to comply to transfer pricing guidelines.
• Thus, the clearing of intercompany Management Accounting postings is rather a technical necessity, but can, depending on business and compliance needs, be posted to clearing accounts configured as Non-operative P&L accounts (recommended) or Balance Sheet accounts.

Intercompany General Journal Entries - triggered via Intercompany Billing.

For intercompany, a tax and a legally relevant transaction the intercompany clearing is posted according to standard configuration and would determine same  GL accounts as the initial posting which is intended to be billed if no deviating clearing account has been specified in the General Journal Entry:

Recommended solution

Define the clearing line within the posting to ensure compliant processing.

Example:

Duplicate postings, Intercompany Billing, Non-Management Accounting, General Journal Entries, Intercompany postings, PPM-SCL-BIL, PPM-SCL-BIL-FIO, 4AN, SSCUI 107009, SSCUI 100297, SAP S/4HANA Cloud Public Edition, Billing. , KBA , PPM-SCL-BIL , Project Billing (Public Cloud) , PPM-SCL-BIL-FIO , Fiori UI for Project Billing (Public Cloud) , Problem