CORAA
Features/Reconciliation/Bank Reconciliation
Bank Reconciliation Statement

Bank Reconciliation

Bank statements matched to the cashbook, transaction by transaction. A BRS built per account.

CORAA bank reconciliation statement, matched per account

The bank reconciliation statement exists to explain the gap between the book balance and the bank balance, unpresented cheques, deposits not yet credited, bank charges not booked, and to catch what shouldn't still be open months later. CORAA reads the bank statement, PDF or Excel, any bank, and matches it against the cash and bank ledger transaction by transaction. A BRS builds itself per account. Items that stay unreconciled beyond a configurable age are flagged and quantified against performance materiality, so the auditor knows which stale items actually matter.

  • Bank statement extraction, any bank, PDF or Excel
  • Transaction-by-transaction match against the cash & bank ledger
  • BRS built automatically, per account
  • Unpresented cheques, uncredited deposits, unbooked charges classified by cause
  • Stale items aged and quantified against performance materiality
  • Multi-account, multi-bank support in one engagement
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

  • -Articles tick-mark bank statement lines against the cashbook by hand
  • -BRS built line by line in Excel, one workbook per account
  • -Stale reconciling items carried forward audit after audit, rarely investigated
  • -A large account can take a full day to reconcile and write up
Time: hours per account. Stale items: easy to miss, easy to carry forward.
CORAA

On the Ledger

  • Bank statement matched to the ledger automatically, any format
  • BRS generated per account in minutes, not hours
  • Every reconciling item classified: unpresented cheque, uncredited deposit, bank charge, unbooked interest
  • Items open beyond the configured age flagged and sized against performance materiality
Time: minutes of runtime, a focused review. Stale items: surfaced, not buried.
How it works

Three steps. Every trace logged.

Step 01

Upload the bank statement

PDF or Excel, any bank, any account. Multiple accounts and multiple banks ingest in the same session.

Step 02

CORAA matches, transaction by transaction

Every bank line is matched to a ledger entry by amount, date and reference. What doesn't match sorts into unpresented cheques, uncredited deposits, and unbooked bank items.

Step 03

The BRS builds itself, stale items flagged

The reconciliation statement assembles per account. Items still open beyond a configurable age are flagged and quantified against performance materiality, so the auditor knows which ones need a client query.

Inside the module

What you actually get.

Bank statement extraction

Reads bank statements as they come, PDF exports, Excel downloads, scanned copies, from any bank. No fixed template required.

  • PDF and Excel formats
  • Any bank's statement layout
  • Multiple accounts in one upload session

Transaction-by-transaction matching

Every bank line is matched to the cash & bank ledger by amount, date, and reference, the same three-bucket logic used across CORAA's reconciliation engines.

  • Matched, book-only, bank-only buckets
  • Cause attached to every unmatched item
  • Ties into the Cash & Bank Working Paper

Ageing and materiality

Reconciling items are aged from the date they first appeared unreconciled. Anything still open beyond the configured threshold is quantified against performance materiality and surfaced, not buried in a BRS nobody re-reads.

  • Configurable staleness threshold
  • Quantified against performance materiality (SA 320)
  • Carried-forward items flagged year on year

Multi-account, multi-bank

An entity with several current accounts, a cash credit account, and an overdraft reconciles in the same engagement, each with its own BRS.

  • One BRS per account
  • Consolidated cash & bank position across accounts
  • Works across multiple banks in the same entity
Frequently asked

Answers, up front.

Any unpresented cheque, uncredited deposit, or unbooked bank entry that remains open beyond a configurable age (a default threshold applies, and the audit team can adjust it per engagement). Stale items are quantified against performance materiality so the ones worth a client query are visible, rather than the whole BRS needing a line-by-line re-read.
No. Bank reconciliation feeds it. The BRS built here is one input into the Cash & Bank Working Paper, alongside balance confirmations and the rest of the cash & bank schedule.
Each account reconciles independently, with its own BRS, and the results roll up into a consolidated cash & bank position for the engagement. Statement formats differ bank to bank; CORAA reads them without a fixed template.
Every bank line is matched to the ledger by amount, date and reference, and lands in one of three buckets, matched, book-only, or bank-only. Unpresented cheques, uncredited deposits and unbooked bank charges are classified by cause rather than left as a generic mismatch.
Items still open beyond the configured staleness threshold are flagged year on year, so a cheque or deposit that's been sitting unreconciled since a prior audit doesn't quietly disappear into a fresh BRS each engagement.
Manually, tick-marking a bank statement against the cashbook and writing up the BRS can take a full day per account. CORAA generates the BRS in minutes, turning the work into a focused review of the items it flags rather than a full line-by-line build.
See it on a real ledger

Run bank reconciliation on one of your engagements.

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

Start the free trial →
Bank Reconciliation AI, BRS Built Per Account for Audit | CORAA