7. Banking, finance, and financial continuity

Two days after the Shock, the CTO declared the infrastructure stabilized. Core services were limping along on a regional provider. Customer data had been restored from offline backups. For the first time, the leadership team exhaled.

But the panic was still real in the finance departement. Six months earlier, the CFO had moved the company's operating cash to a neobank, with the kind with a beautiful dashboard, instant notifications, and an API that plugged directly into the accounting stack. The company had left their long-time banking partner, a mid-sized French institution with a branch around the corner. The fees were higher, the interface was from another era. It had felt like a sensible modernization. Now the neobank's app displayed a loading screen. No error message. No degraded mode. Just silence. Customer support was chat-only, and the chat was unreachable. There was no branch to walk into. 

And there was another problem: most of the company's working capital was not even in that account. The CFO had parked the bulk of the treasury in short-term deposits and US Treasury notes, denominated in dollars. It had been the sound, conservative choice — safe, liquid, yielding. But the same sanctions that had disrupted cloud access were now freezing dollar-denominated assets held by European entities.

The company was technically alive. Its product was recovering. Its customers were being contacted. But it could not pay anyone. Not its employees, not its hosting provider, not the contractors rebuilding its systems. The crisis had shifted from technology to cash. And cash, it turned out, had its own dependencies.

Failure mode

Most companies treat banking as a utility: always available, always responsive. In reality, financial operations depend on a stack of digital services that is just as fragile as the rest of the cloud ecosystem. Modern financial operations typically rely on cloud-based banking portals and neobank APIs, SaaS accounting and invoicing platforms, digital expense management tools, cloud-synced payroll processors, and payment gateways routed through US-controlled infrastructure. If a systemic disruption hits, several of these would fail simultaneously.

The result is not simply inconvenience. It is operational paralysis. The company cannot pay salaries, cannot settle invoices, cannot collect revenue, and cannot prove to its own bank that it has the authority to act. Unlike technical systems, financial systems carry hard deadlines: payroll dates, tax obligations, supplier payment terms, and loan covenants do not pause because a cloud provider is down.

A particularly dangerous failure mode is the authority gap. Banks are structurally conservative. When uncertainty rises, they default to inaction. If a company cannot verify its authorized signatories, or prove account ownership through normal digital channels, the bank will delay. It will not risk executing a fraudulent instruction. From the bank’s perspective, this is prudent. From the company’s perspective, it is a cash freeze at the worst possible moment.

The extraterritorial reach of the US dollar compounds this risk. Because a large share of global financial infrastructure clears through US-dollar-denominated systems, companies can be affected by US sanctions, legal orders, or regulatory actions even when they operate entirely outside the United States. Payment freezes, correspondent banking disruptions, and platform suspensions can cascade from geopolitical events that have nothing to do with the company itself.

Objectives

Financial preparedness ensures that the company retains the ability to move money, pay people, and meet obligations even when its primary financial infrastructure is disrupted. 

Specifically, the company must be able to:

• access operating cash through at least one independent channel,
• pay employees and critical suppliers within contractual or legal deadlines,
• prove signatory authority to financial institutions without relying on cloud-based tools,
• maintain a minimum financial picture: what the company owns, what it owes, and what is owed to it,
• continue invoicing and collecting revenue, even in degraded mode.

Solutions

Reduce single-bank and single-account risk

Concentrating all operating cash in a single bank account, or a single banking institution, is a single point of failure. If that account is frozen, if the bank’s online systems are unavailable, or if the institution itself is affected by sanctions, the company has no financial recourse.

Prepared companies distribute their operating cash across at least two banks, ideally in different jurisdictions. This does not require complex treasury management. It requires maintaining a secondary bank account with enough cash to cover a minimum of four to six weeks of critical expenses: payroll, hosting, and essential supplier payments.

The secondary account should be chosen deliberately. Favour a traditional European bank with robust financial ratios, physical branch access, independent online banking infrastructure, and SEPA connectivity - a “boring boomer bank”. Avoid concentrating both accounts with neobanks or fintechs that share the same underlying banking-as-a-service provider, as they may fail together.

Maintain offline access to banking

Most banking interactions now happen through web portals or mobile apps that depend on cloud infrastructure, identity providers, and internet connectivity. When these fail, the company may be unable to check balances, initiate transfers, or even confirm what transactions have already occurred.

Prepared companies ensure that at least one banking relationship supports access through independent channels: a physical branch within reasonable proximity, a dedicated hardware authentication token that does not depend on a smartphone app, or a pre-agreed telephone banking protocol with identity verification that does not rely on email.

In addition, you should regularly export and store offline copies of recent bank statements, account balances, and pending transactions. If a disruption prevents online access for days or weeks, these records become the company’s only financial picture. Without them, you cannot determine cash position, reconcile payments, or plan expenditures.

Payroll continuity

Payroll is a hard deadline. In most European jurisdictions, failure to pay employees on time triggers legal and regulatory consequences, damages trust, and accelerates attrition at the worst possible moment. If a disruption coincides with a payroll cycle, the company must be able to execute payments even without access to its normal payroll platform.

Modern payroll is typically managed through SaaS platforms that calculate taxes, deductions, and net pay, generate payment files, and submit them to banks. When these platforms are unavailable, the company loses not just the execution mechanism but also the calculation logic.

Preparedness requires two things. First, a recent offline copy of the payroll register: the list of employees with their bank details, gross salaries, and standard deductions. This does not need to be perfect for every edge case. It needs to be close enough to execute an emergency payment that can be corrected later. Second, a pre-tested manual payment path: typically a SEPA batch file uploaded directly to the bank, or individual SEPA Credit Transfers initiated through the secondary bank’s portal or branch.

Practice this at least once. Generate a test SEPA file from the payroll register, confirm that the bank accepts the format, and verify that the authorized signatories can approve the batch. The first time you execute a manual payroll should not be during a crisis.

Diversify payment rails

Many European companies route their payment collection through US-based payment gateways such as Stripe, Adyen, or PayPal. These platforms work extremely well under normal conditions, but they introduce jurisdictional risk. In a scenario involving US sanctions, export controls, or regulatory pressure, these providers may be legally required to suspend service to affected entities, regardless of where the company operates.

Prepared companies complement their primary payment stack with at least one EU-native payment rail. For B2B companies, SEPA Credit Transfers and SEPA Direct Debits are the most straightforward options: they operate entirely within the European payments infrastructure and do not depend on US-based intermediaries. For B2C or subscription-based businesses, emerging schemes such as Wero or domestic instant payment systems may offer additional independence.

The objective is not to replace the primary payment provider. It is to ensure that revenue collection can continue, even at reduced efficiency, if that provider becomes unavailable. A company that can still receive payments survives. A company that cannot, regardless of how functional its product is, has a clock ticking.

Pre-establish financial authority

In normal conditions, banks verify identity and signatory rights through online portals, email confirmations, and digital signature tools. When these channels are unavailable, the bank’s compliance team defaults to the most conservative interpretation: delay everything until certainty is restored.

Preparedness therefore focuses on removing ambiguity before a crisis occurs. The company should maintain offline, signed copies of the following documents, in a format that can be physically presented to a bank if needed:

• a board resolution explicitly authorizing named individuals to execute transfers, open accounts, and manage banking relationships during emergency conditions,
• an up-to-date list of authorized signatories with specimen signatures,
• copies of identification documents for all authorized signatories,
• the company’s certificate of incorporation and current bylaws.

These documents should be stored in at least two physical locations, and at least one person in the company should know where they are and how to access them. If you have more than one banking relationship, verify that each bank has the current signatory documentation on file. Banks that have not received updated records for years may refuse instructions from newly appointed executives.

Accounting, invoicing, and financial records

Cloud-based accounting platforms and invoicing tools have become standard. They centralize financial records, automate reconciliation, and generate reports. They are also, in the context of a systemic disruption, a single point of failure for the company’s financial memory.

If the accounting platform is unavailable, the company may be unable to determine what invoices are outstanding, what expenses have been committed, what its tax position is, or what cash it expects to receive. This uncertainty compounds quickly: without a financial picture, the CFO cannot make allocation decisions, and the company risks either overspending scarce cash or failing to meet obligations it cannot see.

Prepared companies perform regular exports of their financial records: chart of accounts, general ledger, outstanding invoices (both receivable and payable), and recent bank reconciliations. These exports should be in non-proprietary formats (CSV, PDF, or standard accounting export files) and stored independently from the accounting platform.

For invoicing continuity, maintain a simple offline-capable invoice template with the company’s legal information, VAT number, and bank details. If the invoicing platform is down, the company should still be able to issue an invoice manually and send it by email or even by post.

Emergency liquidity

Even with multiple bank accounts, a severe disruption may strain cash reserves. Revenue collection slows or stops while expenses, especially payroll and hosting, continue. The gap between incoming and outgoing cash can become existential within weeks.

Emergency reserves lose much of their value if they are held in the wrong currency or within a jurisdiction that can freeze them. If the company's critical obligations (payroll, hosting, supplier payments) are denominated in euros, then the emergency reserve should be held in euros, in an account at a European bank that clears through European payment infrastructure. The principle is simple: emergency cash should be held in the currency in which it will be spent, at an institution whose payment rails do not transit through the jurisdiction most likely to cause the disruption you are preparing for.

Holding reserves in US dollars, or in an account that clears through US correspondent banks, reintroduces the very jurisdictional dependency that preparedness aims to mitigate. In a sanctions scenario, dollar-denominated assets can be frozen or delayed by US authorities regardless of where the company is incorporated or where the bank is located. This is not a political statement, it is a mechanical property of how dollar clearing works. The same logic applies in reverse for companies with obligations in other currencies. 

Emergency credit lines

Prepared companies consider establishing a pre-approved credit line or overdraft facility with at least one banking partner. The critical word is pre-approved: negotiating credit terms during a crisis is vastly harder than activating a facility that already exists. The credit line does not need to be large. It needs to cover the gap between the disruption and the resumption of revenue, typically four to eight weeks of critical operating expenses.

If a credit line is not feasible, maintaining a cash reserve explicitly earmarked for emergency operations serves the same purpose. The reserve should be held in the secondary bank account and governed by a clear policy: it is not general working capital, and it is not available for opportunistic spending. It exists to buy time.

Conclusion

Financial preparedness is not about predicting which disruption will occur. It is about ensuring that when any disruption occurs, the company retains the ability to pay, collect, and prove its authority to act.

A company that can still move money is a company that can still operate. A company that cannot, no matter how brilliant its recovery plan, is counting down to shutdown. Technical resilience without financial continuity is incomplete. The infrastructure may be recoverable. The team may be coordinated. The customers may be patient. But if payroll does not clear, if suppliers are not paid, and if the bank will not release funds, none of it matters.

Digital preparedness means treating financial infrastructure with the same rigor as technical infrastructure: mapping its dependencies, testing its failure modes, and building explicit paths to continue operating when the systems you rely on stop working.