Give your CA Tally access without WhatsApp company files

Every filing week, someone zips a Tally company, drops it on WhatsApp, and hopes the CA opens the same numbers the accounts desk is still posting. That habit creates two books, two versions of “latest”, and a scramble when GSTR and the ledger disagree.

Why file copies go stale

A company file is a snapshot. The moment sales or purchase vouchers continue in the office, the copy on the CA’s laptop is old. Split-company backups also travel through personal phones — not a place you want year-end data sitting. Tally on Cloud keeps one live data set that branches, owners, and the auditor can open without USB sticks or chat attachments.

Named access, not a shared password

Give the CA their own login. Do not recycle the accountant’s password “just for this month”. Named users make it obvious who is in the company, and you can disable the seat when the engagement ends. Pair that with the remote access habits you already use for staff — same path, same rules.

• One seat for the CA / article, plus a buffer if GST week overlaps office posting — see concurrent user sizing
• Tell them which company to open, the gateway or RDP path, and office hours when locks are likely
• Keep a restore-tested backup anyway — live access is not a substitute for backup habits

What to send on day one

A short note beats a 40 MB zip: how to connect, which company, who to call if login fails, and a link to status so they do not assume DNS when the gateway is actually down. If something is stuck, open a support ticket with those same facts instead of forwarding screenshots in a group chat.

Need a CA seat on your cloud Tally? See Services or contact KC Cloud with user count and whether the auditor works during GST weeks.