CORAA
Audit working papers · built for auditors· WP

Rebuilding the same lead schedules by hand for every client, every year-end.

The working-paper file is mostly mechanical — a lead schedule per account, an ageing per ledger, a PPE roll-forward — and you rebuild it by hand each March because last year's tied to last year's numbers. CORAA reads your Tally Prime, Busy, Zoho or Excel trial balance, proposes the ledger-to-account-area grouping for you to confirm once, then assembles a working paper for every significant account area: lead schedules that drill from the balance head down to the voucher, each tying back to the statement. The assembly is mechanical; the audit — and every figure in it — stays yours to review and sign.

The bespoke motif

From balance head to voucher — in three clicks, in your template.

The lead schedule → voucher drill

Open a balance head and drill: head to grouping, grouping to ledger, ledger to the individual voucher that built it. The number on the face of the statement is never asserted — it is the source entry, a few clicks away, so a reviewer walks down to the voucher instead of taking the lead schedule on trust. Where the source data doesn't carry voucher-level detail, the drill stops at the ledger line and flags it rather than fabricating a link the data can't support.

Your firm template, not ours

Every schedule exports in your firm's own working-paper format — your columns, your headers, your file structure. No proprietary layout, no lock-in, no exit cost. The template is mapped once and reused across every engagement and branch, so the file comes up in the same shape each time without per-client reformatting. If you stop tomorrow, the papers you keep are already in the shape your file has always used.

Mapped once, not rebuilt every March

The hard part isn't typing the schedule — it's mapping a messy ledger to the right account area and Schedule III bucket, where the same expense can sit under three different heads. CORAA proposes that mapping from your trial balance and ledger; you review and correct it once, and it persists to the next engagement and the next year rather than being redone every March. Where a ledger line is mis-grouped or can't be matched, it is flagged for you to place, not silently bucketed.

Every schedule ties back to the statement

The lead schedules foot to the trial balance and the trial balance foots to the financial statements — so the working-paper file and the signed statements carry one set of numbers, not two a peer reviewer can pull apart.

What it generates

Every account area, its own paper — sourced before you open the file.

01

Lead schedules · balance head to voucher

A lead schedule for each significant account, with the drill from balance head through ledger to the underlying voucher. The working shown line by line, each figure traceable to the entry behind it — not a re-typed summary. Where the source data doesn't reach voucher level, the drill stops at the ledger line and flags it rather than inventing a link the data can't support.

02

AR / AP ageing · dual buckets, party-wise

Receivables and payables aged party-wise in two views at once — your operational buckets for the recovery conversation, and the statutory Schedule III due-date buckets for disclosure — so one ageing serves both the file and the notes. Every party in the ledger is aged, not a sample.

03

MSME 45-day split on payables

Payables carry the MSME 45-day split under s.43B(h) and the MSMED Act — micro and small suppliers separated, dues beyond the limit surfaced party-wise — for the disallowance question and the Schedule III MSME disclosure, drawn from the ledger rather than a side spreadsheet. CORAA surfaces the dues for the auditor's assessment; it does not decide the disallowance.

04

Fixed assets · block-wise roll-forward

PPE as a block-wise roll-forward — opening, additions, deletions, closing — with s.32 depreciation and an IT-vs-Books reconciliation that carries the deferred-tax working under AS 22. The book block and the tax block reconciled in one schedule.

05

Cash flow · indirect, AS 3

An indirect-method cash flow under AS 3, offered as a first-cut tie-out rather than a finished figure — operating, investing and financing reconciled to the change in cash, and rebuilt as the trial balance updates through finalisation. Non-cash items and reclassifications are surfaced for the auditor to adjust, not assumed away, so the working stays visible rather than becoming a black-box number you can't unpick.

06

Cessation of liability · stale balances

Creditor and liability balances unmoved beyond three years surfaced for the s.41(1) cessation question — flagged party-wise for the auditor's judgment, not concluded on. CORAA makes no determination that a liability has ceased; it surfaces the stale balance so it isn't left unexamined in the ledger.

Why it holds up

A working-paper file a peer reviewer can re-perform line by line.

Re-performable SA 230 trail

Every schedule carries a timestamped, rule-cited record traced to the source row and exportable straight to the working-paper file. A reviewer re-walks the figure down to the voucher instead of taking it on trust — the working paper stays evidence of the auditor's procedures, machine-assembled, not auto-concluded.

Deterministic, not generative

The same ledger and the same rules produce the same schedules every run — no probabilistic wording or figures that drift between engagements. Reproducible by design, which is what a peer review actually tests.

Materiality-gated under SA 320

What a schedule surfaces for attention — a stale balance, an ageing breach, a depreciation variance — is filtered through the materiality you set, so the file flags what matters and stays quiet on what doesn't. Qualified, not assumed.

Completeness checked, not sampled

The ageing, the roll-forward and the cessation review run across the whole ledger, and each schedule foots to the trial balance and reconciles to the ledger control totals. Completeness is a tested control, not a 2% sample — and any line CORAA can't parse is flagged rather than dropped, so a gap shows up in the file instead of hiding in it.

Who it's for

Three desks, one working-paper file — and the same voucher under each figure.

The article

Stops rebuilding lead schedules and ageings off last year's file. The schedules arrive assembled and sourced from the ledger; the time goes into the testing and the queries that actually need a person, not into formatting columns or re-tying mappings every March.

The manager

Reviews a file where every lead schedule drills to its voucher, the ageing carries both the operational and Schedule III buckets, and the MSME and cessation flags are already party-wise — no more reconciling the schedules against the ledger by hand. The grouping is mapped once and standardised, so the file comes up in the same shape across every office.

The partner

Signs knowing the lead schedules foot to the statement, the PPE block reconciles books to tax under AS 22, and the whole file is re-performable down to the voucher if a peer reviewer asks. The template and grouping map once and reuse across every engagement and branch. The opinion is theirs; the schedules are assembled.

What it changes
balance head to voucher
Three levels
Every lead schedule drills from the head on the statement through the ledger to the underlying voucher — traceable, not asserted, and flagged where the source stops short.
tested and reconciled
Whole ledger
Ageing, roll-forward and cessation run across the whole ledger and foot to the TB — flagged where material under SA 320, with unparseable lines flagged, not dropped.
no proprietary format
Your template
Schedules export in your firm's own working-paper layout — mapped once, reused across engagements, no lock-in and no exit cost.
ties to the statement
Every figure
Lead schedules foot to the trial balance and the trial balance to the financials — one set of numbers across the file.
Questions auditors ask

Working-paper automation, answered straight.

A working paper for every significant account area, read from your Tally Prime, Busy, Zoho or Excel trial balance and ledger: lead schedules with the drill from balance head to voucher, AR/AP ageing in both operational and Schedule III due-date buckets with the MSME 45-day split on payables, a block-wise fixed-assets roll-forward with s.32 depreciation and an IT-vs-Books reconciliation under AS 22, an indirect cash flow under AS 3, and a cessation-of-liability review for balances stale beyond three years under s.41(1). The schedules are built to the Accounting Standards (AS) framework — AS 3 for cash flow, AS 22 for deferred tax — and each ties back to the statement.
Your own. Schedules export in your firm's template — your columns, headers and file structure — not a proprietary CORAA layout. The template is mapped once and reused across engagements, so there is no per-client reformatting, no format lock-in and no exit cost: if you stop using CORAA, the papers you have already exported stay in the shape your file has always used.
The drill runs from the balance head on the face of the statement, down to the grouping and ledger that make it up, down again to the individual voucher behind a ledger line. Where the source data doesn't carry voucher-level detail, the drill stops at the ledger line and flags it rather than fabricating a link. So when a partner asks how a figure was arrived at, the answer is the source itself, not a re-typed summary you have to trust.
No. Real ledgers carry missing or garbled GSTINs and PANs, amended documents and multi-registration clients — the MSME split in particular leans on supplier identification. CORAA flags the unparseable or unidentified lines for review rather than silently dropping them, so a data problem shows up as a flag in the file, not a gap in a schedule. The same applies to messy groupings: the ledger-to-account-area mapping is proposed for you to confirm once, and mis-grouped lines are flagged for you to place — the mapping, not the schedule, is where the real work is, and the page is honest about that.
Data is hosted in India, handled in line with the DPDPA and ISO 27001 controls, and is never used to train shared or third-party models. The output drops into your existing working-paper file as an auditor-reviewed schedule, not an unreviewed source. Your client data stays your client data.
The auditor does, entirely. CORAA is an assistive working-paper generation and analysis tool — it is auditor-performed and machine-assembled, and it does not form, sign or share responsibility for the opinion. CORAA makes no determination on assessability, disallowance or cessation of liability; it surfaces the evidence party-wise for the auditor's judgment. Every schedule is the auditor's to review, test and confirm, and the SA 230 trail records that the figures trace to source. The professional judgment and the report remain yours.
See it on a real file

Bring a sample engagement or a redacted ledger. See the working papers assemble — every figure yours to review.

Load a sample engagement and see a lead schedule assembled for every account, the drill running from balance head to voucher, the ageing carrying both the operational and Schedule III buckets, the PPE block reconciling books to tax — all of it exported in your own template. We'll also walk the firm rollout: how the template and grouping are mapped once and reused across engagements and branches, and how India hosting, data segregation and your independence requirements are handled before any client file is loaded. The assembly is mechanical; the audit is yours.