Retention money isn't forgotten
A contractor's retention amount and smaller overdue milestone invoices get nudged automatically on schedule, rather than depending on remembering to chase each one personally while busy elsewhere.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business gets paid faster because overdue customers get a polite, automatic nudge instead of the owner having to remember to call each one.
Works with
What it does
When an invoice passes its due date, Khata sends a WhatsApp or SMS reminder to the customer with the outstanding amount and a link to the invoice, on a schedule the owner configures. The owner can see reminder history and pause reminders for any customer at any time.
A contractor doing renovation work for a client is owed a retention amount held back until the final handover, plus smaller invoices from earlier milestones that quietly slipped past their due dates while busy on the next job. Remembering to call each client at the right moment, without sounding pushier than the relationship can bear, is its own ongoing task nobody really has time for.
Payment reminder automation sends a WhatsApp or SMS nudge to a customer once an invoice passes its due date, with the outstanding amount and a link to the invoice, on a schedule the owner sets. This is a collections communication tool, not a books-of-account feature — it never alters the ledger; it only nudges toward payment of an amount already recorded there, and the owner can see reminder history and pause reminders for any customer at any time they choose.
Khata runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
A scanner checks every recorded invoice against its own due date on a regular, recurring schedule, identifying exactly which ones have passed their due date without any matching payment recorded anywhere against them just yet at all.
Once an invoice is flagged overdue, a WhatsApp or SMS message goes out with the outstanding amount and a link back to the invoice, timed to whatever schedule the owner has configured for that customer.
Every reminder sent is logged against the relevant invoice and customer, so the owner can see exactly what's already gone out and when, rather than being left wondering afterward if a nudge actually reached anyone at all that day.
Reminders for any specific, named customer can be individually paused at any point in time — useful for a client relationship where a personal call is genuinely more appropriate than yet another automated nudge landing unexpectedly.
Why it matters
A contractor's retention amount and smaller overdue milestone invoices get nudged automatically on schedule, rather than depending on remembering to chase each one personally while busy elsewhere.
A scheduled, polite reminder message replaces the discomfort of deciding when a phone call about overdue payment starts to feel pushier than the relationship can bear.
A long-standing client relationship can have its reminders paused and handled personally instead, without ever losing automation for every other customer still on the books.
The detail
This capability sits deliberately apart from the books-of-account features elsewhere in Khata, and that separation matters a great deal. Payment reminders never alter the ledger — an invoice's recorded amount, due date, and payment status are exactly the same before and after a reminder goes out. What this tool does is nudge a customer toward paying an amount already recorded, using the channel they're most likely to read; it has no write access to the figures a CA would review, and makes no determination on whether an amount is owed or disputed.
Reminder content carries a specific compliance responsibility worth being deliberate about from the start. The message must never misstate a legal collections threat the business hasn't actually made or doesn't intend to pursue. A polite nudge naming the outstanding amount and linking to the invoice is straightforward; language implying legal action or credit-reporting consequences the business isn't prepared to pursue creates a real liability, separate from whether the amount is actually owed.
Delivery isn't guaranteed either, and the owner needs to know when it hasn't happened rather than assuming a reminder landed. A delivery failure — a wrong or disconnected number, a message blocked at the recipient's end — should surface as a failure the owner can see clearly, because the alternative is an owner falsely believing a nudge went out while a client relationship quietly sours over a payment nobody reminded them about. For a contractor managing a retention amount outstanding for weeks, knowing a reminder genuinely reached the client matters as much as sending it.
Industry use cases
12 industries where Khata applies this directly.
A car service center owner photographs a stack of spare-parts supplier invoices at month-end, Khata extracts the HSN codes and tax amounts from each, and the owner's CA opens the shared workspace to review the compiled purchase summary before filing.
See the automotive playbookA wholesale distributor pays several transport contractors during the month, and Khata flags which payments likely crossed the TDS threshold for Section 194C, compiling a worksheet the CA reviews before determining the actual deduction and filing.
See the b2b sales playbookA beauty product retailer sells both services and boxed skincare products, and Khata separates the two revenue streams in the ledger while calculating a consistent closing valuation for the unsold stock ahead of the CA's year-end review.
See the beauty and cosmetics playbookAn online tutoring business receives course-fee payments through multiple gateways during the month, and Khata reconciles each gateway payout against recorded receivables so the CA sees one consolidated income summary instead of three separate statements.
See the education playbookA freelance designer invoices three clients in a month and photographs a handful of software-subscription receipts, and Khata compiles both sides into a period summary the freelancer forwards to their CA before the quarterly GST filing.
See the freelancers and consultants playbookA physiotherapy clinic owner uploads a batch of supplier invoices for consumables, and Khata extracts amounts and HSN codes while keeping patient names on any attached billing documents restricted to the clinic's own staff and CA, not broadly visible in reports.
See the health and wellness playbookA furniture retailer with showrooms in two states ships a large order that crosses the e-way bill value threshold, and Khata pre-fills the consignment and HSN details from the invoice so the dispatch team only needs to generate the bill itself on the government portal.
See the home decor and furnishing playbookA marketing agency pays several freelance video editors as contractors during a campaign, and Khata's TDS worksheet flags the professional-fee payments likely requiring deduction under Section 194J for the CA's review before the agency deducts and deposits tax.
See the marketing agencies playbookA real-estate broker running two project-specific entities under separate GSTINs views a consolidated cash-position dashboard for planning, while their CA still receives two entirely separate GST summaries, one per GSTIN, for filing.
See the real estate playbookA restaurant owner's UPI and card settlements land in the bank account a day after the sale, and Khata's reconciliation queue matches each day's POS batch total against the corresponding bank credit, flagging any settlement that hasn't landed within the expected window.
See the restaurants and food playbookA spa sells packaged skincare products in addition to treatments, and Khata applies the correct HSN code to product line items and the correct SAC code to service line items on the same invoice, keeping the tax split accurate for the CA's review.
See the spas and salons playbookA travel agency books hotel and transport packages from several vendors for a client tour, and Khata's purchase-matching report shows which of those vendor invoices are already reflected in GSTR-2B, letting the CA hold back ITC claims on the ones that aren't yet visible.
See the travel and tourism playbookMore from Khata
A business owner stops losing paper receipts because every bill is captured the moment it's created, from a phone camera, a forwarded email, or a bulk upload.
Learn moreThe owner no longer types out every item, date, vendor, and amount from a receipt by hand — Khata reads it and fills the fields.
Learn moreThe business creates invoices that already carry the correct GSTIN, HSN/SAC code, and tax split so nothing needs re-keying at return time.
Learn moreEvery sale, purchase, payment, and receipt lands in a proper double-entry ledger instead of a loose spreadsheet or paper khata.
Learn moreEvery edit to the books is permanently recorded with who changed what and when, satisfying the statutory requirement companies already face.
Learn moreExpenses land in the right category (rent, salaries, supplies, utilities) automatically instead of the owner deciding from scratch every time.
Learn moreQuestions
No, not in any way. This is purely a collections communication tool — it never alters the ledger, the invoice's recorded amount, or its payment status in any way. It only sends a nudge referencing an amount that's already recorded there, so your books remain exactly as they always were, before and after any single reminder goes out to a customer.
Yes — reminders can be individually paused for any specific customer at any time you personally choose to do so, which is useful when a personal call or a more tailored approach suits that particular relationship better than another automated message. Pausing one customer's reminders doesn't affect the automation still running quietly for anyone else on the books at all.
Only if the business is genuinely prepared to follow through — reminder content should never imply a legal or collections threat that isn't actually intended, since that creates its own liability separate from whether the amount is genuinely owed at all. A factual, polite reminder naming the amount and linking to the invoice is the safer and generally more effective approach here.
Reminder history is logged per customer and invoice, showing what was sent and when it went out, and a delivery failure — a wrong number, a blocked message — should surface as visible rather than silent to the owner. Checking this history matters especially for a larger outstanding amount like a retention payment, where an unnoticed failure could cost weeks of delay.
The rest of your stack
No rip-and-replace — send payment reminders to customers works alongside the systems already running your business.
Coming soon