Record supported credit sales, customer balances, repayments, outstanding amounts and transaction history in SellingIt.
Record a sale on customer credit
A supported credit sale is associated with the appropriate customer and contributes to the recorded outstanding balance. The merchant defines its own credit policy and remains responsible for communicating terms.
Track balances and repayments
Repayments update the supported customer balance and remain part of the transaction history. Clear dates, amounts, customer identity, and controlled adjustments make the operational ledger easier to review.
Understand the scope of customer credit
SellingIt supports merchant credit records; it is not a bank, lender, credit bureau, collections service, or guaranteed replacement for full accounting software.
Explore related SellingIt workflows
Follow an outstanding balance back to the customer ledger
Customer outstanding tracking starts with the correct customer and credit-sale entry. A repayment reduces the recorded outstanding amount and remains in the ledger history. If the balance differs from what you expect, review dated entries and any supported adjustments rather than replacing the total without context.
Billing software with customer credit connects the sale to that history. This customer ledger supports outstanding payment tracking inside retail operations; it is separate from full accounts receivable accounting or automated collections. See the shop udhaar use case for an everyday example.
Keep every customer-credit balance explainable
An outstanding balance should be the result of dated credit sales, repayments and authorized adjustments connected to the correct customer. Staff should be able to follow the total back to those entries. Replacing a balance without preserving its history may make the number look correct while leaving the original mistake unresolved.
How should a partial repayment be recorded?
Keep the original credit sale unchanged and record each repayment as a separate event. If a customer owes 800 and pays 300, the supported record should retain the 800 sale, the dated 300 repayment and the remaining 500 balance before any other activity. Confirm the customer and amount before saving the payment.
What causes a customer balance to be wrong?
Common causes include a missing repayment, a credit sale assigned to the wrong customer, duplicate customer records, an entry saved twice, a return handled without the related credit correction or an unexplained adjustment. Review the dated ledger and supporting transaction context before changing the balance.
How should staff handle disputed udhaar?
Listen to the customer, confirm identity using the merchant’s permitted process and review the relevant sales, repayments and corrections in order. Separate confirmed facts from memory. If a correction is justified, record the reason and authorized action rather than deleting history simply to end the disagreement.
Who should be allowed to change credit records?
The merchant should define who may approve a credit sale, record a repayment, make an adjustment and review balances. Restrict access to necessary customer information and review unusual changes. Software can support the record, but it cannot decide a suitable credit policy or legal process for every business.
Is a customer-credit ledger the same as accounting?
No. It supports the merchant’s operational record of credit sales and repayments. Formal accounts receivable, bank reconciliation, tax records, lending, credit scoring and collections may require separate systems and professional guidance.
Use the customer-credit repayment checklist, read the customer-credit guide, and review the everyday shop udhaar workflow.
Feature summary
Record and manage customer credit information and payment activity where supported by your business workflow.
Who it is for
Merchants who want a clearer way to organize this part of their day-to-day operations.