Sample engagement
See Lekhya in action.
Explore a sample audit engagement and follow evidence from client documents through testing, findings, working papers and review. Nothing is scripted — it is the product, on data built for the demonstration.
A worked procedure, stage by stage, on fixed sample data — the fastest way to see how it actually works. Prefer a guided version instead?
The sample environment
- Client
- ABC Manufacturing Pvt Ltd
- Engagement
- Statutory audit · FY 2025–26
- Firm
- Kulkarni & Associates
- You are
- S. Rao, Audit Manager
Everything here is invented. The client, the transactions, the documents and the people are fictional sample data. No audit is being performed and nothing you do is stored on a server.
Before you go in
Tell us who we are building for.
Three questions, and one you can skip. We ask because knowing which firms and which roles are looking at this is genuinely how we decide what to build — not to put a salesperson in your way.
What is kept, and where
- What you type above: your work email, firm name, role, and the area you chose.
- How you arrived: the page you came from, and any campaign tags in the link you followed.
- Which screens you open in the sample workspace, so we can see which parts of the product people look at.
All of it stays in this browser tab and is deleted when you close it. There is no server to send it to yet, so nothing is transmitted, nobody is notified, and no one will contact you as a result of entering the demo. No password, no verification code, nothing to install.
Inside
What you can work through.
A path runs through the workspace in ten steps. You can follow it, ignore it, or close it — the application is the same either way.
- 01The engagementWhere the file stands and what is blocking it. Everything else hangs off this.
- 02Outstanding evidenceWhat the client still owes you. The same list they see in their own portal.
- 03What was readEvery document received, what the system made of it, and the ones it could not read.
- 04ProceduresNamed procedures, the population each ran against, and how many exceptions came back.
- 05ExceptionsThe queue. Each one is a test that did not pass — not yet a conclusion.
- 06A findingWhy it was raised, and the chain from the figure back to the page it came from.
- 07Source documentsThe documents themselves, and which finding depends on each one.
- 08Working paperThe paper this testing produced. Computed figures, drafted narrative, auditor conclusion.
- 09Review stateThe whole file: what is prepared, in review, approved and signed off.
- 10The reportAssembled from reviewed work. Any paragraph opens into the work behind it.
Would you rather talk to someone?
Thirty minutes with a Chartered Accountant, on your own data rather than ours.