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).
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:
- AIR accounts — leave Owner blank. Only these appear in the statement upload's Bank account list, and only these can receive payment-voucher deposits.
- Customer / user accounts — pick the owner. They are kept for reference (for example, where a refund is paid) and never appear in the statement upload.
To add an account, click New bank account and fill in:
| Field | Required | Notes |
|---|---|---|
| Bank branch | Yes | Search 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). |
| Owner | No | Blank = AIR company account. Otherwise search the customer or user by ID or name. |
| Account name | Yes | How the account appears in pickers, e.g. "HDFC Current — Nagpur". |
| Account number | Yes | Unique across all accounts. |
| Account type | Yes | Saving / Current / OD / CC / CMS. Defaults to Current. |
| Active | No | Inactive 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:
- A bank export — columns such as
Date/Transaction Date,Narration,Chq No/UTR,Withdrawal/Debit,Deposit/Credit,Balance. Dates like13/05/2024are read day-first. - The HO receipts template (e.g. HDFC 30.05.2024 -1.csv) —
funds_credit_in_bank_dateis used as the transaction date (thedatecolumn is only the entry date),instrument_numberas the reference,payment_remarkas the description, andamountas a credit (or a debit whentypeisPayment). Other columns in the template are ignored.
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.
| Column | Shows |
|---|---|
statement_date | The date of the statement, sortable. |
| Bank account | The bank account the statement belongs to (bankAccount.name). |
file_name | The uploaded statement file's name. |
| Status | The statement's processing/reconciliation status — badge, coloured as in the diagram below. |
total_entries | How many lines the statement contains in total. |
matched_entries | How many of those lines have been matched to a voucher. |
unmatched_entries | How many lines are still unmatched. |
Filter
| Filter | Narrows by |
|---|---|
| Status | Any of the 6 BankStatementStatus values (see the diagram below). |
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.
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:
- Statement — the statement date, the bank account, the file name and the status (same coloured badge as the list).
- Reconciliation — the total, matched and unmatched entry counts, who uploaded the statement, and who reconciled it.
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.
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.
| Line | Action | What you do |
|---|---|---|
| Razorpay / CCAvenue settlement (one lump sum) | Map online payments | Tick 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 credit | Record payment | Choose 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 recorded | Match existing voucher | Pick the existing voucher. Only vouchers for the same amount are listed. This avoids recording the same payment twice. |
| Any mapped line | Vouchers / Unmap | Vouchers 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. |
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.
- Find a statement with unmatched lines
Filter by Status = Parsed or Reconciling, and check
unmatched_entriesis greater than zero. - Select Auto-match
Icon: link.
- Confirm
A confirmation dialog asks you to confirm before running the match.
- 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_entriescounts 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.
- 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.
- Select Bifurcate
Icon: arrows-pointing-out.
- Confirm
A confirmation dialog asks you to confirm before proceeding.
- 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.
- Make sure every line is resolved
Run Auto-match and, if it appears, Bifurcate first until
unmatched_entriesis zero (or you have deliberately decided the remaining lines need no action). - Select Close
Icon: lock-closed, colour success.
- Confirm
A confirmation dialog asks you to confirm before closing.
- Result
The statement moves to Reconciled and is finalised.
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.
What isn't in this console Planned / elsewhere
- Automatic suggestions for settlement lines: the console doesn't yet guess which online payments make up a Razorpay/CCAvenue settlement. You tick them yourself under Map online payments.
See also
- Payment Vouchers — the 10-state voucher lifecycle that Auto-match and Close feed into (Clear, and cancelling a duplicate Suspense voucher).
- Discounts, Refunds & Charges — other Billing-group workflows alongside reconciliation.
- Accounting — journal entries and GST e-invoices, the ledger side of billing.