LekhaLift

How it works

From invoice to Tally.
With you in control.

AI prepares the draft. You check the bill and approve the entry.

  1. 01

    Upload

    Choose the company and upload a photo or PDF.

  2. 02

    Claude extracts

    Claude extracts the details and suggests the ledger and GST.

  3. 03

    You approve

    Check the source. Edit, approve, or reject the draft.

  4. 04

    Posted to Tally

    The connector posts the approved voucher and checks the response.

Human approval comes first. AI suggestions can be wrong. The accountant decides the ledger and GST treatment.

Interactive walkthrough

See the approval checkpoint.

Sample workflow

Try a sample invoice below. This browser-only walkthrough uses fixed sample data. It does not call Claude or post to Tally. For a real invoice-to-voucher demonstration in the installed app, request a demo.

Sample invoice · Delhi

Demo Office Supplies

Invoice DEMO-001 · 10 October 2026
Buyer: Demo Accounting · Delhi

Paper and toner
₹9,900.00
CGST (example: 9%)
₹891.00
SGST (example: 9%)
₹891.00

Total₹11,682.00

Illustrative transaction and tax split, not a real client invoice or GST determination.

Step 1 of 4 · Upload

Start with the sample invoice to see how a draft moves through review.

No sample action yet.

    Available for
    your daily work.

    Five workflows offered in the installed LekhaLift app. The website walkthrough uses sample data; request an installed-app demonstration and confirm your Tally setup during onboarding.

    Invoice to voucher

    Turn a purchase bill into a draft. Review it before posting.

    Available

    Bank reconciliation

    Compare bank statements with Tally entries. Review unmatched items.

    Available

    GSTR-2B matching

    Match supplier invoices and purchases against GSTR-2B. Check differences.

    Available

    Ask your books

    Ask questions about your accounts in plain English.

    Available

    Notice-reply drafts

    Prepare a draft from the notice and supporting records. A CA reviews it before use.

    Available

    Tally tools & customisations

    Useful additions.
    Built around your work.

    Alongside LekhaLift, explore focused TDL customisations and a local reporting app. We confirm your installed release, scope and quotation before setup.

    Invoice address automation

    TDL customisation

    Automatically select a configured company address for invoice printing and export. Adapt the company and address settings to your business.

    Discuss setup ↗

    Child & fee management

    TDL customisation

    Maintain child records and a fee tracker. Review the fee dashboard, overdue alerts, pending fees and missing due dates. Stores operational records in the Tally company using UDFs.

    Discuss setup ↗

    OpenTally Audit Suite

    Local reporting app

    Read Tally data for stock statements, ageing, GST and bank reconciliation reports, audit packs and Excel exports. This separate app reads accounting data; it does not post vouchers to Tally.

    Discuss setup ↗

    Customisations are scoped separately from the LekhaLift free pilot. Version compatibility and commercial terms are confirmed before installation.

    Trust & security

    Your books deserve
    a careful checkpoint.

    Review first. Keep Tally local. Confirm permissions and data-handling terms during onboarding.

    Approval before posting

    Check the source invoice, ledger and GST before approving a voucher.

    A traceable audit trail

    Trace the invoice, edits, approval and Tally response. Inspect a real record during activation.

    Only the access needed

    Configure a dedicated user and verify the connector's effective permissions. Tally documents user roles and voucher permissions; role settings alone do not prove that an XML connector enforces them.

    Keep port 9000 restricted

    The connector uses Tally's local XML interface. Restrict port 9000 to the customer PC or approved local network, with no public port forwarding. Cloud traffic uses a separate connection.

    Data handling, explained plainly
    Claude processing
    The installed LekhaLift app sends invoices directly from your PC to the Anthropic API, using your own Claude API account and key. You pay Anthropic for API usage separately. Anthropic says commercial API inputs and outputs are not used for model training by default, with feedback and explicit-permission exceptions. Provider training policy.
    Provider retention
    Anthropic's standard API retention is up to 30 days, with exceptions for features such as the Files API, agreements, safety enforcement, and law. This is not a zero-retention promise. Provider retention policy.
    Local app and API key
    Claude requests originate from your PC. Before activation, confirm how the app stores your API key, documents and logs, who can access them, and how to delete them. Direct API calls do not establish secure key storage or a zero-retention guarantee.
    Your Tally data
    The local company remains under your control. The connector needs only the client context required for the selected workflow; access, backup, and duplicate-posting checks are part of onboarding.
    Website enquiries
    When direct submission is available, the details you provide are saved in a private Cloudflare enquiry database for follow-up. An internal email alert shares only the enquiry reference with the team; it does not include your contact details. You can request deletion at [email protected]. If direct submission is unavailable, the form prepares an email draft for you to send. Only your theme preference is saved on this device. No invoices or API keys are collected by this form.
    Privacy contact
    Request product data-handling details or deletion assistance at [email protected].
    Official documentation

    LekhaLift: validation before activation

    A test-company check must establish access controls, approval, posting response, duplicate protection, and deletion. No independent security certification or production validation is claimed on this page.

    Discuss your setup and data requirements ↗

    Documentation checked on 10 October 2026. Terms and product versions can change.