Tally Prime, Google Sheets and your own systems.
6 answers
Customers, bills and outstanding balances, from Tally Prime to VedLink.
A small connector runs on the machine where Tally is installed and pushes ledger data into VedLink. From there you can message customers about outstanding amounts with the real figure filled in.
Nothing is written back into Tally. The sync is one-way by design, so your books cannot be altered from the messaging side.
Enable Tally's HTTP interface, install the connector, paste your key.
Tally must be open on the machine while the sync runs.
Almost always Tally not running, the wrong port, or a company not selected.
Check in this order: Tally open with the right company loaded, HTTP interface enabled, port matching the connector, and no firewall blocking it.
If rows sync but some are skipped, open the report, each rejected row names the field that failed validation, usually a malformed phone number.
Read a sheet to build an audience; write back campaign and Flow results.
Connect your Google account once per company. VedLink can then read a sheet as a contact source and append rows as things happen.
Common pattern: the sheet your team already maintains stays the source of truth, and VedLink reads it before each send.
For data you want in the platform without wiring up Google.
Create a blank sheet and paste straight from Excel, or import a file. Datasets can back Flow responses and campaign audiences the same way a Google Sheet can.
Use a dataset when the data is only needed here; use Google Sheets when other people are editing it elsewhere.
Tally for accounts, Sheets for shared lists, the API for your own software.
If the data lives in your books, use Tally. If your team maintains it in a spreadsheet, use Sheets. If it lives in software you or a vendor built, use the API.
They coexist, plenty of accounts run all three against the same contact records.
Tell us the number, the time and what you expected. That is usually enough for us to spot it.