Your working capital is sitting in bills nobody is chasing.
A distributor selling on credit does not have a sales problem and a collections problem. It has one follow-up problem, split across two teams, two tools and a spreadsheet that is correct for about a day a month.
Ageing is a monthly ritual, not a number
Somebody exports from Tally, pastes into a sheet, sorts by days, colours the bad rows and mails it round. By the time it is read it is describing last week. Between two of those exports, nobody in the business can say what is overdue right now.
The person selling cannot see who has not paid
The salesman walks into a shop and takes another order. The ledger says that shop is months late on two bills. Those two facts live in different systems, so the conversation that should have happened does not.
Orders arrive on somebody’s personal phone
Half the order book comes in on WhatsApp, across three phones, and is re-keyed later from memory. When that person is on leave, the messages are on a device nobody else can open.
A receipt lands and the bill stays open
A payment posted on account and never matched against a bill leaves the party balance looking settled while individual bills sit open forever. It is the single most common reason an ageing report and a ledger disagree.
Collections and sales are the same conversation.
Look at what actually happens to one bill. At every step the question is the same — who speaks to this party next, and do they know the number before they call.
The bill goes out
Raised in TallyPrime, as it always has been. Nothing about the way your accountant works changes, and Tally stays the ledger of record.
- ·No migration, no re-keying
- ·Your existing company data, read as it is
The due date passes
This is where most businesses lose the thread. The bill is now overdue in Tally and nowhere else — not on a dashboard, not in anyone’s morning list.
- ·Bill-wise ageing in 0–30, 31–60, 61–90 and 90+ buckets
- ·Unmatched on-account receipts flagged, not hidden
Somebody has to ask for the money
Usually the owner, usually on WhatsApp, usually after re-reading the ledger to get the figure right. That step is a tap when the figure and the statement are already on the phone.
- ·Remind a party, or one specific bill
- ·The outstanding statement goes with the message
The same party is being sold to
The order and the overdue bill belong to one relationship. Put the balance next to the deal and the follow-up stops being two teams guessing at each other.
- ·The overdue figure sits where the deal is worked
- ·One decision: supply now, or collect first
Two products do most of this work already.
Comsky TallyBridge and Comsky CRM are live. You can put both in front of a distribution team this week, on your existing books.
Outstanding, on the phone, as of a stated time
TallyBridge reads your TallyPrime data through a small Windows connector and syncs it to a secure cloud. Party-wise receivables and payables, bill-level drill-down, and an explicit “as of” timestamp on every screen so nobody quotes a stale figure in a meeting.
One tap sends the reminder
Remind a party, or one bill, over WhatsApp, SMS or email with the statement attached. Email reminders carry no per-message billing. WhatsApp and SMS show you the cost before the message goes — you are never surprised by a messaging bill.
The morning number, without the export
A daily summary of overdue, collections and sales, plus alerts on large payments and on the overdue thresholds you set. The monthly ageing ritual stops being the only time anyone looks.
Pipeline that knows about the ledger
Comsky CRM holds deals, contacts, companies, tasks, email and sequences on one record. Put a distributor’s outstanding position alongside the open deal and the salesperson walks in already knowing what to ask for.
A sync that cannot double-count
Incremental sync on per-entity cursors with replay-safe batch keys. A retried batch lands on the same keys rather than posting a voucher twice. Sync logs and a data inspector show exactly what arrived.
A read-only seat for your CA
Owner, accountant, viewer and read-only CA roles, scoped per company. Your CA sees the company you invited them to and nothing else on the account, and you revoke the seat when the filing is done.
TallyBridge is read-only until you switch write-back on. Until you do, the connector holds no permission to write anything into Tally — which is usually the first question an accountant asks.
The spreadsheet against the same books, read properly.
Nothing in the middle column is a competing product. It is what a distribution office does on a Tuesday, and it is the thing actually being replaced.
| Ageing in a spreadsheet | A CRM with no ledger | Comsky | |
|---|---|---|---|
| What is overdue right now | Whatever the last export said | Not represented at all | Bill-wise ageing in 0–30, 31–60, 61–90 and 90+ buckets, with the last sync time on screen |
| Sending the reminder | Re-read the ledger, retype the figure | A task with no amount attached | One tap, statement attached, over WhatsApp, SMS or email |
| Salesperson sees the balance | Only if somebody forwards the sheet | No — the ledger is elsewhere | The outstanding position sits next to the deal being worked |
| Receipt posted on account | Quietly wrong until quarter end | Invisible | Flagged as an open bill the ledger balance no longer shows |
| Your ledger of record | TallyPrime, plus a second set of numbers | A third set of numbers | TallyPrime, unchanged. Read-only until you enable write-back |
| Who can see it | Whoever is on the mail thread | Whoever has a licence | Owner, accountant, viewer and read-only CA, scoped per company |
Two more products are being built for this exact loop.
Comsky Chat and Comsky Telephony are not running today. They are described here because they are being built against the retail problem, and because you should know what is coming before you commit to the two that are live.
Chat: the order book stops living on a phone
Comsky Chat will put web chat, WhatsApp and email in one shared inbox, with each conversation attached to the customer record it belongs to. Orders taken on WhatsApp become something the whole office can see, not something one person remembers.
Chat: the reminder gets a reply somewhere useful
A payment reminder that lands on WhatsApp gets answered on WhatsApp. When Chat ships, that reply arrives in the same inbox as everything else from that party rather than on the sender’s personal phone.
Telephony: the collection call leaves a trace
Comsky Telephony is being built to match a caller to the record before the call is answered, and to write the recording and the outcome back onto it. A chased party will show what was said and when it was promised.
Telephony: routing that knows the account
Virtual numbers, IVR and routing running on Indian carriers, DLT-compliant, wired into the same customer records the CRM uses. One user list across the suite rather than a separate phone system to administer.
We are not going to pretend a waitlist is a product. If your decision depends on Chat or Telephony being in your hands, ask us where they actually stand before you buy anything.
What distributors ask first.
Do we have to leave Tally?
No, and that is the point. TallyPrime stays on the machine your accountant already uses and stays the ledger of record. A signed Windows connector reads it and syncs to the cloud. Nothing is migrated and nothing is re-keyed.
Can it write back into Tally?
Yes, once you enable it per company. A receipt, invoice or payment raised on the phone or the web joins a push queue and posts when the connector next polls. Until you switch it on the connector holds no write permission at all.
What does the salesperson actually see?
Comsky CRM holds the deal, the contact and the activity history. Put the party’s outstanding position next to it and the person walking into the shop knows the balance before the conversation starts — which is the whole argument for running both products on one account.
Will it send reminders on WhatsApp by itself?
It sends when you tap. Reminders go to a party, or to one specific bill, over WhatsApp, SMS or email with the statement attached. Email carries no per-message billing; WhatsApp and SMS show the cost before the message goes.
We have several companies in Tally. Does that work?
Yes. You pick the companies the connector syncs, each gets its own sync key, and roles are scoped per company rather than per account. The phone and the web console both switch between them.
Where is the data stored?
In Indian infrastructure, with argon2id password hashing, token rotation and audit logging. The tenant is pinned from the verified token rather than from anything in a request, so a cross-tenant read fails rather than returning somebody else’s books.
Is there a collections workflow with payment links?
Not today. We can show you what is overdue and we can nudge the party; we cannot take the money for you yet. Anyone who tells you their reminder tool collects on its own is describing a payment gateway they have bolted on.
Chase the bill and the order in one place.
Start with your existing TallyPrime books. Bill-wise outstanding, one-tap reminders, and a pipeline that knows who has not paid.
Four products are live today. Chat and Telephony are not — ask us where they stand.