# Payment Order Request, Approval and Bank Instruction Print Program

> A custom program that builds payment requests from due vendor invoices, sends each request to one- or two-step approval by amount limits, removes the payment block of approved items and prints the payment instruction for the bank as a PDF. Who requested and approved what, and when, is tracked in one list.

- Type: Program, Custom development, Form
- Module: FI
- Estimated effort: L (10–15 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/payment-order-request-approval-and-bank-instruction-program/


## Why is the standard not enough?

F110 prepares the payment proposal and makes the payment, but it does not manage who approves the proposal by amount limit, the approval history or the signed instruction form for the bank. Payment blocks are removed one by one in FBL1N, and approval is often collected by email or on paper. The custom program keeps request, approval and printout together and prevents unapproved items from being paid by keeping them blocked.

### Closest standard alternatives

- F110: Makes the payment; no amount-based approval flow and no bank instruction form.
- FBL1N: Payment blocks are removed by hand per item; no approval history is kept.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| BSIK | Due vendor open items, payment block (ZLSPR) and due date | Read | - | ECC + S/4 |
| BSEG | Payment block set during approval and removed after it | Write | BSEG-BUKRS = BSIK-BUKRS AND BSEG-BELNR = BSIK-BELNR AND BSEG-GJAHR = BSIK-GJAHR AND BSEG-BUZEI = BSIK-BUZEI | ECC + S/4 |
| LFA1 | Vendor name and tax details | Read | LFA1-LIFNR = BSIK-LIFNR | ECC + S/4 |
| LFBK | Vendor bank account and IBAN | Read | LFBK-LIFNR = BSIK-LIFNR | ECC + S/4 |
| T042Z | Payment method check | Read | - | ECC + S/4 |
| REGUH | Payment run header: bank, amount and payment document | Read | - | ECC + S/4 |
| REGUP | Invoices paid: item list on the instruction form | Read | REGUP-LAUFD = REGUH-LAUFD AND REGUP-LAUFI = REGUH-LAUFI AND REGUP-VBLNR = REGUH-VBLNR | ECC + S/4 |

## BAPIs and functions used

- FI_ITEMS_MASS_CHANGE: Sets and removes the payment block of items
- SAP_WAPI_START_WORKFLOW: Sends the request to the approver's inbox
- FP_FUNCTION_MODULE_NAME: Finds the generated module of the payment instruction form
- SO_NEW_DOCUMENT_ATT_SEND_API1: Emails the approval notice and the instruction PDF

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_BUKRS | Company code | Single value | BSIK-BUKRS | Yes |
| S_LIFNR | Vendor | Range / multiple | BSIK-LIFNR | No |
| P_DUEDT | Due up to this date | Single value | - | Yes |
| S_ZLSCH | Payment method | Range / multiple | BSIK-ZLSCH | No |
| R_MODE | Mode: create request, approve or print instruction | Radio button | - | No |

## Result list columns

| Column | Source |
|---|---|
| Request no. | Calculated: Sequence number in the request table |
| Vendor | BSIK-LIFNR |
| Vendor name | LFA1-NAME1 |
| Invoice document | BSIK-BELNR |
| Net due date | Calculated: Baseline date (ZFBDT) + payment term days |
| Amount | BSIK-WRBTR |
| Currency | BSIK-WAERS |
| Requested by | Calculated: User who created the request |
| Approval status | Calculated: Waiting (step), approved, rejected or paid |
| Waiting (days) | Calculated: Today − request date |

## How does the program work?

1. The requester lists due open items from BSIK by company code, vendor and due date; the vendor name and IBAN come from LFA1 and LFBK, and the payment method is checked against T042Z.
2. A payment request is created from the selected items; request number, requester, amount and comment are written to the request table. Items without a payment block are blocked with FI_ITEMS_MASS_CHANGE until approval is complete.
3. The approval matrix (company code, amount range, approver and number of steps) is read from a settings table; the request is sent to the approver's inbox with SAP_WAPI_START_WORKFLOW and also by email.
4. The approver sees the request item by item and approves, rejects or reduces the amount. After the final approval, the items' payment block is removed with FI_ITEMS_MASS_CHANGE and they enter the next F110 run.
5. After the payment run, the payment document is read from REGUH and REGUP, and the payment instruction is printed as an Adobe or Smart Forms form with bank, account and item list.
6. The request list is reported in ALV with status, waiting time and approval history.

## Authorization objects

- F_LFA1_BUK: Authorization to display vendor accounts in the company code
- F_BKPF_BUK: Authorization to change the payment block (document change)
- F_REGU_BUK: Authorization to display payment run data
- S_WF_WI: Authorization to process approval work items

## Frequently asked questions

### Can an unapproved invoice be paid by mistake?

Items in a request are blocked for payment until approval is complete, and F110 does not pay blocked items. The block is removed by the program only after the final approval.

### How are the approval limits changed?

Company code, amount range, currency, approver and number of steps are kept in a settings table; when the finance team changes it, new requests follow the new rule.

### Can approvers approve from a phone?

Because the request arrives in the standard inbox, on S/4HANA it can also be approved from a phone through the Fiori My Inbox app.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=fi-payment-order-approval
