We connect sales, purchase and payment data in your system to Tally, which many Indian accountants and CAs use to keep the books.
Operations often run in one system while the accountant works in Tally. Without a connection, someone re-enters every invoice at month end, and names, amounts or tax figures drift apart. Transferring vouchers directly keeps the books matching the business system and leaves your accountant working in the tool they know.
What we build with it
- Exporting sales and purchase vouchers for the accountant
- Sharing ledger masters so names match
- Periodic transfer at month or quarter end
- A transfer log showing what was sent and what Tally rejected
How it works
- We agree with your accountant how parties, sales, purchase and tax ledgers in the system map to ledgers in Tally.
- At the agreed time, the system gathers vouchers not yet transferred, with their tax breakup.
- It sends them to Tally through its XML interface, or produces an import file where a direct connection is not possible.
- Tally's response for each voucher is recorded, so failed entries can be corrected and sent again.
Data exchanged
- Voucher entries with tax breakup
- Ledger and group masters
- Party details
What is needed to set it up
- A Tally installation, with TallyPrime for XML or ODBC exchange
- Agreement on ledger naming so entries map correctly
- A defined transfer frequency
Good to know
- Tally runs on a desktop or local server, so it must be open and reachable for a direct transfer. A small local agent is often used to bridge a cloud system and an office Tally installation.
- Mismatched ledger names are the most common cause of failed imports, which is why mapping is agreed first.
- Where a live connection is not practical, an import file your accountant loads into Tally works reliably.
