Türkiye Issued Cheque Processing, Approval and Printing
Short answer: A program that prepares cheques for vendors from open items, sends them for approval, after approval moves the vendor liability to an 'issued cheques' account with the due date, and prints onto the bank's QR-coded cheque leaf and a cheque list for handing over to the vendor. Cheque number, bank and due date are kept on each item; cheques that fall due are cleared by the bank payment.
- Estimated effort
- L · 10–14 working days
- System
- ECC and S/4HANA
- Tables
- 8
- Scope
- TR
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
Standard check management (F-58, F110 and the check register PAYR) assumes the cheque is debited by the bank on the payment date and prints on a blank leaf with SAP's own form. With post-dated cheques issued in Türkiye, the liability moves from the vendor to an 'issued cheques' account when the cheque is given and stays open there until the due date; the cheque is filled onto the bank's pre-printed QR-coded leaf and handed to the vendor with a cheque list. This flow, the approval step and a cheque leaf layout per bank are not available in the standard.
Who uses it? Accounts payable, finance and treasury teams, managers who approve payments.
Closest standard alternatives
- F-58 Payment with Printout. Payment with cheque printout using the standard form; no post-dated 'issued cheques' account and no bank leaf layout.
- F110 Automatic Payment Program. The payment program can run with a cheque payment method; the approval step and the post-dated cheque flow are not covered.
Localization and legal basis
Türkiye · Turkish Revenue Administration (GİB)
Legal basis: Cheque Law No. 5941 and the cheque provisions of Turkish Commercial Code No. 6102; the banks' QR-coded cheque leaf practice.
The cheque leaf and cheque list layout is set up for each bank's current cheque book format during installation; the mandatory data on the cheque leaf is checked against current regulation at installation.
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| BSIKVendor Open Items | Vendor open items (invoices to be paid by cheque) | Read | ECC + S/4 |
| LFA1Vendor Master (General Section) | Payee name and address | Read | ECC + S/4 |
| T012KHouse Bank Accounts | Bank account the cheque is drawn on | Read | ECC + S/4 |
| BNKABank Master Data | Bank and branch name | Read | ECC + S/4 |
| PAYRPayment Medium File (Check Register) | Standard check register: duplicate cheque number check | Read | ECC + S/4 |
| BKPFAccounting Document Header | Cheque issue document | Write | ECC + S/4 |
| BSEGAccounting Document Segment | Vendor and 'issued cheques' items: cheque number, due date, bank | Write | ECC + S/4 |
| BSISG/L Account Open Items (Secondary Index) | Open issued cheques (due date tracking) | Read | ECC + 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.
- T012K: In S/4HANA reads of T012K go through the compatibility view V_T012K_BAM; bank accounts are maintained in Bank Account Management (BAM).
- BSIS → ACDOCA: In S/4HANA BSIS is no longer filled as a separate index table; it is read through a compatibility view of the same name. New developments should use ACDOCA or the related CDS views.
BAPIs and functions used
- SAP_WAPI_START_WORKFLOWWorkflow: Start Workflow. Starts the cheque proposal approval flow
- BAPI_ACC_DOCUMENT_POSTAccounting: Post Document. Posts the transfer from vendor to the 'issued cheques' account
- POSTING_INTERFACE_CLEARINGPost with Clearing via Internal Posting Interface. Clears the invoices paid by cheque
- SSF_FUNCTION_MODULE_NAMEGet Smart Form Function Module Name. Calls the bank-specific cheque leaf and cheque list form
- SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Emails the cheque list to the vendor
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_BUKRS | Company code | Single value | BSIK-BUKRS | Yes | 1000 |
| S_LIFNR | Vendor | Range / multiple | BSIK-LIFNR | No | 300000 – 399999 |
| P_HBKID | House bank | Single value | T012K-HBKID | Yes | BNK01 |
| P_HKTID | Account ID | Single value | T012K-HKTID | Yes | TRY01 |
| P_PROP | Prepare cheque proposal | Radio button | — | No | X |
| P_POST | Post and print approved cheques | Radio button | — | No | — |
| P_LIST | Issued cheque list | Radio button | — | No | — |
| P_TEST | Test mode | Checkbox | — | No | X |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Cheque number | BSEG-ZUONR |
| 2 | Vendor | BSEG-LIFNR |
| 3 | Payee | LFA1-NAME1 |
| 4 | Bank | BSEG-HBKID |
| 5 | Amount | BSEG-WRBTR |
| 6 | Due date | BSEG-ZFBDT |
| 7 | Status | Calculated Proposed, in approval, posted–printed, handed over, paid or voided |
Sample result list
| Cheque number | Vendor | Payee | Bank | Amount | Due date | Status |
|---|---|---|---|---|---|---|
| 0004512 | 300125 | Örnek Ambalaj A.Ş. | BNK01 | 185,000 | 31.01.2027 | Posted – printed |
| 0004513 | 300125 | Örnek Ambalaj A.Ş. | BNK01 | 185,000 | 28.02.2027 | Posted – printed |
| 0004514 | 300418 | Demo Lojistik Ltd. | BNK01 | 62,500 | 15.12.2026 | In approval |
How does the program work?
- Open items of the selected vendors (BSIK) are listed with due date and amount; the user selects the items to be paid by cheque and enters the cheque amount, due date and the bank account the cheque is drawn on (T012K). One cheque can clear several invoices, or one invoice can be paid with several cheques.
- The cheque number is proposed as the next free leaf from the cheque book of that bank account; numbers that are used, voided or already written to the standard check register (PAYR) are blocked.
- The cheque proposal goes for approval (workflow or email approval); one or two approval levels by amount are defined during installation.
- After approval the posting is made with BAPI_ACC_DOCUMENT_POST: vendor debit, ‘issued cheques’ account credit; the cheque number goes to the assignment field (BSEG-ZUONR), the due date to the baseline date (BSEG-ZFBDT), bank and account to BSEG-HBKID/HKTID. The paid invoices are cleared in the same document.
- The cheque leaf is printed through a Smart Form with the layout of that bank (amount in figures and words, place and date of issue, payee, due date); the QR code and bank data are pre-printed on the leaf and are not printed. A cheque list per vendor (cheque number, bank, due date, amount, cleared invoices) is printed in two copies or sent by email.
- Voiding: if the cheque has not been handed over, the posting is reversed and the leaf is marked in the register with a void reason.
- When the bank pays the cheque on the due date, the bank statement clears the ‘issued cheques’ item by cheque number; overdue cheques that are still open are flagged separately in the report.
Performance notes
Read BSIK by company code and vendor range, and PAYR by bank and account. For bulk printing get the Smart Form function name once per bank and open one spool request.
Features
- ALV list (sort, filter, subtotals)
- Test mode (check without posting)
- Line-by-line result and error log
- Send the result by email The cheque list can be sent to the vendor as a PDF.
Authorization objects
- F_BKPF_BUKPosting authorization for the company code
- F_BKPF_KOAAuthorization to post to vendor accounts
- F_PAYR_BUKAuthorization to read the check register
Frequently asked questions
Why is an 'issued cheques' account used instead of the bank account?
When a post-dated cheque is issued, no money leaves the bank; the liability moves from the vendor to the cheque. The bank account decreases only when the cheque is paid on the due date. The interim account shows cheque exposure by due date and keeps the bank balance accurate.
Is the QR code printed on the cheque leaf?
No. The QR code, serial number and bank data are pre-printed on the leaf by the bank. The program only fills in the blank fields (amount, date, payee, place of issue); the layout is tested on the printer for each bank during installation.
Can payments be made with endorsed customer cheques?
This program covers cheques the company draws itself. Endorsing customer cheques to vendors is handled on the portfolio side; see the cheque and promissory note portfolio report.
Related reports
Electronic Bank Statement Import and Automatic Posting Interface
A custom interface program that reads the account movements banks deliver in different formats (MT940, CAMT.053, bank XML or an Excel export) every …
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 …
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 …
Türkiye Cheque and Promissory Note Portfolio, Risk and Maturity Report
A custom ALV report that lists cheques and promissory notes received from customers with number, drawer, bank, due date and current position (in …
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.