INTERNAL AUDIT SOFTWARE FOR INDIAN ENTERPRISES

Every finding.
A clear line
to evidence.

Test your SAP extracts, inspect the records behind each exception and carry reviewed findings into the audit committee report.

FI / StatutorySample audit run

Where is the deposit record?

Each square represents one of 45 entries. Gold marks a row where tax was deducted at source (TDS) and the deposit date was blank.

  • 40 Deduction with date recorded
  • 4 No positive deduction
  • 1 Deduction with date missing
Inspect flagged entry EX-7002

GUIDED WALKTHROUGH · SAMPLE DATA

Follow one finding into the report.

An auditor planning a review of tax deductions selects procedure STX-002. Follow the sample run from the first test to the signed observation.

Detection procedure · STX-002

Which entries need a closer look?

After the auditor checks the extract against the declared totals, Verilekh evaluates the selected procedure across the uploaded population. This rule looks for two conditions in the same row.

Download the 45-row sample (CSV) ↓

Rule applied to each entry

  1. TDS amount is greater than zero
  2. Deposit date is empty
  3. Both match → stage a draft exception

1 of 45 entries matched (2.2%).

Source evidence · EX-7002

What triggered the flag?

BuildRight’s contractor entry records a deduction of ₹4,000. The deposit date field is empty. Verilekh attaches the original row so the reviewer can trace both fields back to the extract.

Selected fields from the sample row

Document
EX-7002
Posting date
11 May 2026
Contractor charges
₹2,00,000
TDS deducted
₹4,000
Deposit date
Blank in extract

Auditor review · EX-7002

Was the tax actually deposited?

The blank field raises a question. The auditor checks the deposit receipt (challan) and reconciliation, then decides whether to confirm or discard the exception.

What if the auditor finds a matching receipt?

The receipt could support discarding the suspected non-deposit. The auditor can assess why the extract lacked the date as a separate question.

Path in the documented example

  1. Auditor confirms the finding
  2. Verilekh drafts the observation from the finding and its linked risk
  3. Auditor documents the root cause and reviews the wording

Reporting · Risk R-STAT-001

What reaches the committee?

A second reviewer signs the observation. The Report Centre, management reporting and Audit Committee Pack then draw on that signed record. The team tracks the action owner and due date through follow-up.

Trace back to EX-7002

Sample observation · condition

Of 45 entries examined, one recorded a TDS deduction of ₹4,000 with no deposit date in the extract.

Supporting record EX-7002 · Procedure STX-002

OTHER AUDIT SCENARIOS

See the exception.
Understand the evidence.

Start with the data. Apply defined procedures. Give your team the context to decide what deserves attention.

Explore an audit scenario

Choose an area to follow a finding.

Also supporting audit procedures across sales, payroll, production, projects and more.

FINDING REVIEWFictional example
For auditor review

One invoice. Two payment records.

Two entries share a supplier and invoice reference. Review the underlying records before confirming a duplicate.

Illustrative source evidence
DocumentInvoice referenceAmount
DEMO-P001INV-1042₹1,25,000
DEMO-P002INV-1042₹1,25,000

The next questionIs this a duplicate payment, or a valid reversal and reposting?

Source evidence attachedHuman review required

MADE FOR YOUR CONTEXT

Indian enterprises.
Real audit
complexity.

SAP processes, local reporting needs and professional review, brought into the same workspace.

Talk through your audit workflow
01

SAP data, made reviewable

Test uploaded extracts across business processes. Keep source records alongside the exceptions they support.

02

Indian reporting context

Work with statutory compliance procedures and financial statement review, including Schedule III workflows.

03

Documents alongside transactions

Bring policies and contract terms into your audit work. Investigate how transactions compare with documented requirements.

04

AI assistance, professional ownership

Use AI to assist with document interpretation and draft narratives. Auditors assess the evidence and own the conclusion.

BUILT FOR TRUST

Confidence comes
from what you
can trace.

Good audit work should be explainable.
Verilekh keeps the record behind the conclusion.

Evidence that travels with the finding

Source rows stay attached, giving reviewers a direct route back to the data.

A second set of eyes

Finding confirmation and observation sign-off make professional review part of the workflow.

A record of important decisions

A tamper-evident audit trail records key actions, approvals and overrides.

Access with defined responsibilities

Role-based permissions distinguish administration, preparation, review and viewing.

A FEW USEFUL ANSWERS

Before we
talk audit.

Who is Verilekh for?

Verilekh is designed for internal audit teams and audit practitioners working with Indian enterprises that use SAP. A demonstration can help assess how it fits your engagement scope, processes and review requirements.

Do we need a live SAP connection?

The current workflow starts with uploaded SAP data extracts. We can walk through the source files, column mapping and completeness checks for your selected audit area during a demonstration.

Does AI decide the audit conclusion?

No. Defined procedures identify exceptions or indicators for review. AI can assist with selected interpretation and drafting tasks. Auditors evaluate the evidence, confirm findings and review observations before reporting.

Can we see a demonstration first?

Yes. A demonstration can follow an example from the source extract through testing, review and reporting. There is no need to send confidential client data for an introductory conversation.

LET’S START WITH YOUR AUDIT

See the whole picture.
Follow every finding.

Explore how Verilekh could fit your team’s audit workflow.

Demo enquiries opening soon.

A guided walkthrough, from source data to report.