Most accounting and bookkeeping firms already have good accounting software. That isn’t where the time goes. It goes to everything around the ledger: chasing clients for statements over email and chat, keying transactions from PDFs, fixing categories, finding the transfer that was booked as income, and tracking deadlines in a spreadsheet nobody else trusts.
Off-the-shelf practice tools cover part of that, but each one expects you to work its way, and some want to replace your ledger too. Custom software for an accounting firm makes sense when your process is what your clients pay for, and the tools keep pushing you off it.
What we build
- Client portals: document requests with deadlines, shared deliverables, and clients answering their own transaction questions.
- Bookkeeping automation: bank statements read, checked against their own balances, categorized by your rules and posted as balanced double-entry.
- Practice tools: worklists, compliance calendars, year-end checklists and staff assignments.
- Bridges to your accounting package: exports and imports that keep your ledger software as the system of record.
What we learned building our own
Lekhavo is our bookkeeping and practice platform for Indian chartered-accountant practices, built and run in production by Tembrant. It takes a client’s bank statements to closed books. Every claim below comes from its code.
Model the firm as it really is
A practice serves clients. A client can hold several entities, such as a person, their family trust and their company, each with its own taxpayer ID and its own books. Each entity has accounts, and each account has statements. Staff hold one role: partners and head staff work on every client, while staff work only on clients assigned to them. Getting this structure right up front is what makes permissions, reports and the portal straightforward later.
A portal clients will use
Clients sign in with Google, with no password and no app install, and the portal works on a phone. A firm can give someone access to one client as owner, editor or viewer. The firm sends document requests, optionally tied to one entity and a deadline, and accepts or rejects what comes back. Finished documents are shared through the same portal, so they don’t get lost in an email thread.
Automation that stops when it should
A statement is read, then checked: opening balance plus every transaction has to land on the closing balance. If it doesn’t, the import is held for review and nothing is posted. Our bank statement parser covers this step in detail. Categories belong to the client. A per-entity rule decides which ledger each category posts to, so one category can be an expense for one entity and income for another. Transfers between a client’s own accounts are matched and kept out of income and expenses, using the matching rules described on our reconciliation software page.
Work alongside the firm’s ledger, not instead of it
Many Indian practices finalize their books in Tally, so Lekhavo exports to Tally rather than competing with it:
- Ledger masters and vouchers in Tally’s import format, as a year summary or transaction by transaction
- A preview before download that lists every ledger renamed to fit Tally’s rules and why (cleaned, truncated, reserved name or duplicate), plus anything uncategorized or left in suspense
- A balance check on every voucher: if debits and credits differ by a single paisa, the export stops
It works the other way too. A CA can upload the financial statements and tax computation they prepared outside Lekhavo, and Lekhavo compares those figures with its own before importing them. The firm’s existing work stays the reference point.
For a US, UK or Australian firm, the same design would target QuickBooks, Xero, Sage or MYOB through their import formats or APIs. We’d scope that integration with you. We haven’t shipped one yet.
Close the year deliberately
Year-end adjustments are made from templates or keyed as journals. Close checks each report pass, needs attention, or for information. Then the year is locked against edits by the firm and the client until the firm unlocks it. Every change records who made it, on which record, and which fields it touched.
How we work
Tembrant builds with an AI software factory: many agents work in parallel, held to fixed gates. Each piece starts from a written spec, has its tests written first, and goes through independent reviews before a person signs off. For a firm, the spec is written in your team’s terms: client, entity, ledger, held import. That way the people who do the work can check it before any code is written.
What you get
- A portal and practice tool shaped to your firm’s workflow and roles
- Statement-to-ledger automation with checks that hold, not guess
- Integration with the accounting package you already use
- An audit trail, staff permissions and per-client data separation
- Source code, a written spec and tests your team owns
If your staff spend their week around the ledger instead of in it, talk to us about your firm’s workflow.
