VauPrime Docs
Advanced FeaturesCurrent app behaviorDart-source backed

Tally Data Import

Complete guide to the desktop VauPrime Tally Prime importer: local connection, company information, matching financial years, previewing data, importing masters and vouchers, resolving missing mappings and reviewing results.

Source

Tally Prime

Local HTTP/XML connection at localhost:9000

Access

Elite or higher

Plan is checked before importing records

Validation

Financial Year

Matching active April–March FY required

Import types

Masters + vouchers

Category-level preview and import controls

What is Tally Data Import?

Purpose and current behavior of this feature.

VauPrime Tally Data Import connects the desktop application to a running local Tally Prime HTTP service. The current Flutter screen is TallySyncLogic with a desktop sidebar and global header. It requests XML over HTTP from http://localhost:9000 and parses company information, groups, ledgers and vouchers. It is not a browser upload form, cloud Tally sync, or a generic Tally backup-file upload workflow.

The importer offers a connection panel, selected financial year and compatibility check, company details, preview cards and data tables, and a Start Import action. The initial preview loads groups, ledgers and voucher data in parallel; additional masters can be requested separately from their section cards.

Import actions check subscription access (Elite or higher) and selected financial-year compatibility. Data is inserted through dedicated VauPrime routines with group-parent matching, account resolution, date checks and duplicate handling. Import results require review; the total preview-record count is not proof that all records were successfully inserted.

Android UI structure

Screen-by-screen structure, tabs, lists, taps and action behavior on Android.

Platform supportThe inspected importer builds with WindowGlobalSidebar and GlobalHeader and relies on a local localhost:9000 Tally service. This is a desktop-oriented flow; Android access should not be assumed without a separately supported bridge.
No website uploadThe documentation and marketing pages explain the import; they do not implement a browser-based XML/backup upload or cloud-based Tally access.
Plan requirementsThe import method checks SubscriptionPlanAccessService.isAtLeastElite. An ineligible plan opens an upgrade bottom sheet.
Connectivity requirementTally Prime must be running and listening on the expected HTTP service address reachable from the computer running VauPrime.

Windows UI structure

Desktop layout, wide-screen controls, tables and row actions on Windows.

Application shellThe screen shows Windows Global Sidebar, Global Header, connection and synchronization panels, company metadata, preview cards, preview data table and an optional result panel.
Connection panelUse Test Connection to check whether Tally Prime responds. A successful test loads company information. Failed attempts offer troubleshooting guidance.
Financial Year selectorSelect an April–March year; changing it clears existing preview and imported-widget state.
FY compatibilityChecks active financial_years in VauPrime for a matching start and end date; if missing the interface reports Not Compatible, Create FY First.
Preview DataLoads groups, ledgers and all vouchers for the selected financial year, then categorizes vouchers into Sales, Purchase, Receipt, Payment, Journal, Contra and Debit/Credit Notes.
Preview cardsShows counts and section-specific details; optional masters such as units, items and godowns may be loaded on demand.
Start ImportEnabled only after connection, preview and financial-year compatibility. Imports supported categories sequentially with a progress indicator.
Section importSection-level import controls let you work with individual available categories instead of relying exclusively on the full import.
Import resultCompletion panel summarizes processed data and import activity. Review category messages for skipped, duplicate, invalid or failed records.

Connection, preview and import controls

The current TallySyncLogic, TallyHTTPService and TallyImportDbLogic implementation.

Tally Prime connectionTallyHTTPService.baseUrl is http://localhost:9000. The service sends XML HTTP POST requests with Content-Type text/xml; charset=UTF-8.
Test ConnectionRuns checkTallyConnection, updates the status and loads company data on success. On failure, the screen displays a connection-error or troubleshooting panel.
Company metadataShows information fetched from the connected Tally company and helps confirm the correct company is active.
Selected Financial YearThe picker uses April of the selected year to March of the next year. It clears prior preview data after a change.
FY compatibilityA matching active financial year must exist in VauPrime's financial_years table for the selected organization before preview/import.
Preview DataThe initial preview fetches groups, ledgers and vouchers; optional groups of data such as stock masters can be fetched by their own controls.
GroupsImports supported Tally account groups; unresolved parent groups can require mapping to VauPrime group masters or skipping.
LedgersImports ledger/account masters with account mapping and opening-balance handling where supported.
Units / Items / GodownsStock units, stock item masters and godown data have dedicated fetch/import routines. Their preview lists can be empty until requested.
Sales / PurchaseUses dedicated insert logic with voucher number, party/account, date, stock items, bill-sundry and duplicate/conflict handling.
Receipt / Payment / Journal / ContraUses voucher-category-specific transaction import helpers and resolves required accounts for entries.
Debit Note / Credit NoteIncludes dedicated voucher import routines, with record-level validation and duplicate handling.
Import orderFull Start Import processes Groups, Ledgers, Units, Items, Godowns, Purchase, Sales, Receipt, Payment, Contra, Journal, Debit Note, Credit Note.
ProgressThe full import progress fraction follows completion of each category step; it does not guarantee every record succeeded.
Plan checkAt least the Elite subscription is required by the current importer before data insertion.
Voucher financial yearPreview requests vouchers from 1 April of the selected year through 31 March of the next year.
Preview countsA displayed category count represents discovered preview rows. Imported, skipped and failed record counts can differ.

Tally Prime to VauPrime — setup and import

Follow the current in-app flow from start to completion.

01

Prepare a copy of your records

Back up Tally and the target VauPrime organization before a migration. Review the company and financial year you intend to transfer.

02

Start Tally Prime on the same machine

Open the source company in Tally Prime and enable/configure its local HTTP service on port 9000, reachable at http://localhost:9000.

03

Open the Windows importer

In VauPrime, select the destination organization and navigate to Tally Data Import in Settings / Import Export.

04

Test the connection

Click Test Connection. Confirm VauPrime has connected and loaded the expected Tally company metadata.

05

Select the target financial year

Choose the intended April–March period. If it reports Not Compatible, Create FY First, create/activate the matching FY in the organization and retry.

06

Preview available records

Choose Preview Data and inspect group/ledger counts and category-wise voucher data. Load optional stock masters when required.

07

Inspect mappings

Review missing parent groups, account names, bill-sundry mappings, ledger opening values and voucher date assignments before importing.

08

Choose import scope

Use Start Import for the documented sequence, or the available section-specific action when importing a selected category.

09

Review progress and results

Watch category progress and inspect success/skip/duplicate/error feedback, not only the overall preview count.

10

Reconcile after import

Compare group masters, ledger opening balances, sales/purchase vouchers, daybook and Balance Sheet figures with the source Tally company. Investigate differences before operational use.

Validation and common checks

Checks and restrictions applied by the current screen.

The current importer depends on the localhost:9000 Tally HTTP/XML service. Network access and port configuration must be correct on the machine running it.
Tally Data Import is restricted to Elite or higher subscription plans by SubscriptionPlanAccessService.
The destination organization and authenticated account must be available for inserts; permissions and record validation still apply.
An active VauPrime financial year with exactly matching start and end dates is required for the selected April–March period.
Changing the financial year invalidates the existing preview. Fetch a fresh preview after changing FY.
Preview must complete before Start Import. If _previewData is null, the importer blocks the action.
A successful connection or preview does not guarantee that all accounting rows can be imported; invalid accounts, missing mappings, duplicate voucher numbers and date issues may skip individual records.
The initial preview deliberately does not fetch every optional master. Load units, stock items and godowns when those are needed.
A full import is not an atomic all-or-nothing database transaction across categories; inspect partially imported data after errors and avoid blindly rerunning.
The code's totalImported in the final summary is based on attempted preview records, not a verified count of successfully inserted rows.

Important behavior and notes

Details worth knowing before using the feature in daily work.

Source files: App_P0_VauPackage/lib/screens/Settings/ImportExport/Services/Tally/tally_sync_logic.dart, tally_sync_ui.dart, tally_import_db_logic.dart and ParsingService/tally_http_service.dart.
The HTTP service sends XML payloads for Tally Prime export reports, parses results and uses additional voucher/master lookups as necessary.
A local connection uses http://localhost:9000 on the importer's own machine. A browser at docs.vauprime.com cannot use that connection automatically.
Missing group parent mapping can be reviewed in a selection sheet and may prevent a group from importing until a valid parent is resolved.
Voucher import routines include date and voucher-number collision checks and account resolution. Financial-year setup and accurate masters should be reviewed first.
The app includes a special sales-date resolution workflow and bill-sundry account replacement handling; use the presented prompts rather than inventing an account mapping.
For failed connections, confirm Tally Prime is running, the expected company is open, its HTTP server is enabled, port 9000 is available, and no firewall or local service is blocking access.
After import, compare Tally and VauPrime opening balances, account totals and voucher counts. Data quality depends on the source company's records and target account mapping.
The marketing page at www.vauprime.com/tally-data-import is an overview, not an authenticated data-migration tool.