The purchase cycle in Oracle NetSuite

The foundation is built from station three. Now money moves.

The structure: three documents, three events

The cycle here is three steps, each one an independent document with a life of its own:

The document	What it means	Its accounting effect
The purchase order	A commitment, not an entry	Nothing in the books
The item receipt	The goods arrived	Stock debited, the interim account credited
The vendor bill	The liability is established	The interim account debited, the vendor credited
The payment	Money left	The vendor debited, the bank credited

The first row is the first thing to absorb: a purchase order produces no entry.

It is a contractual commitment read in commitment reports, not a movement in the trial balance. Anybody reading their expenses from purchase orders is reading an intention rather than a fact.

The interim account — the item that explains half the questions

Between the receipt and the bill lives an interim account carrying the value of what was received and not yet invoiced.

That is not a technical detail; it is the account that makes your balance sheet honest at month end.

A company that receives on the 28th of the month and whose vendor invoice arrives on the 5th of the next owns goods against which no liability has yet been recorded — and the interim account is what establishes both sides together.

The working rule known by anybody who has worked: this account’s balance must be reviewed every month.

What its balance means	The diagnosis
A small moving balance	Normal — an ordinary timing gap
A large old balance	Vendor invoices that never arrived or were never recorded
A negative balance	Invoices booked before their receipt

Most implementation projects overlook reviewing it for a year, and then find numbers in it whose origin nobody knows.

The three-way match — who decides that a bill gets paid

Three documents are compared before payment: what you ordered, what you received, and what you were invoiced for.

The differences between them are of three kinds, and each carries a different meaning:

A quantity difference — you received less than you were invoiced for. That is a dispute with the vendor rather than an entry error.

A price difference — you were invoiced at a price other than the one agreed on the order. This is the most dangerous of the three because it passes without anybody noticing: the quantity is right and the goods are there.

An item difference — something other than what was ordered arrived. The clearest and the rarest.

The design decision raised on every project: within what tolerance are differences accepted automatically?

Anybody setting it to zero stops every bill with a penny’s difference and drowns the accounts team. Anybody widening it pays a full year of price differences without ever asking.

The right answer is a number written into a policy, not a setting left at its default.

Landed cost — where the real unit price is made

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

The product handles them with a separate concept assigned to the receipt and allocated across its lines — by quantity, by weight, by value, or manually.

Choosing the allocation basis is not a detail: a shipment holding a heavy cheap item and a light expensive one, allocated by weight, loads the cheap one; allocated by value, it loads the expensive one. The two numbers differ, and both are “right” on their own basis — and the basis is chosen deliberately.

Anybody treating freight as an expense shows stock cheaper than it is and a margin higher than it is. It is the most dangerous class of costing error because it produces reasonable-looking numbers that survive for years.

Purchasing inside a group

Here is where this product’s distinction appears: a purchase between two entities in the same group is not an external purchase.

It is a sale for one entity and a purchase for the other, and a profit appearing in the seller’s books — and it must be eliminated when the group is read consolidated, or you sold to yourself and booked a profit.

This is the place the system gets bought for, and the detail is at station seven.

Memorise the rule now: every transaction inside the group has two faces, and both faces must be eliminated together on consolidation.

What you actually do at this station

• Draw the cycle with its four documents, and under each document the expected entry, then correct your prediction from the documentation.
• Write three cases for the interim account’s balance and diagnose each in a sentence.
• Write a price-difference scenario: an order at a hundred and a bill at a hundred and ten, and write what should happen and who decides.
• Propose an acceptance tolerance as a number for an imagined company, and write why that figure and not another.
• Allocate a freight charge across two items by weight once and by value once, and calculate the unit price in both cases and compare them.
• Write an intercompany sale between two entities, and what gets eliminated on consolidation.

The three commonest errors

One: reading expense from purchase orders. An order is a commitment rather than an entry, and the resulting figure is always higher than the truth.

Two: neglecting the interim account. It looks harmless month after month, and then an old balance with no owner is found in it.

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 Oracle NetSuite guide, and the general logic of the cycle — with no particular system — is in the purchase cycle.

The acceptance test for this station

1. Name the three documents and each one’s effect in the books, and which of them has none.
2. Explain the interim account and why it is reviewed monthly, and what a large old balance in it means.
3. Name the three kinds of matching difference, and which one passes unnoticed.
4. Calculate the effect of a freight charge on unit price under two different allocation bases.
5. Explain why an intercompany sale is not read as revenue in the consolidated statements.

What comes next

Money went out. The next station brings it in: the sales cycle — containing the difference between issuing an invoice and recognising revenue, a difference with no counterpart in the purchase cycle that a great many people fall into.