# Customer Payment Behavior and Days-to-Pay Report

> 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.

- Type: Report, Custom development, ALV report
- Module: FI
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/customer-payment-behavior-days-to-pay-report/


## 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.

### Closest standard alternatives

- FBL5N: Lists cleared items with their dates; does not calculate days to pay or weighted delay.
- FD10N: Shows period balances; does not summarize payment habits.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| BSAD | Cleared customer items: document, due and clearing dates (driving table) | Read | - | ECC + S/4 |
| BKPF | Clearing document header, to separate reversals | Read | BKPF-BUKRS = BSAD-BUKRS AND BKPF-BELNR = BSAD-AUGBL | ECC + S/4 |
| BSID | Open items overdue as of today | Read | BSID-BUKRS = BSAD-BUKRS AND BSID-KUNNR = BSAD-KUNNR | ECC + S/4 |
| KNA1 | Customer name | Read | KNA1-KUNNR = BSAD-KUNNR | ECC + S/4 |
| KNB1 | Payment terms and accounting clerk | Read | KNB1-KUNNR = BSAD-KUNNR AND KNB1-BUKRS = BSAD-BUKRS | ECC + S/4 |
| T001 | Company code local currency | Read | T001-BUKRS = BSAD-BUKRS | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BSAD-BUKRS | Yes |
| S_KUNNR | Customer | Range / multiple | BSAD-KUNNR | No |
| S_AUGDT | Clearing date | Range / multiple | BSAD-AUGDT | Yes |
| S_BLART | Invoice document type | Range / multiple | BSAD-BLART | No |
| S_BUSAB | Accounting clerk | Range / multiple | KNB1-BUSAB | No |
| P_TOL | Late-payment tolerance (days) | Single value | - | No |
| P_SUMM | Summary by customer | Radio button | - | No |
| P_DETL | Detail by invoice | Radio button | - | No |

## Output columns

| Column | Source |
|---|---|
| Company code | BSAD-BUKRS |
| Customer | BSAD-KUNNR |
| Customer name | KNA1-NAME1 |
| Payment terms | KNB1-ZTERM |
| Invoices paid | Calculated: Number of invoice items cleared in the period |
| Amount paid | Calculated: Sum of BSAD-DMBTR of the cleared invoices |
| Avg. days to pay | Calculated: Amount-weighted average of (AUGDT − BLDAT) |
| Avg. days late | Calculated: Amount-weighted average of (AUGDT − net due date); negative means early payment |
| Paid late share (%) | Calculated: Amount of invoices late beyond P_TOL / amount paid × 100 |
| Max days late | Calculated: Largest (AUGDT − net due date) in the period |
| Overdue open amount | Calculated: Amount of BSID items past their net due date as of today |
| Currency | T001-WAERS |
| Trend | Calculated: Change in weighted days late versus the previous period of equal length |

## 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".

## Authorization objects

- F_BKPF_BUK: Accounting document authorization by company code
- F_KNA1_BUK: Customer 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.

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