Ask the owner of a trading business how much money is owed to them right now, and you will usually get one of three answers: a number from a spreadsheet last updated on Friday, a figure from Tally that is accurate for accounts but blind to today's dispatches, or an honest "let me check." All three share the same flaw — the number and the goods live in different places, and the gap between them is where cash flow quietly leaks.
For a buy-store-sell operation, the warehouse is not a cost centre that sits apart from the money. It is the exact point where a receivable is created. A dispatch leaves the gate, an invoice is raised against it, and from that instant a customer owes you. If the system that recorded the dispatch is not the same system that tracks the outstanding amount, you are re-keying reality into a spreadsheet and hoping nobody forgets a line.
The receivables blind spot
Most distributors run their outstanding tracking in a tool that has no idea what happened on the warehouse floor today. The spreadsheet knows what was invoiced up to the last time someone updated it. It does not know that three trucks went out this morning, that one customer's goods were returned this afternoon, or that a credit note was issued against a short delivery.
The result is a receivables figure that is always a little behind, and occasionally very wrong. And it is wrong in the most expensive direction: you extend more credit to a customer who is already over their limit because the sheet has not caught up, or you chase a payment that was actually settled last week. Neither mistake is carelessness — it is the structural cost of keeping the debt in a different place from the dispatch.
Why the spreadsheet always lags
A spreadsheet is a snapshot maintained by hand. It is only as current as the last person to touch it, and it has no connection to the events that change the number. Three things guarantee it will drift:
- It updates on human memory, not on events. A dispatch changes what a customer owes, but the sheet only changes when somebody types it in — often in a batch, often late.
- It cannot see returns and adjustments. A sales return or a credit note reduces outstanding, but a standalone sheet has no link to the document that created the reduction.
- It has no single source of truth. When the sheet, the invoice book and the accounts ledger disagree, nobody can say which is right without a manual reconciliation nobody has time for.
Dispatch is where the debt is born
Inside Fast WMS, the outbound flow is not an abstract accounting event — it is a chain of real documents. An order is approved, a pick list is built and confirmed, goods are packed, and then dispatch and gate-out raise a dispatch invoice as the goods physically leave. The tax invoice is then drawn from the un-invoiced dispatch balance. Every one of those steps writes to the same document engine.
Because the debt is born at the same moment and in the same system as the dispatch, the outstanding figure can be computed directly from documents that already exist. There is nothing to re-key. Invoiced value, less receipts recorded against it, netted for credit and debit notes on returns, is the amount outstanding — and it is current the instant the last truck rolls out.
| Aspect | Standalone spreadsheet | Outstanding tracked in the WMS |
|---|---|---|
| Updates when | Someone remembers to type it in | A dispatch or return is posted |
| Sees returns & credit notes | Only if entered by hand | Automatically — same document engine |
| View by customer | Manual filtering and totalling | Grouped by party, with ageing |
| Source of truth | Whichever copy is newest | The dispatch and invoice documents |
| Credit decisions | Made on stale numbers | Made on today's real balance |
The outstanding payment report
The practical output is a live outstanding payment report. Because it is pulled straight from dispatch and invoice documents, it shows receivables the way a collections team actually needs to see them:
- By customer. Who owes what, right now, grouped by party — not a single blended total.
- By age. How long each amount has been outstanding, so overdue accounts surface before they become bad debt.
- Net of returns. Sales returns raise an automatic credit note that reduces the customer's balance, so the figure never overstates what is genuinely owed.
Pair this with customer ABC analysis — which ranks accounts by their share of value — and collection effort goes where it matters. The handful of customers who carry the majority of your outstanding value are visible at a glance, instead of buried in a flat list sorted alphabetically.
A trading firm ships to 300 retailers on credit. In the spreadsheet world, the sales head asks accounts for an outstanding statement, waits, and acts on Friday's picture. With outstanding tracked in the WMS, the same head opens the report, sees that two large accounts crossed their credit period over the weekend's dispatches, and holds the next order before it is even picked. Same data, but now it arrives before the mistake instead of after it.
How Fast WMS closes the loop
Fast WMS is built in Pune by Improsys under the Fast Technology brand, and its trading and distribution variant treats receivables as a direct consequence of the outbound flow, not a separate ledger to maintain:
- Dispatch raises the invoice. Gate-out creates the dispatch invoice and the tax invoice comes from the un-invoiced balance — see dispatch & invoicing.
- Returns adjust it automatically. A sales return re-adds stock and raises a credit note that reduces the customer's outstanding.
- The report reads from documents. Outstanding is computed from the invoices and receipts that already exist — nothing is entered twice.
- Accounts stay in sync. The same transactions post to Tally, so the operational view and the accounts agree instead of drifting apart.
Your receivables, computed from the dispatches that created them
Fast WMS keeps the outstanding number where the goods move. Dispatch raises the invoice, returns raise the credit note, and the outstanding payment report reads directly from both — grouped by customer, aged, and always current. No parallel spreadsheet to reconcile, no number that lags a busy morning.