How to Know Which Parties Still Owe Payment
See exact wholesale receivables, group unpaid and partial invoices by party, follow up on the oldest bills, record later payments and close agreed differences correctly.
A wholesaler can know which parties still owe payment by keeping every invoice's original total, actual receipts and live balance due separate. Order Manager then shows only unpaid and partially paid invoices in Outstanding, groups them by party for collection, and keeps fully settled bills out of the worklist.
This replaces the question “Payment kis party se lena hai?” with a list the owner can act on without searching notebooks, bank screenshots and old WhatsApp chats.
At a glance
| Owner's question | Where to answer it |
|---|---|
| How much money is outstanding in total? | Outstanding summary |
| Which party owes the most among the current worklist? | Outstanding → Party |
| Which open bill should I follow up on? | Outstanding → Invoice |
| What does one particular retailer owe? | Party Detail or Party Dues |
| Was a bill paid partly or kept on full credit? | Invoice status and payment history |
| How do I record money received later? | Invoice Detail → Record payment |
| We accepted less as final payment—what now? | Owner settlement confirmation |
| Did a return reduce what is due? | Linked credit note and recalculated balance |
| Are last month's pending bills correct? | Month-end for CA → Review bills |
Understand the three numbers first
Every collection decision depends on three separate values:
| Value | Meaning |
|---|---|
| Invoice total | What was billed to the customer |
| Amount paid | Money actually recorded as received |
| Balance due | What the business still expects to collect |
Suppose a retailer receives an invoice for ₹75,000 and pays ₹25,000 immediately.
Invoice total ₹75,000
Amount received ₹25,000
Balance due ₹50,000
Payment status Partial
The invoice remains ₹75,000. The Outstanding screen should show ₹50,000—not ₹75,000 and not zero.
What creates an outstanding balance?
When an invoice is saved in Order Manager or Staff Bill, the billing user selects one of three settlement choices.
Paid in full
Use this when both parties consider the transaction complete. If the received amount matches the invoice, balance due becomes zero and the invoice does not enter Outstanding.
Partial payment
Use this when some money was received and the remaining amount is genuinely expected later. Only the remaining balance enters Outstanding.
Full credit
Use this when nothing was received at invoice creation. The complete invoice value remains due.
These choices are business facts, not decorative labels. Selecting Partial for an agreed final payment leaves an unnecessary receivable. Selecting Paid in full for a genuine due removes money the owner still expects.
Start with the Outstanding screen
Order Manager's Outstanding screen is the collection worklist. It queries invoices belonging to the signed-in seller whose payment status is:
- Unpaid; or
- Partial.
It does not download every historical invoice and then inspect each one on the phone. Paid invoices are excluded by the Firestore query itself.
At the top, a server-side count and sum provide:
- exact total outstanding value; and
- exact number of open invoices.
This remains accurate without downloading every matching invoice merely to add its balance. The operational list is intentionally bounded to the latest 100 open invoices, which is practical for the expected wholesale usage while preventing an endlessly growing screen. If a business allows more than 100 invoices to remain open, the exact header can be larger than the currently loaded worklist; that is a strong signal to review old collection practices.
Party view: decide whom to call
The default Party view groups the loaded open invoices by customer. Each row can show:
- party name;
- combined visible balance due;
- number of visible open bills; and
- oldest visible invoice date for that party.
The grouped parties are sorted by highest combined due first. This is useful when the owner wants to prioritise collection by exposure.
Example worklist:
| Party | Open bills | Total due | Oldest open bill |
|---|---|---|---|
| Kumar Garments | 3 | ₹1,20,000 | 04 Aug |
| City Fashion | 1 | ₹72,000 | 11 Aug |
| Raj Footwear | 4 | ₹46,500 | 28 Jul |
| New Style | 1 | ₹9,500 | 19 Aug |
The first phone call may be Kumar Garments because the amount is highest. Raj Footwear may still deserve attention because its oldest bill is earlier. The screen provides the facts; the owner decides the relationship strategy.
Tap a party to open its dues. The party contact details and open invoices appear together, with invoices ordered oldest first within the loaded dues. Each invoice can be opened for full details and payment action.
Invoice view: decide which bill is ageing
Switch to Invoice when the collection question is about individual bills rather than customers.
Each row shows practical details such as:
- party name;
- invoice number and date;
- original bill total;
- current balance due; and
- whether the invoice is Partial or Unpaid.
The loaded invoice worklist is presented oldest first so an ageing bill is not hidden below recent activity. Tap it to inspect products, payments, credit notes and the exact balance before contacting the customer.
Use the Parties tab when you already know the customer
Outstanding is a collection list. The Parties tab is the seller's customer directory.
The default party order is A–Z by name, with an option to sort by recently added. The list is server-paginated in groups of 20 rather than loading every customer at once.
When a wholesaler has 1,000 parties, scrolling is rarely the fastest path. Submitted server search supports prefixes of:
- party name;
- mobile number; and
- GSTIN.
For example, the owner can search Lakshmi, a known mobile prefix, or the beginning of a GSTIN, then open Party Detail. Search remains scoped to that seller's active parties; it does not search another subscriber's customer records.
Party Detail combines:
- contact and GST information;
- recent invoice history;
- credit-note history; and
- an exact server summary of that party's open-invoice count and balance.
This is the better route when a customer calls and asks, “Hamare account mein kitna pending hai?”
Record money when it is actually received
Open an outstanding invoice and choose Record payment. Enter the amount and the mode that reflects what happened:
- Cash;
- UPI;
- Card; or
- Bank transfer.
More than one mode can be stored for the same invoice. A ₹40,000 collection can therefore remain truthful if ₹10,000 arrived in cash and ₹30,000 by bank transfer.
Example payment timeline:
| Event | Money received | Balance after event |
|---|---|---|
| Invoice created on full credit | ₹0 | ₹80,000 |
| First bank transfer | ₹30,000 | ₹50,000 |
| UPI payment | ₹20,000 | ₹30,000 |
| Final cash payment | ₹30,000 | ₹0 |
After the last payment, status becomes Paid and the invoice leaves Outstanding. The original invoice and every payment row remain available in history.
Do not record a fake payment to close a difference
Suppose the bill is ₹51,000. The customer pays ₹50,000, and both sides agree that no more money is due.
Two incorrect options are:
- record ₹51,000 as received even though only ₹50,000 arrived; or
- leave ₹1,000 outstanding forever even though the owner will not collect it.
The correct stored position is:
| Field | Amount |
|---|---|
| Original invoice total | ₹51,000 |
| Money actually received | ₹50,000 |
| Agreed settlement adjustment | ₹1,000 |
| Balance due | ₹0 |
| Status | Paid |
Paid-in-full entry with a mismatch requires explicit confirmation. If staff selected Partial conservatively, the owner can later use Close agreed difference after verifying the commercial agreement.
Only the owner can perform this later correction. It reads the latest invoice balance while saving so another device's recent payment is not accidentally written off again.
Read How to Record Payments and Correct an Invoice's Settlement Status for every settlement scenario.
Staff-created bills still belong to the owner's receivables
Staff Bill lets authorised billing staff create invoices without exposing the owner's cost, profit and reports. The invoice is stored under the connected owner and selected party.
Therefore a credit or partial invoice created by staff appears in the owner's Order Manager outstanding flow. The owner does not need to copy the bill into a separate collection notebook.
This also explains why staff should record the payment state conservatively. When a staff member is unsure whether a short amount was accepted as final, Partial is safer. The owner can review and close an agreed difference later.
Returns and outstanding are connected but separate
If a customer returns goods, use a linked credit note. Do not enter the returned value as if it were a cash payment.
A valid credit note can:
- reverse the relevant sale and tax values;
- restore eligible stock;
- record a refund when applicable; and
- reduce the invoice balance due according to the return.
Payment answers “How much money arrived?” A credit note answers “How much of the sale was reversed?” Keeping them separate produces a clearer party account.
Read How Returns and Credit Notes Work for the complete return flow.
What happens when a party is removed?
Removing a party from the active directory is a soft deactivation. It does not delete old invoices, payments or credit notes.
This matters when the business stops dealing with a retailer but still needs its historical records—or still has an unresolved invoice. Never delete documentary history merely to clean the party list.
Why the screen does not refetch after every tap
Order Manager keeps the loaded outstanding worklist in memory during the app session. Reopening Home, Outstanding and Party Dues can reuse that snapshot instead of repeating the same Firestore reads.
After a successful payment or settlement, the affected invoice is patched immediately:
- its balance is updated;
- the exact total due is adjusted;
- a fully settled invoice is removed; and
- listening screens refresh from the same store.
Pull to refresh reconciles changes made elsewhere. Home also refreshes stale billing data after approximately 30 minutes when relevant navigation returns, while local billing changes can trigger more targeted updates. This balances freshness, speed, mobile data and Firebase cost for a low-frequency wholesale billing pattern.
Review pending bills before the CA report
Before generating a report pack for a completed month, Order Manager checks that month's open invoices.
The owner can open each pending bill and choose the truthful action:
| Situation | Correct action |
|---|---|
| Customer paid, but receipt was not recorded | Record payment |
| Customer genuinely still owes the balance | Keep it pending |
| Both parties accepted a smaller final amount | Close agreed difference |
The owner can still generate a report with genuine outstanding. Credit sales are not an error. The review exists to prevent missed receipts and staff misunderstandings from being treated as real receivables.
See How to Review Outstanding Invoices Before Generating the CA Report.
A practical daily collection routine
Every morning or collection day
- Open Outstanding → Party.
- Review high-value dues and old dates.
- Open the party before contacting them.
- Quote the exact invoice number and current balance.
When money arrives
- Open the invoice.
- Record the actual amount and mode.
- Check the remaining balance.
- Do not create a settlement adjustment unless the owner accepts it.
Every week
- Pull to refresh for changes from other devices.
- Review old Partial invoices.
- Check whether returns need proper credit notes.
- Follow up on large balances before adding more credit exposure.
At month end
- Open Month-end for CA for the completed month.
- Review unexplained open bills.
- Record missing receipts.
- Preserve genuine dues.
- Generate or regenerate the report pack after corrections.
Common mistakes
Looking only at total sales
An invoice is revenue, but it does not prove the money was collected. Review balance due separately.
Looking only at total outstanding
The total says how much is due, not whom to contact. Use Party view for action.
Treating Partial as permanently correct
A staff member may have selected it safely before the owner confirmed a settlement. Review old partial bills.
Recording a bank promise as a payment
Record money after it is actually received, not when the customer says it will arrive.
Hiding a return as payment
Use a credit note so sale, tax, stock and refund effects remain traceable.
Changing the invoice total after collection
Keep the original bill intact. Record receipts and accepted settlement differences separately.
Letting dues accumulate without review
The worklist is bounded for operational performance even though the total summary remains exact. A business with more than 100 open invoices should urgently reconcile older accounts instead of relying only on the visible rows.
Frequently asked questions
Does Outstanding load every invoice ever created?
No. It queries only invoices marked Unpaid or Partial and keeps the operational list bounded. Paid historical invoices are not downloaded for this screen.
Is the total outstanding exact?
Yes. A server aggregate counts open invoices and sums balanceDue, independent of the bounded operational list.
Which party appears first?
Party view sorts the visible grouped worklist by highest combined due. Invoice view shows the loaded open invoices oldest first.
Can I find a party by mobile number or GSTIN?
Yes. The Parties tab supports submitted server search by name, mobile number and GSTIN prefix.
Can staff see the owner's complete outstanding and profit?
Staff Bill is intended for authorised billing work without exposing owner reports, cost and profit. Staff-created credit and partial invoices feed the owner's Order Manager records.
What if a customer pays after the invoice date?
Open the invoice and record the later receipt. The payment history, amount paid, balance and status update without changing the original invoice date or total.
Can an agreed ₹1 difference be removed from outstanding?
Yes, but it must be explicitly accepted as a settlement difference. It is not stored as money received.
Can another subscriber see my parties?
No. Party and invoice queries are scoped to the seller, and staff access depends on an authorised relationship with that owner.
Make receivables actionable
A useful outstanding number should lead to the next action. It should tell the owner how much is due, which party is responsible, which invoice remains open and what happened after every receipt or return.
Order Manager keeps those relationships connected. The owner can prioritise collection, open the exact bill, record real money, preserve genuine credit and close only the differences that were commercially accepted.
Explore Order Manager, learn about Staff Bill, read the complete party ledger guide, or review current plans.
