Company
Software for the way Indian audit is actually done.
We build for Chartered Accountant firms in India. Not for a global template with an India setting, and not for a market that files under different law.
The thesis
The seam between the firm and the audit is where work leaks.
Practices run their administration in one place and their audits in another, and neither knows about the other. An engagement gets accepted in a spreadsheet and audited in a folder of Excel files. We think closing that seam is worth a company.
Why now
Ledgers got bigger. Deadlines did not move.
Clients now generate more transactions in a quarter than a team can read in a season, while statutory timelines stayed where they were and scrutiny went up. Something has to read every row, and it cannot be a person with a highlighter.
Beyond the ledger
A row can be read. An estimate has to be worked out again.
A bank’s provision for expected credit loss reaches the ledger as a single figure. Its working is somewhere else: a model, a view of the economy and a judgment on every account. The Reserve Bank’s Directions on it are in force from 1 April 2027. An auditor can read the bank’s workbook, or work the figure out again from the bank’s own data. Provisio is built for the second.
Why India
Indian audit is the foundation, not a localisation.
The rules an audit runs on answer to Indian statute, the ledger arrives out of Tally, and the numbers read in lakhs and crores. A product that treats any of that as a regional setting is a product a partner has to work around, and working around software is how the seam opened in the first place.
The thesis, in the product
What that argument looks like once it is built.
Each row is behaviour that exists in the products today. Follow it into the page that explains it in full.
-
The ledger arrives from Tally
A desktop Tally connector runs on the client machine and streams the ledger across, so nothing is mailed and nothing is re-keyed.
-
Rules built for Indian audit
The library is grouped by Schedule III position and parameterised per engagement, so a threshold is the client’s threshold and not a global default.
-
The report discloses its own scope
Rules that did not fire, rules that were disabled and rules that had no data to run against are all stated in the deliverable.
-
Engagements carry Indian scope
Statutory, tax, GST and internal audits are tracked separately, because they carry different scope and different deadlines.
-
The field is treated as the office
A native Android app captures attendance, timesheets and engagement updates at client premises, not in the evening after.
-
A bank’s provision is worked out again
Expected credit loss is computed from the bank’s own data under Ind AS 109 and the Reserve Bank’s Directions, and set beside the bank’s figure.
-
The workings can be repeated
Each model is written out as a workbook of live formulas that is checked against the stored figures, so a second auditor can reach the same number.
One system
Why Klok and Quantom sit under one roof.
The engagement a partner opens in Klok is the engagement whose ledger runs in Quantom. Split them across two companies and the context has to be carried by a person.
A clearer practice
See the argument as a working system.
Thirty minutes with the practice and the audit running together, on a real ledger rather than a slide.