Bank

Back to Accounts

Overview

Bank — Business Overview

The Bank document is a foundational setup record used to define and manage the financial institutions your organization works with. It serves as a central reference for all bank-related activities, ensuring consistency and clarity across financial operations.


Purpose in Business Operations

The Bank document is used to: - Maintain a standardized list of all banks your organization deals with
- Support accurate recording of bank transactions, payments, and receipts
- Enable smooth coordination between accounting, treasury, and finance teams

By defining banks centrally, Dafater ensures that all financial activities reference the correct institution, reducing errors and confusion.


Prerequisites and Setup Requirements

Before using the Bank document, you should: - Identify all banks your organization uses for payments, collections, loans, or deposits
- Decide on standard naming conventions for banks to ensure consistency
- Confirm that your finance or accounting team agrees on which banks are active and approved

Once set up, the Bank document is typically used across multiple financial records and should be maintained carefully.


Typical Workflow and Business Fit

  1. Initial Setup
    Finance or accounting teams create Bank records during system setup or when onboarding a new bank.

  2. Operational Usage
    The selected Bank is referenced in:

    • Bank accounts
    • Payment and receipt records
    • Reconciliations and financial reports
  3. Ongoing Maintenance
    Banks are reviewed periodically. Inactive or discontinued banks are marked accordingly to prevent future use while preserving historical data.

This workflow ensures that all bank-related transactions are aligned with approved and recognized financial institutions.


Key Business Scenarios Where Bank Is Essential

In all these cases, the Bank document acts as the trusted reference point.


Important Considerations for Users


In summary, the Bank document is a key setup element that underpins reliable, well-organized financial operations in Dafater. Proper setup and maintenance help ensure smooth transactions, accurate reporting, and strong financial control.

Basic Information

Fields

Field Name Label Type Required Options Description
bank_name Bank Name Data - Official registered name of the bank for Dafater records
swift_number SWIFT number Data - International SWIFT code for identifying the bank globally
cbid_code CBID Code Data - Central bank identification code used for regulatory and reporting purposes
website Website Data - Official bank website URL for reference and verification
address_html Address HTML HTML - Formatted bank address displayed on Dafater forms and documents
contact_html Contact HTML HTML - Formatted bank contact details shown on Dafater records
banktransactionmapping Bank Transaction Mapping Table Bank Transaction Mapping Rules mapping bank transactions to Dafater accounting entries
plaidaccesstoken Plaid Access Token Data - Secure token enabling bank data synchronization via Plaid integration

Child Tables

Bank Transaction Mapping (Bank Transaction Mapping)

Field Name Label Type Required Options Description
banktransactionfield Field in Bank Transaction Select - Select Dafater bank transaction field for mapping.
file_field Column in Bank File Data - Specify column name from imported bank file.

Permissions

Role Read Write Create Delete Submit Cancel
System Manager
DocType Relationship Module
Bank Account Linked from Accounts
Bank Guarantee Linked from Accounts
Bank Statement Import Linked from Accounts
Payment Order Linked from Accounts
Payment Request Linked from Accounts