How the udhaar workflow works
A merchant identifies the customer and records a supported sale on credit. The credit amount contributes to the customer’s outstanding balance. When the customer makes a repayment, the merchant records it so the balance and transaction history reflect the new position.
Keep a useful customer ledger
A customer ledger is useful when it shows the relevant credit entries, repayments, adjustments, dates, and resulting balance clearly. Staff should avoid duplicate customer records and enter repayments promptly.
Review outstanding customer balances
Outstanding information helps authorized users see amounts recorded as due and investigate differences. It does not replace reconciliation, receipts, accounting records, responsible credit policies, or any legal obligations that apply to the merchant.
Connect credit with customer and sales records
Customer credit is most understandable when it remains connected to the supported customer and transaction context. This distinguishes an operational udhaar record from an unexplained total in a separate note.
What SellingIt does not claim
SellingIt does not position customer credit as banking, lending, credit scoring, collections, or full accounting. Merchants decide who may receive credit, set their own terms, control staff access, and remain responsible for accurate records and customer communication.
Explore related SellingIt workflows
- Explore SellingIt customer credit
- Review customer management
- See shop management workflows
- Explore SellingIt for India
A digital khata connected to shop billing
For merchants using a paper khata, the important change is traceability: customer → credit sale → outstanding balance → ledger history → repayment → updated balance. SellingIt’s udhaar app for business is accessed through the web merchant application and keeps supported credit records with the customer’s store activity.
For example, a credit sale of 500 followed by a repayment of 200 leaves 300 outstanding before any other entries. Billing software with udhaar should make both entries understandable, not just show 300. SellingIt supports this operational khata management workflow; it is not a full accounting application or a promise of every dedicated khata feature.
Read how to manage shop udhaar for record-keeping steps, and see customer credit and ledger functionality for the supported product scope.
Move from a paper udhaar notebook to a traceable routine
A digital record is useful when it preserves more than the latest total. Set up the correct customer once, record each supported credit sale when it happens and enter every repayment on the date received. The ledger should help staff answer what was bought, what was paid and what remains recorded without relying on memory or an easily lost notebook.
What information should an udhaar entry contain?
Use the correct customer, transaction date, supported sale or reference, amount and any necessary merchant note. Collect only information the business needs and is permitted to retain. Product-level context can help explain the original purchase where the supported billing workflow provides it.
How do you track several partial payments?
Record each payment separately rather than editing the sale or combining several dates into one unexplained amount. A sequence of 200, 150 and 100 repayments should remain visible as three entries so the customer and merchant can understand how the balance changed.
How often should outstanding balances be reviewed?
Choose a regular schedule appropriate to the number and value of active balances. Review recent repayments, disputed entries, customers approaching the merchant’s own limit and balances that require permitted follow-up. The merchant remains responsible for its terms, communication and compliance with applicable law.
Can software recover overdue udhaar automatically?
Do not assume so. SellingIt does not claim automated reminders, auto-debit, lending, debt collection, legal escalation or repayment guarantees unless current product documentation explicitly confirms a capability. The merchant should use lawful, respectful communication and qualified advice where needed.
How should a correction be made?
First find the incorrect sale, repayment or customer record. Preserve the original context where possible, record the supported correction with a reason and have an authorized person review material changes. Avoid overwriting the final balance without identifying the entry that caused it.
Follow the repayment and balance review checklist, maintain the underlying customer record, and use Customer Credit for the supported ledger workflow.