Dhruva · Accounts Receivable Automation & Collections Agent

Your money is already earned. An AI agent goes and gets it.

Collections doesn’t fail because nobody shouts loud enough. It fails because follow-up depends on who remembered. Dhruva is accounts receivable software that reads your receivables from SAP, chases every overdue account on your policy every week, reads the replies, and holds every promise to the day. Your team approves. Built for Indian businesses.

Book a free 20-min AR review See the agent work

Read-only by default · nothing sends without a human · reads your SAP · TDS, cheque & PDC aware

dhruva · today’s runlive

CHASE

Customer A · 3 invoices, 41 days

One letter for the account, not three for the invoices

₹6,75,000

PROMISE

Customer B · “we’ll clear by the 25th”

Read from the reply · reminders paused · timer set to the day

25 Aug

DISPUTE

Customer C · 40 of 200 drums short

Only the disputed slice pauses. The rest keeps getting chased

₹18,400

QUEUE

9 letters ready for your approval

1 escalation · 2 accounts already paid, dropped from the list

draft

0 skipped

accounts that drop off the list because someone was busy, on leave, or out of time

To the day

every promise carries a date, an amount and an owner, on a timer, not in a diary

1 letter

eight overdue invoices still means one letter. The cap is per customer, not per invoice

The problem

You’ve already done the work. The cash is sitting in someone else’s bank.

The goods shipped. The invoice went out. Now the money is somebody’s follow-up job: a Monday ageing report, a spreadsheet, and whoever has time to call. So the loudest accounts get chased and the quiet ones slide. A promise made on a call lives in a diary until everyone forgets it. Meanwhile your good customers get chased for an invoice they paid last week. This doesn’t need more aggression. It needs someone who never forgets and never skips a week.

Why the name

Dhruva. The one that doesn’t drift.

The boy who was denied what was rightfully his

In the story, the boy Dhruva is turned away from a place that was his. He doesn’t rage and he doesn’t give up. He holds his ground so steadily that he’s made permanent: the pole star, the one fixed point the whole sky turns around. Every other light drifts. Dhruva doesn’t.

That’s the collections job. You were denied what you had already earned. What gets it back isn’t a harder phone call. It’s steadiness no human can keep by hand: the same policy, on every account, every week, remembering every promise you were made.

The shift

Follow-up isn’t a phone call. It’s a pattern.

Ten accounts down the side, ten weeks across. Every mark is one contact. This is the ledger when chasing depends on who had time, and what it becomes on a policy. Watch the rows end early. That’s the book draining.

The receivables ledger · 10 accounts × 10 weeks Coverage 13 touches in 10 weeks

How the agent works

One agent. One job. Every account.

Dhruva doesn’t blast a mail-merge. As accounts receivable automation software, it reads the ledger, works out what each account owes, checks itself against your books before it speaks, then hands your team the call.

READS

Your ledger

Pulls open invoices, credit notes, part-payments and real due dates from your SAP every night.

UNDERSTANDS

Each account

Groups a customer’s invoices into one conversation, and sets the tone by how they actually pay.

CHECKS

Before it speaks

Re-checks the live balance at the moment of sending. If money landed overnight, the letter is stopped.

ACTS

Chases & escalates

Sends the reminder or hands you a ready letter, then moves up the ladder when a promise breaks.

LEARNS

Who keeps their word

Scores every kept and broken promise, so next month’s chase starts from the truth, not a hunch.

Best of both worlds

Product speed. Your rules.

You shouldn’t have to choose between a rigid SaaS box and years of custom build. Dhruva is both.

Switch it on

A specified agent, not a blank page

The collections engine, the rule book, the approval layer and the SAP connector are already designed and built. You’re configuring a working system on the SAP you already run, not funding a discovery project.

Shape it to you

Your ladder, your tone, your patience

How many days before the first nudge, who signs off a firm letter, how much rope a PSU gets versus a distributor, which accounts a machine may never write to. All of it is configuration, not code.

Governance, not vibes

Relentless with the ledger. Careful with the relationship.

These are the three promises that let you point an agent at your own customers. Autonomy is a dial you set, and it starts at zero.

Nothing sends alone

Read-only by default. The agent drafts; a named person releases anything that reaches a customer. Your key accounts can be set so a machine never writes to them at all.

It never chases a wrong number

Every figure is re-checked against your live SAP in the second before sending. If a payment landed overnight, the letter is stopped and rebuilt, never sent stale.

It never harasses

A weekly contact cap per customer, business hours only, and the moment a customer disputes an amount, that amount stops being chased. The rest still is.

Why it fits Indian manufacturers

Built for how you actually get paid

Native SAP Business One on HANA, on-prem or cloud
TDS-aware: a payment short by exactly the withheld tax is settled, not chased
Cheques and PDCs logged on handover, tracked to clearing. A bounce reopens the invoice
The call happened on WhatsApp? Log it in one form and the agent acts on it
Statements show both sides: credit notes and part-payments, not a one-sided demand
Distributors, OEMs, PSUs and exporters each get their own patience

What changes in weeks

Follow-up stops depending on who remembered
Every promise carries a date, an amount and an owner
Disputes surface in days, not at month-end reconciliation
Good customers stop being chased for invoices they’ve paid
One approval queue on Monday, not a hundred WhatsApp threads
DSO falls because the boring part finally happens every week

Questions finance teams ask

Accounts receivable automation, answered

Does Dhruva work with SAP and my existing ERP?

Yes. Dhruva runs natively on SAP Business One on HANA, on-prem or cloud, and reads your open invoices, credit notes and part-payments straight from the ledger every night. There is no rip-and-replace.

How does accounts receivable automation reduce DSO?

DSO falls when every overdue account gets chased every week, not just the loud ones. Dhruva runs that follow-up on a policy, holds every promise to its date and never skips a week, so cash arrives on a rhythm instead of whenever someone finds the time.

How is this different from a payment reminder tool?

A reminder tool sends the same nudge on a schedule. Dhruva is payment collection software that reads each account, groups a customer’s invoices into one conversation, re-checks the live balance before it speaks, pauses a disputed amount while still chasing the rest, and escalates when a promise breaks.

Is Dhruva a debt-recovery agency?

No. Dhruva is accounts receivable software your own team runs. It drafts and chases on your rules, and nothing reaches a customer until a named person releases it. It is not a recovery agent and it never harasses.

Does it handle TDS, PDC and cheque payments?

Yes. A payment short by exactly the withheld tax is treated as settled, not chased. Cheques and PDCs are logged on handover and tracked to clearing, and a bounce reopens the invoice.

Start here

Book a free 20-minute AR review

Tell us your overdue book and your SAP setup. We’ll show you which accounts are sliding today, what weekly follow-up is worth in rupees, and where your DSO could land. No pitch, no rip-and-replace.

Book my AR review →

20 minutes · no pitch · you leave with a number