Shipped but not yet billed
Everything on this page was already earned. Six of May’s 84 deliveries ended the month unbilled, 84,600.00 of revenue waiting on paperwork, and the delivered worklist would have shown items, no values, and no history.
◆ The gap, valuedsix deliveries, one number.
| Delivered not billed, 31 May | Count |
|---|---|
| Deliveries issued in May | 84 |
| Billed by month end | 78 |
| Unbilled at close | 6 |
| The six, valued | Amount |
|---|---|
| Waiting under a week | 51,200.00 |
| Waiting over a week | 33,400.00 |
| Earned, uninvoiced | 84,600.00 |
The 84 and 78 are the delivery page and register totals; this page just subtracts and prices. The over-a-week bucket is the one that pages a manager, because billing blocks and missing data live there. Sample values are illustrative, never client data.
◆ A worklist is not a reportthe delivered view has no memory.
The delivered due list is a processing screen: it shows today’s items so a clerk can bill them, carries no value trend, and forgets yesterday. Practitioners report unbilled revenue discovered in audits precisely because nobody graphed the gap. Landed daily, the gap becomes a line the close watches.
◆ The cutoff tellgaps that breathe monthly.
A due-list value that swells in the last week and collapses after close is billing being steered. The daily trend shows the breathing; the stated rule is that earned revenue bills on the clock, not the calendar.
- SAP
- The vendor. Systems, Applications, and Products in data processing.
- HANA
- SAP’s in-memory database, the platform S/4 runs on.
- SD
- Sales and Distribution, the order-to-cash module.
- due list
- The delivered billing worklist; items, no values, no memory.
- VF04
- The transaction clerks process the due list through.
- billing block
- The hold that strands a delivery on the list.
- earned, uninvoiced
- Shipped revenue waiting on paperwork; the leak.