Udhar khata template
The Excel file the bulk importer expects.
Use this template for a first import into the ledger, or as a paper-replacement spreadsheet.
Download Excel templateColumns
The file matches the Android bulk import: customer name, phone, village, product, quantity, price, payment. Empty rows are ignored. Duplicate names in the same village are merged, so “Ramesh” in two villages stays two people, and two “Ramesh” rows in one village become one customer with two sales.
Import once, then stop the spreadsheet
A paper bahi fails when the sale is in one book and the payment is in another. An Excel khata fails the same way the week you keep editing the sheet after you have imported it. Fill the open dues, import, then treat DueSetu as the book. New sales go in the ledger. If you need a backup, export CSV from the customer list. Do not keep a third copy on the desktop named final-final.xlsx.
The download is a blank file. Nothing you type on this page is uploaded. The import itself happens after you sign in, on the web import screen or in Abhedyam Owner. Delete the filled spreadsheet when you are done. It is a list of who owes you money.
Frequently asked questions
What is this Excel file for?
A first import into the DueSetu / Abhedyam ledger. It is the same template the Android bulk importer expects: customer, phone, village, product, quantity, price, payment.
Do I have to use Excel, or will Google Sheets work?
Export to .xlsx. Sheets can fill the columns. The importer wants the file format the Android app already uses, not a CSV you invented.
What if two rows have the same customer name?
Duplicate names in the same village are merged into one customer. Put a second person with the same name in a different village, or add a last name, so they do not collapse.
Are empty rows a problem?
No. Empty rows are ignored. Leave a gap if you like. Do not delete the header row.
Do I need a phone number on every row?
The customer can sign in later with the mobile you already have. A row without a phone still imports as a name. You will not be able to send that person a pay link until a number exists.
Should I put the remaining due or the original sale?
Put the sale (product, quantity, price) and any payment already received. Remaining due is computed. If you type a running total as the price, the khata will be wrong on day two.
Can I import twice?
A second import is a new set of sales, not a merge of edits. After the first load, stop maintaining the spreadsheet as a second source of truth.
Will this upload my file to DueSetu from this page?
No. This page only downloads the blank template. The import itself happens after you sign in, in the owner app or on the import screen.
What encoding should I save?
Save as .xlsx. Hindi village names and product names are fine. A CSV saved from an old Excel in a local code page is how names turn into question marks.
Is there a row limit?
Treat a first import as the current open dues, not ten years of history. A few hundred rows is the job. A 20,000-row dump belongs in an archive, not in the daily khata.
Do product rows need HSN codes?
Not in this template. HSN belongs on a GST invoice. The khata import is name, qty, price, payment.
Can a customer see this file?
They should not. It has every open due in the shop. Import it, then delete the filled copy from Downloads.
Where is the import button?
Sign in as a shop owner and open Import. The Android owner app has the same file. Both write to the same backend.