User Guide

Google Chrome on a computer with the Tally Connector extension installed, and TallyPrime open on the same computer with the client's company loaded. A Remote Desktop or Citrix session works too, as long as Chrome and Tally run inside that same session. Then a statement, register or GST return to upload.

Bank and loan statements as PDF, Excel (.xlsx, .xls) or CSV, up to 200 MB. Purchase and sales registers in our Excel template. GSTR-2B and GSTR-2A as the Excel or JSON from the GST portal, and GSTR-1 as JSON. Digital statements work best; scanned pages are read where possible but are less dependable.

We match each entry against the client's own Tally ledgers, the rules you make in Mappings, the choices you have confirmed before, and a library of common Indian bank narrations. We only suggest a ledger when we are confident. A rule works from the very next upload; a choice you keep making is suggested on its own after about five confirmations.

New accounts get a 14-day trial with 500 voucher credits and 1 client. After that, prepaid Starter, Growth and Pro plans give 5,000, 15,000 and 35,000 credits, valid for 365 days, with unlimited clients. One credit is used for each voucher created; reviewing, editing and pushing are free. Invoice PDFs read by AI use 2 credits each. See Billing for current prices and any offer.

In the sales or purchase register template, write “Credit Note” or “Debit Note” in the Voucher Type column and keep the amounts positive — or leave Voucher Type blank and enter the invoice total as a negative number. Brackets such as (1,234.00) count as negative. A blank type with a negative total becomes a Credit Note in the sales register and a Debit Note in the purchase register. Don't write “Sales” or “Purchase” against a negative row: it is posted as an ordinary sale or purchase and flagged for you.

Uploads are recognised by their content, so renaming a file does not make it new — this stops the same statement from being imported and charged twice. A failed upload never blocks a retry. If you really do want a second set of vouchers from the same file, choose “Upload anyway”; otherwise delete the earlier upload first.

Not for the same entry. Each voucher carries its own ID, so if it is already in Tally, Tally updates it instead of adding a copy. But the same bank entry on two overlapping statements is two separate entries — so suspected duplicates are left out of a push unless you choose to include them.

Yes — tick the rows and click Unmark Pushed. They become editable, and when you push again Tally updates the same voucher. Unmarking does not delete anything from Tally; if you want a voucher removed from Tally, delete it there yourself.

Only the clients you assign them, or every client if you turn on Full access to all clients — a member with neither sees nothing, which is how a new member starts. Eight permission switches decide what they may do: view the dashboard, create or edit clients, delete clients, upload, categorise, delete transactions, send to client, and push to Tally.

Every export — transactions, ledgers and the audit trail — needs the “Categorize” permission, on the reasoning that handing the data out matters at least as much as editing it. Give them that permission, or export it for them.

Connections are encrypted, passwords are never stored in plain text, and two-factor login by email code is available in Settings → Security. The Chrome extension exchanges data with Tally only for actions you start. Uploaded files are deleted after 90 days. See the Privacy and Security pages for details.