Bank Reconciliation

Matching a bank statement's lines to payment vouchers, so the money that has actually arrived in the bank is confirmed against the vouchers staff have recorded. This page covers uploading a statement, the Bank Reconciliation list and its actions: Auto-match, Bifurcate, Close and Change state.

Change state (on each row and on the statement's page) offers only the allowed moves: Parse again for a Failed statement, or an Uploaded one whose parse never ran (still Uploaded after 15 minutes — a fresh upload is already being parsed) (bank_statement.upload), Reconciled (close) for a Parsed or Reconciling one once no line is still pending or awaiting gateway bifurcation — and Reconciling (reopen) for a Reconciled one, so its lines can be mapped or unmapped again (both bank_statement.close).

Where statements come from

Click Upload statement at the top of the list (permission bank_statement.upload), or upload through the API with the same permission. Once a statement exists, it appears in this list and the console is where you work through its matching and finally close it.

Bank accounts Built

Bank accounts are managed under Billing → Bank accounts (permission bank_master.manage). Each account belongs either to AIR or to a customer / user:

To add an account, click New bank account and fill in:

FieldRequiredNotes
Bank branchYesSearch by branch name or IFSC. Not listed? Click + next to the field to add the branch — and, from inside that dialog, its bank (name and a short unique code such as HDFC).
OwnerNoBlank = AIR company account. Otherwise search the customer or user by ID or name.
Account nameYesHow the account appears in pickers, e.g. "HDFC Current — Nagpur".
Account numberYesUnique across all accounts.
Account typeYesSaving / Current / OD / CC / CMS. Defaults to Current.
ActiveNoInactive accounts are hidden from the statement upload.

The list shows owner (an AIR badge for company accounts), bank, branch with IFSC, number, type and status, with filters for Account type (AIR / non-AIR) and Active. Accounts cannot be deleted — once statements are filed against an account it must stay; switch it inactive instead.

Uploading a statement Built

On the list, click Upload statement, pick the Bank account (AIR accounts only — see Bank accounts), the Statement date and the file (.csv or .xlsx, up to 10 MB). The statement is saved as Uploaded and parsed in the background, so refresh after a moment to see it reach Parsed (or Failed with a reason). The first row must be a header row; two layouts are recognised:

Download template (next to Upload statement, same permission) gives a blank CSV with the same 23 column headers as the HO receipts sheet (e.g. HDFC 30.05.2024 -1.csv). Fill one row per bank entry and upload it. Only date, funds_credit_in_bank_date, instrument_number, amount, payment_remark, type are read; the Odoo reference columns (partner_id/id, journal_id/id, etc.) can be left blank.

The Bank Reconciliation list

Nav: Billing → Bank Reconciliation. Permission required to view the list: bank_statement.view. Like Payment Vouchers, there is no create or edit form — statements arrive through Upload statement or the API (see above) — but each row can be opened to a read-only detail view (below). Every column and action on this list still operates on the whole statement, not on its individual lines.

ColumnShows
statement_dateThe date of the statement, sortable.
Bank accountThe bank account the statement belongs to (bankAccount.name).
file_nameThe uploaded statement file's name.
StatusThe statement's processing/reconciliation status — badge, coloured as in the diagram below.
total_entriesHow many lines the statement contains in total.
matched_entriesHow many of those lines have been matched to a voucher.
unmatched_entriesHow many lines are still unmatched.

Filter

FilterNarrows by
StatusAny of the 6 BankStatementStatus values (see the diagram below).
Line detail is read-only

The detail view (below) lets you see a statement's individual lines, but you still cannot match or unmatch any one of them by hand there — the Lines table is read-only, with no relation-manager actions. The three totals columns (total_entries, matched_entries, unmatched_entries) are the only line-level visibility on the list itself; the actual matching happens through the aggregate actions below.

Screenshot placeholderThe Bank Reconciliation list — columns for statement date, bank account, file name, status and the total/matched/unmatched entry counts; the Status filter open above the table.

Viewing a statement Built

Use the View row action to open a statement's detail page — read-only, gated by the same bank_statement.view permission as the list. It has two info panels plus one child table:

Below the panels is the Lines table: one row per statement line, showing the line number, transaction date, description, reference, debit, credit, status (amber = still needs mapping, green = mapped) and the voucher(s) it is Mapped to. Use the Needs mapping filter to see only the lines still to do. Each line is mapped with the row actions described next.

Screenshot placeholderThe Bank Statement detail page: "Statement" and "Reconciliation" info panels, with the "Lines" table below and its row actions (Map online payments / Record payment / Match existing voucher / Vouchers / Unmap).

Mapping lines to payments Built

Every credit line should end up mapped, so all money that reached the bank is tied to payment vouchers and, through them, to sale orders. Matching a line to existing vouchers (Map online payments, Match existing voucher, auto-match) marks them Cleared straight away — the bank line is the proof the money arrived. Record payment is different: it identifies and allocates the line's own voucher, which then goes through Sales and Account approval; Account approval clears it (no deposit step, as it is already in the bank). Permission: bank_statement.reconcile. Lines can only be mapped while the statement is Parsed or Reconciling; the first mapping moves it to Reconciling.

LineActionWhat you do
Razorpay / CCAvenue settlement (one lump sum)Map online paymentsTick the online payments (Razorpay, CCAvenue, QR, wallet) that make up the settlement. The list shows unmapped payments made on or before the bank line date, by default from 3 days earlier; change Payments made from to look further back. The running total must equal the bank line exactly before it will save. Ten payments in one settlement → ten vouchers, each keeping its own sale-order allocation.
NEFT / RTGS / IMPS / cheque creditRecord paymentChoose the paying customer (pre-filled if it was already set on the voucher with Set customer) and how it was received. Then, for each row, pick the Sale order (shown with its total and what is still due), then a Sale order line of that order — the amount fills in with the line's due — and enter any Gateway charges. Only the customer's open orders (not completed or cancelled) and lines with money still due are listed. Anything already allocated on the voucher page is kept and counted in the running total. The voucher moves to Sales Department Approval (or Pending Amount Allocation if nothing was allocated). The running total shows what is left; tick Put any unallocated remainder on the customer's account to credit the rest to their account. Also needs payment.allocate.
A payment the Sales Executive already recordedMatch existing voucherPick the existing voucher. Only vouchers for the same amount are listed. This avoids recording the same payment twice.
Any mapped lineVouchers / UnmapVouchers lists the mapped vouchers with links, flagging any that are not yet fully allocated (allocate them from the voucher page). Unmap undoes a mistake: vouchers go back to their earlier state (an approved one comes back as allocated and needs re-approving), and a payment recorded with Record payment loses its allocations.
Screenshot placeholderThe "Map online payments" modal: a date field, a searchable tick-list of online payments (voucher number · customer · amount · date · method · reference · state) and a "Selected ₹X of ₹Y · Remaining ₹Z" total.

The statement lifecycle

A statement moves through 5 states on its way to being reconciled, with a 6th (Failed) if parsing goes wrong. Uploading and parsing happen automatically; the three console actions work on a statement once it reaches Parsed.

Auto-match Built

Works through the statement's unmatched cheque/DD lines and matches each one, by instrument number and amount, to a single candidate voucher in state Deposited. Visible on statements in state Parsed or Reconciling.

Permissions

Requires bank_statement.reconcile (or super-admin).

  1. Find a statement with unmatched lines

    Filter by Status = Parsed or Reconciling, and check unmatched_entries is greater than zero.

  2. Select Auto-match

    Icon: link.

  3. Confirm

    A confirmation dialog asks you to confirm before running the match.

  4. Result

    For each cheque/DD line where instrument number and amount match a single Deposited voucher: that voucher is cleared (moves to Cleared), and any duplicate Suspense voucher covering the same money is cancelled. The statement's matched_entries/unmatched_entries counts recompute, and its status advances toward Reconciling.

Bifurcate Built

Splits a single gateway settlement line into the individual payments it actually represents. Only appears when at least one of the statement's lines needs this — a line whose internal processing status shows it is awaiting gateway splitting. Visible on statements in state Parsed or Reconciling.

Permissions

Requires bank_statement.reconcile (or super-admin) — the same permission as Auto-match.

  1. Look for the Bifurcate button

    It only shows up on a statement that has a line description the system recognises as a Razorpay or CCAvenue settlement and that still needs splitting. If you don't see it, the statement has no such line right now.

  2. Select Bifurcate

    Icon: arrows-pointing-out.

  3. Confirm

    A confirmation dialog asks you to confirm before proceeding.

  4. Result

    The system detects which gateway (Razorpay or CCAvenue) the line came from, fetches that gateway's settlement detail, and records the individual settlement payments as vouchers so each can be matched separately.

Close Built

Finalises the statement once every line has been resolved. Visible on statements in state Parsed or Reconciling.

Permissions

Requires bank_statement.close (or super-admin) — note this is a different permission from the one that guards Auto-match and Bifurcate.

  1. Make sure every line is resolved

    Run Auto-match and, if it appears, Bifurcate first until unmatched_entries is zero (or you have deliberately decided the remaining lines need no action).

  2. Select Close

    Icon: lock-closed, colour success.

  3. Confirm

    A confirmation dialog asks you to confirm before closing.

  4. Result

    The statement moves to Reconciled and is finalised.

Close only blocks on unprocessed lines — not on unmatched ones

Close is refused only while a line is still Pending or still awaiting gateway bifurcation. Work through Auto-match and Bifurcate until neither is left, then try Close again.

Lines that simply failed to match do not block it. A statement with a non-zero unmatched_entries count can still be closed — that is deliberate, so a handful of entries that genuinely need no action cannot hold a month open forever. The flip side is that closing does not prove everything was matched: check unmatched_entries yourself before you close, because nothing else will.

Screenshot placeholderThe Auto-match confirmation dialog on a Parsed statement.
Screenshot placeholderThe Bifurcate confirmation dialog, shown only when a gateway-settlement line needs splitting.
Screenshot placeholderThe Close confirmation dialog, and the error notification shown when Close is refused because lines are still pending.

What isn't in this console Planned / elsewhere

See also