The purchase cycle in SAP Business One

The master data is ready from the previous station. This is the first station where money moves.

It is also the best station on the whole path for understanding how this product thinks, because the purchase cycle exposes what most teaching material hides: a document is not a data-entry screen, it is an accounting event with a time.

The documents and their effect on the ledgers

The first rule: not every document produces an entry. Anybody who does not know which ones do and which do not reads a trial balance without understanding where the numbers came from.

Document	What it represents	Produces an entry?	Moves stock?
Purchase request	An internal intention	No	No
Purchase order	A commercial commitment to the vendor	No	No
Goods receipt PO	The goods actually arrived	Yes	Yes
A/P invoice	The financial claim arrived	Yes	No — if a receipt preceded it
Outgoing payment	The money left	Yes	No

Read the first two rows together: a purchase order is a commitment, not an expense. Anyone who believes raising a purchase order charges the period with the cost is reading an income statement that does not exist.

The intermediate account — the clearest window into the product

Here is the concept that is worth an hour on its own.

The question: the goods arrived on the 28th and the invoice arrived on the 4th of the following month. Which period carries the cost?

The answer: the period of receipt, because the stock entered in it. But the obligation to the vendor is not yet established — there is no invoice, no final amount and no claim number.

So what does the product do with that gap?

It uses an intermediate account: at receipt it debits stock — because stock arrived — and credits the intermediate account instead of crediting the vendor. When the invoice arrives it debits the intermediate account — closing it — and credits the vendor.

Event	Debit	Credit
Goods receipt	Stock	The intermediate account
A/P invoice	The intermediate account	The vendor
Paying the vendor	The vendor	The bank

The result to memorise: the balance of the intermediate account at any moment is goods received and not yet invoiced.

That makes it a diagnostic tool rather than merely an accounting head. An old balance sitting in it means one of three things: an invoice that never arrived, an invoice that arrived and was posted independently of the receipt instead of being built on it, or a receipt posted for goods that never came.

The second is the commonest, and it is the price of working without document discipline: every invoice keyed from scratch leaves an intermediate balance behind it that never clears.

Documents are built on one another, not retyped

The second rule in this product, and the one separating a trained user from everyone else: every document is copied from its predecessor.

The purchase order is built from the request, the receipt is built from the order, and the invoice is built from the receipt. This is not a typing shortcut; it is what creates the traceability chain that lets any invoice be traced back to the receipt that built it, and to the order before that.

Anyone who keys each document independently loses the entire chain, and discovers it on audit day rather than on entry day.

A posted document is not edited

The third rule, and the source of most beginners’ frustration: a document that has touched the ledgers is not reopened to be corrected.

A wrong invoice is reversed by a counter-document — a credit note — and then the correct invoice is posted. The fields left editable after posting are few and deliberately limited, and most of them do not touch the entry.

Read that as a feature, not a restriction. A ledger that can be edited retrospectively is not a ledger, and a system permitting a posted entry to be changed cannot be audited.

Which is exactly why training on an environment with nothing to lose matters: so you make and correct the mistake the right way ten times before you do it in front of a client’s accountant.

Three mechanisms understood here and nowhere else

One: partial receipt. An order for a hundred units of which sixty arrive. The order stays open for forty, and closes only on receiving them or on a justified manual close. Old open orders are the commonest source of inflated commitments in a purchasing report.

Two: landed costs. Freight, customs and insurance are part of the cost of the goods rather than a separate expense, and they are allocated across the items by a rule — by quantity, by weight, or by value. Treating them as an expense shows stock cheaper than it is and profit higher than it is, which is the most dangerous class of costing error because it produces numbers that look reasonable.

Three: a return to the vendor. It reverses the receipt’s effect on stock, and the credit note reverses the invoice’s effect on the account. Two documents, not one, for the same reason that separated the receipt from the invoice in the first place.

What you actually do at this station

• Run the full cycle on one vendor: request, order, receipt, invoice, payment — with every document built on its predecessor.
• After every step, open the resulting entry and read it before moving on. That is the station; the rest is execution.
• Run a second cycle with a partial receipt, and verify the remaining quantity on the order.
• Run a third cycle with allocated freight, calculate the new unit cost by hand and compare it with what the system shows. If they differ, the error is in the allocation rule, not in the system.
• Open the intermediate account report after a receipt with no invoice, read the balance, then post the invoice and confirm it cleared.

Document the cycle’s five entries on one sheet. That sheet is the fastest way to convince an accountant that you understand what you are doing.

The three commonest errors

One: posting the invoice independently of the receipt. It works, it produces numbers that look right, and it leaves an intermediate account that never clears — then it surfaces at the first year-end close.

Two: treating landed costs as an expense. Explained above, and its effect shows up in the margin rather than in the trial balance — which is why it survives for years.

Three: leaving purchase orders open and never closing them. Every open order is a declared commitment, and anyone who does not clean them periodically builds a purchasing report nobody reads twice.

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

The acceptance test for this station

1. Write from memory which of the five documents produce an entry and which do not.
2. Explain the intermediate account in two sentences, and say what an old balance in it means.
3. Run a full cycle, read its five entries, and document them on a sheet.
4. Run a partial receipt and prove the order stayed open for the difference.
5. Allocate a freight cost and calculate its effect on unit cost by hand before you look at the screen.

What comes next

Money went out. The next station brings it in: the sales cycle — from quotation to collecting from the customer — containing where revenue is recognised, and the cost of goods sold that is posted with the shipment rather than with the invoice, which is the difference that turns a whole month’s income statement upside down.