Push to Tally

Before you push: the Connector is green, the client's company is open in Tally, its ledgers are pulled, and your changes are saved.

1. 1In the client's transactions, click Push to Tally · N ready. Only rows that have a ledger and are not yet in Tally are counted. Suspected duplicates are left out unless you tick Include suspected duplicates in this push.
2. 2Read the check-up. Anything under Fix before pushing must be sorted out first; Worth checking is advice.
3. 3If Fix Issues appears, confirm or reject close name matches, and create missing ledgers or stock items in Tally.
4. 4Check the connection and the Tally port, choose the company, and click Push to the company.
5. 5For a client's first push, confirm the company. The client stays linked to it for all later pushes.
6. 6Keep Tally open while the vouchers go across. Stop finishes the current batch and then halts.

Vouchers go in batches of 50. When it ends you see All N vouchers pushed, or a list of the vouchers Tally rejected, each with Tally's own reason. Use Jump to row to fix one, or Copy error log (CSV). Rejected rows stay ready to push again. Pushing never uses credits — nor do retries.

Ledgers we create for you — and those we don't

Before sending the vouchers, we create any missing ledgers they need, such as expense heads and suppliers. For safety, these are never created automatically:

• bank, cash, loan, capital, investment and fixed-asset ledgers;
• anything under Duties & Taxes or Provisions, and any GST, TDS, TCS or cess ledger;
• placeholder names such as "Sales Account" or "Purchase Account".

If one of these is missing, the push stops before sending anything and lists the names. Create them in Tally, click Pull Ledgers, and push again.

Pushing the same voucher twice

Each voucher carries its own ID. If it is already in Tally, Tally updates that voucher instead of adding a second copy. The same bank entry appearing on two overlapping statements, however, is two separate entries — which is why suspected duplicates are left out by default.

If a push gets stuck

An unfinished push holds its rows for 30 minutes. If you see N vouchers are stuck, click Release stuck vouchers (it works for pushes started more than 5 minutes ago), then push again.

Common messages