Sales Order vs Delivery Order vs Invoice: AutoCount Stock Timing
One customer order can appear in three different places at three different times.
Sales may see the order today.
Warehouse may deliver the goods tomorrow.
Accounts may invoice next week.
If the team does not understand the document timing, the reports can look like they disagree even when each document is doing its own job.
This is why Sales Order, Delivery Order, Invoice and stock timing matter.
The question is not only "which report is correct?"
The better question is:
Which document step has already happened?
One Order Across Two Months
Imagine this simple flow.
- May 28: customer confirms an order for 100 units.
- May 28: Sales Order is created.
- May 31: warehouse sends 80 units.
- May 31: Delivery Order is saved or posted for the 80 units.
- June 2: Invoice is created for the delivered quantity.
From a sales demand view, the company may say the customer ordered 100 units in May.
From a stock movement view, 80 units left the warehouse on May 31.
From an accounting billing view, the invoice appears in June.
Those are different answers because they answer different questions.
The issue becomes serious when the business treats them as the same thing.
The Document Effect Is Different
In an AutoCount-style document flow, each document has a different role.
| Document | Main meaning | Typical stock effect | Typical accounting effect |
|---|---|---|---|
| Sales Order | customer order or demand | no inventory movement | no G/L posting |
| Delivery Order | goods sent or stock movement | can reduce stock when saved or posted with stock posting | no G/L posting |
| Invoice | billing and accounts record | depends on document path | posts to A/R and related G/L |
This table is simplified, but it gives the core idea.
Sales Order does not mean stock has moved.
Delivery Order does not mean the customer has been billed.
Invoice does not always mean stock is reduced at that moment, because it depends on whether the invoice is direct or transferred from another document.
That is why the document path matters.
Direct Invoice And Invoice From DO Are Not The Same
This is where many teams get confused.
An Invoice created directly, or transferred from Sales Order or Quotation, may reduce stock because the invoice is the document that completes the stock and billing action.
But an Invoice transferred from Delivery Order should not reduce stock again.
Why?
Because the Delivery Order already handled the stock movement.
The Invoice after DO is mainly the billing and accounting step.
If the team does not follow the document path consistently, the business can create confusion:
- one order is invoiced direct;
- another order uses Sales Order to Delivery Order to Invoice;
- a delivered order is invoiced again without proper transfer;
- partial delivery is billed with unclear quantity;
- stock leaves in May but billing happens in June.
The reports then look messy because the process is messy.
The Timing Problem Is Usually A Rule Problem
AutoCount can support the documents.
But the company still needs rules.
For example:
- When should the team create Sales Order?
- When should warehouse create or post Delivery Order?
- Should the invoice be direct or transferred from DO?
- What happens when delivery is partial?
- Should partial delivery be billed now or held?
- What report should owner use for demand, fulfilment and accounting?
- Which date should management use for each view?
Without those rules, staff will choose different paths based on habit.
One person invoices direct because it is faster.
Another person creates DO first because warehouse needs stock movement.
Another person waits for signed delivery confirmation.
Each decision may make sense alone.
Together, they create inconsistent reporting.
A Partial Delivery Example
The customer orders 100 units.
Warehouse only sends 60 units today.
The team has a few possible workflows:
- create Sales Order for 100, DO for 60, then Invoice for 60;
- create Sales Order for 100 and wait before invoicing;
- create direct Invoice for 60 if the business does not use DO;
- hold billing until the remaining 40 units are ready;
- bill 60 now and keep 40 as outstanding.
None of these is automatically wrong.
But the business needs one agreed rule.
If different staff handle partial delivery differently, the owner may see:
- sales demand of 100 units;
- stock movement of 60 units;
- invoice of 60 units;
- remaining order of 40 units;
- customer expectation for 100 units.
That is not just a reporting issue.
It is a document timing rule.
If your main problem is broader report disagreement across departments, read why sales, stock and accounting numbers disagree.
Delivered Not Invoiced Is A Separate View
One practical view many companies need is delivered but not invoiced.
This helps the team find goods that already left the warehouse but have not yet been billed.
But this view only works when Delivery Order and Invoice are connected properly.
If delivery documents are missing, not transferred, or handled in WhatsApp, accounts may not know what is ready to bill.
If this is your main problem, read why delivery orders get lost between dispatch and billing.
This article is about the wider timing logic: Sales Order, Delivery Order, Invoice and stock each answer a different question.
What Each Report Should Be Used For
The business should label reports by purpose.
| Report view | What it answers | Common mistake |
|---|---|---|
| Sales Order view | what customers ordered or demand | treating it as delivered sales |
| Delivery Order view | what stock moved or was fulfilled | treating it as revenue |
| Invoice view | what was billed and posted to accounts | treating it as full operational status |
| Stock movement view | what changed stock balance | ignoring whether customer was billed |
| Outstanding view | what is still open | mixing ordered, delivered and billed quantities |
When the report name is unclear, users argue about numbers.
When the report purpose is clear, users can see which stage they are looking at.
Why Dashboards Need The Same Rule
A dashboard cannot fix unclear document timing.
If the dashboard pulls Sales Order as sales, the number may show demand.
If it pulls Invoice as sales, the number may show billing.
If it pulls Delivery Order as fulfilment, the number may show stock movement.
All three can be useful.
But they should not share the same label.
Before building a dashboard, define:
- ordered quantity;
- delivered quantity;
- invoiced quantity;
- outstanding quantity;
- delivered not invoiced;
- invoiced not delivered, if your flow allows it;
- partial delivery rule;
- date rule for each view.
This is why fixing data before dashboard often starts with document timing.
If the business needs live reporting after the rules are clear, business dashboards and BI should use those same document definitions.
Where AutoCount Integration Can Go Wrong
If another system sends records into AutoCount, timing becomes even more important. This is where AutoCount integration should follow the document path, not just move fields.
The integration should know whether it is sending:
- a confirmed Sales Order;
- a Delivery Order;
- an Invoice;
- an update to an existing document;
- a partial fulfilment;
- an exception that should not sync yet.
If the source system sends the wrong stage, AutoCount may receive a record that looks valid but means the wrong thing.
That is why sales order to AutoCount and delivery to AutoCount billing should be designed around document timing, not just data transfer.
FAQ
Does AutoCount Sales Order reduce stock?
Sales Order is normally an order or demand document. It does not create inventory movement or G/L posting by itself.
Does AutoCount Delivery Order post to G/L?
Delivery Order can affect inventory movement when saved or posted with stock posting, but it does not post to G/L by itself.
Does an AutoCount Invoice reduce stock after DO transfer?
An Invoice transferred from Delivery Order should not reduce stock again because the Delivery Order already handled the stock movement. A direct Invoice, or an Invoice transferred from Sales Order or Quotation, may reduce stock depending on the flow and setup.
Why does stock reduce before invoice?
This can happen when the Delivery Order handles stock movement before the Invoice is created. The stock view and accounting billing view are then looking at different document stages.
What is delivered not invoiced?
Delivered not invoiced means goods have been delivered or stock has moved, but the invoice has not yet been created. It is useful for finding billing gaps.
What To Do Next
Pick one recent order that confused the team.
Trace it through:
- Sales Order.
- Delivery Order.
- Invoice.
- Stock movement.
- Report date.
- Outstanding quantity.
Then ask whether the team followed the intended document path.
If they did not, fix the workflow rule before building a dashboard or integration.
Result Marketing helps SMEs map this document timing so AutoCount, warehouse and accounts can work from the same flow.