HCM Program Custom development Interface TR · Türkiye

Bank-Specific Salary Payment File Generation

Short answer: A program that reads net payment amounts from payroll results after the payroll run and produces the salary file in the format each bank requires. Payments are split by payment type (salary, advance, bonus, severance) and by the employee's bank; IBAN and total checks are performed, and the file is created together with a control list.

Estimated effort
M · 6–10 working days
System
ECC and S/4HANA
Tables
7
Scope
TR
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

PC00_M99_CDTA (PC00_M47_CDTA for Türkiye) runs the preliminary payment program and PC00_M99_FPAYM creates the payment medium; but the payment medium formats do not directly cover the banks' local salary file layouts, the split by payment type or a separate file per bank. Companies run separate Excel conversions per format. The program does this conversion inside SAP using a rule table.

Who uses it? Payroll specialists, finance and treasury teams, HR operations staff.

Closest standard alternatives

  • PC00_M99_CDTA Bank Transfer Preliminary Program (DME, International). Preliminary payment program; does not produce bank-specific formats or separate files per payment type.
  • PC00_M99_FPAYM Create Payment Medium. Creates files using payment medium formats; local salary file layouts require a separate format development.

Localization and legal basis

Tables used

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

TableRoleAccessSystem
HRPY_RGDIRDirectory for Payroll ResultsPayroll result directory: period, payment date, payment type (driving table)ReadECC + S/4
PCL2HR Cluster 2 (PCL2)Payroll cluster: BT payment details and RT net amountReadECC + S/4
PA0009HR Master Record: Infotype 0009 (Bank Details)Employee bank details and IBANReadECC + S/4
BNKABank Master DataBank name and branchReadECC + S/4
T012KHouse Bank AccountsCompany's paying bank accountReadECC + S/4
REGUHPayment Program Settlement DataPreliminary payment program result (if used)ReadECC + S/4
PA0001HR Master Record: Infotype 0001 (Organizational Assignment)Company code and payroll areaReadECC + S/4

S/4HANA notes

  • T012K: In S/4HANA reads of T012K go through the compatibility view V_T012K_BAM; bank accounts are maintained in Bank Account Management (BAM).

BAPIs and functions used

  • CU_READ_RGDIRRead Payroll Directory (Cluster CU). Reads the employee's payroll result directory
  • PYXX_READ_PAYROLL_RESULTRead Payroll Result. Reads the payroll result (BT, RT)
  • GUI_DOWNLOADDownload Internal Table to PC. Downloads the bank file to the user's computer

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_ABKRSPayroll areaSingle valuePA0001-ABKRSYesT1
P_PERIODPayroll periodSingle value—Yes11.2026
P_PAYDTPayment dateSingle valueHRPY_RGDIR-PAYDTNo28.11.2026
S_PAYTYPayment type (salary, advance, bonus, severance)Range / multipleHRPY_RGDIR-PAYTYNoMaaş
P_HBKIDPaying house bankSingle valueT012K-HBKIDYesBNK01
P_TESTTest run (no file)Checkbox—NoX

Result list columns

#ColumnSource
1Personnel no.HRPY_RGDIR-PERNR
2NamePA0001-ENAME
3IBANPA0009-IBAN
4BankBNKA-BANKA
5Payment typeCalculated Salary, advance, bonus or severance
6Net amountCalculated Payment amount from the BT table
7FileCalculated File name created per bank
8StatusCalculated Added to file, IBAN error or test

Sample result list

Personnel no.NameIBANBankPayment typeNet amountFileStatus
00002011Ayşe KorkmazTR33 0006 1005 1978 6457 8413 26Örnek Bank A.Ş.Salary38,450.75MAAS_ORNEKBANK_202611.txtAdded to file
00002018Mehmet UçarTR12 0001 0012 3456 7890 1234 56Demo Katılım BankasıSalary42,110.20MAAS_DEMOKATILIM_202611.txtAdded to file
00002025Zeynep AcarTR45 0006 2000 0000 0000 01Örnek Bank A.Ş.Salary29,875IBAN error
00002031Okan YelTR33 0006 1005 1978 6457 8499 01Örnek Bank A.Ş.Bonus15,000IKR_ORNEKBANK_202611.txtAdded to file
A view built with fictional sample data; not real system data.

How does the program work?

  1. Payroll area, period and payment date are selected; valid payroll results are read from HRPY_RGDIR with CU_READ_RGDIR, and off-cycle runs are included according to the payment type.
  2. The net amount to pay is taken from the RT/BT tables in cluster PCL2 with PYXX_READ_PAYROLL_RESULT; the BT table gives bank details and amount per payment.
  3. Alternatively, if the preliminary payment program was run, amounts and payees are read from REGUH, which keeps the selection logic of the standard preliminary program.
  4. The employee’s IBAN and bank come from PA0009, bank name and branch from BNKA, and the company’s paying account from T012K. IBAN length and check digits are validated.
  5. A format rule table is selected per bank (field order, fixed length or delimiter, date and amount format, character set, header and total lines) and a separate file is produced for each bank.
  6. The file total is compared with the payroll net total; if they differ no file is created. The file is written to the server or downloaded with GUI_DOWNLOAD, and the control list is archived as PDF.

Performance notes

Read payroll results once per employee and process only the BT table. For thousands of employees, produce the file on the application server and run in the background.

Features

  • Test mode (check without posting) Produces the control list without creating a file
  • Line-by-line result and error log Every file is logged with user, time and total; regenerating for the same period gives a warning
  • Download failed lines as a separate file Employees with invalid IBAN or missing bank data are listed separately
  • Runs as a background job Can run in the background once payroll is closed

Authorization objects

  • P_PCLXAuthorization to read the payroll result cluster (RELID RU/TR)
  • P_ORGINAuthorization to read employee data by personnel area, employee group and infotype
  • S_DATASETFile access authorization to write the file to the application server

Frequently asked questions

How long does it take to add a new bank?

If the bank's specification is known, a new set of rows is added to the format rule table; 0.5–1 day is enough for most banks. Banks that want a completely different structure (e.g. XML) add 1–2 days.

Should the standard preliminary payment program still be run?

It is recommended. If it runs, payment documents and postings stay standard and the program only produces the file format. Without it, the amounts are read directly from the payroll result.

Does it work on S/4HANA?

Yes. The payroll cluster, HRPY_RGDIR and the bank details infotype are the same on S/4HANA (H4S4); bank master data stays in BNKA.

Related reports

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: Bank-Specific Salary Payment File Generation