A khata app built for irregular, large-ticket contractor credit
A contractor does not buy every day. When they do, the amount is large, the site is far from where the ledger lives, and the bill matters more than in most trades.
Hardware and building-material credit does not look like daily kirana udhar. Purchases are infrequent, amounts run into thousands, and a single missing invoice can turn into a real dispute at settlement. The record needs to survive weeks between visits.
Large, infrequent entries need the bill attached
A ₹40,000 cement and steel purchase settled two months later depends entirely on both sides agreeing what was actually taken. Attach the invoice photo to the entry itself, so the record and the evidence never separate.
Track by site or project in the notes
A contractor running three sites at once needs to know which purchase belongs to which job. Use the notes field on each entry for the site name, and the full picture is still there when the contractor pays against one project but not another.
Due dates that match how contractors actually pay
Contractor payment often follows their own client's payment cycle, not a fixed monthly date. Set a due date per credit entry so overdue accounts surface accurately instead of by a generic 30-day assumption.
A statement a contractor can check against their own site accounts
When a contractor is reconciling what they owe across several suppliers, a clear dated statement — not a verbal total — is what gets you paid first.
Common questions
Can I record which site or project a purchase was for?
Yes, using the notes field on each entry. It is searchable later when a contractor wants to settle one project without touching the others.
How many invoice photos can I attach to one purchase?
Up to five images or PDFs on a single entry, enough for a multi-item bill.
Can I set different due dates for different contractors?
Yes, due dates are set per party and can be adjusted per credit entry.