The sales cycle in SAP S/4HANA

At station four money went out. Now it comes back. The structure mirrors what you have already seen — but three ideas here have no counterpart in purchasing, and all three get asked about in interviews.

The documents, and what each one does

Document	What it asserts	Ledger effect	Stock effect
Inquiry and quotation	“The customer is asking; we are offering”	None	None
Sales order	“The customer ordered a quantity at a price”	None	A reservation, not a movement
Delivery document	“We picked and shipped”	—	The balance falls
Goods issue posting	“It actually left the warehouse”	Yes — cost of sales	The reduction is made firm
Customer invoice	“We billed the customer”	Yes — revenue and receivable	None
Collection	“We were paid”	Yes — cash rises	None

Stop at rows four and five, because they are half of this station.

When revenue is recognised — the question that separates understanding from memorisation

Notice that cost of sales is posted when the goods leave, and revenue is posted when the invoice is raised. Between those two moments a day or a week can pass.

Which means a shipment that left on the last day of the month and was not invoiced until the next one charges the first month with its cost and gives its matching revenue to a different month — so both months’ profit is distorted together unless somebody controls it.

The remedy is not accounting, it is operational: do not leave a gap between shipping and invoicing at a period boundary. Anyone who understands that sentence understands why a finance director stands at the warehouse door on the last day of the month.

And a general rule that holds here and in any other system: the event that moves stock and the event that moves revenue are not the same event, and must never be assumed simultaneous.

The document flow — the most useful diagnostic in the module

Every document in this cycle knows what produced it and what it produced. The result is a single view showing the whole chain: quotation to order to delivery to invoice to collection.

That is not a display feature; it is a daily working tool. Because the customer’s most repeated question — “where is my order?” — is answered from this chain in seconds, and so is finance’s most repeated question — “why has this shipment not been invoiced?”

The skill worth acquiring is reading the chain backwards: a recorded sale with no collection, a delivery with no invoice, an order with no delivery. Every break in the chain is money suspended somewhere.

Pricing — layers, not a field

This is the third thing that surprises anyone arriving from a simpler system: price here is not a field on the item card; it is a computed result.

A price is assembled from a base price, discounts, additions such as freight, and tax — and every one of those components can depend on the customer, the distribution channel, the quantity, or the date.

The rule to hold on to: a price is a property of a relationship between two parties on a date, not a property of a thing. One item sells at two prices to two customers on the same day, and that is not an error — it is the entire purpose of the structure.

Anyone who starts by putting a fixed price on the item card “to keep things simple” rebuilds pricing from scratch six months later, the first time a manager asks for a price list for a single customer.

Correcting an issued invoice

An issued invoice is not edited. The correction is a separate document: a credit note to reduce, a debit note to increase, linked to the original.

That reads today as conservative accounting practice, and it is in fact a legal requirement in every e-invoicing regime on earth — set out explicitly at station eight. Understand it here and you will find it self-evident there.

The cycle explained independently of any product, from quotation to collection, is in the sales cycle from order to cash.

What you actually do at this station

Write the expected entry for every step, distinguishing clearly between the two that are separated in time: cost of sales and revenue.
Design a period-boundary scenario: a shipment that left on the 30th and was invoiced on the 3rd of the following month. Write its effect on both months’ profit, in figures.
Draw the document flow for one complete sales order, then draw three broken cases and write what each break means financially.
Design a three-layer pricing rule producing two different prices for two customers on the same item.
Correct an invoice with a credit note, and write why the invoice itself was not edited.

The three commonest errors

One: invoicing before shipping to hit a monthly target. It produces revenue with no matching cost in the same month, which is a distortion of profit before it is anything else.

Two: overriding the price by hand on the invoice instead of fixing the pricing rule. It works once, gets repeated a hundred times, and then nobody knows what the correct price for that customer is.

Three: ignoring the customer’s credit limit. A sale that is never collected is not a sale, and setting a credit limit is a decision taken once that prevents a problem that recurs — one of the clearest markers of a disciplined system against one that merely records. What that discipline is worth when the product is being evaluated as a whole is set out in the SAP S/4HANA guide.

The acceptance test for this station

Write the cycle’s documents in order, marking which produce an entry and which move stock.
Calculate the period-boundary gap in figures against two months’ profit.
Draw a document flow for three broken cases, and state what each break means.
Design a three-layer pricing rule that yields two different prices for two customers.
Explain to a non-accountant why an issued invoice is not edited. The same sentence gets used at station eight.

What comes next

Both cycles are understood, and stock has moved in both directions. The next station asks about the number that passed through both and was never discussed: what were the goods valued at? — with the difference between standard cost and moving average, and why that choice is a management decision rather than an accounting one.