Sales Order vs. Sales Invoice in Business Central — What’s the Difference and When to Use Each
Two of the most commonly used documents in Microsoft Dynamics 365 Business Central are the Sales Order and the Sales Invoice. At first glance they seem interchangeable — both result in a posted invoice and updated financials. But choosing the wrong one for the wrong scenario can cost you traceability, warehouse integration, and operational control.
Here is a clear breakdown of what separates them, and how to decide which to reach for.
The Core Distinction
A Sales Invoice is a single-step document. You create it, fill in the lines, post it, and you are done. It is the accounting document — the thing that creates the Customer Ledger Entry, the G/L postings, and the Item Ledger Entries. It is fast, direct, and purpose-built for straightforward billing.
A Sales Order is a process document. It manages the full sales fulfilment lifecycle: reserving stock, picking and shipping goods, partial deliveries, warehouse operations, and finally invoicing. The posted invoice is the outcome of a Sales Order, not the Sales Order itself.
The simplest way to think about it: a Sales Invoice is what you post; a Sales Order is what you manage.
When to Use a Sales Invoice
A Sales Invoice is the right tool when the transaction is simple and immediate — no warehouse involvement, no partial shipments, no reservations needed. Common scenarios include:
- Billing for services (consulting, support, subscriptions)
- Simple one-line product sales where stock is not tracked
- Invoicing for a transaction that has already physically occurred
- Re-invoicing or pass-through charges
- Correcting or supplementing a previous invoice
When you post a Sales Invoice, Business Central creates:
- A posted Sales Invoice (archived, printable, emailable)
- A Customer Ledger Entry (open item for collection)
- G/L Entries for revenue, VAT, and cost of goods
- Item Ledger Entries (if items with inventory tracking are included)
The Copy Document function is your best friend on the invoice side — use it to base a new invoice on a previous one, a quote, or a blanket order, rather than re-keying lines from scratch.
When to Use a Sales Order
A Sales Order is the right tool whenever the transaction involves physical goods, warehouse operations, or commercial complexity. Key scenarios include:
- Selling stocked items that require picking and shipping
- Partial deliveries — shipping goods in multiple consignments against one order
- Stock reservation — committing inventory to a specific customer before shipment
- Warehouse Management System (WMS) integration — pick lists, bin assignments, warehouse shipments
- Drop shipments — purchasing directly from a vendor to ship to a customer
- Prepayments — collecting a deposit before goods are delivered
- Blanket Order call-offs — releasing quantities against a long-term agreement
A Sales Order separates the shipment from the invoice. You can ship goods multiple times before raising the invoice, or invoice in advance of shipment, giving you full control over the commercial and operational timing.
The Shipment vs. Invoice Split
This is the most important operational concept to understand. On a Sales Order, posting happens in two stages:
1. Post Shipment Records that goods have physically left the warehouse. Creates a Posted Sales Shipment document and Item Ledger Entries. Does not affect the customer’s financial balance — no invoice yet.
2. Post Invoice Creates the financial documents: Posted Sales Invoice, Customer Ledger Entry, G/L Entries. Can be done at the time of shipment, or later, or in bulk via the Batch Post Sales Orders function.
This split is invisible on a Sales Invoice — it ships and invoices in a single posting step. That is fine when no warehouse process is involved, but a problem when goods movement needs to be tracked separately from billing.
Partial Deliveries and Blanket Orders
One of the strongest reasons to use a Sales Order over a Sales Invoice is the ability to handle partial deliveries. On a Sales Order, each line has a Quantity to Ship and a Quantity to Invoice field. You can:
- Ship 50 units now, 50 units next week, and invoice once at the end
- Ship all 100 units but invoice in two instalments
- Leave a line partially open while others are fully fulfilled
A Sales Invoice has none of this — it is all or nothing.
Blanket Sales Orders take this further, allowing you to set up a long-term supply agreement with a customer and release individual Sales Orders against it over time. Each release pulls from the blanket quantity, giving you full visibility of how much has been delivered and how much remains outstanding.
Stock Reservation and Availability
Sales Orders integrate with Business Central’s reservation system. When you create a Sales Order line, you can reserve specific inventory for that customer — preventing it from being allocated to another order. This is critical in environments where stock is tight or lead times are long.
Sales Invoices do not support reservations. Posting a Sales Invoice will consume available stock at the time of posting, but there is no mechanism to ring-fence inventory in advance.
Warehouse Integration
If you are running any level of warehouse management — from basic bin locations through to full WMS with directed put-away and pick — you need Sales Orders. The warehouse documents (Inventory Pick, Warehouse Shipment, Pick Worksheet) are triggered by Sales Orders, not by Sales Invoices.
Posting a Sales Invoice bypasses the warehouse entirely. Depending on your setup, this may be by design (for service lines) or a gap that causes stock discrepancies.
Prepayments
Sales Orders support prepayments natively. You can define a prepayment percentage on the order, post a Prepayment Invoice to collect a deposit, and then post the final invoice when goods ship — with the prepayment automatically deducted. This workflow is entirely unavailable on Sales Invoices.
Feature Comparison at a Glance
| Feature | Sales Invoice | Sales Order |
|---|---|---|
| Single-step posting | Yes | No (ship + invoice) |
| Partial deliveries | No | Yes |
| Stock reservation | No | Yes |
| Warehouse integration | No | Yes |
| Prepayment support | No | Yes |
| Blanket order call-offs | No | Yes |
| Drop shipment support | No | Yes |
| Best for services / simple billing | Yes | No |
| Best for physical goods fulfilment | No | Yes |
| Batch posting | Limited | Yes |
A Common Misconception
A lot of smaller or simpler BC implementations default to Sales Invoices for everything — including product sales — because they are faster to enter. This works until it does not: the moment partial shipments, warehouse picks, or stock reservations are needed, the process breaks down and workarounds accumulate.
Equally, some implementations force every transaction through a Sales Order when a large proportion of their billing is for services or non-stock items. This adds unnecessary process steps and creates a backlog of open orders that should have been invoiced and closed.
The rule of thumb:
- Goods being picked, shipped, or partially delivered? → Sales Order
- Service billing or simple immediate sale? → Sales Invoice
Tips for Implementation
1. Use Sales Orders as the default for product companies If your client sells physical goods, Sales Orders should be the standard document. Lock this in with training and, if needed, page customisation that removes the Sales Invoice from the navigation for warehouse-facing roles.
2. Configure Shipment on Invoice for service companies In Sales & Receivables Setup, the Shipment on Invoice setting controls whether posting a Sales Invoice also creates a Posted Shipment document. For pure service businesses this is often disabled — no shipment document is needed.
3. Set up posting date rules Sales Orders allow you to control the invoice date independently of the shipment date. Make sure your team understands how the Posting Date and Document Date fields interact, particularly for month-end close.
4. Use Combine Shipments If you ship a customer multiple times in a period, use the Combine Shipments function to consolidate all outstanding shipments into a single invoice. Cleaner for the customer, cleaner for your AR.
5. Leverage Batch Posting For high-volume environments, use Batch Post Sales Orders (via the job queue or manually) to post shipments and invoices in bulk at end of day or end of month, rather than posting one by one.
6. Blanket Orders for repeat customers If a customer orders the same items regularly or has a fixed annual contract, set up a Blanket Sales Order. It gives procurement visibility, prevents over-delivery, and makes call-offs fast.
Summary
Sales Orders and Sales Invoices are not interchangeable — they serve fundamentally different purposes. The Sales Invoice is your fast, clean billing document for services and simple transactions. The Sales Order is your operational workhorse for anything involving physical goods, warehousing, or commercial complexity.
Getting this distinction right at implementation time prevents a long list of downstream problems: stock discrepancies, missing shipment documents, inability to handle partial deliveries, and a pile of workaround processes that grow harder to unpick over time.
When in doubt: follow the goods. If something is being picked and shipped, use a Sales Order.
Written for Microsoft Dynamics 365 Business Central consultants and implementers. Have questions about configuring your sales workflow in Business Central? Get in touch with NAV SEAL.
#dynamics365 #msdyn365bc #sales
