The purchase cycle in Dynamics 365 Business Central

The matrix is configured from the previous station. Now money moves.

This station holds two peculiarities that surprise everybody arriving from another system, and the second of them produces a question asked on every project.

The first peculiarity: one document, two quantities

In many systems the purchase order is copied into a receipt document, then copied into an invoice. Here that does not happen.

The purchase order stays one document, and each line carries two independent quantities: a quantity to receive, and a quantity to invoice.

Posting happens in three shapes: receive only, invoice only, or both together. Every posting produces its own posted document — a posted receipt, or a posted invoice — and the original order stays alive until both quantities are consumed.

Case	What is posted	What stays open on the order
Receive 100, invoice 0	A posted receipt	The whole invoicing
Receive 60, invoice 60	A receipt and an invoice	40 to receive and 40 to invoice
Receive 0, invoice 100	A prepaid invoice	The whole receipt
Receive 100, invoice 100	A receipt and an invoice	Nothing — it closes

The third row is the one worth stopping on: goods that never arrived can be invoiced. That is commercially correct in some cases, and catastrophic if it happens by accident — because it establishes a liability against stock that does not exist.

The rule: set both quantities deliberately at every posting, and never accept what the screen offers by default. Most errors on this cycle are an error in a number nobody looked at.

The second peculiarity: a receipt may never reach the general ledger

Here is the idea to be understood rather than memorised.

Posting a receipt always produces item ledger entries and value entries — meaning stock rises in quantity and value in the inventory records immediately.

But its effect in the general ledger depends on a setting. Posting expected cost to the general ledger — establishing goods received but not invoiced in an interim account — is not enabled by default.

The result that shocks anybody arriving from another system: you receive a hundred thousand of goods, and the trial balance does not move.

Level	Moves at receipt?	Moves at invoice?
Item and value entries	Always yes	Yes — by adjustment
The general ledger	Only if the setting is on	Always yes

Its effect is practical and sharp: the inventory report and the trial balance will not agree for as long as there are received-not-invoiced goods and the setting is off.

The question asked on every project: do we enable expected cost?

The right answer at most companies is yes — because a company that receives at the end of the month and is invoiced at the start of the next wants its balance sheet to reflect what it actually owns. A company that does not enable it accepts a difference whose cause is known, which is acceptable provided it is a decision rather than an oversight.

Write that question on your sheet. It is one of the few questions a consultant asks and a user does not.

The entries across the cycle

Event	Debit	Credit
Receipt — with the setting on	Stock	The expected cost account
The invoice	The expected cost account + tax	The vendor
Payment	The vendor	The bank

With the setting off the first row disappears, and the invoice entry becomes: stock and tax debited, the vendor credited.

Read both tables together once, because between them lies the whole difference in reading the balance sheet of a month that has not been closed.

Item charges — where the real cost is built

Freight, customs and insurance are not an expense; they are part of the cost of the goods.

This product handles them with a dedicated concept — an item charge — assigned to specific receipt lines and allocated across them by a rule: by quantity, by value, or manually.

The essential idea: the charge is assigned to the receipt, not to the order. It adjusts the value of existing value entries, which is why it still works when the freight invoice arrives two weeks later.

Anyone treating freight as an expense shows stock cheaper than it is and profit higher than it is — the most dangerous class of costing error, because it produces numbers that look reasonable.

A posted document is not edited

What is posted has become a fact in the ledgers.

Correction runs through a credit memo that reverses the effect, then a correct posting. The product provides a ready function that builds the reversing memo from the posted invoice — cleaner than building it by hand, because it links the memo to the invoice and applies them to each other.

Application is the step that gets missed. An unapplied memo corrects the balance and leaves the vendor statement showing two open documents — which comes back at station seven.

What you actually do at this station

• Run a full cycle on one order with three postings: a partial receipt, then the remainder, then invoicing the whole.
• After the first receipt, open the item and value entries, then open the trial balance. The difference between them is the lesson.
• Enable expected cost, run the cycle again, and compare. Do not move on before you can explain the difference in a sentence.
• Assign a freight charge to a receipt, and calculate the new unit cost by hand before looking at the screen.
• Create a credit memo from a posted invoice, and verify they are applied to each other on the vendor statement.

The three commonest errors

One: invoicing without receipt by accident. It establishes a liability against stock that does not exist, and the system does not object because it is commercially legitimate behaviour.

Two: assuming a receipt moves the general ledger. A promise of a matching balance sheet gets built on it, and the difference is discovered at the first close.

Three: treating freight as an expense. Its effect is in the margin rather than the trial balance, which is why it survives for years undiscovered.

What document discipline does to project cost is set out in the Dynamics 365 Business Central guide, and the general logic of the cycle — with no particular system — is in the purchase cycle.

The acceptance test for this station

1. Explain the two quantities on a purchase order line, and what happens in each combination of them.
2. Explain what moves at receipt in the inventory records and in the general ledger, and the condition that separates them.
3. Run the cycle twice with the setting off and then on, and document the difference.
4. Assign an item charge and calculate its effect on unit cost by hand.
5. Correct a posted invoice the right way, and prove the application.

What comes next

Money went out. The next station brings it in: the sales cycle — containing the same two quantities in another guise, the credit limit that objects before posting, and cost of goods sold posted with the shipment rather than with the invoice.