The sales cycle in Dynamics 365 Business Central

Money left at the previous station. Now it comes back.

The structure mirrors what you have seen: one document with two independent quantities — a quantity to ship and a quantity to invoice — and three shapes of posting.

But three ideas in it have no direct counterpart on the purchase side, and all three get asked when somebody tests your understanding rather than your memory.

The first idea: a reservation is not a stock movement

A sales order reduces what is available without reducing what is on hand.

After an order for a hundred units, stock stays at a hundred in the warehouse, and its availability is zero. Two different numbers on the same screen, and anybody reading the first as the second promises a customer goods already promised to someone else.

The product provides a stockout warning that fires when a sales line is created for an unavailable quantity. It is a setting that is on or off, and switching it off is an operational decision rather than a technical detail — anybody switching it off because the warning is “annoying” buys silence at the price of a promise that cannot be kept.

The second idea: revenue and cost are not necessarily posted together

Cost of goods sold is measured when the goods leave — that is, with the shipment. Revenue is posted with the invoice.

Event	What gets recorded
The shipment	Stock leaving, and cost of goods sold
The invoice	Revenue, tax and the receivable
Collection	The bank, and the customer’s balance closed

So if goods ship in one month and are invoiced in the next, the first month carries cost with no revenue and the second carries revenue with no cost.

That is not a fault; it is a faithful reflection of what happened. The remedy is not to edit the entry but to stop leaving a gap between the two events for no reason — an operational decision rather than a configuration one.

And the condition explained at station four returns here: the shipment’s effect on the general ledger depends on the inventory cost posting setting. Until it is enabled, cost is recorded in the inventory records and does not appear in the trial balance until the invoice is posted.

So when an accountant calls a month’s margin “strange”, start from those two causes: the ship-to-invoice gap, and the cost posting setting. They explain most cases before any other investigation.

The third idea: credit objects by level, not in two states

The number written on the customer card does its work here — but the objection behaviour itself is configured at company level, and it has levels:

Level	What it objects to
None	It never objects
Credit limit	Exceeding the limit only
Overdue balance	An overdue amount existing only
Both	Either of them

Choosing between them is not a technical setting; it is the company’s credit policy written into the system. A consultant who configures this without asking writes a policy on the owner’s behalf.

Read that as a miniature of the consultant’s whole job: the field is technical, and the decision behind it is not.

And the practical difference to know: this is a warning, not a block. It notifies and it is logged, and it does not stop a document by itself — anybody wanting a real block builds it with an approval workflow, which is the subject of station nine.

Returns — two routes, not one

Correction has two routes, and choosing between them is not a matter of taste:

One: a corrective credit memo built from the posted invoice. It fits when the error is in the invoice itself — a wrong price, or a wrong customer — and the goods have not come back.

Two: a sales return order. It fits when the goods physically come back, because it produces a return receipt document that restores stock and then a credit memo that corrects the account.

The common error is issuing a credit memo alone for goods that came back — the customer’s account is corrected and the stock stays short for no reason, until a count finds it and it is cleared by an adjustment nobody can explain.

Application — the step that decides whether the ageing is honest

A receipt not applied to its invoice leaves both of them open on the customer’s ledger.

The balance stays right in total, and the ageing lies in detail: an invoice settled two months ago shows as overdue, and an old receipt shows as unapplied.

Read that sentence twice, because it is the source of most “the report is wrong” complaints on live projects. The report is not wrong; the movements are unapplied — and it comes back in full at station seven.

What you actually do at this station

• Run a full cycle on one order with three postings: a partial shipment, then the remainder, then invoicing the whole.
• Read the item entries after the shipment, then the trial balance, and explain the difference in a sentence.
• Ship in one month and invoice in the next, then read both months’ income statements. You will not forget the lesson afterwards.
• Set the credit warning level twice — credit limit alone, then both — and prove the behaviour differs.
• Run a complete return with both its documents, then run a corrective credit memo, and write when each of them fits.
• Leave a receipt unapplied, read the ageing, then apply it and read again.

The three commonest errors

One: reading quantity on hand as quantity available. Its price is an angry customer rather than a wrong entry, which is why it appears in no financial report.

Two: a credit memo with no return. It corrects half the picture, and leaves the other half to a stock adjustment nobody can account for.

Three: leaving receipts unapplied. It looks harmless — until an ageing report is asked for and a collection decision gets built on it.

What that does to running a trading business is set out in the Dynamics 365 Business Central guide, and the general logic of the cycle — from quotation to collection — is in the order-to-cash cycle.

The acceptance test for this station

1. Explain the difference between on hand and available, and when they diverge.
2. Write what gets recorded at shipment and what at invoice, and the condition that decides whether cost appears in the general ledger.
3. Ship in one month and invoice in the next, and explain the effect on both months’ income statements.
4. Configure two credit warning levels and prove the behaviour differs, and explain why it is an owner’s decision rather than a consultant’s.
5. Explain when to use a return order and when to use a corrective memo, with an example of each.

What comes next

You have run both cycles of money. The next station answers the question deferred twice: at what number is stock valued? — inventory and costing, containing the cost adjustment routine most trainees miss, without which your cost stays a provisional number.