Bank reconciliation
Bank reconciliation software for finance teams
Cointab helps finance teams reconcile bank statements with books, ERP records, accounting ledgers, payment reports, collection reports, settlements, refunds, bank charges, and internal finance data.
View demo reportTrusted by teams reconciling bank and financial transaction data
Cointab is used by finance and operations teams handling recurring reconciliation across banks, books, payments, settlements, ledgers, partners, and internal systems.
Bank reconciliation is difficult to manage manually
Finance teams need to compare bank statements with books, ERP records, payment reports, collection reports, settlement files, and accounting ledgers. Each source may show different dates, references, amounts, and transaction descriptions.
Bank entries and books may not match
A transaction may appear in the bank statement but not in books, or may be recorded in books before it appears in the bank.
References are often incomplete or inconsistent
Bank statements may contain UTRs, cheque numbers, narration text, customer names, payment references, or partner settlement IDs that do not cleanly match internal records.
Timing differences create open items
Collections, payouts, refunds, settlements, and charges may be recorded in one period internally and reflected in the bank in another period.
Multiple payment and collection sources add complexity
Finance teams often receive money through payment gateways, marketplaces, COD partners, customers, vendors, wallets, internal systems, and bank transfers.
Bank charges and deductions need review
Bank fees, gateway charges, settlement deductions, reversal charges, cheque bounce charges, and other deductions can create amount differences.
Duplicate and missing entries are hard to catch
Duplicate postings, missing bank entries, missing book entries, repeated UTRs, and incorrect ledger allocations can go unnoticed in large files.
Refunds and reversals complicate matching
Refunds, failed payments, reversals, chargebacks, returned payments, and bounced transactions may appear differently in bank and accounting records.
Excel becomes fragile as volume grows
Finance teams often compare bank statements, cash books, payment registers, collection reports, ERP exports, and ledger entries using repeated VLOOKUPs, formulas, pivots, and filters.
Open items need clear action
Teams need to know whether a difference is due to timing, missing entry, wrong amount, duplicate posting, bank charge, refund, reversal, settlement delay, or accounting issue.
What is bank reconciliation?
Bank reconciliation is the process of matching bank statement transactions with books, ERP records, accounting ledgers, payment registers, collection records, and other internal finance data.
For example, your bank statement may show a credit from a customer, a debit for a vendor payment, a payment gateway settlement, a refund, or a bank charge. Your books or ERP may show the expected receipt, payment, journal entry, settlement, or ledger posting. These records need to be compared to confirm that money movement is recorded correctly.
Cointab helps bring these records together so your finance team can answer:
- Which bank credits match internal collection records?
- Which bank debits match internal payment records?
- Which entries are present in bank but missing in books?
- Which entries are present in books but missing in bank?
- Which transactions have amount differences?
- Which entries are delayed or recorded in a different period?
- Which bank charges, fees, or deductions explain differences?
- Which refunds, reversals, or chargebacks need review?
- Which UTRs, cheque numbers, or references are missing or duplicated?
- Which records need follow-up with banks, payment partners, vendors, customers, or internal teams?
Bring together bank statements, books, ledgers, payments, and collections
Cointab can reconcile bank workflows using multiple reports from banks, accounting systems, ERPs, payment gateways, collection systems, internal finance systems, and partners.
| Data source | Example records |
|---|---|
| Bank statement | Bank date, value date, debit, credit, balance, UTR, cheque number, narration |
| Books / accounting ledger | Ledger date, voucher number, debit, credit, account, narration, reference |
| ERP report | Receipts, payments, journal entries, vendor/customer transactions, document references |
| Cash book | Internal bank ledger, receipts, payments, opening balance, closing balance |
| Payment register | Vendor payments, payouts, refunds, payroll, tax payments, payment references |
| Collection register | Customer receipts, invoice collections, settlement receipts, payment mode |
| Payment gateway settlement report | Settlement ID, transaction amount, fees, refunds, net settlement, payout date |
| Marketplace / partner settlement report | Partner settlement ID, deductions, payouts, adjustments, settlement amount |
| Refund / reversal report | Refund ID, reversal reference, original transaction, amount, status |
| Bank charges report | Bank fees, cheque bounce charges, transaction charges, service charges |
| Customer / vendor ledger | Customer receipts, vendor payments, invoice references, balance movements |
| Supporting data | UTR mapping, customer mapping, vendor mapping, bank account mapping, settlement mapping |
Users can start with a bank statement and books report, then add payment gateway, ERP, customer, vendor, refund, settlement, bank charges, or supporting reports as the workflow becomes more complete.
Find bank and books differences faster
Cointab helps finance teams separate clean bank matches from exceptions that need review.
Entry in bank but not in books
The bank statement shows a debit or credit, but no matching entry is found in books, ERP, or internal records.
Entry in books but not in bank
The books show a receipt, payment, or journal entry, but the bank statement does not show a matching transaction.
Amount mismatch
The transaction reference matches, but the bank amount and book amount are different.
Date difference
The transaction appears in books on one date and in the bank statement on another date.
Missing UTR or reference
A bank entry does not have a clean UTR, cheque number, transaction ID, invoice reference, customer reference, or vendor reference.
Duplicate bank entry
The same bank reference, UTR, cheque number, debit, or credit appears more than once.
Duplicate book entry
The same receipt, payment, journal, or voucher is posted more than once in books or ERP.
Bank charges mismatch
Bank fees, cheque bounce charges, transaction charges, or service charges are missing or recorded with a different amount.
Payment gateway settlement mismatch
The expected payment gateway settlement does not match the final bank credit after refunds, fees, or deductions.
Customer collection mismatch
Customer payment is found in bank, but the customer ledger, invoice allocation, or receipt record does not match.
Vendor payment mismatch
Vendor payment is recorded internally, but the bank debit, UTR, amount, or payment date differs.
Refund or reversal mismatch
A refund, reversal, failed transaction, chargeback, or returned payment does not match across bank and internal records.
Cheque issued but not cleared
A cheque payment is recorded in books, but the cheque has not cleared in the bank statement.
Cheque deposited but not credited
A cheque receipt is recorded internally, but the credit is missing or delayed in the bank.
Opening or closing balance mismatch
The bank statement balance and internal bank ledger balance do not agree after matching transactions.
How Cointab automates bank reconciliation
Cointab gives finance teams a reusable workflow for preparing bank and books data, matching records, reviewing exceptions, and exporting reports.
Select or create the workflow
Start with a bank reconciliation template or build a custom workflow for your bank statement, ERP, accounting system, cash book, payment register, collection report, or internal finance data.
Upload or automate data
Upload CSV, XLS, or XLSX files manually, or automate recurring data input through email, SFTP, or APIs.
Map required fields
Select date, amount, and identifier columns such as UTR, cheque number, transaction ID, voucher number, invoice number, customer code, vendor code, settlement ID, narration, or bank reference.
Add supporting data
Use supporting files for customer mapping, vendor mapping, UTR mapping, bank account mapping, settlement mapping, payment mode mapping, ledger mapping, or internal reference enrichment.
Create derived columns
Use AI to create calculated fields such as clean UTR, normalized narration, net bank amount, debit/credit amount, settlement-adjusted amount, fee-adjusted amount, refund-adjusted amount, or combined transaction reference.
Run reconciliation
Cointab applies structured matching logic across bank statements, books, accounting ledgers, ERP records, payment registers, collection reports, settlement files, refund records, and supporting data.
Review exceptions
See fully matched, partially matched, unmatched, and skipped records, then drill into transaction-level, ledger-level, customer-level, vendor-level, settlement-level, or bank-level details.
Download or automate output
Download Excel reports or push matched, unmatched, exception, or summary data back to ERP, accounting, BI, analytics, finance, or internal systems.
Match structured bank data with rules and difficult exceptions with AI
Cointab applies structured matching first, then uses AI to help with difficult open transactions where references, UTRs, narrations, voucher numbers, or settlement IDs are missing, messy, or spread across multiple reports.
Structured matching
Cointab can match bank records using:
Matching scenarios
One-to-one
One bank debit or credit matches one book entry, ERP entry, receipt, payment, settlement, or accounting transaction.
One-to-many
One bank entry maps to multiple invoices, receipts, payments, deductions, refunds, fees, or accounting entries.
Many-to-one
Multiple internal transactions are grouped into one bank credit, bank debit, payment gateway settlement, partner payout, or bank batch.
Many-to-many
Multiple bank entries and multiple internal records are grouped and compared across receipts, payments, refunds, charges, and settlements.
Partial matching
UTR, reference, narration, customer, vendor, or settlement ID matches, but the amount differs because of bank charges, fees, refunds, deductions, short payments, or timing differences.
Contra / reversal matching
Refunds, reversals, chargebacks, failed payments, returned payments, cheque bounces, and correction entries are netted against original bank or book records.
AI-assisted transaction matching
After structured rules run, AI helps match difficult open transactions where:
- Bank narrations contain embedded references
- UTRs are incomplete or formatted differently
- Voucher numbers appear in different columns
- Customer or vendor names are similar but not identical
- Payment gateway settlement references do not directly match bank credits
- Bank charges or deductions are not shown as separate records
- Refunds or reversals do not directly map to original transactions
- Multiple internal records combine into one bank entry
- Multiple possible matches exist across bank, ERP, books, and settlement reports
- Descriptions are unstructured or incomplete
AI exception analysis
For transactions that remain open, AI can help identify possible reasons such as:
AI assists reconciliation, but Cointab keeps the output transparent, reviewable, and audit-friendly.
Clear bank reconciliation reports your team can use
Cointab gives finance teams a complete report showing what matched, what partially matched, what remains unmatched, and what was skipped.
Report categories
Fully matched
Bank transactions, book entries, ERP entries, receipts, payments, settlements, refunds, or accounting entries where identifiers and amounts match.
Partially matched
Records where identifiers match but bank amount, book amount, settlement amount, fee amount, refund amount, or ledger amount differs.
Unmatched in bank
Book entries, ERP records, expected receipts, expected payments, or accounting entries present internally but not found in the bank statement.
Unmatched in books
Bank debits, bank credits, charges, settlements, refunds, or reversals present in the bank statement but not found in books or internal records.
Skipped
Rows excluded because of missing, invalid, duplicate, incomplete, or unusable data.
Report capabilities
- Summary cards
- Transaction-level tables
- Bank-entry-level detail view
- Book-entry-level detail view
- Ledger-level review
- Customer-wise review
- Vendor-wise review
- Payment-mode-wise review
- Settlement-level detail view
- Matched transaction detail view
- Filters for review
- Difference amounts
- Excel export
- Manual match
- Undo manual match
- Audit-ready output
- Open-item reason and action analysis
Automate recurring bank reconciliation
Once your bank reconciliation workflow is configured, Cointab can automate data input, reconciliation runs, and output delivery.
Bring data into Cointab
Receive or pull data through:
- Bank statement pulled through API or uploaded automatically
- Accounting ledger pushed from ERP or accounting software
- Cash book exported from internal finance system
- Payment register received from ERP
- Collection register uploaded automatically
- Payment gateway settlement report received by email
- Marketplace or partner settlement report pulled from SFTP
- Refund and reversal report received on schedule
- Customer and vendor ledgers pushed from accounting system
- UTR, customer, vendor, and settlement mapping files maintained as supporting data
Run reconciliation automatically
Schedule reconciliation:
Push output back
Send reconciliation output to:
- Fully matched bank entries
- Fully matched book entries
- Partially matched transactions
- Unmatched bank credits
- Unmatched bank debits
- Unmatched book receipts
- Unmatched book payments
- Bank charge differences
- Settlement differences
- Refund and reversal differences
- Duplicate transaction records
- UTR mismatch records
- Timing difference records
- Customer collection differences
- Vendor payment differences
- Opening and closing balance differences
- Exception reasons
- Suggested actions
- Excel reports
- Structured API output
Start faster with bank reconciliation templates
Use a ready-made bank reconciliation template where available, or create a custom workflow for your bank statement, books, ERP, payment, collection, settlement, refund, and accounting reports.
Bank Statement vs Books
Best for matching bank statement transactions with accounting ledger or cash book entries.
View templateBank Statement vs ERP
Best for comparing bank debits and credits with ERP receipts, payments, journals, and internal finance records.
View templatePayment Gateway Settlement vs Bank
Best for matching payment gateway settlements, fees, refunds, chargebacks, and final bank credits.
View templateCustomer Collections vs Bank
Best for reconciling customer receipts, invoice collections, payment references, and bank credits.
View templateVendor Payments vs Bank
Best for matching vendor payment records with bank debits, UTRs, payment references, and accounting entries.
View templateRefunds and Reversals vs Bank
Best for comparing refunds, reversals, chargebacks, failed payments, and bank entries.
View templateBank Charges Reconciliation
Best for reviewing bank fees, cheque bounce charges, transaction charges, service charges, and related ledger entries.
View templatePayment Gateway Reconciliation
Best for teams that want to reconcile payments, refunds, fees, settlements, and bank credits together.
Explore solutionVendor Reconciliation
Best for teams comparing vendor ledgers, vendor statements, payments, invoices, debit notes, credit notes, and balances.
Explore solutionIf a specific bank reconciliation template is not available yet, users can still create a custom reconciliation using their own bank statements, books, ERP exports, payment registers, collection reports, settlement files, refund reports, accounting ledgers, and supporting data.
See a bank reconciliation report before signing up
Open a sample Bank Reconciliation report and see how Cointab presents matched, partially matched, unmatched, and skipped transactions.
Bank Statement vs Books Reconciliation Demo
See how bank statement entries are matched with accounting ledger records, payment registers, collection reports, settlement files, refund records, and internal finance data. Review how missing entries, amount differences, bank charges, delayed postings, duplicate entries, and UTR mismatches are highlighted.
View demo reportBuilt for finance, accounting, treasury, and operations teams
Cointab is useful for teams that regularly reconcile bank statements, books, ERP records, collections, payments, settlements, refunds, bank charges, and accounting entries.
Finance teams
For teams preparing bank reconciliation reports for month-end close, cash tracking, internal review, and audit support.
Accounting teams
For teams matching bank statements with books, ledgers, vouchers, journal entries, receipts, and payments.
Treasury teams
For teams monitoring bank balances, cash movement, collections, payouts, bank charges, and liquidity-related records.
eCommerce and D2C brands
For brands reconciling payment gateway settlements, COD receipts, marketplace payouts, refunds, and final bank credits.
Retail businesses
For companies reconciling store collections, card settlements, bank deposits, gift cards, vendor payments, and internal records.
SaaS and digital businesses
For teams reconciling subscription payments, customer collections, refunds, payment gateway settlements, and bank entries.
Marketplaces and platform businesses
For teams reconciling partner payouts, customer collections, settlements, deductions, refunds, and bank credits.
Accounting firms
For firms handling recurring bank reconciliation for multiple clients.
Audit and compliance teams
For teams that need transaction-level support for bank entries, book entries, matched transactions, open items, and manual adjustments.
Trusted by teams handling bank and financial reconciliation
Cointab is used by finance and operations teams that reconcile high-volume, multi-source transaction data across banks, payments, books, ledgers, vendors, customers, partners, and internal systems.
“We have worked on many softwares but we love the ease of using cointab. The staff and support is very instant. They are approachable, proficient and patient. Team is very cooperative with the customisations. The experience of using cointab was nice.”
Bank reconciliation FAQs
Start reconciling bank transactions faster
Use a ready-made bank reconciliation template, build a custom workflow, or schedule a guided setup with the Cointab team.
View demo reportNo credit card required · Manual uploads and automated data flows supported