# Billing Milestones Reached but Not Invoiced Report

> A custom ALV report that lists completed project milestones, those with an actual date, whose billing plan date in the sales order is still not invoiced, with customer, amount, billing block and days since completion. It shows project and sales teams together where delayed collections come from.

- Type: Report, Custom development, ALV report
- Module: PS
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/billing-milestones-reached-not-invoiced-report/


## Why is the standard not enough?

The VF04 billing due list shows SD billing plan dates, but it does not show items whose milestone is completed while the billing block is still set or the billing date is still in the future, together with the WBS element and project responsible. CN53N lists milestones without billing status or amount. As a result, completed work can stay uninvoiced for weeks.

### Closest standard alternatives

- VF04: Processes the billing due list; does not show items whose milestone is completed but blocked or dated in the future, with the WBS element.
- CN53N: Lists milestones; no billing plan value or status.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| MLST | Milestone: number, WBS element and actual date (driving table) | Read | - | ECC + S/4 |
| PRPS | WBS element and responsible person | Read | PRPS-PSPNR = MLST-PSPNR | ECC + S/4 |
| FPLT | Billing plan date: value, percentage, billing date, status and block | Read | FPLT-MLSTN = MLST-MLSTN | ECC + S/4 |
| FPLA | Billing plan header and sales document | Read | FPLA-FPLNR = FPLT-FPLNR | ECC + S/4 |
| VBAK | Sales order: customer and sales organization | Read | VBAK-VBELN = FPLA-VBELN | ECC + S/4 |
| KNA1 | Customer name | Read | KNA1-KUNNR = VBAK-KUNNR | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_VKORG | Sales organization | Range / multiple | VBAK-VKORG | No |
| S_KUNNR | Customer | Range / multiple | VBAK-KUNNR | No |
| S_VBELN | Sales document | Range / multiple | VBAK-VBELN | No |
| S_POSID | WBS element | Range / multiple | PRPS-POSID | No |
| S_ACTDT | Milestone actual date | Range / multiple | MLST-LST_ACTDT | No |
| P_BLOCK | Billing block only | Checkbox | - | No |
| P_KEYDT | Key date | Single value | SY-DATUM | Yes |

## Output columns

| Column | Source |
|---|---|
| WBS element | PRPS-POSID |
| Milestone | MLST-MLSTN |
| Actual date | MLST-LST_ACTDT |
| Sales document | VBAK-VBELN |
| Customer | VBAK-KUNNR |
| Customer name | KNA1-NAME1 |
| Billing plan item | FPLT-FPLTR |
| Billing date | FPLT-AFDAT |
| Percentage | FPLT-FPROZ |
| Value to bill | FPLT-FAKWR |
| Currency | FPLT-WAERS |
| Billing block | FPLT-FAKSP |
| Billing status | FPLT-FKSAF |
| Days since completion | Calculated: Key date − MLST-LST_ACTDT |
| Status | Calculated: Block set / billing date not reached / due, not invoiced |

## How does the report work?

1. Milestones with an actual date (LST_ACTDT) in the selected range and before the key date, not deleted (LOEKZ), are read from MLST; the WBS element is added from PRPS.
2. Billing plan dates are found in FPLT by milestone number (FPLT-MLSTN = MLST-MLSTN); dates whose billing status (FKSAF) is fully processed are skipped.
3. The sales document comes from FPLA, the customer and sales organization from VBAK and the customer name from KNA1.
4. The billing value FPLT-FAKWR, percentage FPLT-FPROZ, billing date FPLT-AFDAT and block FPLT-FAKSP are shown. Days since = key date − LST_ACTDT.
5. Status: "block set" (FAKSP filled), "billing date not reached" (AFDAT > key date) or "due, not invoiced".

## Authorization objects

- V_VBAK_VKO: Sales document display authorization by sales organization
- V_VBAK_AAT: Display authorization by sales document type
- C_PRPS_VNR: WBS element authorization by responsible person

## Frequently asked questions

### Does the report create the invoice or remove the block?

No, it only reads. Billing is done with VF04 or VF01. If automatic block removal is wanted, it is assessed as a separate program.

### Is resource-related billing covered as well?

No. The report covers billing plan dates linked to milestones. Resource-related billing with DP91 is tracked with a different logic.

### Does this report work on S/4HANA?

Yes. MLST, FPLA and FPLT are used in S/4HANA as well; VBAK and KNA1 are read with the same fields.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=ps-billing-milestones-not-invoiced
