CORAA
AI Modules/Working Papers/Loans & Advances
CARO 3(iii) · Loans & Advances· पत्र

Loans & Advances

Composition buckets split Asset-side loans given from Liability-side loans taken, a signed-movement check flags genuinely static accounts, and related-party screening honestly disables itself when there's no register, cited to CARO 3(iii), Sec 185, and Sec 186.

CORAA ledger scrutiny interface with voucher-level drill

Loans & Advances composes the balance into buckets that respect which side of the balance sheet each account actually sits on, loans and advances given, an asset, kept apart from loans and advances taken, a liability, rather than reviewing both off one blended schedule. A movement check then reads the signed direction of change across the year, not just the opening and closing balance, for every account in the buckets. That distinction matters: a loan account with genuine month-to-month drawdowns and repayments that happens to end the year near where it started is not the same as an account with zero activity all year, and an early version of this check, one that simply summed movement, could not tell the two apart and wrongly flagged the active account as static. The current check reads the actual direction of change, not just the ending number, so that case is no longer caught. Alongside composition and movement, every loan and advance is screened against the related-party register for CARO 3(iii) exposure; when no register has been uploaded, the screen does not fake a pass, it flags itself as unable to run. Sec 185 (loans to directors) and Sec 186 (investments and loans beyond the prescribed limits) checks read off the same composed buckets.

  • Composition buckets split Asset-side loans & advances given from Liability-side loans & advances taken, never blended into one schedule
  • Movement check reads signed direction of change across the year, not just the ending number, so a loan with real in-year activity that ends near its opening balance isn't wrongly flagged as static
  • Related-party screening runs against the RP register for CARO 3(iii); with no register uploaded, the screen flags itself as disabled rather than reporting a false pass
  • Sec 185 flag for loans to directors or persons connected to them
  • Sec 186 flag for investments or loans beyond the prescribed limits
  • Cited throughout to SA 501/505, CARO 3(iii), and Companies Act Sec 185/186
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

  • -Loans & advances given and loans & advances taken reviewed off the same schedule, blurring which side of the balance sheet is in question
  • -Static-account review looks at opening vs closing balance only, a loan drawn down and repaid within the year can look dormant, or a genuinely dormant one can look active
  • -Related-party loans cross-checked against whatever register the client hands over; no register on file usually means the check is quietly skipped
  • -CARO 3(iii), Sec 185, and Sec 186 applicability worked out from memory late in the audit, easy to miss a loan that technically breaches a limit
Build time: a schedule per account per year. The static-vs-active call is exactly where a same-balance, high-activity account gets waved through, or a genuinely dormant one gets missed.
CORAA

On the Ledger

  • Composition buckets split Asset vs Liability presentation automatically from the ledger classification
  • Movement check reads the signed direction of change, not just start and end balance, across every month in the year
  • Related-party screen against the RP register for CARO 3(iii); honestly flagged as disabled, never a faked pass, when no register exists
  • Sec 185 and Sec 186 flags computed from the same composed buckets and the same RP screen every time
Build time: instant. No register is a flag, not a shortcut; no static-account call is a guess.
How it works

Three steps. Every trace logged.

Step 01

Composition buckets, Asset vs Liability

Every loan and advance ledger is bucketed by which side of the balance sheet it actually presents on, loans and advances given sit on the Asset side, loans and advances taken sit on the Liability side. The two are never reviewed off one blended schedule.

Step 02

Signed movement, not the ending balance

The static-account check reads the actual direction of change across the year for each account, not just opening vs closing. An account with real month-to-month activity that happens to end near where it started is not flagged as static; only accounts with genuinely no in-year movement are. An earlier version of this check summed movement and could not make that distinction; the current version reads direction of change, so that false positive no longer fires.

Step 03

Related-party screen, honestly disabled without a register

Every loan and advance is screened against the related-party register for CARO 3(iii) exposure. When no register has been uploaded, the screen does not report a pass, it flags itself as unable to run, so the gap stays visible to the auditor rather than reading as a clean result.

Inside the module

What you actually get.

Asset vs Liability composition

Loans and advances given, an Asset, and loans and advances taken, a Liability, are composed into separate buckets from the ledger classification, so the presentation always matches which side of the balance sheet each account belongs on.

  • Asset-side bucket: loans and advances given
  • Liability-side bucket: loans and advances taken
  • Bucket assignment reads off the classification, not the account name
  • CY and PY columns for each bucket

Signed-movement static-account check

Flags accounts with genuinely no movement across the year, using the direction of change month to month rather than the ending balance, so an active account that nets back near its opening figure is not caught by mistake.

  • Reads signed movement, not raw ending balance
  • Distinguishes real dormancy from an active account that nets back to near its opening figure
  • Fixes a specific false-positive the platform's own smoke test first caught
  • Flags carried into the working paper's exceptions

CARO 3(iii) related-party screen

Every loan and advance is checked against the related-party register. An empty or missing register does not produce a quiet pass, it produces its own visible flag.

  • Screens against the uploaded RP register
  • No register: screen flags itself as disabled, never a false pass
  • Candidates for related-party loans surfaced for the auditor to confirm
  • Cited to CARO 3(iii)

Sec 185 / Sec 186 flags

Loans to directors or connected persons, and investments or loans beyond the prescribed Companies Act limits, are flagged off the same composed buckets used for the rest of the working paper.

  • Sec 185: loans to directors or connected persons
  • Sec 186: investments/loans beyond prescribed limits
  • Flags read off the composed Asset/Liability buckets
  • Surfaced as evidence for the auditor's conclusion, never asserted as a breach
Frequently asked

Answers, up front.

No. CORAA surfaces the loan, its terms where available, and the director/connected-person match as evidence. Whether it breaches Sec 185, and what the remedy is, stays the auditor's judgment call, recorded against the working paper.
The CARO 3(iii) screen flags itself as unable to run rather than reporting a clean pass. The gap itself is the finding; it does not disappear from the working paper.
Opening-vs-closing alone can't tell a dormant account from an active one that happens to net back near its starting balance. Reading the signed direction of change month to month tells the two apart, which is exactly the distinction an earlier, simpler version of the check got wrong.
See it on a real ledger

Run loans & advances on one of your engagements.

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

Start the free trial →
Loans & Advances Working Paper | CARO 3(iii), Sec 185/186 | CORAA