CyberFreezeDev Loading
  1. Home
  2. Integrations
  3. Tally (TallyPrime)

Tally integration with WhatsApp, your store and payments

Keep TallyPrime. Invoices go out on WhatsApp, and orders, payments and bills come in as vouchers.

Book a consultation
3D render of a paper stack and a scanner bed whose light bar reads fields into a record card

At a glance

Tally integration
Interface
TallyPrime XML over HTTP, port 9000 by default
Message
ENVELOPE with HEADER (TALLYREQUEST Import, Export or Execute) and BODY
Imports
Vouchers (sales, receipts, credit notes), ledgers, stock items, units
Exports
Day Book, Trial Balance, ledgers and collections with a FETCHLIST
Import result
CREATED, ALTERED, ERRORS and LASTVCHID read from every response
Push from Tally
TDL HTTP Post on voucher save, where polling is too slow

What a Tally integration does

Tally stays the book of record. The integration feeds it and reads from it.

Out of Tally, invoices and reminders reach customers on WhatsApp. Into Tally, orders, settlements and bills arrive as vouchers through its XML interface.

Read more about What a Tally integration does

A Tally integration with WhatsApp and your other systems removes two kinds of copying. Out of Tally: a sales invoice saved in TallyPrime reaches the customer as a WhatsApp message with the invoice number, amount and due date, and overdue balances become polite reminders with a payment link. Into Tally: Shopify orders, Razorpay settlements and purchase bills read by OCR arrive as vouchers with the right ledgers and the GST split, ready for the accountant to review.

TallyPrime does this through its XML interface: with its HTTP server enabled, it accepts XML requests on a port (9000 by default) to import data or export reports. See Tally's XML integration guide. The accounting logic around it, such as GSTR-2B matching and return checks, is covered by our GST and accounting automation service.

Typical flows we build

Invoices from Tally on WhatsApp

New sales invoices go to the party's mobile number as approved WhatsApp templates.

Read more about Invoices from Tally on WhatsApp

A Day Book export filtered to sales vouchers finds new invoices since the last run; the party's mobile number comes from the ledger master. Each invoice goes out as an approved utility template through our WhatsApp integration. Where minutes matter, a small TDL addition posts the voucher to us on save instead of waiting for the next poll.

Payment reminders from ledger balances

Overdue debtors get a reminder with a Razorpay link, and the receipt flows back in.

Read more about Payment reminders from ledger balances

Closing balances of Sundry Debtors are exported on a schedule; customers past their credit period get a reminder with a Razorpay payment link, and the receipt comes back into Tally when they pay.

Store and gateway entries into Tally

Shopify orders, refunds and Razorpay settlements become vouchers with fees on their own ledgers.

Read more about Store and gateway entries into Tally

Paid Shopify orders become sales vouchers in invoice mode, refunds become credit notes, and Razorpay settlements become receipts with fees and GST on fees on their own ledgers. Missing party ledgers or stock items are created first.

Purchase bills from email or WhatsApp

OCR-read bills validated for GSTIN, tax maths and place of supply before import.

Read more about Purchase bills from email or WhatsApp

Bills read by our OCR pipeline are validated (GSTIN format, tax maths, place of supply) and imported as purchase vouchers, or held for a person when anything is unclear.

Reports where owners look

Trial Balance and Day Book refreshed into a Sheet each morning.

Read more about Reports where owners look

Trial Balance and Day Book exports refreshed into a Google Sheet or dashboard each morning, so the owner sees sales and receivables without opening Tally.

How an import into TallyPrime is run

  1. 01 Map the ledgers once

    Ledger names, voucher types and GST ledgers agreed with your accountant first.

    Read more about Map the ledgers once

    We agree your ledger names, voucher types and GST ledgers with your accountant. An import that guesses a ledger name creates a new one, which is the most common way Tally integrations make a mess.

  2. 02 Build the XML

    Each entry becomes an Import Data envelope for the right company.

    Read more about Build the XML

    Each entry becomes an Import Data envelope with REPORTNAME Vouchers and the company set in SVCURRENTCOMPANY, following Tally's sample XML.

  3. 03 Try it on a copy

    Imports run on a backup copy and are compared with hand-booked entries.

    Read more about Try it on a copy

    Imports run first against a backup copy of the company, and the result is compared with entries your team booked by hand for the same days.

  4. 04 Read the response

    Every response is checked and the voucher id stored, so a retry never books twice.

    Read more about Read the response

    Every response is checked for CREATED, ALTERED and ERRORS, and LASTVCHID is stored against the source record, so a retry never books the same order twice.

Limits and Tally's rules

Tally must be running

Sync works only while TallyPrime is open, and catches up once it is.

Read more about Tally must be running

The XML interface answers only while TallyPrime is open with the company loaded. If the office PC is off, the sync waits and catches up; for always on flows we discuss a machine that stays on. See prerequisites for integrations.

Keep port 9000 inside the office

Tally's port stays off the internet; a local connector makes outbound calls only.

Read more about Keep port 9000 inside the office

Tally's HTTP port is not something to expose to the internet. A small connector on the same network makes outbound calls only, so no inbound firewall rule is needed.

The accountant still decides

We prepare entries and list each import run. Filing returns and closed periods stay with your accountant.

Read more about The accountant still decides

We prepare entries; we do not file returns or change closed periods. Every import run produces a list of what was created, so your accountant can review those entries in Tally and correct them there.

No partnership claimed

Built on Tally's documented XML and TDL interfaces, without any partner status.

Read more about No partnership claimed

We are not a Tally partner. We build on the XML and TDL interfaces Tally documents for developers.

Questions

Can we send invoices from Tally on WhatsApp without retyping anything?

Yes. New sales vouchers are read from TallyPrime and sent as a WhatsApp template to the mobile number on the party ledger, after a one-time setup of the WhatsApp Business API in your name.

Do we have to move from Tally to Fint?

No. Most of this work is built around TallyPrime. Fint is our own web accounting product and an option if you want invoicing, banking and GST in one web app, not a requirement.

Does this work with Tally ERP 9?

The XML interface exists in older releases too, but we build and test on TallyPrime. Tell us your release and we will check before quoting.

What do you need from us?

The TallyPrime release you use, a machine on your network where it runs during working hours, permission to enable its HTTP port, your accountant's time to agree ledger mapping, and API access to the other systems in your company's name.

Is our Tally data sent to the cloud?

Only what a flow needs, such as invoice number, amount and mobile number for a reminder. The connector and n8n can run on your own server if data must stay in the office.

Last updated