Station 5 of 10
The sales cycle in Oracle NetSuite
What you leave this station with
Tracing the sales cycle through its documents, separating invoicing from revenue recognition, configuring the credit hold logic, and choosing the right correction route.
At station four money went out. Now it comes back.
The structure mirrors what you have seen: an order, then fulfilment, then an invoice, then collection. But it holds three ideas with no direct counterpart on the purchase side, and the first of them separates somebody who understood the system from somebody who memorised its screens.
Where cost is recorded and where revenue is
| The event | What gets recorded |
|---|---|
| The sales order | No entry — a commitment and a reservation |
| The fulfilment | Stock leaving, and cost of goods sold |
| The invoice | Revenue, tax and the receivable |
| The collection | The bank, and the customer’s balance closed |
Cost is measured when the goods leave, and revenue is recorded with the invoice.
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 an entry; it is to stop leaving a gap between the two events for no reason.
The idea that catches so many
Issuing an invoice is not recognising revenue.
An invoice is a collection document: it establishes a receivable and asks for money. Recognising revenue is an accounting decision governed by a standard, not the moment a piece of paper is issued.
They coincide in a simple sale: goods delivered and invoiced on the same day.
They diverge in everything else:
- An annual subscription invoiced once in advance — and the revenue belongs to twelve months.
- A contract with supply, installation and support at one price — and the revenue is allocated across its components.
- A service invoiced up front and delivered in stages — and the revenue follows the delivery rather than the invoicing.
The product handles this with a separate module that is bought — meaning it is a line in the quotation rather than an assumption.
The question asked before signature: does our revenue model need it? Anybody selling subscriptions who answers no is building a permanent monthly close problem.
Memorise the sentence in this form: “the invoice asks for money, and recognition decides when revenue became revenue.”
The credit hold — an objection with logic rather than two states
The number written on the customer record does its work here, but the design question is sharper than “what is the limit”.
| What is decided | The alternatives |
|---|---|
| What goes into the calculation | Balances alone, or orders not yet invoiced with them? |
| When it objects | At the order, at fulfilment, or at both? |
| Who releases the hold | Sales, or finance alone? |
| And is it a block or a warning? | A policy decision, not a configuration one |
The first row is the one overlooked. Anybody calculating balances alone grants a customer already at their limit new orders that are not yet invoiced, and discovers the real exposure after shipping.
The third row is the one that ruins the whole control if it is got wrong. Anybody giving sales the right to release the hold builds a control released by the party with an interest in releasing it.
Read this as a model of the consultant’s job: the field is technical, and the decision behind it is a credit policy owned by the company’s owner rather than the consultant.
Returns — two routes, not one
Correction has two routes, and choosing between them is not a matter of taste:
One: a credit memo built from the invoice. It fits when the error is in the invoice itself — a wrong price, or a wrong quantity — and the goods have not come back.
Two: a full return authorisation. It fits when the goods physically come back, because it produces a receipt that restores stock and then a credit memo that corrects the account.
The common error is 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 item that decides whether the ageing is honest
A collection not applied to its invoice leaves both of them open on the customer’s record.
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.
This is the source of most “the report is wrong” complaints on live projects. The report is not wrong; the movements are unapplied — and it returns at station seven.
What you actually do at this station
- Draw the cycle with its four events and their entries, then correct your prediction from the documentation.
- Write the effect of shipping in one month and invoicing in the next on both months’ income statements, with figures you assume.
- Take three revenue models — a simple sale, an annual subscription, and a bundled contract — and write for each when revenue is recognised.
- Design a complete credit hold logic with the table’s four answers, and write the reason for each answer.
- Write two correction cases — one that suits a credit memo alone and one that needs a return — and show what stays wrong if the choice is inverted.
- Write the effect of leaving a collection unapplied on an ageing report, with an example carrying two dates.
The three commonest errors
One: confusing invoicing with revenue recognition. It passes for a year on simple sales, and detonates at the first subscription contract.
Two: a credit hold calculated on balances alone. It looks like a control, and leaves the real exposure outside the calculation.
Three: a credit memo with no return. It corrects half the picture, and leaves the other half to a stock adjustment nobody can account for.
What this does to running a trading business is set out in the Oracle NetSuite 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
- Write what gets recorded at each of the cycle’s four events.
- Explain the difference between issuing an invoice and recognising revenue, with two examples in which they diverge.
- Present the credit hold logic you designed, and why sales does not release it.
- Explain when a credit memo alone suffices and when a return is required, with an example of each.
- Explain why the balance stays right while the ageing lies.
What comes next
You have run both cycles of money. The next station answers the deferred question: at what number is stock valued? — inventory and costing, containing a method the product offers and the international standards do not accept.