In this guide
Here is a conversation we have with almost every Indian business moving to ERPNext. Operations loves it: sales orders, stock, production and approvals finally live in one system. Then the accountant says, quietly, "But I file from Tally. My CA works in Tally. Our auditor wants Tally."
So someone re-keys every invoice into Tally at month end. Two systems, two sets of numbers, and a reconciliation exercise nobody enjoys. This guide shows a better way: an ERPNext Tally integration that posts every master and voucher into TallyPrime automatically - in real time, or at day end, week end, month end or quarter end - and checks every day that both books still agree.
Why Run ERPNext and Tally Together?
If you can move fully to ERPNext, do it - our Tally to ERPNext migration guide covers how. But many businesses have good reasons to keep Tally for a while longer:
- Your CA or auditor works in Tally and will not change their process for one client.
- The accounts team knows Tally deeply and you want ERPNext live in operations first, without retraining everyone on day one.
- Group reporting runs on Tally across sister companies that are not moving yet.
- You want a safety net during the first year: if anything looks off, the familiar Tally books are right there.
None of these reasons justify typing the same invoice twice. Manual re-entry is slow, and worse, it is where numbers quietly start to differ.
| Approach | Effort | Risk of mismatch | Handles cancellations |
|---|---|---|---|
| Re-keying invoices into Tally | Hours every week | High - typos, missed bills | Only if someone remembers |
| Monthly Excel or XML export and import | A day every month | Medium - duplicates on re-import | No |
| Automatic ERPNext to Tally sync | Zero after setup | Low - verified daily | Yes, automatically |
How the ERPNext Tally Integration Works
TallyPrime has a built-in XML server that third-party software uses to read and write Tally data. Our connector is a Frappe app installed on your ERPNext site. When something changes in ERPNext, it sends Tally the matching ledger or voucher over that XML interface, then reads Tally's reply and records the result.
ERPNext is the source
Invoices, payments and journals are created, approved and submitted in ERPNext. That is where your controls, workflows and stock live.
Tally is the mirror
Tally receives an exact accounting copy: same voucher numbers, same dates, same ledgers, same amounts - ready for your accountant, CA and auditor.
The sync is deliberately one-way. Two systems that can both change the same voucher always end up arguing about which one is right. Instead, the connector reads Tally back every day and tells you when something was changed there.
What Syncs from ERPNext to Tally
Masters: customers, suppliers and ledgers
| ERPNext | Tally | Details carried across |
|---|---|---|
| Customer | Ledger under Sundry Debtors | Name, GSTIN, state (from the GSTIN), GST registration type |
| Supplier | Ledger under Sundry Creditors | Name, GSTIN, state, GST registration type |
| Account (ledger) | Ledger under the matching Tally group | Bank, Cash, Duties & Taxes, Fixed Assets, Sales, Direct and Indirect Expenses and more, chosen automatically |
Account groups are mapped onto Tally's predefined groups from the account type and its parent groups in ERPNext. When the automatic choice is not what your accountant wants, set a Tally Group on that account and it wins. If your accountant has moved a ledger into a sub-group in Tally, the connector keeps it there instead of moving it back.
Debtors and creditors control accounts are not created as ledgers: in Tally the customer or supplier is the ledger, exactly as Tally users expect.
Vouchers: every posted transaction
| ERPNext document | Tally voucher type |
|---|---|
| Sales Invoice | Sales |
| Sales Invoice (return) | Credit Note |
| Purchase Invoice | Purchase |
| Purchase Invoice (return) | Debit Note |
| Payment Entry - Receive / Pay / Internal Transfer | Receipt / Payment / Contra |
| Journal Entry / Contra Entry | Journal / Contra |
Each voucher is built from the GL Entries ERPNext actually posted, not recalculated. Whatever ERPNext booked - including CGST, SGST, IGST, TDS and round-off ledgers - is exactly what Tally receives, with the ERPNext document number as the Tally voucher number and the remarks as the narration. Your trial balance in Tally matches ERPNext because it is built from the same entries.
Real-Time vs Periodic Sync: You Choose
Not every accounts team wants Tally changing all day. Some want it updated the moment an invoice is submitted; others want a clean batch at day end after the day's corrections are done. The connector supports both, and you can set masters and vouchers independently.
Real Time
Each voucher reaches Tally within moments of being submitted or cancelled. Each customer, supplier or ledger is sent as soon as it is saved. Best when the accountant works in Tally through the day.
Periodic
Changes wait and are sent together at Day End, Week End, Month End or Quarter End, at the time you choose. Quarter End follows the Indian financial year: 30 June, 30 September, 31 December and 31 March.
Periodic mode is smarter than a simple timer:
- Mistakes never reach Tally. An invoice submitted and cancelled within the same period is never sent. Tally only sees what survived.
- Several edits, one update. A customer edited three times before day end is sent once, with its final details.
- No missed periods. If the server was offline at the scheduled time, the sync runs as soon as it is back.
- Need it now? One click on Sync Pending Now sends everything waiting without changing the schedule. Each document shows when it will be sent.
- Switching back is safe. Change a mode back to Real Time and everything waiting for it is sent immediately.
Built for Accounting: The Safety Rules
An integration that is right 99% of the time is dangerous in accounting, because nobody knows which 1% is wrong. These are the rules the connector follows so that does not happen.
-
1
No duplicate vouchers, ever
Before posting, the connector searches Tally for the same voucher type and number in that financial year. An identical voucher is marked as already synced; a different one with the same number is refused and flagged. It does not rely on Tally's own duplicate setting.
-
2
Cancellations follow automatically
Cancel an invoice in ERPNext and its Tally voucher is cancelled too. The connector then checks that Tally really shows it as cancelled.
-
3
Renames rename, they do not duplicate
Rename a customer or account in ERPNext and the same ledger is renamed in Tally, so its history stays together. If two records would share a ledger name, the second gets a clear suffix rather than silently posting into someone else's ledger.
-
4
Posted means permanent
A document that has reached Tally cannot be deleted in ERPNext, only cancelled, so ERPNext can never reuse its number for a different document. Successful sync records cannot be deleted either: they are your audit trail.
-
5
Daily verification against Tally
Every night the connector reads Tally back and compares every synced voucher with ERPNext. Vouchers deleted or cancelled in Tally, amounts or ledgers edited there, changed dates, or vouchers still active in Tally after cancellation in ERPNext are all flagged. When they are fixed, the flag clears itself.
-
6
Automatic retries when Tally is closed
Tally closed, the PC asleep, the network down? The sync is retried automatically every 10 minutes for about five hours. Nothing is lost: anything still waiting after that stays in the log, and one click on Retry sends it.
Full Visibility: The Sync Log
Every attempt is recorded in a Tally Sync Log: which document, what was sent, Tally's exact reply, how many attempts, and the outcome - Pending, Queued, Success, Failed or Skipped. Errors are written in plain language with what to do next, not just a raw Tally message.
Your team does not even need to open the log. Every submitted Sales Invoice, Purchase Invoice, Payment Entry and Journal Entry shows its Tally status at the top of the form: synced, waiting for the periodic sync (with the time it will go), or failed with the reason. Problems are seen where people work.
Setting It Up
Everything is configured on one Tally Settings page in ERPNext.
-
1
Enable the TallyPrime XML server
In TallyPrime, enable it to act as a server on a port, open the company, and keep Tally running on a PC the ERPNext server can reach.
-
2
Connect
Pick the ERPNext company, type the Tally company name exactly as Tally shows it, and enter Tally's host and port. Click Test Connection: it confirms Tally answered and that the company is open.
-
3
Choose what and when
Switch on masters and vouchers, set a Sync Vouchers From date so history already in Tally is never sent again, and choose Real Time or Periodic for each.
-
4
Push masters, then catch up
Push All Masters creates every customer, supplier and ledger in Tally. Queue Unsynced Documents sends every submitted voucher since your go-live date that has not been synced yet.
-
5
Verify
Verify Against Tally compares everything on demand. After that, the nightly check does it for you.
What It Does Not Do (Honestly)
- No stock items or quantities. Vouchers are posted at accounting level. Items, batches and warehouses stay in ERPNext, where inventory belongs.
- No Tally to ERPNext sync. Entries made directly in Tally are not copied back. The daily check flags changes to synced vouchers so you can correct them at the source.
- Tally must be running. The sync needs Tally open with the company loaded. With Periodic mode, choose a sync time when the Tally PC is on.
- Ledger merges are manual. Tally cannot merge ledgers over its API. If you merge two customers in ERPNext, the connector flags it and tells you exactly what to move in Tally.
- File GST from one place. We recommend filing GST returns from ERPNext with India Compliance, and using Tally for the books your CA reviews.
ERPNext Tally Integration Checklist
Before you switch the sync on
Frequently Asked Questions
Can ERPNext be integrated with Tally?
Yes. A Frappe app on your ERPNext site pushes customers, suppliers, ledgers and posted vouchers into TallyPrime over Tally's XML server, in real time or on a day-end, week-end, month-end or quarter-end schedule.
Is the ERPNext Tally sync one-way or two-way?
One-way, from ERPNext to Tally. A daily verification reads Tally back and flags any synced voucher that was changed, deleted or cancelled there.
Can I sync ERPNext to Tally at day end instead of in real time?
Yes. Masters and vouchers each have a Real Time or Periodic mode. Periodic sends everything waiting at the end of the day, week, month or quarter, at the time you set.
Will the integration create duplicate vouchers in Tally?
No. It checks Tally for the voucher type and number in that financial year before posting, and every job runs under a per-document lock, so retries are harmless.
Does it sync stock items and inventory?
No. Vouchers are posted at accounting level from ERPNext's GL Entries. Item quantities, batches and warehouses stay in ERPNext.
Does ERPNext on the cloud work with Tally on an office PC?
Yes, over a VPN or private network link between the server and the Tally PC. Tally must be open with the company loaded when a sync runs; otherwise it retries automatically.
Why does Tally say "voucher date is missing"?
TallyPrime in Educational mode only accepts vouchers dated the 1st, 2nd or 31st of a month. A licensed TallyPrime has no such limit, and the sync log explains this when it happens.
Final Verdict
You do not have to choose between ERPNext for the business and Tally for the accountant. With an automatic, verified sync, operations runs on ERPNext, the accounts team keeps the Tally books they trust, and nobody re-keys an invoice again. Choose real time or day end, and let the nightly check prove both books agree.
