← Back to Raven
Product · Audit

An audit that runs every time your books change.

About 25 deterministic statutory checks plus an independent AI pass for related-party, Ind AS 115 and FEMA. Findings persist across runs and carry state, so you work them like a real review instead of a dashboard that resets every quarter.

Findings · Run #1427 open · 4 new
MSMED dues past 45-day window
6 vendors · ₹8.2L · MSMED §15 · disallowance risk
open
Customer concentration — Acme Foods
#2 by revenue, 38% of FY25 inflows
open
GST treatment — IGST on intra-state line
3 invoices · INV-2041, 2044, 2058
open
TDS 194Q · Stellar Supplies past ₹50L threshold
2 invoices · disallowance risk · cited to PO-1187, 1212
open
Near-duplicate vendor records
3 likely duplicates · vendor master
snoozed
Voided invoice carrying balance
Resolved since run #13
resolved
What it checks

The categories a senior CA would flag.

Coverage is deliberately Indian-SMB-specific. Each rule is hand-written and tested with a golden-snapshot eval harness, so what passed last quarter passes again on the same data — no silent drift between releases.

MSMED §15
45-day breach window and §43B(h) disallowance exposure on MSME payables.
Schedule III aging
AR and AP aging buckets formatted for direct disclosure.
GST treatment
CGST/SGST vs IGST mismatches, zero-GST from registered vendors.
TDS thresholds
Section-specific thresholds, vendor-by-vendor, on every run.
HSN / SAC
Code consistency across line items and vendor masters.
Concentration risk
Customer and vendor concentration trends across periods.
Data hygiene
Draft bills, voided invoices carrying balances, near-duplicate vendor records.
Related-party & Ind AS 115
AI judgment pass on disclosure adequacy and cross-table reasoning.
How it works

Deterministic first. AI only where judgment is genuinely needed.

The deterministic pass runs every time Zoho changes — same input, same output, every time. The AI pass runs alongside it on the things rules can't capture (related-party language, transaction context, cross-table reasoning), with hard spend caps so it can never run away with your bill.

Findings carry state across runs: open · acknowledged · snoozed · resolved · cleared · regressed. If a finding you cleared last run reappears this run, it shows up as regressed, not as a new finding — so your queue reflects actual change, not noise.

Compliance · Coverageevery change · cited
MSMED §15 · 45-day & §43B(h) exposure
deterministic
Schedule III · AR/AP aging buckets
deterministic
GST · CGST/SGST vs IGST treatment
deterministic
TDS · Section thresholds, vendor-wise
deterministic
HSN / SAC · Code consistency across lines
deterministic
AI
Ind AS 115 · Related-party & disclosure
judgment
AI
FEMA · Cross-border flow checks
judgment
↳ Deterministic rules tested on every release. AI pass on judgment categories.
By construction

The audit stays read-only.

Audit and reporting hit Zoho through a read-only OAuth scope. The AI never has a direct path to your books; for anything that does write to Zoho (reconciliation entries, for example), deterministic code carries out the change after you approve.

See the audit run on your own books.

Read-only Zoho OAuth. First findings in about a minute, each cited to the records behind it.