An ERPNext sales workflow needs to distinguish a customer commitment from the physical movement of goods, a legal or commercial invoice and a payment. These are related but separate events. When a company tries to represent all four with one status field, partial shipments and early payments become difficult to reconcile. The standard document chain offers a clearer basis for sales, warehouse and accounting teams.
Five core documents in the sales process
A Quotation records an offer, including items, rates, terms and validity. A Sales Order captures the accepted commitment. A Delivery Note records what the warehouse actually dispatches. A Sales Invoice represents the amount billed under the agreed policy, while a Payment Entry records money received and its allocation. This sequence is illustrative; different businesses may invoice before or after delivery.
Each document has its own lifecycle, validation and accounting effects. A submitted Sales Order is not automatically proof of revenue recognition or a completed delivery. Financial and inventory impacts depend on document type, configuration and submitted transactions.
What happens when only part of an order can ship
Suppose a customer orders ten units, but only four are available today. The warehouse can prepare a partial Delivery Note for four units while the Sales Order retains the outstanding quantity. The commercial team needs to understand how the remaining six will be fulfilled, cancelled or backordered.
Do not change the original order quantity to four merely to make the screen appear complete. Preserving the difference between ordered, delivered and outstanding quantities is essential for customer communication and stock planning.
Avoid duplicate stock movements
In a standard stock-item flow, a Delivery Note can record the outgoing stock movement. Certain invoicing configurations can also update stock from a Sales Invoice. Teams must agree which document is authoritative for that movement so the same dispatch is not posted twice.
During testing, inspect the Stock Ledger after each relevant document is submitted. A workflow may look correct from the sales page while producing an incorrect warehouse balance if two integrations both trigger stock-affecting documents.
Accepting payment before an invoice
Some businesses receive customer deposits or advance payments. ERPNext Payment Entries and allocation processes can support this scenario when configured correctly. The team must define whether the advance is associated with a Sales Order, how it is reconciled after invoicing and how refunds or cancellations are handled.
Receiving a marketplace payment event must not cause an additional Payment Entry every time a webhook is retried. Use a unique transaction reference, validation and idempotency so the resulting accounting record is created once.
Why Sales Order, invoice and receivable totals can differ
A Sales Order describes what a customer agreed to purchase, including items not yet delivered. An invoice describes amounts billed. Accounts receivable reflects posted invoices and payments under the applicable accounting rules. Different amounts are not automatically a defect, but they must be explainable.
Compare the correct documents using a consistent date range and status. Returns, discounts, credit notes, partial invoicing and advances can explain differences. Start with linked records rather than forcing one total to match another.
Decisions to make before automation
Agree on payment confirmation rules, whether paid orders are submitted automatically, how partial fulfilment is tracked, when invoicing occurs and who can cancel submitted records. Document what should happen when marketplace status is delayed or when the warehouse reports missing goods.
Run end-to-end UAT with normal role permissions and inspect the General Ledger and Stock Ledger. Integration scripts should use standard ERPNext documents and protect against duplicate submissions rather than bypassing validation.
Where to go next
For deeper implementation planning, review ERPNext implementation services, inventory workflows and business integration options. The desired outcome is a document trail in which each team can identify exactly what happened, when and why.
Prioritise clarity in document ownership over adding new statuses. A few consistently defined stages are more useful than dozens of labels that do not align with inventory and accounting.
