# Türkiye Input VAT List Report

> A custom ALV report that produces the input VAT list required for Turkish VAT refund files from purchase documents in SAP, one line per invoice. Invoice date, series and number, vendor name, tax ID, amount excluding VAT and VAT come in one Excel-ready list.

- Type: Report, Custom development, ALV report
- Module: FI
- Estimated effort: S (3–5 working days)
- Localization: TR
- Last updated: 2026-11-16
- URL: https://nekuhub.com/en/reports/turkey-input-vat-list-report/


## Localization and legal basis: Türkiye

- Legal basis: The input VAT list requested for VAT refund claims under the Turkish VAT General Application Communiqué.
- The list columns are checked against the current Revenue Administration (GİB) rules during installation and updated if needed.

## Why is the standard not enough?

S_ALR_87012357 totals tax lines per tax code but does not give an invoice-level list with the vendor tax ID and invoice series and number. Teams usually build this list by hand in Excel from ledger extracts, which can take days at period close.

### Closest standard alternatives

- S_ALR_87012357: Totals per tax code; does not give an invoice-level list with vendor tax ID and invoice series and number.
- FBL1N: Lists vendor items; does not show the VAT base and VAT amount on the same line.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| BKPF | Document type, document date, period and invoice number (driving table) | Read | - | ECC + S/4 |
| BSET | Tax code, amount excluding VAT and VAT | Read | BSET-BUKRS = BKPF-BUKRS AND BSET-BELNR = BKPF-BELNR AND BSET-GJAHR = BKPF-GJAHR | ECC + S/4 |
| BSEG | Vendor line (account type K) and item text | Read | BSEG-BELNR = BKPF-BELNR AND BSEG-KOART = 'K' | ECC + S/4 |
| LFA1 | Vendor name and tax ID | Read | LFA1-LIFNR = BSEG-LIFNR | ECC + S/4 |
| T001 | Company code local currency | Read | T001-BUKRS = BKPF-BUKRS | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BKPF-BUKRS | Yes |
| P_GJAHR | Fiscal year | Single value | BKPF-GJAHR | Yes |
| S_MONAT | Period | Range / multiple | BKPF-MONAT | Yes |
| S_MWSKZ | Input VAT tax codes | Range / multiple | BSET-MWSKZ | Yes |
| S_BLART | Document type | Range / multiple | BKPF-BLART | No |

## Output columns

| Column | Source |
|---|---|
| Invoice date | BKPF-BLDAT |
| Invoice series and number | BKPF-XBLNR |
| Vendor name | LFA1-NAME1 |
| Tax ID | Calculated: LFA1-STCD1 or LFA1-STCD2 depending on system usage (Business Partner tax number in S/4HANA) |
| Goods / services | BSEG-SGTXT |
| Amount excl. VAT | BSET-HWBAS |
| VAT | BSET-HWSTE |
| Tax code | BSET-MWSKZ |
| Deduction period | Calculated: BKPF-GJAHR / BKPF-MONAT |

## How does the report work?

1. Purchase documents are read from BKPF for the selected company code, fiscal year and periods, optionally narrowed by document type.
2. Each document's tax lines are read from BSET and limited to input VAT tax codes; the amount excluding VAT (HWBAS) and the VAT (HWSTE) are in local currency.
3. The vendor is taken from the document's vendor line (BSEG, account type K); name and tax ID come from LFA1.
4. The invoice series and number come from the document reference (BKPF-XBLNR), the invoice date from the document date (BKPF-BLDAT).
5. Lines are totalled per invoice and shown in the column order of the GİB list.

## Authorization objects

- F_BKPF_BUK: Accounting document authorization by company code
- F_LFA1_BUK: Vendor master authorization by company code

## Frequently asked questions

### Which field holds the tax ID?

In SAP systems in Türkiye the tax ID is usually kept in LFA1-STCD1 or LFA1-STCD2; which one is used is checked during installation. In S/4HANA, Business Partner tax numbers can be read as well.

### Does the list follow the GİB format?

The columns follow the order of the input VAT list. Because GİB rules can change, the current format is checked during installation and columns are updated if needed.

### Does it work on S/4HANA?

Yes. BKPF, BSEG and BSET are still used in S/4HANA; for high volumes, ACDOCA-based CDS views can be preferred.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=fi-tr-input-vat-list
