3806394 - Payment card settlement falls back to TCCAA clearing G/L XXXXXXXX instead of desired account in digital payments - SAP S/4HANA Cloud Public Edition

• When running the Accounts Receivable settlement job template SAP_FIN_AR_CREDIT_CARD_SETTLMT, the job determines clearing G/L XXXXXXXX.
• Attempts to change DPSETTLEMENT masking and the G/L in a PSP-type house bank do not change the posting account.
• Error appears in job log: “Payment serv. provider acc. : No house bank account could be determined.” (example alias: PSP)

• Product: SAP S/4HANA Cloud Public Edition
• SAP digital payments add-on (Public Cloud)

1. Open Schedule Accounts Receivables Jobs.
2. Select job template SAP_FIN_AR_CREDIT_CARD_SETTLMT and schedule the settlement run.
3. Observe the job determines clearing G/L XXXXXXXX and/or logs “No house bank account could be determined.”

• Merchant Alias was not maintained at the time existing authorizations were created; settlement therefore falls back to TCCAA, which resolves to G/L XXXXXXXX in Public Cloud.
• The House Bank Account lookup failed because the House Bank Account “Account Number” did not exactly match the Merchant Alias; when lookup fails, the process falls back to TCCAA.
• In Public Cloud, direct maintenance of TCCAA is not available; if Digital Advice is not used, the fallback TCCAA mapping is fixed and cannot be changed.

1. Use Digital Advice with Merchant Mapping:
2. 1 In the BTP merchant mapping, maintain a Merchant Alias for each relevant merchant.
3. Maintain House Bank Accounts in S/4HANA:
4. 1 For each Merchant Alias, create a House Bank Account and set the Account Number exactly equal to the Merchant Alias (no extra spaces/characters).
5. 2 Ensure the account is active and assigned to the correct company code.
6. 3 Assign the intended reconciliation G/L account to the House Bank Account.
7. Configure Electronic Bank Statement account symbol:
8. 1 In the EBS configuration, set DPSETTLEMENT to a mask that matches the desired G/L account’s ending (for example, change the pre-delivered “+++070” to “+++020” if the target G/L ends with 020).
9. Recreate authorizations for existing transactions:
10. 1 For authorizations created before Merchant Alias maintenance, create new billing/authorization documents so the alias is stored on the authorization.
11. 2 Note: Reauthorization alone does not update the stored alias on existing authorization records.
12. Validate job execution:
13. 1 Re-run SAP_FIN_AR_CREDIT_CARD_SETTLMT and confirm postings route via the House Bank Account determined by the Merchant Alias and DPSETTLEMENT mask.
14. Important limitation:
15. 1 If Digital Advice is not used, the system uses the fallback TCCAA determination in Public Cloud, which is fixed and cannot be changed.
16. If the log indicates a missing house bank account for a G/L, create and assign the required house bank account in Manage Bank Accounts before re-running the job.

• 3366157 - Digital Payments Add-On: No Clearing Account could be determined in Settlement Run
• 3743246 - Parameter check during payment card settlement
• 3469540 - Error message "Assign classic and digital payment card type to different G/L accounts" in Settlement Run
• 2524512 - Integration of SAP S/4HANA with the application "Digital Payments Add-On"
• 2712471 - Manage Bank Accounts: Missing or inconsistent bank account data
• 3059653 - Manage Bank Accounts: General guidance

SAP_FIN_AR_CREDIT_CARD_SETTLMT, digital payments, TCCAA, DPSETTLEMENT, merchant alias, House Bank Account, Account number match, Clearing account, Fallback determination, Electronic bank statement, Reconciliation account, BTP merchant mapping, Public cloud, Settlement run error, No house bank account could be determined , KBA , FIN-FSCM-DP-DP-2CL , SAP digital payments add-on (Public Cloud) , Problem