Skip to Content

Workflow Based Approval of Payment Proposal

From EHP 7 onwards SAP offers a workflow based solution for release of payment proposal. This means that the payment proposal gets routed to a concerned approver before the payment run can be made. Unless the approval has been made, the payment run cannot be carried out.

Basically this involves implementation of the following SAP notes:

  • 2418713 – F110 F111: Workflow-based release of payment proposal
  • 2441804 – F110 F111: Workflow-based release of payment proposal (installation for SAP Note 2441805)
  • 2441805 – F110 F111: Workflow-based release of payment proposal

The overall implementation is governed in by SAP note 2441770 – FI payment program: Workflow based release of payment proposal.

Below configuration is needed to have this working:

IMG path

Financial Accounting-Accounts Receivable and Accounts Payable-Business Transactions-Outgoing Payments-Automatic Outgoing Payments-Payment Proposal Processing-Configuration:

The company code and the payment method for which a workflow based release has to be activated is defined here:

The agent for approval can be defined at combination company code and currency level.

The agent determination can happen based on Vendor, Accounting Clerk, Payment Method, Amount etc.

In the below example we have based it on Vendor Number which means approval for vendors falling in a certain range would be directed to a particular agent based on the set up made:

The system checks the conditions for agent determination in the order specified. Once a condition for the payments of a business partner is fulfilled, the system transfers this to the work package of the selected agent for the workflow.

Case Study

Open Items posted on a vendor

Carrying out a proposal run based on the above list:

Agent determination in the payment proposal:

Attempting to carry out the payment run before the acceptance/rejection run:


Inbox of the approver:

Approver can block or reject some items:

Blocking items in payment proposal:

Payment proposal after editing:

Confirming the payment proposal

Payment proposal after being edited by the approver:

Once confirmed, the person initiating the transaction does not have the option to change the proposal:

Payment Run:

Payment document posted:


Thus we see that workflow based approval of payment proposal restricts unauthorized changes to the payment proposal during processing and restricts payment run before the workflow is completed.

You must be Logged on to comment or reply to a post.
  • Dear Harsha,

    You have shared very good information. We have similar requirement. I have configured and activated workflow at company code level and executed F110 with payment proposal. In this step system gave below message.

    Link to the event is deactivated

    Message no. WZ165


    The linkage between the triggering event and the task has not been activated.


    When the triggering event is activated, the linkage is entered in the table automatically.

    Goto the definition of the corresponding task and activate the event linkage from there.

    Now we are migrating to S/4 HANA 1809 version.

    Can you please tell me is there missing any step? I will be waiting your reply.

    Thanks & Regards




  • Dear Harsha,

    According to note 2712448 the existing workflow in ECC for the approval of the payment proposal will not work for S/4HANA with the FIORI-apps F0770 / F0771.

    In my humble opinion SAP should make a workflow to make it possible in the 1809 release, to work with a functional similar workflow.

    Kind regards,  Gerard Jonker

  • Hi Harsha,


    thanks for the informative blog. I have a requirement to issue notifications if a payment proposal is being made to a certain country (risky countries).

    Is it possible to issue workflow only if payments to certain countries are in the proposal?

    I checked the BADI FI_PAYMENT_PROPOSAL_WF and the method CHECK_WF_ACTIVE but it works only with the same basic parameters as the customizing (LAUFI, LAUFD, ZWELS), not really with REGUP or REGUH.

    Also I tried to customize some rules and when I issue a proposal that fit to no rule, some dummy package 9999999999 is assigned. So not really an option to skip the whole workflow.

    Thanks for any hints.


    Ondrej ZATOPEK

  • Hi Folks,

    Does anyone else have an issue where once the payment proposal is approved, WF-BATCH schedules and executes the payment run in background? Any way we can prevent this from happening ?



  • Hi Harsha

    I'm getting below message while running the payment proposal log.


    Please let me know which event we need activate in SWE2



  • Thanks for the informative and concise blog.

    I was able to successfully implement one step approval for Payment Proposals by implementing the sap notes.


    However, we have the requirement of 2-step approval for payment proposals.

    Do you have any insights as to how we can achieve that?

    • A workaround for a 2nd step of the approval is restricting authorization to subset of users who can execute the payment run. Basis should be able to assist you here.

  • Hi Harsha

    In above solution, Can we configure multi level approval hierarchy OR Approval can be done by one approver only ? In this solution, WF is triggered on Proposal. Please confirm if my understanding is correct ?