What “Tally to Google Sheets” means on this page
Tally to Google Sheets, here, means taking figures out of TallyPrime (the accounting software from Tally Solutions) and placing them in a Google Sheet on a timetable, so that people who are not sitting at the Tally computer can read them. It is a reporting feed, one way only.
Search results for this phrase are crowded with a different product: Tally Forms at tally.so, an online form builder with its own Google Sheets connector. If you want form responses in a sheet, that is a two-minute setting inside the form tool and you do not need a developer. The rest of this page is about accounting data.
The typical person asking for this is a business owner or partner who travels, runs several branches, or simply does not want to call the accountant three times a day. They already trust Tally for the books. What they lack is a way to see today’s numbers from a phone without logging into the office machine.
Sending data the other way, from sheets into Tally, is a separate job covered on our Excel to Tally import page.
Can Tally export directly to Google Sheets?
Not by itself. TallyPrime can export a report to Excel, PDF or other formats when a user clicks Export, but it has no switch that keeps a Google Sheet updated. Getting Tally to Google Sheets automatically needs a small program that asks Tally for data and hands it to Google.
Tally Solutions documents two doors for that program. The first is Tally’s HTTP server: TallyPrime listens on a port you configure (their help pages use 9000 as the example) and answers XML requests for reports, ledgers and vouchers. The second is ODBC, which Tally can enable from the same connectivity settings, letting tools that speak ODBC read Tally collections like database tables. Either way, Tally’s prerequisites are explicit: TallyPrime must be running with a company loaded.
There are also marketplace add-ons that claim to sync Tally reports to Sheets. They can be fine for a standard report on a single company. People come to us when they need a specific report layout, several companies combined, or when their IT policy does not allow a third-party service to hold their accounting data.
So the honest answer to “can Tally export to Google Sheets” is: manually, yes, one file at a time; automatically, only with a connector, either bought or built.
Which Tally reports are worth sending to a sheet?
Send the handful of figures that change what you do today. A Tally to Google Sheets feed that copies every report ends up unread; one that answers four questions gets opened every morning.
The reports owners actually use, in rough order of how often we are asked for them:
- Outstanding receivables with ageing: who owes money, how much, and for how long. The sales team’s call list for the day.
- Day and month sales: totals by branch, salesperson or item group, compared with the same period last month.
- Cash and bank position: closing balances of each bank and cash ledger, so you know what you can pay today.
- Stock summary with reorder flags: items below a minimum level, per godown.
- Payables due this week: supplier bills falling due, to plan payments.
- Top customers and items: a monthly ranking that shows where profit really comes from.
Write your list as questions (“Which dealers are over 60 days?”), not report names. We then decide which Tally collection answers each one most cheaply, and which figures can be calculated in the sheet instead of asked from Tally every hour.
Method one: scheduled ODBC reads
ODBC suits tabular data such as ledgers with closing balances, stock items with quantities, and voucher registers for a date range. The agent opens an ODBC connection to Tally on a schedule, runs queries against Tally’s exposed collections, and pushes the rows to the sheet.
Its strengths are simplicity and familiarity: any analyst who has used Excel’s data connections understands the idea, and many reports are one query. Its weak points show up with calculated reports. Ageing, for instance, is something Tally computes on screen from bills and due dates; reproducing it from raw ODBC rows means recreating Tally’s logic, which is possible but has to be checked against Tally’s own figure.
ODBC reads also depend on the 32-bit or 64-bit driver matching the tool reading it, a small detail that trips up many do-it-yourself attempts on Windows. We install and test the right driver on your Tally machine as part of setup.
Use ODBC in your Tally to Google Sheets feed when the figures you want are closing balances, masters or registers, and when you are happy to do a little calculation in the sheet.
Method two: XML requests to Tally’s HTTP server
The XML route asks Tally for a report the way a user would see it. The agent posts an XML envelope naming a report (a trial balance, a bills receivable report, a stock summary) with a date range and company, and Tally replies with the figures it has already calculated.
That is the main reason we lean on XML for owner reports: the ageing buckets and totals come from Tally itself, so the sheet matches what your accountant sees on screen. If your Tally has TDL customisations that add fields or reports, XML can usually ask for those too.
The trade-off is size. A full-year day book as XML is large and slow to generate, so we request in date slices and cache results. For heavy history we mix methods: XML for the calculated owner reports, ODBC or voucher exports for bulk rows that feed trends.
Both methods are read-only in our setup. The agent never sends an import request, which means a mistake in the reporting feed cannot change a single entry in your books. If you later want writes (for example orders from an app), that is a separate project described on our Tally API integration page, with its own safeguards.
Where the sync script should run, and why Apps Script alone is not enough
The part that reads Tally must run on the same network as Tally, usually on the Tally PC itself. Google Apps Script lives in Google’s cloud and cannot reach a computer sitting behind your office router, so a pure Apps Script solution cannot fetch Tally data on its own.
We therefore split the job. A small agent on the Tally machine reads Tally and pushes data outward to Google over an encrypted connection. Nothing needs to connect into your office, so no router port is opened and Tally’s HTTP server stays reachable only from the local machine.
Apps Script still has a role on the sheet side: formatting, highlights, alerts, and small calculations. Google’s published quotas are worth knowing when you design it. A single script execution is limited to 6 minutes, and time-driven triggers get 90 minutes of total runtime a day on consumer accounts versus 6 hours on Google Workspace accounts. That is why heavy lifting stays in the agent, and sheet scripts stay light.
If your Tally already runs on a cloud virtual machine, the agent simply runs there. For owners considering that move, our cloud hosting setup page explains the choices.
How often should Tally data refresh in Google Sheets?
Hourly during business hours is right for most owners; once a morning is enough for ageing and stock. Refreshing every minute sounds attractive but loads Tally while your staff are billing, and figures rarely change that fast in a way that matters.
A sensible schedule for a Tally to Google Sheets feed looks like this:
- Sales and collections: every hour from opening to closing time.
- Cash and bank balances: at 11 am and 4 pm, before payment runs.
- Outstanding with ageing: once, early morning, before sales calls.
- Stock below reorder level: morning and mid-afternoon.
- Monthly history tabs: overnight on the first of the month.
Each sheet shows a “last updated” cell with the time of the last successful run. If Tally was closed, that time simply stays old, which is more honest than showing stale numbers as if they were fresh. When Tally is found closed during business hours, the agent can send one alert to a named person rather than failing silently.
Remember that Tally has to be open with the company loaded for any refresh to happen. If the office PC shuts down at 7 pm, the evening figures arrive with the first run next morning.
Designing the Google Sheet so it stays fast
Keep raw data and the owner’s view on separate tabs. The agent writes only to raw tabs; formulas and charts on a summary tab read from them. That way a refresh never breaks your layout, and anyone can add a chart without touching the feed.
Decide per tab whether data is overwritten or appended. Balances and ageing are snapshots, so overwrite them each run. Sales by day is history, so append new days and leave old ones alone. Mixing the two is the most common reason a home-made sheet slowly shows wrong totals.
Size matters too. Google’s help centre states a spreadsheet can hold up to 20 million cells. That sounds endless until a feed appends every voucher line of a busy business for three years. For history at that scale we keep item-level detail in a small database or in yearly files, and only daily totals in the owner’s sheet, so it opens quickly on a phone over mobile data.
Finally, freeze header rows, format rupee columns in the Indian lakh style if you prefer it, and name ranges used by the dashboard. These small touches are what make a sheet readable at a glance rather than a dump of Tally exports.
An owner dashboard in Looker Studio
A dashboard turns the Tally to Google Sheets feed into a one-screen answer. Looker Studio, Google’s reporting tool (its current documentation refers to it as Data Studio), connects directly to Google Sheets, so the same data that lands in your sheet can drive charts without another export.
A practical owner dashboard has four blocks: today and month-to-date sales against last month; receivables by ageing bucket with the ten largest overdue parties; cash and bank position; and items below reorder level. Filters for branch and date sit at the top. On a phone, blocks stack vertically so nothing needs pinching and zooming.
Google offers a paid Pro edition. Its documentation lists features such as organisation-owned reports, team workspaces, scheduled delivery to more recipients, and access through the Looker mobile app. Most owner-managed businesses do well with the standard version; the Pro features start to matter when several managers build and share reports and you want ownership to stay with the business when someone leaves.
If you already live in Microsoft tools, the same sheet or an Excel file can feed Power BI instead; see our Power BI dashboard cost page for what that involves.
How to see Tally data on your phone without remote desktop
Open the Google Sheets app or the dashboard link; that is the whole routine once the feed is running. No remote desktop session, no Tally licence on the phone, and no risk of accidentally altering an entry from a small screen.
A few details make phone use comfortable. The summary tab is built narrow, with large figures and short labels, so it reads well in portrait mode. Party names that are long in Tally get a short display column. Conditional colours mark overdue amounts. The dashboard link can be bookmarked to the home screen so it opens like an app.
Owners who prefer not to open anything can receive a short morning message instead: yesterday’s sales, collections, and the three largest overdue parties, sent by email or over WhatsApp with a link to the full sheet. Our Google Sheets to WhatsApp page covers how those messages are sent and what the WhatsApp side costs to run.
If your team needs to act on the data (mark a call made, add a note to a party), that can live in a separate tab they edit, while the Tally-fed tabs stay protected so staff cannot overwrite them.
Is it safe to put Tally data in Google Sheets?
It can be, if you control who sees the sheet and how the data gets there. The risks are rarely Google’s servers; they are a sheet shared with “anyone with the link”, an ex-employee still on the access list, or a script key left in a shared folder.
The safeguards we build into every Tally to Google Sheets setup:
- The sheet belongs to your Google account, shared only with named people. Link sharing stays off.
- The agent writes using a dedicated service account that can edit only the target sheets, and whose key you can revoke in one click.
- The agent reads Tally; it never sends import or alter requests.
- Tally’s HTTP port is not opened to the internet. All traffic goes outward from your office to Google.
- Only the columns you need are sent. If you do not want bank account numbers or staff salaries in the cloud, they never leave Tally.
- Two-step verification on every Google account with access, which you switch on in your account settings.
We are not auditors and do not certify security. If your business has formal data policies, share them at the start and we will design to them, and your own IT or legal adviser should approve the setup.
Tally to Excel instead of Google Sheets
Choose Excel when your owner and accountant already work in Microsoft 365, or when your group uses Power BI. The agent can write the same scheduled reports to an Excel workbook in OneDrive or SharePoint instead of, or as well as, a Google Sheet.
Excel on the Tally PC itself can also pull Tally data through ODBC with a data connection and a refresh button. That is a perfectly good setup for an accountant sitting at that machine. It stops being useful the moment the owner is travelling, because the workbook lives on a desktop that is not reachable. Moving the refreshed file to OneDrive on a schedule fixes that.
Google Sheets wins when several people outside the office need to view the figures on phones, when you want free dashboards through Looker Studio, or when staff use Gmail-based accounts anyway. Excel wins for heavy pivot work and for teams already paying for Microsoft 365.
You do not have to choose for ever. Because the agent is ours to configure, switching destination later is a settings change, not a rebuild. Many clients start in Sheets and add an Excel copy for the auditor at year end.
How much does Tally to Google Sheets automation cost?
A scheduled Tally to Google Sheets feed with a few core reports starts at ₹40,000 (US$600) with BtechWaleTech. Google Sheets itself costs nothing extra on a normal Google account, and Looker Studio’s standard version has no licence fee, so ongoing running costs are usually close to zero unless you choose a cloud VM for Tally.
Price drivers, in order of impact:
- Number of Tally companies or separate branch PCs to read.
- Calculated reports that must match Tally exactly, such as ageing with custom buckets.
- Item-level history kept for trends over several years.
- A multi-page dashboard with filters and drill-downs.
- Alerts by email or WhatsApp.
- Excel output alongside Google Sheets.
Rates from other freelancers and vendors vary widely, largely depending on whether they reuse a generic export or build to your report list. Ask each for a sample sheet built from your own Tally data before committing. Our itemised quote arrives within about two working days, and nothing is billed before your written approval.
Worked example: a distributor with three branch PCs
This is a made-up scenario to show the pieces working together. Imagine a paint and hardware distributor with a head office in Raipur and branches in Bilaspur and Durg, each running its own Tally company on its own PC. The owner spends mornings on calls asking each branch for sales and dues, and the figures arrive in three different formats.
The setup: one agent on each branch PC, each reading four reports through XML (sales by day, bills receivable with ageing, stock below reorder level, cash and bank balances) every hour from 9:30 am to 8 pm. All three write to one Google Sheet with a raw tab per branch. A consolidated summary tab adds them up, and a Looker Studio report shows the group view with a branch filter. The owner and two partners have access; branch managers see only their own branch through a separate filtered report.
If a branch PC is off, its “last updated” time stays old and the owner gets one alert. No branch can change another branch’s data, and nobody can change anything in Tally from the sheet.
For a setup like this the quote would start at ₹40,000, with the second and third branches and the dashboard listed as separate lines, and a typical delivery time of three to four weeks.
Checklist before you commission a Tally to Google Sheets sync
Answer these before you talk to any developer; they decide both price and whether the result will actually be used.
- Which five questions should the sheet answer every day?
- Which Tally release do you run, on which PC, and is it on all business hours?
- How many Tally companies or branch machines are involved?
- Who should see what? List people and the branches they may view.
- Which data must never leave Tally (salaries, bank details, specific ledgers)?
- How fresh is fresh enough: hourly, twice a day, or daily?
- Google Sheets, Excel, or both?
- Who will check the first two weeks of figures against Tally on screen?
Red flags when comparing offers: anyone asking you to open Tally’s port on your router, anyone storing your data on their own servers without saying so, and anyone who cannot show a sample built from your data before you pay in full.
Tally to Google Sheets setups across India
Tally is everywhere in Indian business, and so is the owner who is not at the Tally PC. We set these feeds up remotely for distributors in Nagpur and Raipur who supply several districts, traders in Guwahati serving the North East, and wholesalers in Patna and Vijayawada with branch godowns.
Manufacturers in Nashik and Jamshedpur want daily dispatch and dues figures, and multi-outlet retailers in Madurai and Dehradun want each outlet’s takings by evening. The method is the same everywhere; what changes is the report list and the number of Tally machines.
We talk on WhatsApp or video calls in English or Hindi, and install the agent over a remote session on your Tally PC. There is no need for anyone to visit, and your books never move from where they are today.