ReadyBooks supports direct Tally Prime XML import. Parties, items, ledgers, vouchers, and opening balances map automatically. Most small businesses complete migration in a single session.
The import wizard reads your Tally XML, classifies every record, and maps it into the ReadyBooks model with field-level fidelity.
From Tally: Tally ledger groups Sundry Debtors / Sundry Creditors
Into ReadyBooks: ReadyBooks Parties with Customer / Vendor flags, GSTIN, addresses, and contact info
From Tally: Tally Stock Items, Stock Groups, Units of Measure
Into ReadyBooks: ReadyBooks Inventory items with HSN/SAC, GST rates, units, and opening stock
From Tally: Tally Ledgers under all standard groups (excluding Sundry Debtors/Creditors)
Into ReadyBooks: ReadyBooks Chart of Accounts mapped to standard categories with parent groups preserved
From Tally: All Tally voucher types from your selected period
Into ReadyBooks: ReadyBooks invoices, bills, payments, receipts, and journal entries with original dates and numbers
From Tally: Tally opening balances for ledgers and stock as of the financial year start
Into ReadyBooks: ReadyBooks opening balance journal posted on the chosen cutover date
From Tally: Tally Cost Centers and Cost Categories
Into ReadyBooks: ReadyBooks Tags applied to entries; existing assignments preserved
The whole flow is reversible. You can re-run the import after any change in Tally without creating duplicates — every voucher is matched on its original voucher number and date.
Open Tally Prime → Gateway of Tally → press F3 → Backup → choose XML format → select the company and date range. A typical one-year backup is 5–50 MB.
Create your account at readybooks.ai/signup. Free in under a minute, no credit card needed. Set up your business profile (GSTIN, fiscal year, currency).
Settings → Import → Tally XML → upload your file. The wizard parses the XML, shows a preview of every data type with counts, and flags any conflicts (duplicate party names, missing references) before committing.
Spot-check three balances against Tally — a customer balance, a vendor balance, and the GST liability. Run the trial balance in both systems for the same date and confirm they match. Most discrepancies (under 1%) come from rounding and resolve on the first cleanup voucher.
Pick a cutover date, lock posting in Tally beyond that date, and continue posting in ReadyBooks. Keep Tally accessible read-only for historical reference. Re-imports are safe — duplicate vouchers are detected and skipped.
Real Tally setups aren't textbook. The wizard accommodates the common deviations — here's what to expect.
A single Tally XML can contain multiple companies. The import wizard detects this and asks which company to load. For CA firms, import each company as its own ReadyBooks tenant.
Voucher types you defined in Tally (e.g. "Cash Sale", "Material Out") map to the parent class (Sales, Stock Journal) with the original type kept as a tag — so your custom-named reports still work in ReadyBooks.
Tally.ERP 9 below Release 6 has XML schema differences. Upgrade to the latest ERP 9 (free) or Tally Prime first; both export the schema we ingest. The import wizard flags any unsupported elements before committing.
Ledgers marked as inactive in Tally still come over as inactive in ReadyBooks. They're hidden from new transactions but remain visible in historical reports — no data lost.
Technical questions teams ask before they start the import.