Where you tell MISAC which machine Tally is running on, and which company inside Tally to read from and write to.
When to use it
Once per fiscal year, before anyone tries to pull masters or push vouchers to Tally. Come back when Tally moves to a different machine, or the company in Tally is renamed.
Before you start
- Tally must be running, with a company open and its XML listener switched on (in Tally: Gateway of Tally, F12, Advanced Configuration).
- The MISAC server must be able to reach that machine over the network. The server makes the connection, not your browser, so reaching Tally from your own desk proves nothing.
- Have the exact company name as it appears in Tally, and the fiscal year this connection is for.
Where to find it
Setup > Integrations > Tally Server Setup.
The fields on this screen
| Field (on screen) | What to enter | Required |
|---|---|---|
| Fiscal Year | The fiscal year this Tally connection is for. Sync picks the row for the current year, so keep one per year. | No |
| Site Name | (not explained yet) | No |
| Company Name in Tally | The company name exactly as it is in Tally. Masters and vouchers are read from and written to it. | No |
| Server Hostname | Name or address of the machine running Tally. Left blank, the sync refuses to run. | No |
| Server Port | Port that Tally's XML listener answers on. Left blank, 9000 is used. | No |
How it works
Every Tally action looks the connection up here, on the server, for your company and fiscal year. That covers testing the connection, listing companies, pulling masters, pushing or pulling vouchers, and running an export template. Nothing a user or a script sends can point the connection somewhere else. That is on purpose, and it means this screen is the only place the connection can be changed.
Keep exactly one row per fiscal year. When no year is asked for, the row for the fiscal year that covers today is used. If more than one row exists for the same year, the most recently added wins, and the older ones look valid while doing nothing.
What happens when a setting is wrong:
- No row at all for the current fiscal year: every Tally action stops with a message that there is no configuration for this company and fiscal year. This is the usual symptom on the first working day of a new year.
- Server Hostname left blank: the action is refused before anything is attempted, with a message that the server host is missing.
- Server Port left blank: port 9000 is used, which is Tally's normal port. Fill it in only if your Tally listens on another port.
- Company Name not matching Tally exactly: the connection succeeds but the pulls come back empty. An empty master pull almost always means a mistyped company name, not a network problem.
Site Name is stored but not used. The connection is built from the hostname, the port and the company name only, so setting a site here does not restrict or route anything.
Saving changes nothing by itself. It takes effect on the next Tally action anyone runs.
Tips and common mistakes
- Copy the company name from Tally instead of typing it. Trailing spaces and a stray full stop are the two that catch people.
- Roll the row forward at year end. A connection that worked all last year goes quiet on the day the fiscal year turns over, and the message will point at the year, not at Tally.
- Before trusting a two-way sync with real data, push a handful of vouchers, pull the same date range back, and compare the amounts, dates and account names.
Related guides
See also Integrations, and the Ledger and Product masters that the pulls are checked against.