AI Modules/Working Papers/Overall Analytical Review

SA 520 · Overall Analytical Review· पत्र

Overall Analytical Review

SA 520 trends and ratios, plus a cross-statement consistency engine that checks whether movements that should move together, actually do.

Start the free trial

CORAA indicator panel showing analytical review signals

SA 520 calls for analytical procedures over the financial statements as a whole. CORAA runs the standard trend and ratio analysis, but adds a cross-statement consistency engine on top: it checks whether movements that should move together across statements actually do. Revenue increased, did Receivables move consistently with it? The implied cost of debt from the P&L's interest charge, does it imply the same borrowing level as the Borrowings schedule? This cross-check has caught gaps a single-statement analytical review misses, a missing interest accrual, for instance, that only shows up when the P&L's implied interest rate is compared against what the Borrowings schedule actually carries.

Trend and ratio analysis over the financial statements as a whole, per SA 520
Cross-statement consistency engine, checks whether related movements actually move together
Example: Revenue increased, did Receivables move consistently with it
Example: implied cost of debt from the P&L versus actual Borrowings on the books
Catches gaps, like a missing interest accrual, that a single-statement review misses
Cited to SA 520

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

-Ratios and trends computed per statement, in isolation
-Cross-statement checks done ad hoc, if at all, and rarely documented
-A missing accrual surfaces only if a reviewer happens to compare two schedules by hand
-Analytical review conclusions written without a documented cross-check trail

A ratio that looks fine on its own statement can still be hiding a gap that only shows up next to a different one.

CORAA

On the Ledger

Trend and ratio analysis computed automatically across the statements
Cross-statement consistency checks run alongside, not as an afterthought
Revenue-to-Receivables and implied-interest-to-Borrowings checks documented with the underlying figures
Every consistency exception carries the specific comparison and the fact that triggered it

The comparison that catches the gap is run by default, not left to whichever reviewer happens to think of it.

How it works

Three steps. Every trace logged.

Step 01

Trend and ratio analysis

Standard SA 520 analytical procedures run over the financial statements as a whole, current-year movement against prior year, and the usual ratio set, computed from the same figures every other working paper reads.

Step 02

Cross-statement consistency checks

CORAA checks pairs of figures that should move together across different statements, Revenue against Receivables movement, the P&L's implied interest rate against the Borrowings schedule's actual balance, and others, rather than reviewing each statement in isolation.

Step 03

Exceptions surfaced with the triggering fact

When a cross-statement check does not hold, the exception carries the specific comparison and the numbers behind it, for example the implied interest rate versus the actual borrowing level, so the auditor can see exactly what triggered it rather than a generic variance flag.

Inside the module

What you actually get.

SA 520 trend and ratio analysis

Standard current-year-versus-prior-year movement and ratio computation over the financial statements as a whole.

›CY vs PY movement across every major line
›Ratio set computed from the same source figures as every other working paper
›Cited to SA 520

Cross-statement consistency engine

Checks whether figures that should move together across different statements actually do, rather than reviewing each statement on its own.

›Revenue movement checked against Receivables movement
›Implied cost of debt checked against the Borrowings schedule
›Additional pairings surfaced where a structural relationship exists

Gaps a single-statement review misses

The cross-check exists because some gaps, like a missing interest accrual, only appear when one statement's implied figure is compared against another statement's actual figure.

›Example: missing interest accrual surfaced via the implied-rate comparison
›Exception carries both figures being compared, not just a variance percentage
›Never asserted as an error, surfaced as evidence for the auditor's review

Documented exception trail

Every cross-statement exception is recorded with the comparison it came from, so the analytical review conclusion has a visible trail behind it.

›Each exception linked to the two figures compared
›Feeds into the working paper's own conclusion section
›Reviewable independent of the AI-drafted narrative

Frequently asked

Answers, up front.

No. CORAA surfaces the trend, the ratio, and any cross-statement inconsistency as evidence. Whether a movement warrants further procedures or represents a misstatement is the auditor's judgment, recorded in the working paper's conclusion.

A missing interest accrual: the P&L's implied interest rate did not match what the Borrowings schedule actually carried. Neither statement looked wrong on its own, the gap only appeared when the two were compared.

No. Overall Analytical Review is a risk-identification and completeness-check layer per SA 520. It surfaces where to look closer; it does not replace the detailed testing that follows.

See it on a real ledger

Run overall analytical review 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 →