Multi-Bank Account Management Nepal - Consolidated Cash Position Dashboard

A mid-sized Kathmandu trading company typically operates accounts at two or three banks. There might be a current account at Nabil Bank for day-to-day supplier payments, an account at NIC Asia for payroll, a fixed deposit at Himalayan Bank earning interest on surplus cash, and possibly a USD account at Standard Chartered for import payments. Each account has its own online banking portal, its own statement, and its own reconciliation cycle. The finance director who needs to know the total cash position at 9:00 AM on a Tuesday has to log into four different portals, note the balances, and add them up manually.

This is not a minor inconvenience - it creates a real information gap. Treasury decisions depend on knowing the total available cash position across all accounts before making a commitment. Deciding whether to take a supplier's early payment discount requires knowing that the surplus cash is actually in an accessible current account, not locked in a fixed deposit. Deciding whether to defer a payment versus drawing on an overdraft requires knowing that the other accounts are not low. Without a consolidated view, these decisions are made with partial information and often the wrong account gets used.

Multi-bank account management in an ERP context means all bank accounts live in the same general ledger, with each account's transactions, reconciliation status, and current balance visible from one login. The cash position dashboard aggregates balances across all accounts, categorized by account type and currency. The treasury team sees the full picture; the accounts team reconciles each account separately; and both are working from the same data.

Setting Up a Multi-Bank Account Structure in ERP

Each bank account needs its own general ledger account code. This is standard accounting practice, but the configuration matters: the account code structure should allow aggregation at different levels. A company with four bank accounts might want to see individual account balances, total balance by bank (for banking relationship management), total by currency (for FX exposure), and total cash across all accounts. A well-designed chart of accounts groups bank accounts under a parent "Cash and Bank" category that rolls up to the balance sheet automatically.

Account attributes beyond the ledger code are important for operational management: account type (current, savings, fixed deposit), bank name, branch, account number, SWIFT code (for foreign currency accounts), overdraft limit if applicable, and the person responsible for reconciliation. Fixed deposits need additional fields: maturity date, interest rate, and whether the deposit auto-renews. These details support the alert system - a fixed deposit maturing next week needs a decision about renewal before the maturity date, and that decision should surface automatically rather than be discovered after the fact.

Currency management is a separate layer for businesses that hold foreign currency accounts. A company importing goods from India or China may hold a USD account to reduce conversion friction. The USD account balance needs to appear on the balance sheet at the closing exchange rate, with exchange gain/loss recorded when the rate changes between transaction date and settlement date. NRB publishes buying and selling rates daily; the ERP should use the appropriate rate for the transaction type (buying rate for USD receipts, selling rate for USD payments) and flag any significant FX exposure on open transactions.

The Cash Position Dashboard

The consolidated cash position dashboard shows the one number every finance director wants first: total available cash right now. Below that number, the breakdown matters: how much is in current accounts (accessible immediately), how much is in savings accounts (accessible with minor notice), how much is in fixed deposits (locked until maturity), and how much is held in foreign currency (accessible but subject to conversion rate).

A useful cash position dashboard for a Nepal trading company might show five panels: total cash across all NPR accounts, total foreign currency holdings converted at current NRB rate, upcoming fixed deposit maturities in the next 30 days, overdraft utilization per facility, and the current balance in each account with a 7-day trend. The 7-day trend is particularly useful - a current account balance that has been declining for six consecutive days signals that incoming receipts are not keeping pace with outgoing payments, which is actionable before the account goes negative rather than after.

Inter-Bank Transfer Management and Payment Routing

Businesses with multiple bank accounts regularly move cash between accounts: sweeping excess current account balance into a fixed deposit, transferring payroll funding from the operating account to the salary account on the 28th of each month, covering a payment from whichever account has the appropriate available balance. These inter-bank transfers need to be recorded correctly in the accounting system - as a transfer between bank ledger accounts, not as an income or expense. Mis-recording a transfer as a receipt or payment doubles the apparent cash or creates a phantom expense.

Payment routing decisions - which bank account to use for a specific payment - are also worth managing explicitly. Some businesses designate specific accounts for specific payment types: supplier payments go from the current account, import payments go from the USD account, tax payments go from the payroll account because the remittance reference is linked to that account's tax registration. Recording these routing preferences in the system means junior accounts staff can follow the rule consistently without needing to call the finance director each time a payment needs to go out.

For businesses with project-specific or donor-specific accounts (common in construction and NGO sectors), payment routing controls ensure that project expenses are paid from the correct project account rather than the main operating account. This segregation is not just an accounting preference - it is often a contractual requirement in donor-funded projects and a practical necessity for project cost reporting.

Reporting and Audit Requirements for Multiple Bank Accounts

Audit preparation for a multi-bank position requires a bank confirmation letter from each bank (confirming account balance, overdraft facility, and any security interests as of the audit date), a reconciled bank register showing closing balance per account, a list of outstanding cheques, and an analysis of any unusual transactions. With manual management across multiple banks, assembling this documentation at year-end is time-consuming. With an ERP that maintains all accounts in one system, the audit preparation report is generated from the same data used for day-to-day management.

IRD may request bank account details as part of a tax assessment or investigation. The ability to produce a complete account register - all accounts, all banks, all transactions in a period, reconciled and auditable - from a single system output is considerably faster and more credible than assembling it from separate bank portals and Excel files. A complete reconciliation history also demonstrates that the business maintains financial controls, which is relevant context when IRD is reviewing the adequacy of accounting records.

For cooperative societies and NGOs that must submit financial reports to the Department of Cooperatives or Social Welfare Council, the ability to produce per-fund or per-project reports from a multi-bank structure is a compliance requirement, not a nice-to-have. Managing these accounts in a single ERP with proper account segmentation makes the reporting process straightforward rather than requiring a rebuild of the figures from multiple sources.