Quotes and sales orders
The cycle starts with a quote or an order, with pricing, terms, and delivery details. Where a separate CRM manages opportunities, decide at which point the order is created in NetSuite and how the two systems exchange data. Use price levels, customer-specific pricing, and discount approval rules to keep pricing consistent. A sales order should carry everything fulfillment and billing need, so nobody has to ask the salesperson later.
- Pricing rules and discount approvals defined once.
- Customer credit checked before the order is released.
- Tax, shipping, and payment terms set at order entry.
Credit management and order approval
Releasing orders to customers who are past due or over their limit creates avoidable losses. Set credit limits and use holds that stop orders for review, with a clear path for exceptions. The rules should be strict enough to protect cash and flexible enough to avoid frustrating good customers. Give sales teams visibility of the customer's balance so conversations about holds are informed.
Fulfillment, shipping and inventory
For physical goods, the order moves to picking, packing, and shipping, with inventory reduced on fulfillment. Decide whether to bill on shipment, on delivery, or in advance, since this affects when revenue and receivables are recorded. For services, fulfillment may be time or milestones, which belongs to project billing. Integration with warehouse or shipping systems should update status and tracking automatically so customer service can answer questions.
NetSuite inventory management fundamentals →Invoicing and revenue recognition
Invoices should generate from fulfilled orders or contract schedules without manual rekeying. Where revenue must be recognized over time or according to performance obligations, set up recognition rules so billing and revenue can differ correctly. Your accountants should confirm the treatment for your contracts. Invoice presentation matters to customers, so include purchase order numbers, references, and the information their payables teams require.
Revenue recognition setup guide →Collections and cash application
Prompt collections depend on timely reminders and clear ownership. Use dunning schedules that escalate in tone and contact, and give collectors aging views by customer with notes of promises and disputes. Cash application matches payments to invoices, which is simple for single payments and demanding for remittances covering many invoices. Automating matching and handling short payments systematically keeps receivables accurate.
Disputes, credits and returns
Disputes slow payment. Record the reason, owner, and expected resolution date, and report on dispute causes so the root problems in pricing, delivery, or quality can be fixed. Returns and credit memos should follow a controlled approval path, with inventory and revenue effects handled correctly. Reviewing credit-note reasons monthly often reveals recurring errors that cost more than the credits themselves.
Revenue and billing solutions →Making it stick
Review the whole cycle as one flow rather than as separate departmental tasks. Sales, warehouse, billing, and collections each optimize their own step, yet the customer experiences a single process. A monthly review of cycle time from order to cash, with the biggest delays traced to their causes, usually finds a handful of fixable problems such as missing purchase order numbers or unclear delivery terms. Assign one executive owner for the end-to-end result so improvements are not lost between teams.
Decisions to settle before configuration starts
- Order entry point. Define where orders originate and how they reach NetSuite.
- Billing trigger. Choose shipment, delivery, schedule, or milestone billing by product type.
- Credit policy. Set limits, holds, and exception authority.
- Collections model. Assign ownership and dunning cadence.
A realistic first 90 days
- Days 1 to 30. Map the current cycle, find the delays and errors, and define the target process.
- Days 31 to 60. Configure pricing, credit holds, fulfillment, and invoicing, and test with real orders.
- Days 61 to 90. Go live by customer group, set up dunning and cash application, and track cycle-time and days sales outstanding.
Pitfalls to avoid
- Manual invoicing. Retyping creates errors and delays. Generate from orders.
- Weak credit control. Late holds lead to bad debt. Apply them at order release.
- Ignoring disputes. Unresolved disputes inflate aging. Track and fix causes.
- No cash application discipline. Unapplied cash distorts receivables and collections.
