AI Modules/Engagement Setup/ଲେଜର୍ Classification

ଚ ।· सेटअप

ଲେଜର୍ Classification

Classify ଲେଜର୍ under ICAI guidelines once. ବର୍ଷ 2 opens with zero ଲେଜର୍ to reclassify.

Start the free trial

CORAA ଲେଜର୍ Classification across four statutory dimensions

Every ଭାଉଚର୍ in the books has four statutory consequences: which TDS section applies (192 to 206), which TCS section (206C variants), which GST nature (Normal, RCM, Composition, Exempt, Nil-rated), and which Schedule III line code (A1 Equity Capital through P9 ଅନ୍ୟ ଖର୍ଚ୍ଚ). CORAA captures all four classifications in one ଲେଜର୍ Classification exercise. AI auto-classifies roughly 80 percent on first ingest; the ଅଡିଟର୍ confirms the residual. Mappings persist year-on-year.

ଏ ।
AI auto-classifies ~80% of ଲେଜର୍ on first ingest
ଅଡିଟର୍ confirms or overrides the residual 20%
ଏ ।
Mappings persist across financial ବର୍ଷ
Rule weights adapt per client ଏଙ୍ଗେଜମେଣ୍ଟ୍

Two paths, one ledger

The old way, and ours.

Two paths to the same audit conclusion. One leaves traces; the other doesn't.

Traditional

The old way

-ଅଡିଟର୍ classifies ଲେଜର୍ from scratch every financial year
-ଟ ।
-Inconsistencies between sheets create ସମନ୍ୱୟ effort downstream
-ସ ।

First ଅଡିଟ୍ classification: 4-6 ଘଣ୍ଟା of partner ସମୟ. Repeats every year.

CORAA

On the Ledger

Single ଲେଜର୍ Classification screen captures all four dimensions
AI pre-classifies ଲେଜର୍ names against ICAI ଅଡିଟିଂ ମାନଦଣ୍ଡ guidance
ବର୍ଷ 1: 30-45 minute review of AI suggestions
ବର୍ଷ 2: typically zero ଲେଜର୍ requiring reclassification
ଅଡିଟ୍ log preserves who classified what and when, per SA 230

ବର୍ଷ 1 classification: under 45 minutes. ବର୍ଷ 2 onwards: typically under 5 minutes.

How it works

Three steps. Every trace logged.

Step 01

AI ।

After the ERP data ingests, the AI reads every ଲେଜର୍ name and narration pattern, then proposes classifications across TDS section, TCS section, GST nature, and Schedule III line. Each suggestion shows a confidence score.

Step 02

ଅଡିଟର୍ reviews and confirms

The ଲେଜର୍ Classification screen lists ଲେଜର୍ grouped by confidence band. Above 90 percent confidence: one-click accept all. Between 70 and 90 percent: review individually. Below 70 percent: requires explicit ଅଡିଟର୍ classification.

Step 03

ମ ।

Classifications are stored against the ଏଙ୍ଗେଜମେଣ୍ଟ୍, not the year. Next year's ଅଡିଟ୍ opens with the same ଲେଜର୍ names already classified. The ଅଡିଟର୍ reviews only what changed: new ଲେଜର୍, renamed ଲେଜର୍, or ଲେଜର୍ where Schedule III mapping shifted.

Inside the module

What you actually get.

TDS ।

Maps every applicable ଲେଜର୍ to its TDS section under the ଆୟକର ଅଧିନିୟମ: Sec 192 Salary, 194A Interest non-bank, 194C Contractor, 194I Rent, 194JB Professional, 194Q Goods Purchase, 194R Perquisites, 206AB Non-filer higher rate. Drives Form 3CD Clause 34(a).

›ପ ।
›ହ ।
›ନ ।
›ସ ।

TCS ।

Maps sale ଲେଜର୍ to TCS sections under Sec 206C: 206C(1) Scrap, 206C(1F) Motor Vehicle over ₹10L, 206C(1G) Overseas remittance, 206C(1H) Sale of Goods over ₹50L buyer-wise.

›ଗ ।
›Per-ଚାଲାନ୍ threshold for 206C(1F)
›Form 27C ଶୂନ-ହାର ଘୋଷଣା ହ୍ୟାଣ୍ଡଲିଂ
›ଏ ।

GST ।

Classifies each ଲେଜର୍ by GST nature: Normal (ITC eligible), RCM (reverse charge), Composition (ନା ITC), Exempt, Nil-rated, Zero-rated (exports), Blocked (Sec 17(5)), Non-GST.

›ବ ।
›ଆ ।
›ନ ।
›ଉ ।

Schedule III ।

Maps every ଲେଜର୍ to its Schedule III line code per କମ୍ପାନୀ ଅଧିନିୟମ 2013 Schedule III. Division I (Indian GAAP / AS) for most entities; Division II (Ind AS) for listed and large unlisted. Drives Balance Sheet, P&L, Cash Flow, Notes to Accounts, and ratios.

›~90 line codes from A1 Equity through P9 ଅନ୍ୟ ଖର୍ଚ୍ଚ
›ଏ ।
›ବ ।
›ର ।

Frequently asked

Answers, up front.

CORAA reads ଲେଜର୍ names, group hierarchy from the Chart of Accounts, and narration patterns from sample ଭାଉଚର୍. It matches against a dictionary of ICAI-aligned classifications built from prior ଏଙ୍ଗେଜମେଣ୍ଟ୍ and ଅଡିଟିଂ ମାନଦଣ୍ଡ guidance. Each proposal carries a confidence score from 0 to 100. Above 90 is high-confidence; the ଅଡିଟର୍ can accept all such suggestions in one click.

Mixed-purpose ଲେଜର୍ need split classification. CORAA flags these as 'optional GST classification' and lets the ଅଡିଟର୍ either subdivide the ଲେଜର୍ or apply GST at the ଭାଉଚର୍ level rather than the ଲେଜର୍ level. For Schedule III mapping, ଲେଜର୍ can split between two lines with a percentage allocation.

If the GL Code is the same and only the name changed, the classification persists by code. If a new GL Code appears, it shows up as 'unclassified' and the ଅଡିଟର୍ classifies it once. The ଅଡିଟ୍ log captures the rename ଇଭେଣ୍ଟ.

See it on a real ledger

Run ଲେଜର୍ classification on one of your engagements.

Bring a Trial Balance and a General Ledger. We'll walk through engagement setup end-to-end on your data, not a sandbox.

Start the free trial →