Tally API Integration
Connect TallyPrime to your website, mobile app, e-commerce store or third-party system, so data moves once and stops being typed twice.
The most common hidden cost in a small business is double entry. An order arrives on the website, someone types it into Tally. A payment clears in the bank, someone types it into Tally. Stock moves in the godown app, someone types it into Tally. Every one of those keystrokes is a chance to get a figure wrong, and every correction takes longer than the original entry.
Tally exposes an XML gateway over HTTP, which means it can be read from and written to by other software. We use it to make your systems talk to each other, so a record is entered once and appears everywhere it is needed.
What we connect
Website and e-commerce
Orders, customers and invoices flowing from your store into Tally, and live stock and price flowing back out.
Mobile apps
Field orders and collections posted to Tally as vouchers the moment they are approved.
Payment gateways and banks
Receipts matched and posted, with reconciliation reports for anything that does not match.
CRM and ERP systems
Two-way sync of masters so the same customer is not spelled three ways across three systems.
Dashboards and BI
Live Tally data pushed into reporting tools, so management stops waiting for a month-end export.
Custom middleware
A service that sits between Tally and everything else, queueing, retrying and logging every exchange.
How an integration is built
Map the data
Which records move, in which direction, and what happens when the two sides disagree. This is the part that decides whether an integration is trustworthy.
Agree the rules
Duplicate handling, failure handling and who wins when the same field is edited on both sides.
Build the connector
Developed against a copy of your company data, with full logging from day one.
Run in parallel
The integration runs alongside manual entry for a short period, and we compare the two.
Cut over
Manual entry stops only once the figures match.
Monitor
Failure alerts and a log you can read, so a broken sync is noticed by us rather than by your auditor.
Common questions
Does Tally need to stay open?
Tally's gateway runs while Tally is running, so the machine hosting it stays on. For always-on syncing we set that machine up as a small server, or queue the data and post it when Tally is available.
Is it safe to write into Tally automatically?
It is, provided the rules are agreed first and everything is logged. We run in parallel with manual entry before cutover precisely so you can see the figures agree.
What if the sync fails overnight?
Nothing is lost. Failed exchanges are queued and retried, and an alert goes out so somebody knows before the next working day.
Other services
Tell us what you want to build
Send a few lines about the problem. You get back an approach, a price and a realistic timeline within one working day.