FI Report Custom development ALV report

Customer Payment Behavior and Days-to-Pay Report

Short answer: A custom ALV report that uses customer invoices cleared in the selected period to calculate each customer's average days to pay, amount-weighted days late against the due date and the share of invoices paid late. It compares with the previous period and flags customers whose payment habits are getting worse.

Estimated effort
M · 3–5 working days
System
ECC and S/4HANA
Tables
6
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

FBL5N shows the posting and clearing date of cleared items but does not calculate a days-to-pay or days-late column and does not give an amount-weighted average per customer. FD10N only shows period balances. There is no standard list that summarizes a customer's payment history for credit-limit and payment-term discussions.

Who uses it? Credit control and collections teams, finance managers and sales managers.

Closest standard alternatives

  • FBL5N Customer Line Items. Lists cleared items with their dates; does not calculate days to pay or weighted delay.
  • FD10N Customer Balance Display. Shows period balances; does not summarize payment habits.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
BSADCustomer Cleared ItemsCleared customer items: document, due and clearing dates (driving table)—ECC + S/4
BKPFAccounting Document HeaderClearing document header, to separate reversalsBKPF-BUKRS = BSAD-BUKRS AND BKPF-BELNR = BSAD-AUGBLECC + S/4
BSIDCustomer Open ItemsOpen items overdue as of todayBSID-BUKRS = BSAD-BUKRS AND BSID-KUNNR = BSAD-KUNNRECC + S/4
KNA1Customer Master (General Section)Customer nameKNA1-KUNNR = BSAD-KUNNRECC + S/4
KNB1Customer Master (Company Code)Payment terms and accounting clerkKNB1-KUNNR = BSAD-KUNNR AND KNB1-BUKRS = BSAD-BUKRSECC + S/4
T001Company CodesCompany code local currencyT001-BUKRS = BSAD-BUKRSECC + S/4

S/4HANA notes

  • BSAD → I_OperationalAcctgDocItem: In S/4HANA BSAD is not filled as a separate table; it is read through a compatibility view of the same name. For new developments the I_OperationalAcctgDocItem CDS view is recommended.
  • BSID → I_OperationalAcctgDocItem: In S/4HANA BSID is no longer filled as a separate index table; reads work through a compatibility view of the same name. For new developments the I_OperationalAcctgDocItem CDS view is recommended.

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_BUKRSCompany codeRange / multipleBSAD-BUKRSYes1000
S_KUNNRCustomerRange / multipleBSAD-KUNNRNo200118
S_AUGDTClearing dateRange / multipleBSAD-AUGDTYes01.05.2026–31.10.2026
S_BLARTInvoice document typeRange / multipleBSAD-BLARTNoRV
S_BUSABAccounting clerkRange / multipleKNB1-BUSABNoT1
P_TOLLate-payment tolerance (days)Single value—No3
P_SUMMSummary by customerRadio button—NoX
P_DETLDetail by invoiceRadio button—No—

Output columns

#ColumnSource
1Company codeBSAD-BUKRS
2CustomerBSAD-KUNNR
3Customer nameKNA1-NAME1
4Payment termsKNB1-ZTERM
5Invoices paidCalculated Number of invoice items cleared in the period
6Amount paidCalculated Sum of BSAD-DMBTR of the cleared invoices
7Avg. days to payCalculated Amount-weighted average of (AUGDT − BLDAT)
8Avg. days lateCalculated Amount-weighted average of (AUGDT − net due date); negative means early payment
9Paid late share (%)Calculated Amount of invoices late beyond P_TOL / amount paid × 100
10Max days lateCalculated Largest (AUGDT − net due date) in the period
11Overdue open amountCalculated Amount of BSID items past their net due date as of today
12CurrencyT001-WAERS
13TrendCalculated Change in weighted days late versus the previous period of equal length

Sample output

Company codeCustomerCustomer namePayment termsInvoices paidAmount paidAvg. days to payAvg. days latePaid late share (%)Max days lateOverdue open amountCurrencyTrend
1000200118Bereket Tarım ÜrünleriZ030421,865,00047176458184,500TRYWorsening
1000200245Kuzey Yapı MarketZ045281,120,40044-11190TRYStable
1000200377Selin KozmetikZ03015356,90081519313841,780TRYWorsening
1000200402Akdeniz Soğuk ZincirZ06019948,25058-2560TRYImproving
A view built with fictional sample data; not real system data.

How does the report work?

  1. Invoice items with a clearing date (AUGDT) in the selected period and an empty special G/L indicator are read from BSAD. The payment document itself (BELNR = AUGBL) and items cleared by a reversal (clearing document is a reversal in BKPF) are excluded.
  2. Days to pay = AUGDT − document date (BLDAT). The net due date is derived from ZFBDT and ZBD1T/ZBD2T/ZBD3T; days late = AUGDT − net due date.
  3. Averages are weighted by amount (DMBTR), so small invoices do not distort the result.
  4. Invoices whose days late exceed the P_TOL tolerance count as paid late; the share of amount paid late and the maximum delay are calculated.
  5. For the current exposure, the overdue open amount as of today is added from BSID.
  6. The previous period of the same length is calculated the same way; if the weighted days late rose by more than 5 days the trend is “Worsening”, if it fell it is “Improving”.

Performance notes

Read BSAD by company code, customer and AUGDT range; the second read for the previous period uses the same keys. For many customers, run the summary view rather than the detail view in the background.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document From a customer row you drill down to invoice detail, and from an invoice to FB03.
  • Export to Excel
  • Runs as a background job Can be scheduled monthly to cover the last six months.
  • Send the result by email

Authorization objects

  • F_BKPF_BUKAccounting document authorization by company code
  • F_KNA1_BUKCustomer master authorization by company code

Frequently asked questions

How are partial payments handled?

An invoice enters the period when the last partial payment clears it completely, and that clearing date is used. If needed, residual-item payments that reference the invoice can be tracked separately to show the first payment date as well.

Why is an amount-weighted average used?

With a simple average, a delay on a small invoice weighs as much as the on-time payment of a large one. The amount-weighted average shows the delay that really affects cash flow; a simple average can be added as an extra column.

Is the result written to the credit limit automatically?

No, the report only reads and does not change master data. The results support decisions in credit-limit reviews and payment-term discussions.

Packages that include this solution

FI Package Custom

Customer Receivables Collection Pack

A pack that brings together four solutions a collection team needs, with one customer and company code selection: receivables aging, the customer's …

4 components · v1.0

Related reports

FI Report Custom ALV report

Customer Receivables Aging Report

A custom ALV report that ages customer open items by net due date and shows down payments received and other special G/L items in the same list. …

BSID · BSAD · KNA1 · KNB1

SD Report Custom ALV report

Sales Order – Delivery – Invoice Status Report

A custom ALV report that shows every sales order item on the same line as its delivery and invoice documents. You see in one list which orders have …

VBAK · VBAP · VBFA · LIKP

Let us build this report 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: Customer Payment Behavior and Days-to-Pay Report