Tally troubleshooting
A bill is in BizOS but not in Tally, or Tally says something you have never seen before. Most Tally sync problems are one of a handful: Tally is closed, the wrong company is open, a ledger name does not match, or a record from Tally is waiting for a person to decide. This page lists every status and message BizOS and the BizOS Agent show, what each means, and the safe fix.
Where do I look first?
| Screen | What it tells you |
|---|---|
| Accounting → Tally sync, top panel | "Tally is connected", "Tally sync is paused", "Tally reports an error" or "Waiting for the Tally Agent", last push, last pull, and the Last agent error |
| Accounting → Tally sync, Not reaching Tally | Each record Tally has not accepted, with Tally's message and what to do |
| Accounting → Tally sync, Review queue | Records from Tally waiting for a decision |
| Accounting → Tally sync, Recent pull runs | Each read from Tally and how it went |
| Settings → Connections & AI → Tally, Paired devices | Each PC, its agent version, when it was last seen |
| The BizOS Agent on the Tally PC | The Sync tile (Working, Tally not running, No internet, Disconnected), Check connection, and the Logs tab |
When nothing is wrong, Accounting → Tally sync says "Nothing waiting on you". BizOS also notifies the Owner, Admin and Accountant when an agent has not checked in for an hour.
Is the agent connected?
These appear in the setup wizard's Pair step and, after setup, as the connection status.
| What you see | What it means | What to do |
|---|---|---|
| Waiting for the code | No agent is paired yet | Open the BizOS Agent on the Tally PC and type the code shown in BizOS |
| That code has expired. / "Pairing code is invalid or expired" (in the agent) | Codes last 15 minutes and work once | Click Generate a new code (or Pair another on Paired devices) and type the new one |
| The agent has gone quiet | The agent has not checked in for a few minutes | Check the Tally PC is on, online, and the BizOS Agent is running (tray icon). Restart it from the tray if needed |
| TallyPrime is not answering | The agent runs, but Tally did not reply | Open TallyPrime with the company loaded and its gateway on. The agent checks again within a minute |
| Checking TallyPrime… | The first check is under way | Wait up to a minute |
| The agent stopped on this company | The company or GSTIN check failed; the line below says which | See "Why did BizOS stop syncing with a company or GSTIN message?" below |
| An older agent | The paired agent is older than 3.4.0 | Install the newer BizOS Agent; setup can go on without it |
| Status Paused | An Owner or Admin paused sync | Resume on Accounting → Tally sync. Bills wait in BizOS and go out when you resume |
What does the BizOS Agent's message mean?
| Message on the Tally PC | What to do |
|---|---|
| Sync: Tally not running / "Could not reach Tally on http://localhost:9000. Is TallyPrime running, with Gateway enabled?" | Open TallyPrime. If it is open, turn the gateway on: F1 (Help) → Settings → Connectivity → Client/Server configuration, act as Both or Server, port 9000 |
| "Tally is running but no company is open." | Load the company in TallyPrime |
| "'Company' is not open in Tally. Open that company in TallyPrime — syncing resumes on its own." | Open that exact company, or pick the right one under Tally company on the agent's Dashboard (it must match exactly) |
| Sync: No internet / "Could not reach BizOS…" | The Tally PC has no internet, or a firewall blocks outgoing traffic for the agent |
| Sync: Disconnected / "This PC was removed in BizOS Settings. Pair it again to resume syncing." | Someone revoked this PC. Pair it again with a new code |
| Service Status Stopped | Click Start on the Dashboard, or Start Service in the tray menu |
Check connection on the agent's Dashboard runs the same checks and shows a tick or a cross for the settings file, pairing, Tally, the company and BizOS.
Why did BizOS stop syncing with a company or GSTIN message?
BizOS stops a connection, rather than book anything in the wrong books, in these cases. The connection shows Error and the message below as the last agent error; the Owner, Admin and Accountant are notified.
| Message (shortened) | Cause | Fix |
|---|---|---|
| "This PC is set to Tally company 'A', but this BizOS account is connected to 'B'. Syncing is stopped…" | A different company is selected on the agent than the one this connection was first paired with | Reopen company B in TallyPrime and select it on the agent. To move the account to another company, contact support |
| "The Tally company open on this PC carries GSTIN X, but this connection is for GSTIN Y…" | The open company is another GSTIN's books | Open the company for GSTIN Y |
| "The Tally company open on this PC does not hold GSTIN Y, which BizOS keeps in it…" | BizOS was told this company keeps GSTIN Y, but its GST registrations in Tally do not include it | Add that GST registration in TallyPrime, or stop keeping Y in this company (Settings → Connections & AI → Tally) |
| "This Tally company doesn't hold GSTIN Y, by what the BizOS Agent last reported…" (when keeping a GSTIN) | Same as above, caught before saving | Add the registration in TallyPrime, then restart the BizOS Agent so it re-reads the registrations (it does so hourly and at start), and try again |
| Keeping a GSTIN refused because the agent is too old | An agent older than 3.4.0 cannot name a registration on a voucher | Update the BizOS Agent |
The next check that passes clears the error by itself.
Why is a record "Not reaching Tally"?
Each row shows a state, Tally's own message, and a line from BizOS on what to do.
| State | Meaning |
|---|---|
| Retrying | Tally did not accept it yet; BizOS tries again automatically (1, 2, 5, 15, 30, 60 minutes, then 3 hours). Fix the cause and it clears on its own, or click Retry to send it on the next sync |
| Gave up | Retries are used up, or Tally rejected it in a way that would repeat. Fix the cause, then Retry |
| Waiting for a godown | A stock transfer whose shelf is not matched to a Tally godown. Click Match a godown; it goes by itself once matched |
Common Tally rejections:
| Tally says | What it means | Fix |
|---|---|---|
Ledger 'Sales - BizOS' does not exist! (any ledger name) | BizOS posted to a ledger your Tally company does not have. BizOS creates party ledgers only, never sales, tax, cash or bank ledgers | Pick an existing ledger under Settings → Connections & AI → Tally → Ledgers & timing, or create that ledger in Tally. Then Retry |
Stock Item 'X' does not exist! / Unit 'X' does not exist! / Stock Group 'X' does not exist! | The master did not reach Tally ahead of the bill | Click Send older records on Accounting → Tally sync to send the catalogue, then Retry |
BAD UNIT NAME / DUPLICATE ORIGINAL NAME | Tally refused the unit master (Tally rejects digits in a unit symbol) | Check the item's unit in BizOS. BizOS already sends Nos for a unit label Tally would refuse; if it persists, contact support |
Voucher type … does not exist | The Tally type a series names is gone or renamed | Pick another type for that series in Settings → Selling → Numbering |
| Duplicate voucher number / voucher number already exists | The voucher type already has that number | Check the type's numbering in Tally, or give BizOS's series its own type numbered Manual |
| A refusal naming a GST registration ("Pick a Tally receipt type of Puducherry Registration…", "Give each GSTIN's invoice series a Tally type of its own…") | In a company keeping several GSTINs, a Tally voucher type serves one registration only | Do what the message says in Settings → Selling → Numbering, then Retry |
| Licence not active / educational mode | Tally's licence has lapsed | Reactivate the Tally licence; then Retry |
| Locked for backup / busy | Tally was busy | Nothing: BizOS retries |
| "The BizOS Agent took this but never said whether Tally accepted it (the PC may have shut down). It will be sent again." | The PC went off mid-send | Nothing: it is resent, and a resend never duplicates |
| "The BizOS Agent took this several times but never said whether Tally accepted it. Check in Tally whether it is there before retrying." | Repeated silent failures | Look for the voucher in Tally first, then Retry |
A dialog box in Tally can block everything
TallyPrime answers one request at a time. If a message box is waiting for a click on the Tally PC, every request waits behind it. Close it and leave Tally at the Gateway of Tally screen.
What is in the review queue, and what should I do?
The review queue holds records pulled from Tally that BizOS would not guess at. It is grouped as: customers and suppliers from Tally, bills from Tally waiting, bills made in Tally after BizOS took over, bills made from an order BizOS couldn't match, unmatched Tally sales orders, items, receipts and purchases.
| Reason shown | What it means | Safe actions |
|---|---|---|
| Looks like one in BizOS | A name close to an existing customer, supplier or item | Link suggested (or pick another and Link), Create in BizOS, or Ignore. Linking a party also brings in the bills that waited for it |
| Not in BizOS yet | No match at all, or a bill whose party or item is missing | Create or link the party or item; a bill then comes in by itself, or click Try again |
| More than one match | Several records fit equally, or a bill BizOS cannot read safely: a quantity in two units ("1 Box 5 Nos"), a stock line with an amount and no quantity, or a voucher that may be one BizOS sent and Tally has not confirmed yet | Link the right record. For a bill, fix it in Tally or wait for the confirmation, then Try again |
| Money held from Tally | A Tally receipt that names no bill BizOS holds; recorded as the customer's credit | Apply to this bill (the one its amount fits), Another bill…, or Keep held |
| Stock to confirm | An item linked by someone who may not change stock; its stock is held back | Someone with stock rights (Owner, Admin, Manager) clicks Confirm stock |
| Changed in Tally | BizOS owns the item list and Tally edited an item | Keep BizOS's or Take Tally's |
| Held from GSTR-1 | Tally made a bill in a voucher type after BizOS took its numbering over | Keep this bill, or cancel it in Tally. Tell staff to stop billing in that type |
| Order not matched | A Tally bill names an order BizOS could not match exactly | Keep as it is (it counts as a sale, not against an order) |
A Tally bill, receipt or sales order cannot be linked by hand to an existing BizOS document; link its party instead ("Link its party to a customer first — it then comes in by itself"). Rows BizOS sets aside itself (Between your branches, Comes in by godown, BizOS sent this) need nothing. Ignore moves a row to the Ignored view; an Owner or Admin can Bring back a row a person ignored.
Why are there duplicate customers, or renamed ledgers?
- Renamed in Tally: BizOS follows the rename. It knows a ledger or item by Tally's internal id, so the same customer stays linked and nothing is created twice.
- Renamed in BizOS: for a customer BizOS pushed, the Tally ledger is renamed on the next sync. A customer that came from Tally keeps Tally's ledger name on every voucher, so renaming it in BizOS changes nothing in Tally.
- Avoiding duplicates: when the review queue says "Looks like one in BizOS", link it rather than create a new one. BizOS compares names without spaces and punctuation across all your customers.
Why do stock figures differ?
| What you see | Meaning | Fix |
|---|---|---|
| Stock differences row | Tally's closing quantity and BizOS's differ | Adjust (BizOS writes a stock adjustment to match Tally) or Ignore. A row closes itself when the two agree again |
| "Check per godown" when adjusting | The company has godowns, so the company total is not compared | Compare per godown on the Godowns card instead |
| Stock lines from Tally to check | A Tally entry at a live godown BizOS will not apply without a person: a stock count, an entry re-dated to before go-live, one no longer in Tally, or one dated the day BizOS took Tally's quantity | Follow the row: for a re-dated entry, keeping it is the normal answer; undo a missing one only if it was deleted in Tally |
| "Update the BizOS Agent to bring in stock per godown" | The agent is older than 3.7.0 | Update the agent; nothing else is held up |
| "Tally's godown list hasn't arrived yet" | Waiting for the agent's next read; needs agent 3.1.0 | Wait, or update the agent |
| "Shelves billing with no Tally godown" | A BizOS shelf is not matched to a godown; its bills use the company's default godown | Match the shelf on the Godowns card |
Adjusting BizOS stock needs stock rights (Owner, Admin, Manager). Details: Tally stock & godowns.
Why is a pull "Stalled"?
"The BizOS Agent is not delivering" means a read from Tally was handed to the agent again and again with no answer. Open the agent on the Tally PC and check its Logs tab. A read that never arrives is failed after 30 minutes and asked for again later. Other pull states: Waiting for the agent, Receiving, Partly done (some records applied, some not), Replaced (a newer run took over) and Failed.
Why can't I edit an invoice or payment?
| Message | Why | Fix |
|---|---|---|
| "This invoice has already been synchronized with Tally and cannot be modified. Raise a credit note to change it." | The voucher is in Tally | Raise a credit note |
| "This invoice cannot be edited because Tally synchronization is enabled. Disconnect Tally, or correct it with a credit note." | Tally is connected and invoices sync, so issued bills are closed to editing even before they reach Tally | Correct it with a credit note. Drafts stay editable |
Payments show the same two messages. A failed push does not unlock a record: fix the push instead.
The Tally add-on ended
Settings → Connections & AI → Tally shows "Tally Prime sync is off" with Add-on ended. Nothing is sent to Tally until the Tally Sync module is added again; queued entries wait and go out then. Issued invoices and payments become editable again, except those already in Tally.
Common questions
- Why is my BizOS invoice not showing in Tally?
- Open Accounting, Tally sync in BizOS. If the invoice is under Not reaching Tally, the row shows Tally’s own message and what to fix, often a ledger name that does not exist in the Tally company. If nothing is listed, check that the Tally PC is on, the BizOS Agent is running and TallyPrime is open with the right company loaded; BizOS keeps the invoice queued until then.
- BizOS says TallyPrime is not answering. What do I check?
- On the Tally PC, make sure TallyPrime is open with the company loaded, no dialog box is waiting for a click, and the gateway is on under F1 Help, Settings, Connectivity, Client/Server configuration at port 9000. Opening http://localhost:9000 in a browser on that PC should return a short XML reply. The BizOS Agent checks again within a minute.
- Why did BizOS stop syncing and mention a GSTIN?
- BizOS stops a Tally connection when the open Tally company does not carry the GSTIN the connection is for, so that no bill is booked under the wrong registration. Open the right company in TallyPrime, or add the missing GST registration in Tally and restart the BizOS Agent. The error clears on the next check that passes.
- Tally says a ledger does not exist. What should I do?
- BizOS creates party ledgers for customers, but never sales, tax, cash or bank ledgers. Either create the named ledger in Tally, or point BizOS at an existing one under Settings, Connections, Tally, Ledgers and timing. Then click Retry on the row in Accounting, Tally sync.
- Can I edit an invoice that has gone to Tally?
- No. Once an invoice or payment is in Tally, BizOS locks it, and while Tally sync is on, issued invoices are locked even before they reach Tally. Correct it with a credit note. Drafts are always editable.
- What is the review queue in BizOS Tally sync?
- It lists records pulled from Tally that BizOS would not match by guesswork: a customer that looks like one already in BizOS, a bill whose party is missing, a receipt that names no bill, an item whose stock waits for confirmation. Each row says why and offers safe actions such as Link, Create, Try again, Apply or Keep. Owners, Admins and Accountants can work it.
- How do I know if the BizOS Agent needs updating?
- BizOS shows the agent version under Paired devices and warns when it is older than 3.4.0. Features that need a newer agent say so, for example Needs BizOS Agent 3.3.0 or later for bringing sales orders in, or 3.7.0 for godown stock. Install the newer agent from BizOS support over the old one.