Mapping External Bank Accounts to Internal Bank Accounts

After successfully linking an external bank account to RunSensible via the Plaid integration, the system will prompt the user to perform an essential step associating the newly connected bank account with one of the internal bank accounts defined within the system. In RunSensible, internal bank accounts may include operating accounts, trust accounts, credit card accounts, or any other custom-defined ledger. It is important to map the external bank account to the correct internal account in order to establish a clear connection between the two.

By selecting the appropriate internal bank account, the user ensures that transactions from the linked real-world bank account are properly categorized in the system. Once this mapping is completed, users can proceed to associate each imported bank transaction with the corresponding financial records, such as invoices or expenses.

Establishing this relationship between the actual bank data and the system’s internal accounting structure ensures that financial activities from external bank accounts are reflected accurately in the system. This process not only streamlines the tracking of transactions but also maintains a fully traceable connection between real-world banking activity and case or matter-specific financial workflows.