Frequently Asked Questions
No. We read your chart of accounts so entries can be matched to the right ledger, and we write only the vouchers you approve. Vouchers already in Tally — whoever created them — are never altered or deleted. By design, nothing in our cloud can delete anything inside your Tally.
Install the YAA Tally Connector from the Chrome Web Store on the Windows PC where Tally runs. In Tally, press F1 → Settings → Connectivity and set 'TallyPrime acts as' to Both. The port in Tally must match the port the connector uses — 9000 by default; any port from 9000 to 9100 works.
Both. The connector works with TallyPrime and Tally.ERP 9 running on Windows, and the steps are the same for either: switch on connectivity in Tally, match the port, and push from here.
PDF, Excel (.xlsx, .xls) and CSV statements from Indian banks, including SBI, HDFC, ICICI, Axis, Kotak and IndusInd. Download the statement from net banking — scans and photographs of a printed statement will not work. If a statement cannot be read cleanly it is held for your review, rather than imported with rows missing.
No. Every line is matched against your client's own Tally chart of accounts and a ledger is suggested for you, which you approve or change. Matching runs in order — exact name, differences of case, your saved aliases, then close matches — and it is group-aware, so an expense is not suggested where a bank ledger belongs and CGST is not confused with SGST. Corrections you make are remembered, so the same narration is matched on its own next month. Nothing reaches Tally until you approve it.
The web app works in modern browsers, but Tally operations require the YAA Tally Connector extension in Google Chrome on the same Windows computer where Tally is running.
The web app works on any OS. Since Tally runs on Windows, pushing vouchers uses the Google Chrome extension on the same Windows computer where Tally is open.
New accounts start with a 14-day trial: 500 voucher credits and 1 client. Nothing is billed automatically when the trial ends — buy a paid plan to keep going, or stop using the Service and no further charges apply.
The trial allows 1 client. Paid plans do not cap the number of clients — they are metered by entries, so your whole practice can sit in one account and credits are spent wherever the work is.
Once your entries carry the right ledgers, click Push to Tally. A check runs first for missing ledgers, period mismatches and incomplete vouchers, and any missing ledgers can be created in Tally before the push proceeds. You see progress voucher by voucher as it runs.
The result screen lists every rejected voucher with the reason Tally gave. The usual ones: the ledger does not exist in Tally, the date falls in a closed period, Tally treats the voucher as a duplicate, the date is outside the company's books, or the ledger sits in a group that will not accept the entry. Fix those rows here and push again — vouchers that already went through are not sent a second time.
Partly, and the distinction matters. On the Transactions page, select the rows and choose Unmark Pushed — they unlock here so you can correct them and push again. It does NOT delete anything from Tally: by design, nothing in our cloud can reach into your Tally to delete. Remove or correct the voucher in Tally yourself first, then re-push. If you re-push without doing that, Tally updates the original voucher rather than creating a new one.
Not the vouchers you created by hand — those are never touched. A re-push of a voucher we already created uses the same reference, so Tally may update that voucher instead of creating a duplicate; if it cannot, the push is flagged as a duplicate and skipped so you can review it.
Yes, as long as that period is still open in Tally. If the books are closed or the period is locked, Tally rejects the voucher and the row is listed as Period Locked — reopen the period in Tally, or move the entry to a date inside the open books, then push again.
The app defaults cash withdrawals, deposits and transfers between your own bank and cash ledgers to Payment or Receipt, which you can change per row to Contra before pushing. If your company's chart has its own Contra voucher type, the push uses that name. Nothing is written to Tally without your approval.
Pushes are sent in small batches, and each voucher carries a unique reference tied to that entry. Vouchers already written to Tally before the drop stay in Tally; anything not yet sent stays pending here. Reconnect the extension and push again — the reference means Tally updates a partly-pushed voucher instead of creating a duplicate.
Bank and loan statements (PDF, Excel, CSV), purchase and sales registers, and GSTR-1, GSTR-2A and GSTR-2B exports. PDF invoice extraction is coming soon and is not available yet.
No. We import GSTR-1, GSTR-2A and GSTR-2B exports only, to create sales or purchase vouchers that you review and push to Tally. We do not reconcile GST data, prepare returns, or file anything with the portal.
Upload it anyway. The app detects the encryption and asks you for the password in the review screen, with five attempts to get it right. If you would rather not share it, most net banking portals offer an unprotected download — open the PDF with the password and save a copy without it, which is always the simpler route.
Some PDFs with unusual layouts do not parse perfectly. Download the same statement as Excel or CSV from net banking instead — those are almost always read correctly. Scanned or photographed statements are not supported; ask the bank for a digital statement. You can review and correct any misread value before pushing.
Upload it anyway. Recognised layouts are parsed as usual, and a layout we do not know is held for your review rather than imported with rows missing — send it to us and we will add it. For an unusual bank, Excel or CSV from net banking is the surest route.
Yes, and they are specific. A file you upload yourself can be up to 200 MB. A PDF can be up to 500 pages — split longer statements by date range. When a client uploads through an Ask Client link, the limit is 10 MB per file, so a large scanned statement is better sent to you directly. There is no fixed cap on the number of entries in one file; statements with several thousand rows are normal. Anything over a limit is rejected at upload with the reason shown, never silently truncated.
A typical monthly statement is usually ready while you wait. A large statement of several hundred pages takes longer — you can leave the page and come back, since processing continues in the background.
Yes. Share an upload link and your client uploads the statement themselves — no account and no app at their end. Files arrive under that client and are processed as though you had uploaded them. You can also raise an Ask Client query on a suspense entry, and their reply comes back into your dashboard.
Yes. Upload several files in one session and each is processed independently. They all appear under the same client and can be pushed to Tally together or separately.
New accounts get a 14-day trial with 500 voucher credits and 1 client. Prepaid Starter, Growth and Pro plans are valid for 365 days. See Pricing or Billing for the live catalogue, GST and any current offer.
Yes. Credits are valid for 365 days from the date of purchase, and the Billing page shows the expiry against each plan you have bought.
Staff you add draw on the admin account's plan credits — one plan for the whole firm, not one per person. Permissions and per-staff usage are managed in Settings → Team. Staff do not buy a separate plan.
Go to Billing and select a plan. The server calculates the amount and Razorpay processes the payment. The checkout summary shows credits, validity, GST and the total before you pay.
No. One credit is used for each final voucher you keep. Failed, unreadable, unsupported and duplicate files cost nothing, and editing, clarifying, pushing, retrying or re-pushing the same voucher never costs a second credit. The one thing that does cost more: splitting one entry into several vouchers charges for the extra vouchers you create.
Connections use TLS, and data is encrypted in transit and at rest: uploads are encrypted by the storage provider, backups are encrypted, and passwords are hashed with bcrypt and salt — plaintext passwords are never stored. You can add a second step at sign-in, a one-time code sent to your registered email, with a backup code as fallback. The Chrome connector carries out only the Tally operations you start. See the Privacy and Security pages for full detail.
Yes. Settings > Security > Danger Zone > Delete My Account deactivates your account after password (or, for Google sign-in, typing DELETE) confirmation. It stays reversible for a 30-day grace period — sign back in and cancel to reactivate. Records the law requires us to keep are retained. For immediate, irreversible erasure of your personal data instead, use Settings > Data Compliance > Data Retention > Erase my data.
Access is controlled by your account and team permissions. Authorised service providers process the limited data needed to operate the product, as described in the Privacy Policy. We do not sell personal data.
The Chrome extension exchanges Tally data only for an operation you start, such as pulling selected company or ledger data, or pushing reviewed vouchers. It does not upload your entire Tally database. Connections to the service use TLS.
Aliases are shortcuts you create so a narration keyword always resolves to the right Tally ledger — set 'Zomato' as an alias for 'Marketing Expenses', and every later entry mentioning Zomato is matched to that ledger for your approval. Manage aliases from the Mappings page.
Yes. Open Mappings → Blacklist and add the narration together with the ledger you never want it paired to. That pairing is then skipped everywhere a ledger is suggested, not only for AI suggestions.