How to Track Customer Due Payments for Bangladeshi Shops
Customer due, or baki, is normal in many Bangladeshi shops. A grocery shop in Gazipur, a pharmacy in Sylhet, a fashion seller in Chattogram, or a Facebook page seller in Mirpur may allow trusted customers to pay later. The problem starts when due records live in paper khata, Messenger notes, staff memory, and separate Excel files.
This guide explains customer due payment tracking Bangladesh workflows for shop owners who want clearer sales, collection, accounts, and reports. It also shows how business management software in Bangladesh can reduce missed collections.
If customer due is becoming hard to control, request a Hishab demo and compare your current khata process with a more organized workflow.
Quick Answer
Customer due payment tracking means recording who owes money, how much they owe, when the sale happened, what they bought, how much they already paid, and when follow-up is needed. A clear due register helps owners protect cash flow and avoid forgotten baki.
Why Due Payments Become a Problem
- Sales are written quickly during busy hours and details are missed.
- Partial payments are not updated against the original sale.
- Staff allow due without owner approval.
- Customers buy again before old due is collected.
- Due records are mixed with supplier payable and daily expenses.
- Owners cannot see total outstanding due at the end of the week.
What Every Due Record Should Include
| Field | Why It Matters |
|---|---|
| Customer name and phone | Makes follow-up easier and avoids duplicate customer records. |
| Sale date and invoice note | Connects the due amount to the original purchase. |
| Total bill, paid amount, due amount | Shows the real balance after partial payment. |
| Collection date | Helps staff follow up before the amount is forgotten. |
| Collector or staff name | Creates accountability inside the shop. |
For a broader accounting workflow, see accounting software in Bangladesh and shop management software in Bangladesh.
Bangladesh Example: Grocery Shop in Gazipur
A grocery shop gives due to 40 regular customers. Some pay every Friday, some pay after salary, and some pay only when reminded. If the owner writes due in a notebook, staff may not know the customer already owes money. After one month, total due can become larger than expected.
With a cleaner workflow, each sale is recorded against the customer, partial collections reduce the balance, and the owner can review a customer-wise due list before allowing more baki.
Mini Workflow for Due Collection
- Create one customer list with phone numbers.
- Record each sale and mark whether it is paid, partial, or due.
- Update every collection immediately.
- Review due customers at the end of each day.
- Follow up weekly with customers who crossed the agreed date.
- Stop new due for customers with old unpaid balances.
Sample Due Calculation in BDT
| Customer | Total Bill | Paid | Due |
|---|---|---|---|
| Customer A | ৳4,500 | ৳2,000 | ৳2,500 |
| Customer B | ৳8,200 | ৳5,000 | ৳3,200 |
| Customer C | ৳2,750 | ৳0 | ৳2,750 |
This small list already shows ৳8,450 in outstanding due. Without regular tracking, a shop owner may think sales are strong while cash collection is weak.
Checklist: Your Due Tracking Needs Improvement If
- You cannot quickly say total customer due today.
- Customers argue about old payments.
- Staff keep separate due notes.
- You allow new due without checking old balances.
- Supplier payments are delayed because customer collection is unclear.
- You spend too much time matching khata, cash, and sales.
Manual Khata vs Software Workflow
| Area | Manual Khata | Software Workflow |
|---|---|---|
| Customer balance | Requires page-by-page checking | Customer-wise balance is easier to review |
| Partial payment | Can be missed or written in another place | Collection can update the same customer record |
| Follow-up | Depends on memory | Owner can review due lists regularly |
| Reports | Total due is manually calculated | Due, sales, and collection reports are clearer |
How Hishab Fits
Hishab helps Bangladeshi SMEs organize sales, customer due, supplier payable, inventory, expenses, and reports in one workflow. For shops that give baki, this can support cleaner customer-wise due and collection records instead of depending only on notebooks.
If you need special requirements such as SMS reminders, automatic payment links, VAT/NBR/Mushak reporting, offline mode, or branch-level approval, confirm current support with the Hishab team before setup.
Related reading: business software in Bangladesh, shop accounting software, and inventory management for Facebook sellers.
FAQ: Customer Due Payment Tracking Bangladesh
What is customer due tracking?
It is the process of recording customer-wise unpaid amounts, partial payments, collection dates, and remaining balances.
Why is due tracking important for shops?
It protects cash flow. Sales are not useful if too much money remains uncollected for too long.
Can software replace a due khata?
Software can make due records easier to search, update, and report, but staff still need to enter sales and collections correctly.
Can Hishab help with customer baki?
Hishab is positioned for customer due tracking alongside sales, accounts, inventory, and reports. Confirm your exact workflow during a demo.
How often should owners review due?
Daily review is best for busy shops. At minimum, review due balances every week before new purchasing or supplier payments.
Next Step
If customer due is affecting your cash flow, book a Hishab demo and review your sales, collection, and reporting process with the team.