Skip to main content
Connect your bank accounts to DualEntry to pull in transaction feeds automatically. Each connection links a bank account to a GL cash or liability account so incoming transactions land in the right place for reconciliation. DualEntry supports checking accounts, savings accounts, credit cards, lines of credit, and brokerage or investment accounts, with no per-organization limit on the number of connections you can add.

​
Prerequisites

Before connecting, confirm the following:
  • You have Admin or IT role access in DualEntry (see User Roles and Permissions).
  • The GL cash or liability account the bank will map to already exists in your chart of accounts.
  • You have online banking credentials for the institution you want to connect.

​
Connect via a certified aggregator

DualEntry connects to your bank through a certified third-party aggregator. The aggregator handles authentication with your bank and returns a secure access token to DualEntry. You never paste banking credentials into the DualEntry interface. To connect a bank account:
  1. Navigate to Company → Bank Connections in the DualEntry sidebar.
  2. Choose Add Bank Connection, then DualEntry Router from the menu. For a brokerage or investment account, choose Investment Account Router instead so holdings come across as well as transactions.
  3. Search for your bank and choose it. DualEntry opens that institution’s hosted sign-in, where you enter your online banking credentials.
  4. Choose the accounts you want to connect. You can connect multiple accounts from the same institution in a single flow.
  5. After approval, the flow redirects back to DualEntry. Each selected account appears in the Bank Connections list with a status of Connected.
Some institutions require multi-factor authentication during the hosted flow. If your bank requires MFA, you complete it inside the aggregator’s window. DualEntry never sees the MFA code.

​
If your bank is not supported

Coverage determines whether your bank is reachable through the aggregator search. If you cannot find your institution there, it is not currently reachable that way, and there are three alternatives in rough order of effort:
  • SFTP. Ask your bank whether they deliver a daily transaction file over SFTP. This is the usual answer for an institution without a live connection, and it is self-serve. See SFTP bank connections.
  • Build the feed yourself. If your systems already pull transactions from the bank, a developer can push them into DualEntry over the Bank Connections API. See Bank Connections: Inbound Feed API.
  • Ask for a non-standard connection. DualEntry builds against the same API at its discretion, subject to feasibility review and additional fees quoted in your Order Form. Raise it with your account manager.
Manual upload, covered below, remains available at any point and needs no engineering work. For how connections are routed and how DualEntry handles provider-side outages, see Banking Connections: Paths, Sync, and Security.

​
Upload bank statements manually

If your bank is not supported by the aggregator, or you prefer to upload statements manually, use CSV or BAI import from Bank Match instead. Manual statement uploads rely on you to provide transaction data on a regular cadence. The bank is not polled automatically. To upload a CSV or BAI bank statement:
  1. Open Close Workflows → Bank Match from the sidebar.
  2. Choose the bank account from the account bar at the top of the Bank Match page.
  3. Open the To Match tab.
  4. On the Bank Statement Lines side of the page, choose Upload statement.
  5. In the side drawer, download the template if you need to reformat the statement into the accepted format.
  6. Drag and drop the CSV or BAI file into the drawer, or choose the file from your computer.
Manual uploads do not refresh automatically. Upload a new file each time you want to bring in recent activity, at minimum monthly by the 5th business day of the following month if you want reconciliation to stay current. Once uploaded, statement lines appear in Bank Match for the selected bank account, so reconciliation, rules, and bank match use the same downstream workflow regardless of how the data arrived.

​
GL mapping and feed frequency

Every bank connection must be mapped to exactly one GL account. This mapping determines where transactions appear in your ledger and which account is reconciled during reconciliation. To configure or change the mapping:
  1. Open Company → Bank Connections.
  2. Choose the connection you want to configure.
  3. Under GL Account, choose the cash or liability account from the dropdown.
  4. Save.
If you change the GL mapping after transactions have already been imported, existing transactions keep their original GL account. Only new transactions use the updated mapping. Aggregator-backed connections refresh automatically. You can also trigger a manual refresh from the Bank Connections screen by choosing Refresh on any connection. For sync cadence, refresh cooldowns, and feed latency by institution, see Banking Connections: Paths, Sync, and Security.

​
Manage, disconnect, and reconnect

The Bank Connections list shows the status, last sync time, and GL account for every active connection. To keep things organized, name each connection with the institution and last four digits of the account number (for example, “Chase ••1234”). DualEntry doesn’t enforce a naming convention, but a consistent pattern makes it easier to identify connections at a glance. To disconnect a bank connection:
  1. Open Company → Bank Connections.
  2. Choose the connection and choose Disconnect.
  3. Confirm the action.
Disconnecting stops future syncs but does not remove previously imported transactions or reconciliation history. The connection becomes inactive in the list, and any GL accounts it mapped to are unlinked from the disconnected feed but otherwise unchanged. To reconnect the same account, start a new connection through Add Bank Connection. DualEntry creates a fresh connection rather than reactivating the old one. You need to re-map the new connection’s accounts to the same GL accounts to keep the reconciliation history continuous.
If a connection enters an error state (typically because the bank revoked the token or your credentials changed), DualEntry flags it as Needs Attention. Reconnect by choosing Reconnect on the affected connection and completing the aggregator’s hosted flow again. This preserves the existing connection record and its GL mappings.

​
After connecting

After you connect through an aggregator, connect an SFTP feed, or upload a statement manually, bank transactions are ready for matching and reconciliation. For an aggregator-backed connection, the first sync begins immediately and typically completes within a few minutes. Transactions then continue to flow on the aggregator’s regular cadence with no further action required. For an SFTP connection, transactions arrive after the daily scheduled pickup, or immediately if you choose Pick up now; see Schedule pickups. For manual statement uploads, new activity appears only after you upload the next CSV or BAI file. The Bank Connections screen serves as your central dashboard for monitoring sync status, troubleshooting feed issues, and managing GL mappings across all connected accounts. If a connection stops syncing or enters an error state, the dashboard surfaces the issue immediately so you can reconnect before it affects your reconciliation workflow. You can also use the dashboard to verify that each connection’s GL mapping is correct and that sync timestamps are current. As your organization grows, you can add new connections at any time without disrupting existing ones. Each new connection begins syncing independently and populates its own staging area for reconciliation. For the next step in the workflow, see Reconciliation to match imported transactions against your ledger. For details on how DualEntry’s AI accelerates the matching process, see Bank Match AI.
Last modified on September 23, 2026