Do I need a valid TSS (Tally Software Services) subscription for remote access?

Yes. Remote access requires an active TSS subscription. If TSS has expired, the Tally.NET broker server will reject the connection, and the option to connect the company will be disabled.

What is the shortcut to connect a company to Tally.NET in TallyPrime?

Load the company on the office host computer, press Alt+K (Company) > Connect (or click the 'Connect' option on the top control bar). Once connected, a small '(c)' symbol will appear next to the company name.

Why does Tally.NET say my remote user email is 'Unauthorized'?

This happens if you have not added the user's registered Tally.NET ID in the 'Users and Passwords' menu, or if the role assigned to that email has 'Allow Remote Access' toggled to No in the User Roles menu.

What ports must be open on the router for Tally.NET remote access?

Tally.NET uses outbound TCP Ports 9050 and 9450 to establish secure sockets. Ensure your office router and local antivirus do not block outgoing traffic on these ports.

Can TrulyInvoice work remotely without a Tally.NET setup?

Yes. TrulyInvoice is cloud-native. You can upload and process invoices from any computer, home office, or phone. The TrulyInvoice system stores the data securely and syncs it with TallyPrime when the office computer is active, eliminating the need for a Tally.NET setup.

Fixing Tally.NET Remote Access Error: Company Not Connected

Tally.NET remote access allows accountants and business owners to log in and review books or post entries from home. If you encounter a "Remote login failed" or "Company not connected" error, follow this checklist to restore connectivity.

As businesses adopt hybrid work models, remote access to on-premise accounting data has become essential. The Tally.NET framework allows users to connect to their office computers and work on databases from home or client locations. However, because this setup relies on a continuous connection between the local office computer, the Tally.NET broker servers, and the remote laptop, any configuration mismatch will disconnect the system. This guide covers the steps needed to troubleshoot and resolve Tally.NET remote connection errors.

Step 1: Check TSS (Tally Software Services) Status

Tally.NET services are subscription-based. The security certificate validation, remote database tunneling, and data encryption processes are all managed under your active Tally Software Services (TSS) subscription.

On the host computer in your office, open TallyPrime.
Press F1 (Help) > About.
Under the **Product Information** column, look for the **TSS Expiry Date**.
If the subscription has expired, you must purchase a TSS renewal before Tally.NET will allow remote connections.

Step 2: Connect the Company database to Tally.NET

A common cause for the "Company Not Connected" error is that the office host computer has not published the active company to the Tally.NET directory. Simply leaving the computer on is not enough; the user must explicitly connect the company.

How to Publish the Company:

Load your company database on the office desktop.
Press Alt+K (Company) to open the company control panel menu.
Select Connect (or press the hotkey Alt+F11).
Once connected, look for the company name in the active list. A small (c) symbol will appear next to it, indicating the company database is connected to the Tally.NET server.

Step 3: Setup Security Roles and User Credentials

Even if the database is connected, remote login requests will be blocked if the user's email ID does not have explicit remote access permissions.

Tally.NET User Setup Guide

Enable Remote Access for User Roles

Go to Alt+K > User Roles. Select the role you want to configure (e.g., Tally.NET Owner or Tally.NET Auditor). Under the security properties, ensure Allow Remote Access is set to Yes.

Add Remote User Emails

Go to Alt+K > Users and Passwords. In the User list, select the role (e.g., Tally.NET User). Enter the user's registered Tally.NET email ID. Set Allow Remote Access to Yes, and save the settings.

Tally.NET Security & Encryption Standards

Tally.NET uses a proprietary handshake protocol combined with standard SSL/TLS data encryption wrappers to transfer corporate data packets. When a remote user triggers an operation, the request is packaged, encrypted on the client device, and transmitted to the Tally.NET gateway. The gateway routes this packet to the office host, which decrypts it, updates the local database files, and sends back an encrypted response.

This direct end-to-end encryption ensures that your financial ledgers cannot be intercepted during transmission. Because no accounting records are permanently stored on the Tally.NET broker server, the risk of data leakage is minimized.

Step 4: Resolve Router Firewall and Network Blockages

Tally.NET establishes secure database tunnels using TCP ports. If your company's local router or corporate firewall blocks these ports, remote users will experience connection timeouts.

To configure a reliable network path:

Open Ports: Ensure your router's security configuration allows outbound traffic on TCP Ports 9050 and 9450. These are the default channels Tally.NET uses to tunnel database requests.
DNS Settings: If the remote application displays connection errors, change the network DNS server on the client computer to Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1). Some local ISP DNS setups can misroute Tally's broker lookups.
Network Latency: High ping latency (above 150ms) can cause connection drops during remote syncs. If this occurs, adjusting your router's MTU (Maximum Transmission Unit) setting to 1400 can help stabilize the connection.

Tally.NET Connection States Reference Table

Error Message / Code	Root Cause	Troubleshooting Action
Company not connected	The office host computer is offline or has not connected the company.	Go to office PC, load company, press Alt+K > Connect.
Remote login failed	Mismatched login credentials or email is not added to the user list.	Verify email spelling in Users and Passwords and reset the password.
Socket closed / Timeout	Network disconnections or local router firewall blocking Port 9050.	Add TCP Port 9050 outbound exclusion rules to your router.

A Modern Alternative to Tally.NET Remote Access

Setting up and maintaining Tally.NET remote access requires an active TSS subscription, stable office internet speeds, and regular network configurations. If the office computer is turned off or loses internet connection, remote users lose access to the system.

With TrulyInvoice, you can work remotely without these limitations. TrulyInvoice allows your billing and data entry teams to upload and process vendor invoices on our secure cloud platform from any location. TrulyInvoice validates the data and holds it in a secure queue. The moment your office computer launches TallyPrime, the database syncs automatically in the background. This ensures your remote workflows continue uninterrupted, even without Tally.NET.