The order still shows a quantity outstanding after I invoiced it all
You invoiced the order in full. The KO For tab, or the order listing, still shows a quantity to come — five ordered, three invoiced, and it says five outstanding.
The knock-on matters more than the report. Available stock reads this number. Available is stock on hand, minus the un-invoiced balance of open orders, minus reservations. An order line whose stored balance never came down is quietly refusing goods that are sitting on your shelf — which is what the counter reports as “item not found even though got stock”.
The 30-second check
1. Which document are you looking at it from? BigLedger keeps one balance per order line per downstream document type. The sales invoice reads its own row. The delivery note reads a different one. So the delivery note will still offer you the full 40 after the invoice has already taken 22, and that is correct — the goods have not gone out yet.
If the “outstanding” you are worried about is on a different document type from the one you knocked off, you are done. Nothing is wrong.
2. Has it been seconds rather than minutes? Writing that row is a background job, not part of the Finalise you just pressed. A balance missing or stale in the seconds after FINAL is usually a balance that has not arrived. Wait, refresh, look again.
3. Does your company have a Knock Off Configuration row for that pair of document types? If not, no row was ever created — see below.
The three ordinary causes
No row was ever created. The processor writes nothing unless your company holds an enabled Knock Off Configuration row for that source-to-target pair. Without it the order finalises normally, the invoice simply cannot find it, and the outstanding quantity never decrements because there is nothing to decrement. Across the fleet, 50 of the 90 live tenants hold any knock-off configuration at all.
The row is for the other document type. As above — the invoice and the delivery note each keep their own.
The line was removed from the order after the row existed. If a line was deleted from a draft that had previously been FINAL, the row for it can be left behind. The order looks right and the outstanding quantity is high by the deleted line’s quantity.
How the number is kept, and why that matters
When a sales order reaches FINAL, a job processor writes one row per order line per downstream document type, holding the quantity still to come. That row is rewritten synchronously the moment a knock-off link is saved — and when it reaches zero it is deleted outright rather than left showing zero. Void the invoice or delete the link and the quantity goes back: the row is re-created if it had been deleted.
Across the fleet this is the largest of the platform’s stored figures — 44 of 90 tenants hold these rows, about 11 million of them, a median of 62,000 per tenant.
Several reports do it the other way, working the balance out by subtracting the knock-off links from the ordered quantity. That is why an order report and the stock availability figure can disagree while both are doing arithmetic correctly — and why the report can look right while availability is still wrong.
What to do about it
- Confirm the configuration exists for the source and target document types, in Organization. If it does not, add it — but note that adding it now does not retrospectively create rows for orders already finalised.
- Re-check from the right document. Read the balance from the document type you are actually knocking off with.
- If the row is genuinely stale, this is a repair, not a self-service rebuild.
When it is a support matter
Report it when the outstanding quantity is wrong and the knock-off configuration is in place and the links on the documents are correct. Two shapes cover nearly all of them:
- Extra outstanding quantity — the order shows a balance the invoices have already covered.
- The order is missing from the KO tab entirely, even though it is FINAL and has a balance.
Give the order number, the company, and both quantities — ordered and invoiced.
What this page cannot tell you
- Whether the background job ran on your tenant. Which processors are subscribed is a per-tenant setting with no screen that lists it.
- How to rebuild the balance yourself. There is no self-service rebuild for it in the sales applets.
Related documentation
- Partial delivery workflow — Base Qty., Bal. Qty. and Knockoff Qty. in use, and the Knock Off Configuration row an order needs before anything decrements.
- Internal Sales Order applet — the order itself, and what FINAL sets off.
- Which figures BigLedger stores, and which it works out fresh — the same trade-off in the other four places it appears.