Key Highlights
- Auto-dispatch means every invoice saved in Tally fires automatically to the buyer's WhatsApp within seconds — no manual step, no forwarding, no accountant involvement
- Manual WhatsApp invoice sharing is the current norm for most Indian distributors; it creates a 4–24 hour gap between invoice creation and invoice delivery, which delays the payment clock by the same amount
- Auto-dispatch, combined with a UPI payment link on the invoice, measurably compresses Days Sales Outstanding for distributors with 20+ daily invoices
In This Article
- What auto-dispatch of invoices actually means
- How most distributors currently share invoices on WhatsApp
- What the manual process costs in time and collections
- How auto-dispatch works technically
- What changes when every invoice fires immediately
- Frequently Asked Questions
What Auto-Dispatch of Invoices Actually Means
When a distributor's accountant creates a sales invoice in Tally and saves it, two things happen. The voucher posts to the ledger. And, if auto-dispatch is configured, the invoice PDF is sent to the buyer's WhatsApp phone number — automatically, within 10–15 seconds, with no human action required.
No one opens WhatsApp. No one clicks forward. No one copies the PDF to their phone. The invoice leaves Tally and lands in the retailer's WhatsApp before the accountant has moved to the next entry.
That is the complete definition. The word "auto" in auto-dispatch means the trigger is the invoice save action, not a person.
How Most Indian Distributors Currently Share Invoices on WhatsApp
The dominant workflow today, across the distributors we interact with:
- Accountant creates invoice in Tally Prime on the office desktop
- Invoice is printed or exported as PDF
- PDF is shared to the office WhatsApp on mobile — either directly or via Bluetooth/USB transfer
- Accountant opens WhatsApp on the mobile phone, searches for the retailer's contact
- Sends the PDF with a message like "Invoice bheji hai, payment date par kar dena"
- Moves to the next invoice
At 10 invoices per day, this takes 15–20 minutes. At 30 invoices, it takes 45–60 minutes. At 50 invoices — common for a mid-sized FMCG distributor — it occupies 60–90 minutes of the accountant's day, every day.
And this is assuming the accountant does it on the same day. Many distributors share the previous day's invoices in the morning. Which means the retailer's payment clock is running 18–24 hours behind actual delivery.
What the Manual Process Costs
| Volume (invoices/day) | Manual sharing time/day | Annual time cost | Invoice delay (average) |
|---|---|---|---|
| 10 | 15–20 min | ~90 hours | 2–4 hours |
| 25 | 35–45 min | ~190 hours | 4–8 hours |
| 50 | 60–90 min | ~340 hours | 12–24 hours |
| 80+ | 90–120 min | ~470 hours | 12–24 hours |
Beyond time, the manual process has a reliability problem. If the accountant is out sick, invoices do not go. If the WhatsApp account is on one phone and that phone is with the owner, invoices do not go. If a batch of invoices was created on Saturday afternoon, the retailer gets them Monday morning.
A Guwahati electrical goods distributor told us the invoice delay on Saturday batches was consistently three days. The retailer's credit clock did not start until Monday. For invoices on 30-day credit, that pushed actual collection to day 33 by default, before any late payment was even counted.
How Auto-Dispatch Works Technically
Tally Prime exposes a real-time API. When a voucher is saved, the system can trigger an outbound event. A companion app or integration layer catches that event, formats the invoice as a PDF or structured message, and routes it through a WhatsApp Business API-connected number.
The key components:
- Tally connector — a lightweight service running on the office PC that listens for new voucher events via the Tally XML gateway
- WhatsApp Business API — a verified business number registered with Meta's API (not the regular WhatsApp app; this is the API for automated messaging)
- Invoice formatter — the service that takes the Tally voucher data and produces the PDF and message content
- Delivery confirmation — the WhatsApp API returns a delivery receipt, which can be logged against the invoice
For the accountant or owner, none of this is visible. They create the invoice in Tally normally. The dispatch happens in the background.
What Changes When Every Invoice Fires Immediately
Payment clock starts at invoice creation, not hours later
For a retailer on 30-day credit, the payment due date is calculated from when they receive the invoice. An invoice dispatched at the moment of creation — 2 PM — starts the clock at 2 PM. An invoice forwarded manually the next morning starts the clock 18 hours later. Over 300 invoices per month, that compounding delay is a real DSO drag.
Disputed invoices surface faster
When the retailer receives the invoice immediately, they can raise disputes immediately. A quantity discrepancy, a wrong rate, a wrong GST code — these come back within hours instead of at payment time. Resolving them at invoice-creation time is faster and less contentious than resolving them on day 28 when the payment is due.
Accountant time shifts to higher-value work
60–90 minutes of daily invoice forwarding is not skilled work. Eliminating it does not reduce headcount — it shifts the accountant's attention to reconciliation, credit limit reviews, and exception management. Distributors who make this shift report the accountant's day feeling materially less pressured within two weeks.
The invoice becomes a payment request, not a record
When auto-dispatch includes a UPI payment link embedded in the invoice message, the invoice arrives as both a record and a payment prompt. The retailer sees the amount, sees the due date, and has a one-tap payment option. The friction between "received invoice" and "made payment" collapses.
A pharma distributor in Dibrugarh with 45 daily invoices shared a before/after from six months of operation: average collection time on invoices with UPI links went from 38 days to 29 days. No change in credit terms, no change in retailer mix, no collection calls added. The link moved the number.
Frequently Asked Questions
Q: Does auto-dispatch require a separate WhatsApp number?
A: Yes. Auto-dispatch uses the WhatsApp Business API, which runs on a dedicated business phone number registered with Meta. This is different from the WhatsApp Business app on a phone. The API number cannot send or receive personal messages — it is a programmatic channel only. Your accountant's or owner's regular WhatsApp number is unaffected.
Q: What does the retailer actually receive — a PDF or a message?
A: Both. A properly configured auto-dispatch sends a message with the key invoice details (party name, invoice number, amount, due date, UPI link) and attaches the PDF for the retailer's records. The PDF is the same format as your existing Tally print template. Retailers who want to file it digitally can do so from WhatsApp directly.
Q: What happens if the retailer's WhatsApp number changes?
A: The dispatch system pulls the phone number from the party master in Tally. If the number in Tally is outdated, the message will fail delivery and a failed-delivery log should flag it. This is why keeping party contact details current in Tally matters more once auto-dispatch is live.
Q: Can I auto-dispatch only to some parties and not others?
A: Yes. Most implementations allow per-party opt-in or opt-out in the party master. Some large retailers prefer invoice delivery by email or through their own procurement system — those parties can be excluded from WhatsApp auto-dispatch without affecting the rest.
Q: What is the cost of WhatsApp Business API messages?
A: Meta charges per conversation on the API. A conversation is any exchange within a 24-hour window. Business-initiated messages (like invoice delivery) are charged at the template message rate, which is typically ₹0.50–₹0.80 per conversation. At 50 invoices per day, this is ₹750–₹1,200 per month in messaging costs. Some companion apps bundle a message pack; others pass the API cost through. Confirm before buying.
Q: Does auto-dispatch work with GST-compliant invoices including e-invoice IRN?
A: Full-stack apps that support e-invoice generation from mobile also support auto-dispatch of the IRN-stamped invoice. The flow is: invoice created → IRN fetched from GSTN → IRN embedded in invoice → invoice auto-dispatched to WhatsApp. The retailer receives the compliant invoice, including the QR code with embedded IRN, before goods are even unloaded.
Takkada's Full Access plan auto-dispatches every Tally invoice to the buyer's WhatsApp the moment it is saved — including e-invoices, with UPI payment links, and delivery confirmation logged against each voucher. Book a free demo.