Order to cash: from opportunity to collected payment
Win the deal, quote, order, deliver, invoice, receive and apply payment, and chase overdue customers.
On this page
Process at a glance
- Qualify and winSales rep / managerWon deal; draft sales order created.
- Quote and orderSales repApproved quotation and sales order.
- DeliverDispatcher / driverStock issued; proof of delivery captured.
- InvoiceBillingPosted sales invoice; customer owes the amount.
- Receive paymentAccounts receivableReceipt posted and applied to invoices.
- Collect overdueCredit controllerReminders sent; credit hold where needed.
#Purpose and scope
This chapter covers selling: CRM leads and opportunities, quotations, orders, delivery and shipments (including the driver app), invoicing, receipts and cash application, collections, returns and point of sale.
#Two kinds of sales order
BSuit has an accounting sales-order voucher and a separate operational sales order. They are not linked; know which one your team uses.
| Type | Created by | Used for |
|---|---|---|
| Sales order voucher (Sales transactions › Orders) | Sales staff, or conversion from a quotation | The voucher chain Estimate → Quotation → Order → Invoice |
| Operational sales order (Sales orders) | Automatically, from a won CRM deal or a web-store checkout | Confirming and delivering (delivery notes are raised from it) |
#Before you start
- Customers: a CRM account with a customer ledger (needed to win a deal), and a customer ledger for invoicing.
- Products, price lists (reference only — prices are not applied automatically), tax codes, warehouses.
- Record types EST, SQ, SO, SI, SR, CASH-REC, BANK-REC, CHQ-REC and CN with approval workflows (seeded for SI, SO, SQ, SR, CN and receipts).
- Sales posting configuration (Posting config) for web and POS sales.
- Dunning levels if you chase overdue customers.
#1. Lead, opportunity and win
- Capture leads in Leads; Convert a qualified lead — BSuit creates the account and an opportunity.
- Work the opportunity in Opportunities or the pipeline board; add product lines and create quote versions for the customer.
- Choose Win. BSuit checks the amount is positive and, when the opportunity has product lines, that the account has a customer ledger; with the JV-CRM-WIN workflow configured it then waits for approval.
- When the win is approved, BSuit marks the opportunity won and creates a draft operational sales order from the product lines. Nothing is posted to the ledger: revenue is recorded when the sales invoice is posted.
#2. Quotation, order and invoice vouchers
- Create the document in Sales transactions (Quotations, Orders or Invoices).
- Choose the customer, add product lines; save as draft.
- Submit for approval; approvers act in their inbox.
- Post when approved.
| Type | Code | Moves stock when posted | Needs approval |
|---|---|---|---|
| Estimate | EST | No | Yes |
| Sales quotation | SQ | No | Yes |
| Sales order | SO | No | Yes |
| Sales invoice | SI | Yes (stock out) | Yes |
| Sales return | SR | No | Yes |
#3. Confirm and deliver
- Confirm the operational order in Sales orders (from draft).
- Raise a delivery note from the confirmed order in Delivery notes; generate a pick list and assign a vehicle.
- Dispatch: stock is issued from the warehouse and reservations are consumed.
- Deliver, capturing proof of delivery.
- On a dispatched or delivered note choose Create sales invoice: BSuit drafts the invoice priced from the sales order, with each line linked to the note.
#4. Shipments and the driver app
- Plan shipments in Shipments, hand them to drivers in Handoff.
- The driver, in the BSuit Smart app, starts the trip, marks Arrived, then Delivered (recipient name, signature, delivery code and photo as your shipment settings require), or Couldn’t deliver with a reason, or Return to warehouse. It works offline and syncs later.
- Customers are notified of shipment status by email and in-app.
| Code | Meaning |
|---|---|
| photo_required | A delivery photo is required by the shipment settings. |
| signature_name_required | The recipient’s name must be entered as signature. |
| otp_required / otp_invalid / otp_locked | The customer’s delivery code is required, wrong, or locked after too many attempts. |
#5. Receive and apply payment
- Record the payment as a Bank receipt, Cash receipt or Cheque receipt.
- Enter the customer (or income) lines as credits. The bank or cash side is generated automatically and hidden.
- Open Bill-wise and select the invoices this receipt settles; BSuit proposes open posted invoices for the customer.
- Submit, approve and post.
| Message | Meaning |
|---|---|
| “Select at least one bill to apply this receipt against.” | Choose invoices in Bill-wise. |
| “Allocations (x) exceed the receipt amount (y).” | Reduce the allocations. |
| “Allocation (x) exceeds the bill's outstanding amount (y).” | The invoice is already partly paid. |
| “…its line items must be entered as credits.” | On a receipt, enter customer/income lines as credits. |
| “Cheque … is tracked in the Post-Dated Cheque register…” | Use the PDC register for post-dated cheques. |
#6. Collections
- Review AR aging (buckets current, 1–30, 31–60, 61–90, over 90, by transaction date) and Statement of account.
- Set up dunning levels, then run Dunning. BSuit ages open invoices by due date, logs a collection activity, emails the level’s template to the customer and puts the customer on credit hold where the level says so (lifting it when paid).
- Track calls and promises in Collections.
#7. Returns and credit notes
- Web-store returns: Returns — approve, receive (stock goes back to a warehouse and a credit journal is posted), then refund (store credit gift card or refund pending to the original payment).
- Other credits: raise a Credit note against the customer.
#8. Point of sale
Terminal sales sync to POS transactions and post automatically using the sales posting configuration (debit cash/bank/customer, credit sales and tax). If the configuration is missing the sale stays in draft marked “failed — no config”. POS postings do not go through approval or the period and budget checks.
About this guide
- Status
- Partially reviewed
- Application
- BSuit ERP
- Audience
- Sales reps, sales managers, dispatchers, drivers, accounts receivable and credit controllers
- Owner
- BSuit documentation team
- Reviewer
- Editorial review pending
- Last verified
- 2026-09-25
- Checked against
- cb3691bbf
- Seen on a running system
- Not yet
- Help version
- 2026.0.0-preview
- Guide ID
erp:article/guide/order-to-cash
Known limits: Written from a line-by-line read of the implementation (every statement traced to source). Not yet walked through end to end by a trainer on a running system.