Tally Connector App roadmap

Overview

A correctness release, in three parts. Voucher type numbering was read from a field TallyPrime stops maintaining, so it could disagree with what Tally's own voucher-type screen shows. Vouchers with no stock items — a service sale, an expense bill — could not be posted into Tally at all. And the Statistics screen could describe a company as starting up for an hour while nothing was happening to it.

Fixes

• A voucher type's numbering method now matches TallyPrime. A voucher type set to Manual could be reported as None, and a type set to Automatic as Automatic (Manual Override) — so an integration deciding whether Tally would keep or replace its own voucher number was deciding on the wrong value. TallyPrime writes the voucher type's numbering method once, when the type is created, and never updates that field again however often the setting is changed; the live setting lives on the type's numbering series. The connector now reads the series. Pulled voucher types also carry the numbering behaviour on insertion/deletion (Renumber Vouchers / Retain Original Voucher No.) and, for types using more than one numbering series, every series with its own method.
• Sending a voucher type without a numbering method no longer changes it. Updating a voucher type through the API while leaving the numbering method out used to silently set it to Automatic — which could turn a Manual type into one Tally numbers itself. The setting is now left alone unless you send it.
• A sale or purchase with no stock items can now be posted. A service invoice, room revenue, an expense bill booked straight to a ledger — anything with nothing to put in an inventory block — failed to reach Tally. Sending no inventory at all returned TALLY_IMPORT_FAILED … 'invoice_items', naming a field you never sent; sending an empty inventory list got further and was then discarded by Tally with no reason given. Such a voucher is an accounting invoice — it posts its income or expense ledgers as ordinary ledger lines — and the connector now tells Tally so. Send your income/expense ledgers in ledger_entries[] alongside the party line and the voucher imports; send inventory and nothing changes from before. Applies to Sales, Purchase, Credit Note and Debit Note.
• A push Tally would have silently parked is now refused, with the reason. Tally does not reject a malformed trading voucher outright: it answers 200, Errors: 0, Exceptions: 1 and parks a voucher carrying the party name but no particulars — which reads as a successful push and is only visible by opening the voucher in Tally. Two cases are now caught before sending. An accounting voucher whose lines do not balance is refused with both totals; where the cause is is_party sitting on an income or expense line instead of the party ledger — which silently removes the income side — the message names the offending line. An accounting voucher with nothing but a party line is refused too.
• Pulled vouchers now report Tally's own entry mode. vch_entry_mode carries Tally's "Item Invoice" / "Accounting Invoice" verbatim. Note that Tally exports an empty inventory block on an accounting invoice rather than omitting it, so use inventory_entries — not the block's presence — to tell the two apart.
• invoice_items[] / inventory_entries[] is now optional, and is_item_invoice is ignored. The connector decides whether a voucher is an item or an accounting invoice from the lines you actually send, because that flag's meaning was inconsistent between Bizmitra modules and could contradict the voucher it was attached to. Sales orders still require inventory — an order with none is now refused with a message saying so, instead of failing with an internal error.
• The voucher type filter on Statistics opens when you click it. Any filter holding more than twenty entries turns into a type-to-search box, and clicking a search box places a cursor instead of dropping the list down — so on a company with many voucher types the filter looked dead while the shorter filters beside it worked. Clicking now lists every type and typing narrows it. The filters also stop rebuilding themselves under your hand while you are choosing (the screen reloads every fifteen seconds), and the dropdown arrow is visible again on all of them.
• The Statistics filters now list only the companies you are actually syncing. A company you unsynced and removed from the connector kept offering its voucher types in the Voucher type filter, and selecting a single company still listed every other company's types alongside its own. Picking one of those showed an empty screen — which looks exactly like a company that has stopped syncing. Both filters are now rebuilt from what the connector syncs today, a selection that disappears falls back to "All" rather than quietly filtering by something that no longer exists, and the totals and breakdown no longer count a removed company's vouchers.
• A company that is not being synced now says so. If a company's voucher types are not enabled in your Bizmitra sync settings — or its scan fails every cycle — the Statistics screen said Warming up and Not scanned yet indefinitely, which reads as "starting up", not as "nothing is happening". It now names the reason on the card, per company, while the rest of the connector keeps reporting its own state.

Notes

• Voucher types already synced keep their old value until a full master scan runs. One runs automatically the first time the connector polls after it starts, and again every 30 minutes, so restarting the connector refreshes them immediately.

Overview

A first-sync release. Activating a company used to mean an afternoon of a frozen Tally and a progress screen that could not say how much was left. This release makes the connector ask Tally for only what you ticked, keeps Tally usable while it does so, and makes every screen say what is actually happening.

Fixes

• Only the voucher types you enabled are now exported from Tally. The connector used to ask Tally for the entire day book — payments, receipts, journals, contras, all with full ledger and inventory detail — and then throw away everything you had not ticked. On a company syncing only sales invoices and credit notes, most of that work existed to be discarded. It now requests each enabled voucher type directly. Custom and renamed voucher types (an "Export Sales" or a branch-specific invoice type) are recognised and included automatically. If a Tally build does not support the filter, the connector notices on the first request and falls back to the old behaviour without losing anything.
• Tally stays usable while a first sync runs. A first sync that has to run during working hours now fetches in much smaller pieces and deliberately leaves Tally idle between them, so the person using Tally is not locked out for long stretches. It speeds up on its own outside business hours.
• The sync window showed one thing and did another. On a new install the settings screen displayed "Entire book (all years)" while the sync was in fact reading a single year — and saving that screen, for any reason, made the whole-book setting real. Installs left in that state are corrected once on update, to the current financial year. Re-select "Entire book (all years)" if you need earlier years; that choice now sticks.
• The financial year is read from your company, not assumed. Companies whose books do not start in April — Bahrain and elsewhere — were given an April–March window, silently missing the year's first quarter. The connector now reads each company's own financial-year start. The old April–March option is still selectable.
• Recent vouchers can no longer be hidden by a post-dated one. A single advance invoice dated into the next financial year used to move the whole sync window forward, past everything in the current year. Post-dated vouchers still sync; they no longer decide which year is current.
• A stopped sync no longer reports itself as working. If Tally closed or stopped responding mid-sync, the statistics screen carried on showing "Voucher backfill — estimating time remaining" indefinitely. It now says Waiting for Tally, and keeps the progress so far ("stopped at 40%, resumes from there"). It will no longer say "Up to date" while Tally is unreachable.
• "Sync paused" is no longer shown when Tally is simply closed. That is now "Sync waiting for Tally" — Paused means you chose to pause it.
• The Tally connection status was out of date. It was checked only when the settings screen opened, so a window left open could claim "Tally is running" long after it had stopped. It is now stamped with the time it was checked and re-checks while you are looking at it.

Improvements

• Statistics now answers "how long will this take?" A per-company estimate and a progress bar that tracks the work honestly, refreshing on its own every few seconds while open. Progress during a first sync is measured by how much of the date range is done, which cannot overshoot — the old count could reach 100% while the sync carried on.
• "Vouchers in Tally" survives a restart and is no longer overwritten by a routine change-check. When no scan has completed yet it says so plainly instead of showing a bare zero.
• Business Hours is the default for new installs. Heavy scans move to the evening; ordinary sync and pushes continue all day. A first sync is exempt, so activating a company still completes the same day.
• Large books no longer stall on a timeout. The change-check's time limit now scales with the size of the book, instead of a fixed limit a large company could exceed on every attempt and so never make progress.

For developers

• A new environment setting points the connector's whole data directory elsewhere, so a build run from source can be tested against a company without touching an installed connector's identity, settings or log.
• Ctrl+C stops a source run cleanly instead of printing a traceback and continuing.
• A new diagnostic asks Tally which financial year a company is on, three different ways.

Multi Company Sync Support provided with this Release

Overview

A master-sync reliability release. Masters (ledgers, currencies, and other account data) now push to Tally and pull back correctly for books that use the rupee symbol and other non-English characters, a completed push is no longer reported as done until it can actually be paired, freshly pushed masters show up in the pulled feed promptly, and sync statistics are now scoped to the specific Tally company you're looking at.

Fixes

• Rupee symbol and accented characters no longer get mangled when writing to Tally. Characters like ₹ or Café could arrive at Tally garbled (₹ turning into â¹) because Tally's listener misread the character encoding. Master data is now sent using an ASCII-safe representation that Tally's XML parser resolves back to the intended character, so names and currency symbols are stored correctly.
• Currency shows the real symbol instead of "?" in pulled masters. Tally exports its base-currency symbol as a literal "?" in bulk data (even though its own screens display it fine). The connector now recognises the currency code (e.g. INR) and repairs the placeholder to the correct symbol (₹, $, £, €, ¥) on both currency masters and the currency field of ledgers.
• A master push is no longer marked "done" if it can't be paired. When Tally imported a master but its identity (GUID) couldn't be read back, the connector used to report success with no GUID — leaving a record that could never be matched up. It now treats a failed read-back as a retryable failure with a clear reason, so the push is retried until pairing can succeed.
• Statistics are scoped to the selected Tally company. Pulled-voucher counts are now filtered to the specific company you're viewing (matched by its Tally company identity) rather than mixing companies together.

Improvements

• Freshly pushed masters appear in the pulled feed sooner. Right after a successful master push, the connector requests a full master reconciliation for that company. This works around Tally occasionally omitting a just-imported object from its incremental (change-only) exports, so the new master surfaces on the next pull instead of waiting for a later full scan.
• A full master scan runs once per connector start. The first master pull after the connector starts always does a complete scan (ignoring the incremental high-water mark), providing a reliable baseline before incremental pulls take over.
• Clearer "Pending delivery" statistic. The former "Pulled" metric is now labelled "Pending delivery", with a tooltip noting the figure covers this Tally company and may include earlier scans.

Overview

A small wording refinement on the sync statistics screen.

Improvements

• Brand-neutral status wording. On the statistics screen, pulled vouchers are now described as "Pulled from Tally and awaiting acknowledgement by the connected application" (previously "awaiting ERP acknowledgement") — clearer and correct for white-label setups where the connected application isn't called an ERP.

Overview

A reliability release for large Tally books: heavy report pulls no longer time out and freeze the connector, big date ranges are fetched in smaller chunks, and sync statistics are more accurate and detailed.

Fixes

• No more freezing on large books during report pulls. Heavy reports (GST, TDS, Funds Flow, Cash Flow, Bank Reconciliation, Cash/Bank Book) and the voucher scan could hit a 30-second limit on a big company and abort the whole sync cycle — repeatedly, so some reports (GST especially) never completed on those machines. The connector now waits long enough for Tally to finish (default 120 seconds, configurable) instead of giving up early. Giving up never helped — Tally keeps building the export regardless and holds its single request slot until done — so waiting is the reliable choice.

Improvements

• Large date ranges are pulled in smaller chunks. A full financial year of vouchers in one request is too heavy for a high-volume book; date-range pulls now split automatically into smaller windows (about a month at a time), so GST and Bank Reconciliation complete reliably even on large books.
• Clearer, more accurate sync statistics. Pulled-voucher statistics now show explicit pulled counts, include pending vouchers in the totals, and can be filtered by period and voucher type — with a more optimized way of gathering these figures from Tally.

Overview

This update completes the stock value sign fix started in 0.0.35 — closing values now show the correct sign in the stock item tree as well as the summary — and adds a behind-the-scenes diagnostic that lets support resolve "stock summary is empty" questions much faster.

Fixes

• Stock item values show the correct sign. 0.0.35 corrected the sign in the Stock Summary, but some values in the stock item tree were still inverted (a negative closing showing as positive, or the reverse) — the two came from different sources and only one had been fixed. Both now use one shared rule, so stock closing values match Tally everywhere. Examples that were wrong before: WHEEL NUT 14×1.5 and Continental Valve now match Tally's sign.

Improvements

• Faster support for "stock summary looks empty" questions. A new read-only diagnostic pinpoints the cause in a single pass — the stock cycle hasn't run yet, Tally returned nothing for the requested period, the records are hidden by scope, or a mismatched date is being requested — and it distinguishes a genuine deferral (heavy reports run off-hours) from a wrong date or company. It also lists items that appear in the item tree but not the summary, which is normal: Tally's Stock Summary only carries items that have a closing balance.

Overview

This update makes master sync faster, adds an in-app control to pause syncing, and fixes how dates and amount signs are handled.

What's new

• Pause syncing from the app. A new button lets you deactivate syncing right from the connector — handy for stopping background activity without unpairing.
• New transaction types start from the current financial year. When you enable a transaction type for sync, it now defaults to the current financial year, so you get the relevant records without pulling years of old data.

Improvements

• Faster master sync. Masters (ledgers, stock items and other master data) now sync noticeably quicker.

Fixes

• Consistent dates. Dates are now normalised to DD-MM-YYYY, so they're read and shown consistently.
• Correct amount signs. Fixed a case where an amount could appear with the wrong sign (a positive value showing as negative, or vice-versa).

Overview

This update is about keeping Tally responsive while the connector works. Tally can only deal with one request at a time, so when the connector ran its bigger background reports it could occupy Tally almost continuously — and on larger books, or where Tally is reached over a network, Tally could feel slow or stop responding altogether until sync finished. The connector now paces itself, lets Tally settle after it starts, and remembers what it already did so a restart no longer sets off a fresh burst of heavy work. There is nothing to configure — it adapts to your setup on its own.

Fixes

• Tally slowing down or hanging while sync runs in the background. The connector used to send its reports back-to-back, which could keep Tally busy for the whole time a large report set was being collected — leaving little room for the person actually working in Tally. It now leaves gaps between background requests, sized automatically from how long each one took, so Tally stays usable while sync continues. Larger books and slower connections get bigger gaps, because that is where the effect was worst.
• A burst of heavy work right after Tally opens. Starting Tally is exactly when you are opening your company and running your own reports — and it was also the moment the connector tried to run everything it had been waiting to do. Heavy reports now wait a few minutes after Tally becomes available. Ordinary sync and anything you trigger yourself carry on immediately.
• Restarting the connector no longer repeats that burst. The connector used to forget how recently it had run its heavy reports whenever it was closed and reopened, so restarting it — the natural thing to do if Tally felt slow — made it start them all over again. It now remembers across restarts.

What's new

• Settings your support team can adjust for you. If your provider ever needs to change how the connector behaves on your machine, they can now do it from their end, without sending anyone out and without asking you to edit any files. The change arrives on its own within a few minutes and no restart is needed. Only behaviour settings can be adjusted this way — nothing that identifies your machine or points it at a different Tally.

Notes

• Your own work always takes priority. Vouchers you send to Tally from the web app, reports you request on demand, and a manual Sync now are never held back by the new pacing — it applies only to background work.
• Sync still completes; it simply spreads out. On a large book a full set of background reports may now take longer end to end. That is the trade being made deliberately: Tally stays usable throughout instead of being tied up until the run finishes.
• If Tally is closed, the connector stays idle as before and does not contact it.

Overview

This update is about keeping Tally responsive while the connector works. Tally can only deal with one request at a time, so when the connector ran its bigger background reports it could occupy Tally almost continuously — and on larger books, or where Tally is reached over a network, Tally could feel slow or stop responding altogether until sync finished. The connector now paces itself, lets Tally settle after it starts, and remembers what it already did so a restart no longer sets off a fresh burst of heavy work. There is nothing to configure — it adapts to your setup on its own.

Fixes

• Tally slowing down or hanging while sync runs in the background. The connector used to send its reports back-to-back, which could keep Tally busy for the whole time a large report set was being collected — leaving little room for the person actually working in Tally. It now leaves gaps between background requests, sized automatically from how long each one took, so Tally stays usable while sync continues. Larger books and slower connections get bigger gaps, because that is where the effect was worst.
• A burst of heavy work right after Tally opens. Starting Tally is exactly when you are opening your company and running your own reports — and it was also the moment the connector tried to run everything it had been waiting to do. Heavy reports now wait a few minutes after Tally becomes available. Ordinary sync and anything you trigger yourself carry on immediately.
• Restarting the connector no longer repeats that burst. The connector used to forget how recently it had run its heavy reports whenever it was closed and reopened, so restarting it — the natural thing to do if Tally felt slow — made it start them all over again. It now remembers across restarts.

What's new

• Settings your support team can adjust for you. If your provider ever needs to change how the connector behaves on your machine, they can now do it from their end, without sending anyone out and without asking you to edit any files. The change arrives on its own within a few minutes and no restart is needed. Only behaviour settings can be adjusted this way — nothing that identifies your machine or points it at a different Tally.

Notes

• Your own work always takes priority. Vouchers you send to Tally from the web app, reports you request on demand, and a manual Sync now are never held back by the new pacing — it applies only to background work.
• Sync still completes; it simply spreads out. On a large book a full set of background reports may now take longer end to end. That is the trade being made deliberately: Tally stays usable throughout instead of being tied up until the run finishes.
• If Tally is closed, the connector stays idle as before and does not contact it.

Overview

This update brings your key Tally reports into the connector. The Reports tab now shows financial and inventory statements pulled straight from Tally — including the new Cash/Bank Book(s) view — so you can check balances and figures at a glance without opening Tally. Reports refresh on their own and always mirror what Tally shows.

What's new

• Cash/Bank Book(s) report. A new report lists every cash and bank ledger, grouped under its heading, with its closing balance (Debit / Credit) — exactly like Tally's Cash/Bank Book(s) screen (Cash-in-Hand and Bank Accounts, with each ledger underneath). It refreshes automatically, so the connector always shows current balances.
• A complete Reports tab. The Reports tab now covers Stock, TDS Payable, GST Returns (GSTR-1 & GSTR-3B), Funds Flow, Cash Flow, Bank Reconciliation, and Cash/Bank Book — each pulled from Tally and kept up to date on its own schedule, and each viewable per company with a row-level detail view.

Improvements

• Figures match Tally exactly. Every report is reconstructed to mirror Tally's own screens (validated against real Tally exports), so the numbers you see in the connector line up with the numbers in Tally — same rows, same closing balances.
• Lighter, on-its-own-schedule refresh. Reports are heavier than voucher sync, so they refresh on a slower, separate cadence and can be deferred to off-hours — they never slow down your day-to-day voucher syncing.

Notes

• Reports are read-only views pulled from Tally — nothing is ever written back.
• Each report appears only when your provider has enabled it for your account; if a report isn't turned on for you, it simply won't show — nothing else changes.

Overview

This update makes the connector more resilient and far easier to support. If it ever hits an unexpected problem it now recovers on its own and can tell us exactly what happened (with your permission), so crashes and freezes get fixed quickly instead of staying a mystery. It also runs lighter on memory and rides out network hiccups more gracefully. You can now choose where it installs, and — where your provider requires it — approve data-processing consent right from your account.

What's new

• Automatic recovery from freezes. If a sync task ever gets stuck, the connector now notices and restarts that background task by itself — with sensible limits so it never loops — instead of sitting frozen. You don't need to do anything.
• Crash reporting you control. If the app closes unexpectedly, it now safely records a technical diagnostic report (what went wrong, the app version, and system resource usage — never your vouchers or passwords). A new Diagnostics setting lets you choose how it's handled: Ask (you're prompted before anything is sent — the default), Automatic (sent on its own to help support), or Off (kept only on your machine). You can add a short note about what you were doing.
• Choose your install folder. The installer now lets you pick where the connector is installed, and Settings → Installation shows the current location with an Open folder button. Upgrades keep the folder you chose.
• Data-processing consent (when your provider enables it). If required, the app now tells you when sync is paused pending consent and points you to your account to approve it. Sync resumes automatically once it's granted. If your provider doesn't require this, nothing changes.

Fixes

• Freezes and "Not Responding" during syncing. A slow or stuck request to Tally or the network could previously hang the app. Requests now time out and retry sensibly instead of blocking, and a wedged sync task is restarted automatically — so the window keeps responding.
• Out-of-memory slowdowns and crashes on large books. Big bulk pulls held too much in memory at once — a leading cause of slow-downs and crashes. The connector now works in smaller chunks (about half the previous peak memory), and an unusually large single voucher is set aside and reported instead of taking down the whole batch.

Improvements

• Steadier connection to the server. Network calls now reuse a shared, pooled connection and retry brief blips automatically, so momentary outages cause fewer interruptions.
• Much faster problem diagnosis. When something does go wrong, your provider's support can now see why — the crash details, the conditions leading up to it, and whether it's a one-off or a recurring pattern — from central diagnostics, so you no longer have to find and send log files by hand.

Notes

• Everything the connector reports about itself is technical only — sync outcomes, timing, and resource usage — with no business data or credentials, and it's queued safely if the server is briefly unreachable (it never blocks your syncing).
• The Diagnostics setting defaults to Ask, and data-processing consent is only requested if your provider turns it on — otherwise the app behaves exactly as before.

Overview

This update makes pulling vouchers from Tally complete and dependable. The connector now syncs your entire history by default (not just the current financial year), your most recent vouchers appear promptly even when there's a large backlog, and a momentary Tally hiccup no longer stops a sync partway through.

What's new

• Your full history syncs by default. Earlier versions pulled only your current financial year unless you changed a setting, so older years never came across on a default install. The connector now syncs the whole book — every financial year — reading each company's own "Books beginning from" date so it never wastes time on empty periods. Prefer to limit the range? You can still choose a specific financial year or date range.

Fixes

• Recent vouchers no longer wait behind a backlog. When a company had a lot to catch up on, the newest vouchers could sit at the back of the queue and take a long time to appear. Sync now brings in the most recent vouchers first, so today's entries show up quickly while older ones continue in the background.
• A brief Tally hiccup no longer stops the whole sync. A single slow or dropped request to Tally used to abort the entire cycle — the rest of that company and every other company had to wait for the next round. The connector now rides out a momentary blip (skipping just that one voucher, retried next cycle) and pauses only when Tally is genuinely down.
• Busy days no longer get skipped. If Tally returned an unusually large or garbled batch for a date range, that whole range could be dropped silently. The connector now automatically re-fetches the range in smaller pieces, so at most a single day is ever affected — and it's clearly noted in the activity log.
• Post-dated vouchers are included. Vouchers dated ahead — an advance, or the first entries of a new financial year — could previously fall just outside the sync window. They're now picked up.

Notes

• This reverses the "current financial year only" default introduced in v0.0.20 — by request, full history is now the default.
• One-time catch-up: on the first sync after this update, connectors that were on the old default will pull their earlier years in the background. It runs in bulk, is safe to leave running, and never duplicates vouchers you already have.

Overview

A maintenance update with small fixes and interface polish.

Fixes

• Correct account owner and version shown. The footer and Home screen now always show your real account owner and the actual installed version. Some earlier builds could display a leftover placeholder (for example an acme-textiles owner or a v1.0 version) that didn't match the paired account or the release you're running.

Improvements

• Minor interface polish and under-the-hood refinements for a more consistent, stable experience.

Overview

This update fixes automatic updates for connectors installed on a drive other than C: and makes the app keep working on machines where the C: drive is locked down.

Fixes

• Auto-update now works on any drive. When the connector was installed somewhere other than C: (for example E:\…), an update could fail with "Update could not be applied". The update is now prepared in the app's own folder, so it installs correctly no matter which drive the connector runs from.

Improvements

• Runs on locked-down PCs. The connector's settings and support log (config.json, connector.log) now adapt automatically: if the usual Windows location isn't writable, they're kept safely alongside the app instead — so a restricted C: drive no longer stops the connector from running or logging.

Note: this fix must be installed once manually on any connector that is already on the affected version; after that, future updates apply automatically.

Overview

A maintenance update that makes the connector easier to support with a cleaner, safer activity log.

Improvements

• Smaller, safer support log. The connector keeps an activity log (connector.log) that is now:
  • stamped with the date and time of every entry, so an issue can be pinned to exactly when it happened;
  • automatically scrubbed of sensitive details (server address, keys and identifiers) — so the file is safe to send to support;
  • no longer bloated with large technical data on every voucher, keeping the file small.
• Clearer sync activity. Each pull cycle records the exact date window it scanned, making it easy to see at a glance what range of vouchers is being pulled.

Overview

This update makes syncing selective. The connector now pulls only the voucher types and reports that have been enabled for it in Bizmitra, instead of everything — so you sync exactly what you need, with less data transferred and less storage used.

What's new

• Sync only what's enabled. Which voucher types (Sales, Purchase, Receipt, Payment, Credit/Debit Note, Contra, Journal, Sales Order) and reports (stock summary, masters) get pulled is now controlled from Bizmitra. The connector reads that list and pulls only those — anything not enabled is never scanned, fetched or uploaded.
• Follows your settings automatically. Turn a voucher type or report on or off in Bizmitra and the connector picks up the change on its next sync (within about a minute) — no reinstall or restart needed.
• Lighter on Tally and your connection. Skipping the voucher types you don't need means fewer Tally requests and less uploaded data on every cycle, which keeps large books syncing quickly.

Notes

• If nothing is enabled for a connector, it syncs nothing until at least one voucher type or report is turned on — this is intentional, so you only ever sync what you've chosen.
• Connectors that aren't set up with a specific enabled list keep syncing every voucher type as before — unchanged.

Overview

This update makes pulling vouchers from Tally far faster and more complete. The first sync of a company now finishes in minutes instead of hours, every voucher arrives with its full details, and syncing stays smooth without freezing. Sync also now focuses on your current financial year by default, read straight from your Tally company.

What's new

• Much faster first sync. Instead of pulling vouchers one at a time, the app now fetches them in bulk by date range. A company's current year of vouchers syncs in a couple of minutes rather than dragging on for hours.
• Syncs your current financial year automatically. The app reads the financial year directly from your Tally company — so it works whether your year starts in January, April, or any other month — and brings in that year's vouchers. It follows the year your data is actually in, so there's always something to sync. (Choosing a different period from within the app is coming in a follow-up update.)

Fixes

• Vouchers now include all their details. Some pulled vouchers were arriving empty — no items, no ledgers. Every voucher now comes in complete, with its line items, quantities, amounts and ledger entries.
• The "Synced" count keeps up. Pulled vouchers are now delivered to Bizmitra continuously in the background, so the Synced total climbs steadily instead of getting stuck at zero.
• No more freezing or dropped connection during large syncs. Big syncs could make the app hang or lose its connection; they now run smoothly in the background without blocking the app.
• Vouchers no longer re-sync in a loop. A problem that caused already-synced vouchers to be pulled over and over — which kept the Synced count from rising — is fixed.
• Correct units for dual-unit items. Items measured in two units (for example "1.90 mtr = 0.317 PCS") now show the right unit.
• Cleaner activity log. The console no longer prints large technical responses on every voucher.

Notes

• Only your active financial year syncs by default. Earlier years aren't pulled automatically yet — a period picker to include them is coming next. Vouchers you've already synced stay as they are.
• Internal stock-movement documents (Stock Journals, Gate Passes) aren't pulled, as they don't carry standard sales/purchase lines.

Overview

This update makes the sync controls faster and easier to reach, and fixes automatic updates so the app reliably picks up new versions.

Improvements

• Sync controls moved to the top of the Synced-companies screen — Pause, Resume and Unsync now sit right under the header, above the company list.
• The selected company stays selected after you pause or resume it, so the buttons stay usable instead of greying out.

Overview

This update syncs all your everyday vouchers both ways between Tally and Bizmitra — not just sales — and now recognises when a voucher has been cancelled in Tally.

What's new

• More voucher types sync from Tally. Alongside Sales invoices and Sales Orders, the app now brings in Receipts, Payments, Contras, Journals, Purchases, Credit Notes and Debit Notes automatically. Your custom and renamed versions of these are picked up too.
• Send more voucher types to Tally. You can now push Receipts, Payments, Contras, Journals, Purchases, Credit Notes and Debit Notes from Bizmitra into Tally — earlier this was limited to sales invoices and orders.
• Cancelled vouchers are recognised. Cancel a voucher in Tally and the app now detects it, marks it Cancelled, and highlights it — even for a voucher that had already been synced.

Improvements

• New Cancelled column on the pulled-vouchers screen, with cancelled rows highlighted so they stand out at a glance.
• Foreign-currency amounts and cheque / bank details on receipts, payments and contras are captured accurately.

Fixes

• Cancelling a voucher that was already synced is now picked up reliably.

Overview

This update makes the sync recognise your custom and renamed Sales / Sales Order voucher types automatically, so the invoices and orders created under them are synced too.

What's new

• Your custom voucher types now sync. If you use your own Sales or Sales Order voucher types — for example "Sales - Amazon", "Online Sales", or a renamed default — their invoices and orders are now picked up and synced automatically. No extra setup needed.
• New voucher types are detected quickly. A voucher type you've just created starts syncing from the next sync cycle.

Improvements

• More accurate voucher classification for renamed voucher types.

Fixes

• The app no longer downloads the same update repeatedly, and now prompts you to restart to finish updating.

2026-07-09 — Stronger separation between your applications

What's new

Each of your applications now works in complete isolation. An API key belongs to a single application and only ever works with that application's companies — never another application's, even within your own account.

• Your API keys only reach companies that belong to their own application.
• In the connector's company selection screen, only that application's companies appear — companies from your other applications never show up.

What you might notice

• When you add a new company, it's automatically placed under the application your key belongs to — you don't need to choose one.
• When you list your companies, you'll see only the ones for that application.
• If a request points at a company from a different application, it's declined with a clear message explaining why.

Action needed

• Using an older key that isn't linked to an application? Create a new key for the specific application from the API Keys page. Older unlinked keys can no longer reach companies.
• Was a connector set up for your whole account? Re-pair it using a customer pairing code so it's tied to the right application. Until then, its "add a company to sync" list stays empty — companies it's already syncing keep working normally.

Good to know

• Your normal requests don't change — existing per-application keys keep working as before.
• The connector updates on its own; there's nothing to install.