Free tool
Screen related-party transactions for free, right now.
Drop in a transactions CSV. See every transaction above a threshold you set with no approval reference recorded, and a count and total by counterparty — not a fuzzy name match for undisclosed related parties, which this tool deliberately doesn't attempt.
Drop your transactions CSV here, or choose a file.
Needs a counterparty name column and an amount column; relationship, transaction type and an approval reference make the check complete.
What this does and doesn't do
- Your file is read entirely in your browser and never uploaded anywhere.
- It only flags what the relationship and approval columns actually state. It does not attempt to detect an undisclosed related party from a counterparty's name — that is a real audit risk and a judgement-based procedure, not something a CSV check can claim to catch.
How to use this
Set the approval-required threshold
Defaults to ₹1,00,000 — adjust it to whatever materiality level fits the engagement.
Export the transactions register as CSV
Needs a counterparty name and amount column; relationship, transaction type and an approval reference make the check complete.
Drop it in above
The tool matches common header variations automatically.
Treat a blank relationship field as a data gap, not a finding
Confirming whether an undisclosed relationship actually exists needs separate, judgement-based procedures.
This free tool, and where it stops
This free tool checks
- Transactions above a threshold you set with no recorded approval reference
- Transaction count and total value grouped by counterparty
A full engagement in Lekhya also checks
- Related-party identification procedures, not just a review of a stated-relationship column
- Approval terms matched to the actual board/audit-committee minutes, not just a reference number
- Arm's-length pricing testing on the flagged transactions
- Full-population checks every period, not a one-time scan
One run, one file, four or five rules — versus every procedure a real engagement needs, run continuously against the full population, with every exception linked to its source document.