Budgeting & Forecasting

How does cash forecasting software connect to multiple banks?

How does cash forecasting software connect to multiple banks?
Key Takeaways
  • Most companies need several connection methods at once, because banks differ in their APIs, file formats and supported regions.
  • Bank balances refresh on different schedules by bank and method, so a consolidated view should show when each balance was last updated.
  • Switching banks means re-establishing connections and mapping new accounts, while history from the old bank stays in the forecast.

Cash forecasting software connects to multiple banks through a mix of methods: direct bank APIs (application programming interfaces), aggregator connections, Swift statement feeds and scheduled file imports. Each account ends up in one consolidated view with balances and transactions. The right method for each bank depends on its country, its technology and how often your forecast needs fresh data.

How do I connect multiple banks and multiple accounts to one forecast?

To connect multiple banks and accounts to one forecast, connect each bank with the method it supports, then map every account to an entity, currency and purpose in one structure. The forecast reads the mapped accounts, so adding a bank later means adding its connections and mappings while the model stays as it is.

Start with an inventory. List every bank, every account, its entity, currency and use: operating, payroll, collections, savings or restricted. Mid-market groups are often surprised by the count. A company with five entities can easily hold 30 accounts across six banks once local payroll and deposit accounts are included.

Account purpose matters for liquidity. A payroll account funded the day before payday and a restricted escrow account both hold cash, but neither is freely available. The forecast should show total cash and available cash separately.

The common manual process breaks at scale. Picture a treasury analyst logging into six bank portals every Monday, downloading statements and pasting them into a workbook. One bank changes its export layout in March, and the analyst’s lookup formulas pull the wrong column for three weeks. Automated connections remove the downloads, and mapping removes the dependence on each bank’s file layout.

Intercompany sweeps and transfers need tagging. When cash moves between entity accounts, the consolidated view should show it as one transfer between entities, so it never appears as a receipt in one entity and a payment in another.

Read-only bank feed vs API feed: what is the difference?

A read-only feed delivers balances and transactions so software can see them. An API feed uses the bank’s own interface, which can be read-only or can also support actions such as initiating payments. For cash forecasting, read-only access is usually all you need.

The terms overlap in practice. Many bank APIs are offered in read-only and payment-enabled tiers. Aggregators, which connect to many banks through one service, typically provide read-only access. Statement feeds through Swift or file transfer are read-only by design.

Read-only access is also easier to approve. Treasury, IT and auditors tend to accept read access for forecasting software because it cannot move money. Payment initiation adds approval workflows, dual control and more scrutiny of the vendor’s security.

Data depth differs by method. Some feeds provide only end-of-day balances. Others include intraday balances, transaction descriptions, counterparty names and references. Forecast quality depends on the detail: a transaction with the customer’s name and invoice number can be matched to receivables, while one labeled "deposit" cannot.

Ask each provider to show a sample transaction from your own bank, with every field it will receive. That sample tells you more than a list of supported banks.

What if my bank does not have an API?

A bank without an API can still feed a cash forecast through another connection method. Banks without a usable API can usually provide statements through Swift, through secure file transfer, or as scheduled exports from their online portal. Each method delivers balances and transactions on a set schedule.

Swift statement messages are common for larger and international banks. Statement formats such as MT940 and the ISO 20022 camt.053 message carry end-of-day balances and transactions in a standard structure. Payment instructions on Swift have moved to ISO 20022, with the coexistence period for cross-border payment messages ending in November 2025 (Swift, 2025). Statement formats are moving more gradually, so many banks still send MT940.

Secure file transfer is the next option. The bank drops a daily statement file into an SFTP folder, and the software picks it up. It is reliable once set up, though setup may need IT and bank paperwork.

Portal exports are the fallback. Someone downloads a file on a schedule, or a robot does. Both work, but both depend on a person or a script that can break, so add a check that the file arrived and that its closing balance matches the bank.

Small local banks are the usual gaps. Plan for them early, because they often hold payroll or deposit accounts that matter more than their size suggests.

Does cash forecasting software support non-US banks?

Non-US bank coverage varies widely between cash forecasting tools, so check every bank by name and country. US-focused aggregators often cover North American banks well and international banks less consistently. Groups with entities in Europe, Asia or Latin America usually need a provider that combines several connection methods.

Regional standards help. In the European Union, the revised Payment Services Directive (PSD2) requires banks to give authorized providers access to payment accounts, and UK open banking rules do the same, which improves coverage for accounts in those regions. Elsewhere, coverage depends on each bank’s own APIs, Swift connectivity or file exports.

Currency handling matters as much as connectivity. Each account should keep its own currency, with conversion to the reporting currency at a stated rate. A consolidated balance in dollars can look healthy while the entity that owes a supplier in euros holds mostly dollars.

Local banking calendars affect timing. Bank holidays differ by country, so receipts and payments expected on a holiday shift to the next business day. A forecast built on one country’s calendar will misplace cash in another.

Test with the hardest bank first. The most remote subsidiary’s bank is usually the one that decides whether the group view is complete.

How often do bank balances refresh: real time or lagged?

Bank balance refresh timing depends on the bank and the connection method. Some bank APIs provide intraday balances updated through the day. Aggregator and statement feeds usually provide prior-day balances, with today’s transactions arriving overnight. A consolidated view should show the timestamp of each balance.

For most forecasting, daily refresh is enough. A 13-week forecast is reviewed weekly and managed daily. Intraday balances matter more for companies that move large sums daily, sweep accounts or manage tight credit lines.

Timestamps prevent bad decisions. If one bank shows this morning’s balance and another shows yesterday’s, a group total adds numbers from different moments. Display "as of" times beside each account.

Datarails Cash brings every bank and account into one consolidated view. It supports 100 percent of banks worldwide through a multi-faceted integration approach, including banks that standard aggregators and integration networks do not cover. It also connects to payment platforms such as Stripe, so cash held with processors sits in the same position as bank cash. Balances and transactions arrive across entities and currencies with automated conversion, and every figure drills down to the transactions behind it.

Because Datarails Cash is built on FinanceOS®, the foundation underneath Datarails, the same bank data is available to Datarails FP&A for financial planning and analysis, and to Datarails Month-End Close to support reconciliation and the close.

How do I handle MFA on bank connections?

To handle multi-factor authentication (MFA) on bank connections, prefer connection methods that run without a person’s MFA prompt. API connections authorized at company level, Swift feeds and file transfers run without someone approving a code each time. Connections that rely on a user’s portal login break when that user’s MFA session expires or the user leaves.

MFA on portal-based connections is the most common cause of silent gaps. As an illustration, picture a connection that relies on a controller’s personal bank login. When the controller goes on leave, the session expires, the bank stops sending data and the forecast shows a stale balance for nine days.

Three practices reduce the risk. Use service-level credentials or company-authorized API access where the bank offers it. Assign each connection to a role with a named backup. Monitor connection health daily, with an alert when a bank’s data stops updating.

Re-authorization schedules vary. Some open banking connections need consent renewed periodically. Put renewal dates on the treasury calendar so a connection does not lapse during close.

What happens to my bank connections if I switch banks?

When you switch banks, you connect the new bank, map its accounts to the same entities and purposes, and close the old connections once the accounts are closed. History from the old bank stays in the forecast and reporting, so trends and variance analysis continue across the switch.

The overlap period needs care. During a migration, payments may leave from old accounts while receipts arrive in new ones. Keep both banks connected until every old account is closed, and tag transfers between them so they do not appear as receipts and payments.

Customer remittance details are the slowest part to change. Customers continue paying the old account for weeks or months after notice. Track receipts by account during the transition, and follow up with customers still paying the old bank.

Mapping makes the switch manageable. Because the forecast reads accounts by entity and purpose, a new operating account replaces the old one in the same line. The overview of cash forecasting tools covers how this architecture fits together.

Where to start

List every bank account across your entities, with its connection method today and the date its balance was last updated. The oldest date shows where the forecast is weakest. A Datarails demo shows what that looks like on your own data.

Related Articles

Become a Partner

Drive Business Performance With Datarails

Drive Business Performance With Datarails

Drive Business Performance With Datarails

Drive Business Performance With Datarails

Drive Business Performance With Datarails

Drive Business Performance With Datarails