A useful unpaid-invoice list explains what remains outstanding, what is overdue and who will resolve the next action. Start with one checked review date.
Turn the unpaid-invoice list into checked actions.
The sales register looks busy, but the supplier payment is due and the bank balance is lower than expected. Some customers have paid part of their bills. One says there is a delivery issue. Another invoice is still within its agreed payment period.
An unpaid invoice review helps the owner see which amounts need action and why. The useful result is a checked list with an owner and a next step for each invoice.
Here is a routine for a small printing and packaging supplier in Hetauda. The business, invoice references, dates and NPR figures are hypothetical. The process can also suit wholesalers and service firms that invoice customers on agreed payment terms.
Review the invoice list using one reporting date and consistent records.
Start with one report date and a checked balance
Choose the date of the review. Use the same business, currency and reporting cut-off throughout the list. For each open invoice, bring together the invoice total, allocated payments, relevant approved adjustments, due date and remaining balance.
ERPNext’s Accounts Receivable and Payable documentation illustrates why these settings matter: its report distinguishes outstanding invoices, ageing and payment allocations, with a choice of ageing basis. Check whether your own report measures age from the invoice date or the due date before interpreting it.
For this review, use calendar days after the due date. An invoice due on 5 November is seven days overdue on 12 November. An invoice due on 20 November is still not due on that review date.
Keep the agreed due date visible. A later promise to pay is useful follow-up information, but should not quietly replace the original due date and make the invoice appear younger.
Separate outstanding amounts from overdue amounts
Assume the following three invoices are the entire sample. The invoice totals are already the posted totals; no additional tax calculation is being made. There are no credit notes, other adjustments or payments outside the amounts shown.
| Invoice |
Invoice total |
Allocated payments |
Outstanding |
Due date |
| INV-101 |
NPR 60,000 |
NPR 20,000 |
NPR 40,000 |
5 Nov 2026 |
| INV-102 |
NPR 35,000 |
NPR 20,000 |
NPR 15,000 |
10 Nov 2026 |
| INV-103 |
NPR 25,000 |
NPR 0 |
NPR 25,000 |
20 Nov 2026 |
| Total |
NPR 120,000 |
NPR 40,000 |
NPR 80,000 |
Review 12 Nov |
Outstanding = NPR 120,000 − NPR 40,000 = NPR 80,000
Only INV-101 and INV-102 are overdue in this example. Their balances add to NPR 55,000 overdue. The remaining NPR 25,000 is outstanding but not yet due.
Do not add NPR 55,000 to NPR 80,000: the overdue amount is already included in the outstanding total. Neither total is a measure of profit or a guarantee of when cash will arrive.
Hypothetical balance logic counts each amount once.
Check the reason before sending another reminder
Open the supporting records for each overdue invoice. Confirm that the customer has the correct invoice, the delivery or service evidence is available, and the payment contact is still appropriate.
Ask whether a payment has already arrived but has not been linked to the invoice. ERPNext’s Payment Reconciliation documentation describes matching recorded payments and credits with invoices. This is separate from checking a bank statement against the books.
If the customer sends a payment screenshot, the accounts person should verify the receipt and its allocation through the normal process. Avoid closing an invoice solely because a message says “paid.” Likewise, a promise to pay next week does not reduce today’s outstanding amount.
For a disputed invoice, record the issue and the evidence needed. A request for a credit or a return does not, by itself, establish the approved adjustment. Let the responsible accounts person review the treatment before changing the balance.
Check the evidence behind an invoice query before repeating a reminder.
Give each invoice a useful next action
A reminder list becomes easier to manage when it records the action required, rather than just “call customer.”
For the hypothetical review on 12 November:
| Invoice and position |
Next action |
Owner and review point |
| INV-101: NPR 40,000, 7 days overdue |
Confirm the customer’s stated 15 November payment plan |
Accounts coordinator checks on 15 November |
| INV-102: NPR 15,000, 2 days overdue; delivery query raised |
Retrieve the delivery acknowledgement and agree the disputed details |
Dispatch lead supplies evidence by 13 November; Accounts reviews |
| INV-103: NPR 25,000, not due |
Confirm the invoice reached the correct payment contact |
Accounts coordinator checks before the 20 November due date |
These are proposed actions, not assumed customer agreements. Record what is actually confirmed. Keep a dated note of the conversation and the next review point so another colleague can understand the position.
A concise message might say: “Our records show NPR 40,000 outstanding on INV-101, due on 5 November. Please confirm the planned payment date, or share the payment reference if it has already been settled.” Adapt it to the checked balance and the customer’s circumstances.
Match the next action to the issue that needs resolving.
Connect accounts with the teams that hold the evidence
The accounts team may need delivery information from Inventory or Dispatch, acceptance details from Project/Task Management, or the current customer contact from CRM. Link the existing invoice and supporting records so each team works from the same references.
Assign responsibility for the specific blocker. If the delivery note is missing, a collection reminder will not retrieve it. If the payment is unallocated, the sales team should not create another payment entry to make the invoice disappear.
For planned WorkSphere workflows, evaluate invoice-level tasks, permission-controlled evidence links and clear handovers between these modules. These are requirements to assess, not claims that those connections are currently available.
End the review with decisions you can check next time
At the next review, check whether each action happened and whether the invoice balance changed after verified processing. Keep payment promises, disputes and amounts awaiting allocation visible until their particular issue is resolved.
Use the list to identify collections that need attention, but base purchasing and payment commitments on a broader cash review. An expected receipt can be late.
Start with a manageable group of open invoices and keep a clear owner for the register. A short review that produces checked actions is more useful than a long spreadsheet nobody updates.
Keep the original due date visible beside the next follow-up date.