Tally Connector — Live Two-Way Sync

What the Connector Does

Tally can act as a small HTTP server. Switch that on and it will accept XML requests and answer with your data — that is the door the ERP Connector walks through. Nothing is exported to disk and nothing is re-typed; the two programs talk to each other while both are open.

Four buttons, and that is the whole screen:

Everything runs locally between the two programs. No AI credits are used, and no data leaves your computer.

Connector vs XML File

iAccounting can move Tally data two ways. Both end up in the same place — pick by situation:

Step 1 — Turn On Tally's Gateway (One Time)

Tally will not answer until you tell it to act as a server. Do this once:

TallyPrime

1. Press F1 (Help) → Settings → Connectivity → Client/Server configuration.
2. Set "TallyPrime acts as" to Both (or Server).
3. Confirm Port is 9000.
4. Accept and return to the Gateway of Tally.

Tally ERP 9

1. Press F12 → Advanced Configuration.
2. Set Tally is acting as = Server.
3. Confirm Port is 9000.
4. Accept.

Then — and this catches nearly everyone the first time — open the company you want to sync inside Tally. The gateway always works on whichever company is currently open. Leave Tally running while you use the connector.

Step 2 — Open the ERP Connector

In iAccounting, open the File menu and click 🔗 ERP Connector (live sync)….

The screen has a Connection box at the top, a voucher date range, a Push section, a Pull section, a Repair section, and an Activity log at the bottom that records every step — worth reading when something doesn't go as expected.

Step 3 — Test the Connection

1. Host — 127.0.0.1 when Tally runs on the same PC. For Tally on another machine, see Tally on Another PC.
2. Port — 9000, unless you changed it in Tally.
3. Click Test Connection.

Success looks like "Connected. Companies: …" followed by the company names open in Tally. Read that list carefully — it tells you exactly which company the connector will read from and write to. If it names the wrong one, switch companies inside Tally before going further.

Your host and port are remembered for next time.

Step 4 — Pull from Tally into iAccounting

This is the direction most people want: bring an existing Tally company into iAccounting.

1. In the Pull from ERP box, tick what you want:
   • Masters (accounts, items, units…) — groups, ledgers, stock items, units, stock groups and godowns.
   • Vouchers (Day Book) — the transactions.
2. Set the Voucher date range. All dates is ticked by default; un-tick it and set From / To to limit the transactions. The range defaults to your company's financial year.
3. Click ⬇ Pull from ERP → this company and confirm.

The log reports what arrived — ledger, item, group and voucher counts — then the merge result.

Pull masters on the first run even if you only care about transactions. Vouchers reference ledgers and stock items by name, so the masters need to be there for the entries to land correctly.

Step 5 — Push from iAccounting into Tally

The other direction — useful when you work in iAccounting and your CA wants the data in Tally.

1. In Tally, open the company you want to write into. Push writes to whatever is open — there is no company picker on the iAccounting side.
2. In the Push to ERP box, leave Include vouchers ticked for masters + vouchers, or un-tick it to send masters only.
3. Click ⬆ Push entire company → ERP and read the confirmation carefully — it names the host and port and states that this writes into your ERP.

When it finishes you get Tally's own tally: "Created …, altered …, deleted …, errors …".

One result deserves explanation. If the push reports 0 created and 0 altered, iAccounting flags it as a problem rather than a success — Tally accepted the envelope but wrote nothing. Almost always that means no company is open in Tally, or Tally is in Educational mode where import is restricted. Open the target company and push again.

The Closing Stock Match

There's a quiet piece of work worth knowing about. After a pull that includes masters, iAccounting also asks Tally for each stock item's closing quantity and value as on your To date, and stores that snapshot.

Why: iAccounting normally recomputes closing stock by average cost, and that legitimately diverges from Tally, which values each item by its own costing method and handles negative stock and same-day ordering its own way. By taking Tally's figures directly, your Balance Sheet and P&L closing stock ties to Tally to the rupee — which is what you need when an auditor compares the two.

The log shows how many items were stored and the total value. If some names didn't match it says so; those are usually items renamed on one side.

The "Fix Group Natures" Repair Tool

Every group is Asset, Liability, Income or Expense, and that nature decides which side of the Balance Sheet or P&L a figure lands on. If data was imported before this was handled correctly, some groups can sit on the wrong side — capital or provisions being the usual suspects.

🔧 Fix group natures from ERP re-reads every group's nature from Tally and corrects it here. It's safe and narrow: only group natures change — no ledgers, vouchers or stock are touched, and there's no need to re-pull anything.

Open the same company in Tally that the data came from, then click it. Afterwards re-open your Balance Sheet or P&L to see the corrected sides.

Tally on Another PC

The connector works across a LAN. On the machine running Tally:

1. Enable the gateway as in Step 1, set to Both or Server.
2. Find that machine's IP address (ipconfig in Command Prompt — the IPv4 address, typically 192.168.x.x).
3. Allow port 9000 through Windows Firewall on that machine, for the private network.

Then put that IP in the connector's Host box instead of 127.0.0.1 and click Test Connection.

Keep this to your own trusted network. Tally's gateway has no password of its own, so anyone who can reach that port can read the open company — don't expose port 9000 to the internet.

Error Messages Explained

Whatever the message, the Activity log at the bottom of the screen carries the detail, including Tally's own reply. Read it before retrying.

Tips & Best Practice

1. Always Test Connection first. It costs a second and tells you which company you're about to sync.
2. Back up both sides before your first push. Pull is safe by design; push writes into Tally.
3. Pull masters before vouchers on a fresh company, so entries have ledgers and items to attach to.
4. Use the date range for big books. Pulling years of vouchers in one go is slow — a financial year at a time is easier to verify.
5. Verify after every sync. Compare Trial Balance totals on both sides. If a Balance Sheet figure sits on the wrong side, run Fix group natures.
6. Re-pulling is safe. Masters upsert, duplicate vouchers are skipped — so a pull after fresh Tally entries tops up rather than doubles.
7. Watch for renamed masters. Matching is by name, so a ledger renamed on one side arrives as a second ledger. Rename before syncing, not after.
8. Leave Tally alone during a sync. Don't switch companies mid-run.

What's Next?

• Import from Tally (XML file) — the no-setup route, available in every edition
• Import a Bank Statement with AI — statements straight to vouchers
• Import a Party / Ledger Statement with AI — for supplier and customer statements