Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
AI agent

AI Agent for Bank Statement Categorisation: Code Every Bank Line to the Right Ledger

For accountants and finance teams in Indian SMEs: turn a month of bank lines into coded, reconciled entries, and spend your time only on the lines that need judgement.

An accountant's hands sorting statement strips into coloured trays

An AI agent for bank statement categorisation takes the line that says NEFT, UPI or a truncated vendor name and suggests which ledger it belongs to. Most bank lines repeat every month: rent, salaries, card fees, a regular supplier. A small share is new or ambiguous, and those are the ones that hold up the close.

Many Indian businesses still download the statement, paste it into a sheet and code each line by hand. The work is slow, and the same line gets coded differently by different people.

This page explains the split between rules and AI, an illustrative example, and how Apragya keeps a person in charge of what is posted.

An example: a Ludhiana hosiery exporter

Take an illustrative exporter with two current accounts and about 900 bank lines a month, from buyer receipts and card settlements to freight, power and wages.

Where each bank line went

Imported statement

Lines parsed from the bank's file.

  • Mapping rules

    Recurring lines coded and matched on import.

  • Agent suggestion

    New payees given a likely ledger and a reason.

  • Accountant review

    Accepts, edits or rejects each suggestion.

  • New rule

    A confirmed payee becomes a rule for next month.

  • Reconciliation

    Coded lines matched to their entries.

  • Audit log

    Who approved which entry, and when.

Rules take the repeat lines; the agent helps with the rest.

Most lines were coded by rules the moment the file was imported. The agent suggested ledgers for the remaining new payees, the accountant confirmed them in one sitting, and several became rules so the next month needed even less review.

A finance executive placing the last few strips into a tray
Rules coded the repeat lines on import; only the new payees needed a person.

How bank transaction categorisation works in Apragya

Step 1 of 5

Import the statement

Upload the bank's file for the account.

  1. Import the statement: Upload the bank's file for the account.
  2. Rules apply first: Contains or matches a pattern, by direction, to a target ledger.
  3. AI suggests the rest: An agent proposes a ledger for unmatched lines, with its reasoning.
  4. Review and post: The accountant approves before any entry is posted.
  5. Reconcile: Posted entries are matched to the bank lines.

What hand-coding bank lines costs

Days at month end

Hundreds of lines coded one at a time, every month.

Inconsistent ledgers

The same payee lands in different accounts.

Unexplained lines

Receipts sit in suspense because nobody knows who paid.

Late reconciliation

The bank balance and the books agree only after the close.

Choosing bank statement import software with AI

Rules are exact and cheap, so they should carry the repeat work. AI is useful where rules have not been written yet, and its suggestions should turn into rules over time. Look for a system that does both and records who approved what.

Spreadsheet coding, against Apragya

FeatureSpreadsheetApragya
Recurring linesCoded by hand each monthCoded by mapping rules on import
New payeesGuessed or parked in suspenseLedger suggested with a reason
ConsistencyVaries by personSame rule every time
PostingKeyed again into the booksEntries created and reconciled
TrailNoneAudit log of approvals

Checked against public information on 16 September 2026.

What sets this approach apart

Same ledgers

Bank lines code into the accounts your books already use.

Suggestions on journals too

A ready-made classifier suggests ledgers on new journal entries.

Multi-company

Each company keeps its own accounts and rules.

Access by role

Only finance roles approve and post.

Fewer lines each month

Confirmed payees become rules, so review shrinks.

Metered AI use

AI Credits are tracked per company.

Read more on bank statement import and bank reconciliation. The unmatched-line agent is built with the no-code agent builder; see also the journal entry suggestion agent.

Getting started with automatic bank reconciliation in India

  1. Set up your bank accounts and import last month's statement.
  2. Write rules for the twenty payees that appear most often.
  3. Build the agent for lines no rule matches.
  4. Review its suggestions and turn the good ones into rules.
  5. Repeat next month and watch the review list shrink.

The first month is the heaviest. After that, most lines never need a human look.

What it costs to start

INR 7,999
Pro, a month
Up to 25 users, with Finance and Accounting and every enterprise app
5,000
AI Credits a month
Included on Pro
Free
Up to 3 users
CRM and HR, to try the platform first

Bank statement categorisation agent, answered

Is the AI part ready-made?
Mapping rules and the journal entry classifier are part of the Finance app. An agent that suggests ledgers for unmatched bank lines is built for your account with the agent builder.
Does it post entries without approval?
Lines matched by a rule you wrote can be coded on import. AI suggestions wait for a person to approve them.
Which bank formats are supported?
Statements are imported from the bank's downloadable files. Check the formats for your bank during setup.
Can we see why a ledger was suggested?
Yes. The suggestion carries a short reason, and the approval is recorded.
What does it cost to start?
Finance and Accounting comes with the Pro plan, INR 7,999 a month for up to 25 users, which includes every enterprise app, 5,000 AI Credits a month, single sign-on and audit logs. The free plan covers up to 3 users with CRM, HR and Vendor Onboarding if you want to try the platform first.

Spend your close on the lines that need you

Import a statement, write your first rules, and let the agent help with the rest.