What shipped, and when it counted

A delivery is paperwork until the goods issue posts. May issued 84 deliveries moving 240 units, the exact 601 row the materials module counts, and six of them ended the month shipped, unbilled, and on a list someone owns.

RuleLand deliveries with their goods-issue dates and read revenue timing from the issue, because the issue posting is the event that counts, not the delivery paperwork.

Nevertrust delivery creation dates for cutoff. Paper is created early and often; the goods issue is when stock left and revenue earned the right to exist.

A delivery is paperwork until the goods issue posts. The issue is the moment stock, cost, and revenue all pivot.

◆ May deliveriesthe other side of the 601 row.

Deliveries, May 2026	Count
Delivery documents issued	84
Units shipped	240
Billed by month end	78
Delivered, not yet billed	6

The 84 documents and 240 units are the materials module’s 601 row, seen from the selling side: one tie across two modules. The six unbilled deliveries are valued and aged on the due list, not footnoted here. Sample values are illustrative, never client data.

◆ The backdated issuemonth end’s favorite lever.

The goods issue date can be entered in the past, and practitioners report month-end dances where issues backdate to pull revenue in or wait a day to push it out. The landed history keeps entry date beside posting date, so the dance leaves footprints.

◆ The owned answerdeliveries joined both ways.

Each delivery lands joined to its order lines and its billing documents, so cycle time from order to dock, the unbilled gap, and cutoff behavior are groupings, and the backlog shrinks in step with what actually shipped.

Use case

Problem

Cutoff reads delivery paperwork dates, backdated issues steer revenue invisibly, and the order-to-dock cycle time is a guess.

What we build

Deliveries landed with issue and entry dates, joined to orders and billing: cutoff behavior visible, cycle times computed, the unbilled gap fed forward.

What you get

Shipping truth with dates that confess: revenue timing read from the issue, backdating visible, and one tie to the materials module’s movement row.

Do your month-end goods issues cluster on the last day?

We land both dates and show the pattern.

Talk to us

Terms on this page

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.
goods issue: The posting that moves stock out and triggers revenue timing.
LIKP: The delivery header table.
LIPS: The delivery item table.
601: The movement type behind every issued delivery; see the materials module.