Tally Customization

Tally already runs your books.Make it run your business.

One accountable India-based team brings implementation, operations and detailed handover together, with a tailored scope and India-based service rates. For finance teams whose Tally workflows rely on repeated exports or manual workarounds, customization adds scoped reports, validations and integrations around the books. We begin with the accountant’s rules and the current Tally version. Development is reviewed against a copy of company data, with source and maintenance guidance delivered to the client.

What's included

Concrete deliverables, with the details agreed upfront.

Why Archonova: one accountable team, India-based rates, your repository and your data, and detailed handover. Start quickly with a scoped pilot, using strong working-hour overlap with the Gulf and Africa or structured handoffs for the USA and Canada. The deliverables below turn your priorities into reviewable work. Where needed, hosting in the UAE is delivered through our partners in the UAE; ARCO Mail is available in any country.

  • Finance workflow specification

    Observe the voucher, report or integration problem with the accountant who owns it. Record required inputs, expected output and exceptions, so the developer implements approved accounting behaviour.

  • TDL module design

    Package the agreed customization with clear dependencies and configuration. Review supported Tally behaviour and existing extensions before changing it, keeping the scope modular so a future engineer can understand what was added and why.

  • Reports and print formats

    Define calculations, grouping and document fields with finance, using representative transactions. Reconcile output against the source records and approved examples, so acceptance checks the financial meaning as well as the appearance of a report or invoice.

  • Voucher and field validation

    Implement the approved checks and additional information needed for the workflow. Test rejected and unusual cases with the owner, explaining how users correct records.

  • Integration mapping

    Assess the external application’s interfaces and map identifiers, fields and ownership. Define duplicate handling, reconciliation and failure recovery before connecting systems, so a repeated transfer does not create uncertain or conflicting financial records.

  • Safe test environment

    Use a controlled copy of company data and restrict engineer access under agreed handling arrangements. Validate existing customizations and representative transactions together, recording limitations.

  • Deployment and rollback

    Prepare a verified backup, approved deployment window and recovery instructions before applying the customization. Confirm the new output with the accountant after release, with unresolved issues and rollback decisions visible to the person responsible for the books.

  • Source and upgrade handover

    Deliver the scoped TDL source and dependencies with installation and re-test guidance. Identify pre-existing components and licence conditions, and explain which workflows need review when Tally or a connected application changes.

Running Tally on one office machine?

Customization and hosting are two different problems. If your books also need to be reachable from other branches — with automated backups and access control — we host TallyPrime and Tally ERP 9 on our own cloud and VPS infrastructure.

See Tally on Cloud

Remote access

Run Tally and Windows apps remotely with TSplus

Archonova is a TSplus reseller. Buy TSplus through us and pay significantly less than TSplus's published online prices, with installation, Tally and ERP setup, and ongoing support included.

Explore TSplus

Related capabilities

One team for the connected work.

When you need this

Situations your team may recognise.

  • Finance repeatedly rebuilds a report

    A standard export does not answer the recurring business question. Define the calculation and source transactions with the accountant before building a custom report that staff can reconcile and maintain.

  • Vouchers need consistent business checks

    Required fields or validations depend on people remembering a rule. Encode approved requirements with clear correction messages, retaining finance ownership of the accounting treatment.

  • Tally must exchange records with another system

    A CRM, inventory or application handoff causes re-entry. Map record ownership, supported interfaces and reconciliation before introducing automated transfers into the books.

  • Existing customizations need maintenance

    An upgrade or changed workflow affects old TDL. Inventory extensions, preserve test cases and review source and dependencies before deploying another change.

Intended outcomes

What a Tally customisation is meant to change

The goal is fewer manual steps between what your business does and what Tally records.

  • Data entry cut at the source

    Sales, purchase and payment data flowing in from your website, ERP or field application instead of being keyed a second time into Tally.

  • Vouchers that match how you trade

    Custom voucher types, mandatory field validation and approval controls that reflect your actual process, not a generic default.

  • Reports your accountants stop rebuilding in Excel

    Custom reports and print formats generated inside Tally, so the monthly pack does not depend on one person's spreadsheet.

  • Compliance filings prepared with less reconciliation

    GST, TDS and e-invoice data captured correctly at entry, so return preparation is a check rather than a clean-up exercise.

  • Controls on who can change what

    Role-based restrictions and edit logging on sensitive vouchers and masters, so changes are traceable.

  • Customisations that survive upgrades

    TDL written to be maintainable and re-tested against new Tally releases, rather than a patchwork nobody dares touch.

How it works

A clear process, with responsibilities at every step.

  1. 01Assess the real work

    We walk through normal work and difficult cases with the people responsible for the process. We identify access, data and external dependencies before recommending a delivery approach.

    You provideTally version, accountant-approved rules and current extensions.

    You receiveA current-state map, feasibility findings and a prioritised scope, including questions that need an owner decision before work can proceed.

  2. 02Design and agree the scope

    We turn the findings into a practical implementation plan with clear responsibilities and review points. You approve the scope and priorities, giving the team a focused route to delivery.

    You providereport examples, integration ownership and test-data permissions.

    You receiveA reviewed design and delivery backlog with acceptance examples, dependencies and the agreed route for handling changes.

  3. 03Build and validate

    We deliver reviewable increments and exercise the important failure paths in an approved environment. Your nominated owners review the evidence and confirm whether each increment meets the agreed behaviour.

    You providecompany-data copy, expected balances and acceptance by finance.

    You receiveReviewable deliverables, relevant test evidence and a clear issue list, with correction or deferral decisions visible to the client owner.

  4. 04Support the transition

    We prepare the transition with documented operating tasks, a receiving-team walkthrough and clear support contacts. Your owner approves release, and your team receives the knowledge to operate and extend the result.

    You providesource recipients, upgrade responsibilities and support contacts.

    You receiveAn accepted handover pack, operating walkthrough and a transition checklist with named responsibilities and support escalation.

Engagement options

How Tally engagements are structured

From a single report to a fully integrated Tally environment — sized to what you actually need changed.

Fixed-scope customisation

A defined set of TDL changes — reports, print formats, voucher types, validations — quoted and delivered against a written specification signed off by your accounts team before development starts.

Best for: A known list of gaps in your current Tally setup.

Integration build

Connecting Tally to your other systems — e-commerce, CRM, ERP, banking or a custom application — with mapping, scheduling, error handling and reconciliation reporting so failed records are visible rather than silently lost.

Best for: Duplicate entry between Tally and another system.

Support and enhancement retainer

Ongoing cover for your customisations: fixes, small enhancements, statutory and Tally version updates, and a monthly allocation of development hours, under an agreed response target.

Best for: Businesses depending on customised Tally daily.

Dedicated team

An agreed team works an evolving backlog with your product or process owner. Planning, demonstrations and quality reviews follow a shared cadence; your priorities guide the work and capacity changes are discussed through the engagement terms.

Best for: A continuing roadmap that benefits from consistent delivery context.

Handover

What you get at handover.

Documents, artefacts and access

Handover includes the scoped TDL source, report and validation specification, integration mappings and test evidence. Finance and technical owners receive deployment, backup, rollback and upgrade re-test instructions, with component ownership and support terms recorded.

Account ownership, repository permissions and third-party licences are checked with your nominated administrator. Secrets are transferred only through approved secure channels, and temporary access is removed or reassigned at transition.

Training and support terms

Your receiving team gets a practical walkthrough of everyday operation, important exceptions and administrator tasks, with clear documentation they can use after handover. Bring the people who will maintain the result so training fits their work.

Continuing support is arranged around covered work, service hours, response targets, change requests and escalation. We coordinate platform issues and operating tasks with named owners, giving your team a clear route for help and future improvements.

Tools and platforms

Technologies we work with.

We match the tools to your existing environment and the capabilities your team needs. Compatibility checks, practical implementation and documented handover help you maintain the result with confidence. Share your current stack and preferred platforms with us.

  • TDL (Tally Definition Language)
  • TallyPrime
  • Tally ERP 9
  • GST & Compliance Reporting
  • Multi-Location Data Sync
  • REST/SOAP APIs

Related services

Connect this work to the next requirement.

  • Tally on Cloud

    TallyPrime and Tally ERP 9 hosted on Archonova's own cloud and VPS infrastructure — access from anywhere, backed up automatically.

  • ERP & CRM

    Business systems, data migration and connected sales, finance and operations workflows.

  • Invoice Automation

    Invoice capture, extraction, PO/GRN matching and ERP posting — with approval controls and human exception handling.

  • Automation Enablement

    Business process automation across your actual systems — not just one script, a coordinated automation practice.

FAQ

Questions we get asked about Tally customisation

Licensing, upgrades, data safety, timelines and who can maintain the work afterwards.

Let's make Tally work the way you do.

Tell us how your team uses Tally today and where it forces a workaround. We'll come back with a customization scope that closes the gap. We work with clients across India, the Gulf, Africa, the USA and Canada.