Bank details

Capturing bank accounts

📷 Image placeholder

Add a screenshot here: the vendor Bank tab showing a bank account form (bank name, account number, IFSC, MICR, SWIFT, transaction type) with the Default-for-payments toggle.

Store a vendor’s bank accounts so payments and reconciliation use the right details. For each account capture:

• Bank name
• Account number
• IFSC
• MICR
• SWIFT
• Transaction type (NEFT / RTGS / IMPS / cheque)

A vendor can hold multiple bank accounts, and one is marked default for payments. For multi-currency vendors you can keep a separate primary account per currency.

Validation

• IFSC is validated; an invalid code is rejected.
• MICR (9 digits) and SWIFT (8 or 11 alphanumerics) are format-checked when provided.
• The routing-code field validates against your organisation’s active region format, IFSC, SWIFT/BIC, IBAN, ABA, sort code or MICR.

Masking and secure reveal

Bank data is sensitive, so it’s protected:

• Account numbers are stored securely (kept scrambled so they can’t be read directly) and shown masked by default.
• Roles without bank-view permission see bank fields masked everywhere, the detail page, the directory and any export. The full values are never sent to the screen for these users, and any attempt to edit a masked field without permission is rejected.
• A role with explicit reveal permission can view the full account number. Every reveal is audited (who revealed it and when), and any change to a bank account is recorded using the masked number.

📷 Image placeholder

Add a short animation here: a permitted user clicking Reveal on a masked account number to show the full number once, with a note that the reveal is recorded in the audit trail.