One workspace.
All your clients.

Stop logging into seven Tally instances. Stop emailing GST reconciliations. Run every client’s books from one login with proper RBAC so your team can post but not approve.

Talk to us about the practice tier →See the migration flow
7 tally logins → 1 workspace
0 → 1
tally logins
one workspace, every client
0%
coa auto-mapped
common Tally groups
0 min
manual mapping
for the rest — once
₹0/client/mo
after the pilot
3 clients free for 60 days
what changes for your practice

What you stop doing.

Each ✕ is a ritual you run today. Each ✓ is what replaces it.

stop · client switching

Seven logins, retired

Logging into a separate Tally instance for every client.

All client books live in one tenant. Switch context with a dropdown, not a re-login — pinned recent clients across the top.

stop · hand-rolled audit trails

The chain signs itself

Reconstructing who-changed-what for the auditor.

Every entry is signed with user, IP, timestamp, before/after value. Article posts; you approve; auditor reads the chain.

stop · re-keying tally files

XML in, ledger out

Re-typing vouchers out of client Tally files.

95% of common Tally setups auto-map. The rest takes 20 minutes, once.

stop · emailing gstr reconciliations

Mismatches become a queue

Reconciliation PDFs emailed back and forth every month.

Trex pulls GSTR-2B from the portal weekly. Mismatches show up as a queue, not a PDF — email goes to the client with one click.

stop · statutory calendar in a spreadsheet

Due dates that chase you

A statutory close calendar maintained by hand.

Per-client period close, due-date alerts, statutory filing tracker. Roll-up dashboard for ‘what’s due this week’.

stop · permissions on trust

RBAC, the real kind

Access controlled by goodwill rather than roles.

Articles can post journals but not change COA or approve payments. Audit log shows everything.

the part most CAs ask about first

Migrating a client takes an afternoon.

Auto-mapping for common Tally groups, manual for custom ledgers. We’ve done it across audit firms running 30+ clients in parallel.

See the migration flow
  1. 01

    Export Tally XML

    your side

    One XML export per client — masters and vouchers, straight out of Tally.

  2. 02

    COA mapping

    ~20 min

    Auto for common groups, manual for custom. 95% of common Tally setups auto-map; the rest takes about 20 minutes.

  3. 03

    Preview 50 vouchers

    you approve

    Spot-check real entries against the source before anything is committed.

  4. 04

    Migrate

    same afternoon

    The client’s books go live in Triam — double-entry intact, audit trail from day one.

book.demo --persona=ca

$ run practice --clients=all

Run your practice from one screen.

Pilot tier for CA practices: 3 clients free for 60 days. After that, ₹2,000/client/mo with full Trex access.

$ talk to us about the practice tier →see the migration flow