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
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| BSADCustomer Cleared Items | Cleared customer items: document, due and clearing dates (driving table) | — | ECC + S/4 |
| BKPFAccounting Document Header | Clearing document header, to separate reversals | BKPF-BUKRS = BSAD-BUKRS AND BKPF-BELNR = BSAD-AUGBL | ECC + S/4 |
| BSIDCustomer Open Items | Open items overdue as of today | BSID-BUKRS = BSAD-BUKRS AND BSID-KUNNR = BSAD-KUNNR | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = BSAD-KUNNR | ECC + S/4 |
| KNB1Customer Master (Company Code) | Payment terms and accounting clerk | KNB1-KUNNR = BSAD-KUNNR AND KNB1-BUKRS = BSAD-BUKRS | ECC + S/4 |
| T001Company Codes | Company code local currency | T001-BUKRS = BSAD-BUKRS | ECC + 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
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BSAD-BUKRS | Yes | 1000 |
| S_KUNNR | Customer | Range / multiple | BSAD-KUNNR | No | 200118 |
| S_AUGDT | Clearing date | Range / multiple | BSAD-AUGDT | Yes | 01.05.2026–31.10.2026 |
| S_BLART | Invoice document type | Range / multiple | BSAD-BLART | No | RV |
| S_BUSAB | Accounting clerk | Range / multiple | KNB1-BUSAB | No | T1 |
| P_TOL | Late-payment tolerance (days) | Single value | — | No | 3 |
| P_SUMM | Summary by customer | Radio button | — | No | X |
| P_DETL | Detail by invoice | Radio button | — | No | — |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Company code | BSAD-BUKRS |
| 2 | Customer | BSAD-KUNNR |
| 3 | Customer name | KNA1-NAME1 |
| 4 | Payment terms | KNB1-ZTERM |
| 5 | Invoices paid | Calculated Number of invoice items cleared in the period |
| 6 | Amount paid | Calculated Sum of BSAD-DMBTR of the cleared invoices |
| 7 | Avg. days to pay | Calculated Amount-weighted average of (AUGDT − BLDAT) |
| 8 | Avg. days late | Calculated Amount-weighted average of (AUGDT − net due date); negative means early payment |
| 9 | Paid late share (%) | Calculated Amount of invoices late beyond P_TOL / amount paid × 100 |
| 10 | Max days late | Calculated Largest (AUGDT − net due date) in the period |
| 11 | Overdue open amount | Calculated Amount of BSID items past their net due date as of today |
| 12 | Currency | T001-WAERS |
| 13 | Trend | Calculated Change in weighted days late versus the previous period of equal length |
Sample output
| Company code | Customer | Customer name | Payment terms | Invoices paid | Amount paid | Avg. days to pay | Avg. days late | Paid late share (%) | Max days late | Overdue open amount | Currency | Trend |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1000 | 200118 | Bereket Tarım Ürünleri | Z030 | 42 | 1,865,000 | 47 | 17 | 64 | 58 | 184,500 | TRY | Worsening |
| 1000 | 200245 | Kuzey Yapı Market | Z045 | 28 | 1,120,400 | 44 | -1 | 11 | 9 | 0 | TRY | Stable |
| 1000 | 200377 | Selin Kozmetik | Z030 | 15 | 356,900 | 81 | 51 | 93 | 138 | 41,780 | TRY | Worsening |
| 1000 | 200402 | Akdeniz Soğuk Zincir | Z060 | 19 | 948,250 | 58 | -2 | 5 | 6 | 0 | TRY | Improving |
How does the report work?
- 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.
- 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.
- Averages are weighted by amount (DMBTR), so small invoices do not distort the result.
- 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.
- For the current exposure, the overdue open amount as of today is added from BSID.
- 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
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 …
Related reports
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. …
Customer Account Statement and Balance Confirmation Email Program
A custom program that prepares a customer account statement as PDF, with opening balance, period movements, open items and closing balance, and sends …
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 …
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.