FI Program Custom development Form

Payment Order Request, Approval and Bank Instruction Print Program

Short answer: 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.

Estimated effort
L · 10–15 working days
System
ECC and S/4HANA
Tables
7
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

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.

Who uses it? Accounts payable teams, treasury and finance managers, managers who approve payments and internal control teams.

Closest standard alternatives

  • F110 Automatic Payment Program. Makes the payment; no amount-based approval flow and no bank instruction form.
  • FBL1N Vendor Line Item Display. Payment blocks are removed by hand per item; no approval history is kept.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
BSIKVendor Open ItemsDue vendor open items, payment block (ZLSPR) and due dateReadECC + S/4
BSEGAccounting Document SegmentPayment block set during approval and removed after itWriteECC + S/4
LFA1Vendor Master (General Section)Vendor name and tax detailsReadECC + S/4
LFBKVendor Master: Bank DetailsVendor bank account and IBANReadECC + S/4
T042ZPayment Methods for Automatic PaymentPayment method checkReadECC + S/4
REGUHPayment Program Settlement DataPayment run header: bank, amount and payment documentReadECC + S/4
REGUPPayment Program Processed ItemsInvoices paid: item list on the instruction formReadECC + S/4

S/4HANA notes

  • BSIK: In S/4HANA BSIK is no longer filled as a separate index table; reads work through a compatibility view. For new developments the I_OperationalAcctgDocItem CDS view is recommended.

BAPIs and functions used

  • FI_ITEMS_MASS_CHANGEMass Change of FI Line Items. Sets and removes the payment block of items
  • SAP_WAPI_START_WORKFLOWWorkflow: Start Workflow. Sends the request to the approver's inbox
  • FP_FUNCTION_MODULE_NAMEGet Adobe Form Function Module Name. Finds the generated module of the payment instruction form
  • SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Emails the approval notice and the instruction PDF

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_BUKRSCompany codeSingle valueBSIK-BUKRSYes1000
S_LIFNRVendorRange / multipleBSIK-LIFNRNo200000-299999
P_DUEDTDue up to this dateSingle value—Yes20.11.2026
S_ZLSCHPayment methodRange / multipleBSIK-ZLSCHNoT
R_MODEMode: create request, approve or print instructionRadio button—NoTalep oluştur

Result list columns

#ColumnSource
1Request no.Calculated Sequence number in the request table
2VendorBSIK-LIFNR
3Vendor nameLFA1-NAME1
4Invoice documentBSIK-BELNR
5Net due dateCalculated Baseline date (ZFBDT) + payment term days
6AmountBSIK-WRBTR
7CurrencyBSIK-WAERS
8Requested byCalculated User who created the request
9Approval statusCalculated Waiting (step), approved, rejected or paid
10Waiting (days)Calculated Today − request date

Sample result list

Request no.VendorVendor nameInvoice documentNet due dateAmountCurrencyRequested byApproval statusWaiting (days)
PO-2026-0412200145Demo Kimya San. Ltd.510000884111/18/2026248,000TRYAYILMAZWaiting (step 2)2
PO-2026-0412200388Örnek Ambalaj A.Ş.510000885611/19/202661,250TRYAYILMAZApproved0
PO-2026-0409200512Mavi Lojistik Ltd.510000870211/15/202618,400EURKDEMIRPaid0
PO-2026-0410200601Demo Enerji A.Ş.510000876011/17/202695,600TRYKDEMIRRejected1
A view built with fictional sample data; not real system data.

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.

Performance notes

The BSIK read is limited by company code and due date. A request usually has few items, and the block change is one update per item.

Features

  • ALV list (sort, filter, subtotals)
  • Send the result by email Notice to the approver, result to the requester and the instruction PDF to the bank.
  • Line-by-line result and error log Every approval, rejection and amount change is kept with user and time.
  • User-specific layout variants

Authorization objects

  • F_LFA1_BUKAuthorization to display vendor accounts in the company code
  • F_BKPF_BUKAuthorization to change the payment block (document change)
  • F_REGU_BUKAuthorization to display payment run data
  • S_WF_WIAuthorization 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.

Related reports

FI Report Custom ALV report

Payment Proposal Exceptions and Blocked Items Report

A custom report that collects, in one ALV list, the items in an automatic payment program (F110) proposal that will not be paid and the vendor items …

REGUH · REGUP · BSIK · LFA1

FI Report Custom ALV report

Vendor Open Items Aging Report

A custom ALV report that ages vendor open items by net due date and spreads the amounts into not-due, 0–30, 31–60, 61–90 and 90+ day buckets. The …

BSIK · LFA1 · LFB1 · T001

FI Program Custom Form

Vendor Payment Advice Email Program

A custom program that, after an automatic payment run, emails every vendor a PDF payment advice listing the invoices that were paid. A preview comes …

REGUH · REGUP · LFB1 · LFA1

Let us build this program for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: Payment Order Request, Approval and Bank Instruction Print Program