# Customer–Vendor Netting Open Items Report

> A custom ALV report that puts open receivables and payables side by side for business partners that exist both as a customer and as a vendor, and calculates the amount that can be netted. It also shows whether the clearing-with-vendor/customer indicator is set in the master data.

- Type: Report, Custom development, ALV report
- Module: FI
- Estimated effort: S (2–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/customer-vendor-netting-open-items-report/


## Why is the standard not enough?

FBL5N and FBL1N show receivables and payables on separate screens. F.13 clears automatically, but it does not first report how much can be netted per partner, and it never sees the items when the master data link or the clearing indicator is missing. The netting decision and the confirmation letter to the partner need the net position of both sides in one list.

### Closest standard alternatives

- F.13: Clears automatically; does not report the nettable amount beforehand.
- FBL5N: Lists customer items; does not show the vendor side in the same list.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| KNA1 | Customer name and linked vendor number (driving table) | Read | - | ECC + S/4 |
| LFA1 | Vendor name and linked customer number | Read | LFA1-LIFNR = KNA1-LIFNR OR LFA1-KUNNR = KNA1-KUNNR | ECC + S/4 |
| BSID | Customer open items | Read | BSID-KUNNR = KNA1-KUNNR AND BSID-BUKRS IN S_BUKRS | ECC + S/4 |
| BSIK | Vendor open items | Read | BSIK-LIFNR = LFA1-LIFNR AND BSIK-BUKRS = BSID-BUKRS | ECC + S/4 |
| KNB1 | Clearing-with-vendor indicator on the customer | Read | KNB1-KUNNR = KNA1-KUNNR AND KNB1-BUKRS = BSID-BUKRS | ECC + S/4 |
| LFB1 | Clearing-with-customer indicator on the vendor | Read | LFB1-LIFNR = LFA1-LIFNR AND LFB1-BUKRS = BSIK-BUKRS | ECC + S/4 |
| T001 | Company code currency | Read | T001-BUKRS = BSID-BUKRS | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BSID-BUKRS | Yes |
| S_KUNNR | Customer | Range / multiple | KNA1-KUNNR | No |
| S_LIFNR | Vendor | Range / multiple | LFA1-LIFNR | No |
| P_KEYDT | Key date | Single value | SY-DATUM | Yes |
| P_SPGL | Include special G/L items (down payments, guarantees) | Checkbox | - | No |
| P_MINNET | Minimum nettable amount | Single value | - | No |

## Output columns

| Column | Source |
|---|---|
| Company code | BSID-BUKRS |
| Customer | KNA1-KUNNR |
| Customer name | KNA1-NAME1 |
| Vendor | LFA1-LIFNR |
| Vendor name | LFA1-NAME1 |
| Open receivables | Calculated: Sum of BSID-DMBTR, positive when SHKZG = S |
| Open payables | Calculated: Sum of BSIK-DMBTR, positive when SHKZG = H |
| Net balance | Calculated: Open receivables − open payables |
| Nettable amount | Calculated: The smaller of open receivables and open payables |
| Oldest receivable date | Calculated: Smallest BSID-BUDAT among the pair's open receivables |
| Clearing set on customer | KNB1-XVERR |
| Clearing set on vendor | LFB1-XVERR |
| Currency | T001-WAERS |
| Suggestion | Calculated: "Net with F.13" when both indicators are set, otherwise "fix master data" |

## How does the report work?

1. Customer–vendor pairs are found: customers with KNA1-LIFNR filled and vendors with LFA1-KUNNR filled are merged; one-way links are taken as well.
2. For every pair, open items posted up to the key date are read per company code from BSID (customer) and BSIK (vendor); unless P_SPGL is set, special G/L items (UMSKZ filled) are skipped.
3. Amounts are signed by the debit/credit indicator (SHKZG) and totalled in the company code currency (T001-WAERS).
4. Nettable amount = the smaller absolute value of the receivable and payable totals; net balance = receivable − payable.
5. KNB1-XVERR and LFB1-XVERR are read; when the indicator is off, the suggestion "fix master data" is added. Pairs below P_MINNET are not listed.

## Authorization objects

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

## Frequently asked questions

### What if the customer and vendor are not linked in the master data?

The link comes from KNA1-LIFNR or LFA1-KUNNR. Optionally, an extra selection that finds unlinked pairs by matching the tax number can be added.

### How are items in different currencies totalled?

Totals use the company code currency amount (DMBTR). A breakdown by document currency can be added as a second view.

### Does the report post the netting?

No, the report only reads. Netting is done with F.13 or manual clearing; the report shows which pairs are ready.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=fi-customer-vendor-netting
