Find, Verify and Settle Pending Customer Payments

Before Selling on Credit

• Create or select the real customer instead of Walk-in Customer when the balance must be collected later.
• Enable Allow credit (pay later) on that customer and apply the store's credit limit and reminder policy.
• Save a phone or email address and, when useful, a customer category before the sale. Missing customer context produces weak collection evidence and blank grouped fields.
• At tender, use Unpaid or enter a partial Pay amount only when the customer has agreed to the balance.
• Give the customer the sale receipt and record any agreed due date outside this report. Pending Payments does not provide ageing buckets, invoice due dates or collection-status notes.

Run the Report

• The range is applied to the sale record's last updated date, not necessarily its original creation date. A payment, edit or partial return can move a sale into a later reporting period.
• The report includes qualifying Add, Edit and PartialReturn sale records when their saved status or payment_pending value still indicates debt.
• Users with Sales Session Filter can see only sales in their permitted login-session window even when the screen says All Time.
• Report read permission is required. Free-plan report panels are blurred and export actions are restricted.

1. Open Reports -> Sales -> Pending Payments.
2. Choose the date range and one or more branches, then select Apply.
3. Start with Sale Details to identify the exact invoices that still carry a balance.
4. Use Customer Details to plan customer-level collection and Customer Category Details to review exposure by credit group.
5. Refresh after a settlement and confirm that the due amount has reduced or the fully settled invoice has left the report.

Read Sale Details

• Sale Details is sorted by the largest total/pending value rather than by newest date.
• An Unpaid status can still appear when payment_pending is greater than zero even if the status label differs from Pending or Partialy Paid.

Inspect One Pending Sale

• Phone and email become call and mail links only when those fields are saved.
• The sidebar does not show the cashier even though the report service retains user context.
• The sidebar is read-only evidence. It does not collect payment or modify the sale.

1. Select the Sale Id.
2. Confirm the invoice number and branch in the right sidebar.
3. Verify customer name, phone, email and address before discussing the account.
4. Review Product history for each grouped item name, summed quantity and amount.
5. Page through the product list when the invoice has more than five distinct items.
6. Close the sidebar and open the same sale in Sales History for receipt, tender and settlement actions.

Use Customer Details

Customer Details combines all qualifying sales in the range for each customer and shows Name, Phone, Referred By, Products, Total, Partial and Due.

• Products is the sum of saved item counts across that customer's qualifying sales. It is not the number of invoices.
• Total, Partial and Due are summed across those sales; confirm individual invoices in Sale Details before accepting a lump-sum payment.
• Walk-in Customer debt can appear with blank phone or referral information. Investigate the original sale because this row is not a reliable customer account.
• Rows are sorted by total value, so the largest customer exposure appears first.

Use Customer Category Details

Customer Category Details combines qualifying sales by the category saved on the sale, with Name, Products, Total, Partial and Due.

• Products is summed item count, not customer count and not invoice count.
• Use categories such as business accounts or wholesale customers to monitor policy exposure, then return to Customer Details and Sale Details for collection.
• Sales without a useful category can appear as a blank group in current data. Assign categories before future credit sales; do not rewrite historical evidence merely to clean this report.
• This view is a policy roll-up, not an ageing schedule or customer statement.

Export the Three CSV Files

• The small export/share action inside each tab requests all matching rows, not only the visible page.
• `PartialyAmount` is the current exported spelling on the customer and category files; keep it when building an import or reconciliation template.
• Set and apply filters before exporting, then compare the exported row count and due total with the screen.
• The shared top PDF, CSV, Excel and Email toolbar is registered to a report surface; verify its output against the active tab before distributing it.

Collect and Settle the Balance

1. Confirm the customer and every open invoice in Pending Payments.
2. Open Sales History or the customer's credit and wallet settlement workflow; Pending Payments itself is read-only.
3. Record the amount actually received against the intended invoice or account using the correct payment method.
4. Issue payment evidence or a revised receipt and keep provider evidence for non-cash payments.
5. Rerun Pending Payments with a period that includes the sale's updated date.
6. Confirm Due reduced by exactly the receipt amount and reconcile the payment in Payment Reports and Day-End Summary.

Troubleshooting

Daily Credit Control

• Every due invoice is tied to the correct named customer and branch.
• Customer and category Products values are treated as item counts, not invoice counts.
• Collections are posted through Sales History or customer settlement, never through the report.
• Due reductions match receipts and Payment Reports.
• Walk-in, blank-contact and blank-category debt is investigated before close.
• Unresolved differences are documented and escalated before the next shift.