interpretation algorithm 029 (Payment Order Number) - not clearing automatically

[Camis99]

Hello all,

We have encountered an interesting issue related to Electronic Bank Statements (EBS) and automatic clearing in SAP. Supplier payments are not cleared automatically and instead end up in the APP: Reprocess Bank Statement Items.

The interpretation algorithm in use is 029 (Payment Order Number). When the reference in the memo line is not adjusted within the Reprocess Bank Statement Items app, the system allocates two invoices: one correct and one incorrect, with the incorrect invoice even belonging to another company code.

However, if we adjust the memo line and only retain the payment order before reallocating the open item, only the correct invoice is assigned.

Detailed Scenario:

• In the memo line, the amount of the correct invoice (869 SEK) is included.
• The incorrect invoice (belonging to a different company code) has "869" as the payment order.
• It appears the system interprets the amount (869 SEK) as the payment order, which doesn’t align logically, as the incorrect invoice belongs to another company code.

Invoices:

• Correct Invoice: Amount = 869 SEK, Payment Order = 688
• Incorrect Invoice (Different Company Code): Amount = 35,037.52 SEK, Payment Order = 869

This issue requires manual adjustment of the memo line to correctly allocate items, which can be time-consuming and inefficient in the long run, particularly if such cases occur frequently.

Additionally, this issue seems somewhat related to SAP Note 3413102 - Algorithm 029 Payment Order (PYORD) for Several Accounts, but there are differences in the scenarios, and the note does not apply to SAP Cloud.

Has anyone encountered a similar issue with interpretation algorithm 029?

I would greatly appreciate any insights or solutions.

[erickgoulardt]

Hello Camis, I am adjusting the tags of your question, and soon as possible a topic expert will assist you. Thank you for contributing in the community. Best Regards, Erick Goulardt SAP Support

[HenrikeGrtecke]

Hello, thank you very much for your question; it has been forwarded to the experts. Kind regards, Henrike

[HenrikeGrtecke]

Sent to the experts again...

[MalgorzataS · Accepted solution]

Yes, short numbers in memo lines are recognized as payment order numbers. This is SAP mistake.

SAP themselves recommend longer numbers to be used as payment order in note 114713:

"Moreover, you should not use "low" payment order numbers.
In particular, the number range interval 00 (0000000001 - 0999999999) may cause problems in connection with low number levels (four digits or below)"

However, they deliver number range 00, starting with number 1, as default in Public Cloud and they took away the configuration to change it (transaction FBN2).

I had the same issue and created a ticket. The number range can be changed by SAP only. The resolution suggested by SAP is in the attached screenshot.

Interesting fact - that ticket was resolved over a year ago and none of the promised changes has happened. I am working on the new system, installation from last month, and payment orders are still numbered starting with 1. And there is still no configuration to change it so SAP ticket has to be created.

[JGY · Accepted solution]

encountered the same problem. May I ask what's the component you use to raise the ticket to SAP for the number range adjustment?

[JGY · Accepted solution]

I encountered the same problem. May I ask what's the component you use to raise the ticket to SAP for the number range adjustment? In my case, SAP has correctly identified that it should apply the clearing algorithm 029 to a bank statement with the payment order (000000001 or 00001) in the note to payee. However, it does not automatically clear. It takes a user to manually go in the reprocess bank statement app and pressing allocate open items button for it to match off. I wonder why would manually pressing allocate open items button in the reprocess app work but not automatically upon import of statement and posting.

[MalgorzataS · Accepted solution]

The final component was FI-AP-AP-B-2CL. In my case there was also no automatic clearing because too many payment orders were assigned to the item. It was seen in the "Reprocess bank statement" app when checking item and its assigned "items to be cleared". Random invoices were assigned due to their payment order number being e.g. 25 and memo line contained text like "payment amount 150,25".

If nothing is found and allocated, then check if parameters are maintained with prefix ZR, as in the note: "704015 - electronic account statement: Interpretation algorithm 029" and documentation in SAP help: https://help.sap.com/docs/SAP_S4HANA_CLOUD/918bca53037f408f91a2295d04ac16bc/4dc5efb40c381c36e1000000... 

Default SAP-delivered parameters do contain ZR* range in the range "-'ZZZZZZZZZZZZZZZZ'.