Mistakes that surface in the first unusual hour at a branchless bank

Almost nothing goes wrong with a branchless account on an ordinary day. It goes wrong during the move onto it, and during the first hour of an unusual event, when it turns out that the thing everybody assumed would work has never been tried.

Nine failures account for most of the damage. They are all avoidable, none of them require special knowledge, and every one of them is cheaper to prevent than to fix. The order below roughly follows the order in which they happen.

What to take away

One: closing the old account too early

The new account works, so the old one looks redundant. Then a customer pays into it, a standing payment fails, or a refund needs to go back where it came from.

Run both for at least one full cycle, and preferably through a payroll run and a tax payment. Close the old account only once a month has passed with nothing arriving in it. The cost of keeping it open is small and known; the cost of closing it early is unknown and lands at the worst moment.

Two: repointing payers all at once, then hoping

Telling customers and platforms about new details is not one task, it is a campaign with a long tail. Some will keep using the old details for months, and a few will never change until an invoice bounces.

Make a list of everyone who sends you money, work through it in order of size, confirm each change individually, and keep watching the old account for arrivals. Anything still landing there after your parallel period is a customer who has not actually updated their records.

Three: treating the provider's app as your records

Statements, exports and receipts kept only inside one provider's interface are records you do not control. Access can be interrupted for reasons that have nothing to do with you.

Export monthly into your own storage, in a format your bookkeeping accepts. If the export is poor, that is a finding about the provider rather than a chore, and it is worth knowing before it matters. The recurring cost of a bad export is covered in where the cost of a branchless account really lands.

Four: one person and one phone

Access secured to a single device held by a single person is the most common structural weakness in small business banking. The phone gets lost, the person goes on holiday, someone leaves without handing over.

Bind access to at least two people or two devices, record how account recovery works, and test the recovery path once while you do not need it. Do the same for any email address that access depends on, since that is often the real key to the account.

Five: never asking who holds the money

Some providers are banks. Some are payment firms holding funds at a bank on your behalf. Some products are not deposits at all. The differences matter most on the day something goes wrong.

Ask which institution holds the balance and whether it is a deposit. Keep the answer with your account record.

Deposit insurance covers insured banks and insured credit unions, with limits and conditions depending on titling. They are published as deposit insurance rules by the FDIC and share insurance material by the NCUA, and an intermediary's summary is not the rule.

Six: assuming cash can be handled

Cash is the capability most often assumed and least often checked. By the time you find out, you are already taking money you cannot easily bank.

Establish before opening where a deposit can physically be made, what it costs, who charges it, and how coin is treated. If any part of your business takes notes, this belongs at the top of the selection criteria rather than in a footnote.

Seven: not testing a payment before it matters

The first payroll run should not be the first time you have sent money in bulk. Nor should the first large supplier payment be the first time the provider sees an amount out of pattern, because a review can hold funds while you explain.

Send a small test of every payment type you will rely on, record how long each took end to end, and tell the provider in advance about a payment that will look unusual. Timings vary by route and by institution, and yours are the only ones that count.

Eight: discovering the support model during an emergency

Support quality is invisible while everything works. Then a payment is missing and the difference between providers is enormous.

Before you commit, check what channels exist, their hours, and whether anyone can escalate a stuck payment.

In month one, ask one real question and time the reply; that answer becomes evidence, not hope. What happens in an application review, and what to have ready, is in how applications are assessed.

Nine: running with one banking relationship

A single relationship means an outage, a review or an account closure stops the business completely. That is a bigger exposure than any fee difference you are optimizing.

Keep a second account somewhere structurally different, with enough in it and enough set up to run payroll and pay critical suppliers for a short period. Refresh the details occasionally so it works when needed.

What that costs, set against what a single blocked day would cost you, is arithmetic worth doing once. The formulas are in pricing redundancy against an outage.

The migration order that avoids most of this

Common questions

How long should the parallel period be?

At least one full statement cycle, and longer if your billing runs quarterly or your customers pay slowly. The cost of a second month of parallel running is trivial next to one lost payment.

Is it worth moving at all if the current account works?

Only for a structural reason: capability you need, permissions you cannot get, cost that is provably higher on your own numbers, or a relationship that has become unreliable. Moving to save a small monthly amount rarely survives the switching cost once the hours are counted.

What should I do if funds are held during a review?

Ask in writing what is required and by when, provide it precisely, and keep a record of every exchange. Meanwhile run critical payments through your second relationship, which is the reason it exists. Reviews are a normal part of how institutions operate, and the practical protection is preparation rather than argument.

Which mistake is the most expensive?

Running with one relationship, because it turns any single problem into a full stop. Everything else on this list costs money or time. That one can cost you the ability to trade for a period, which is why the redundancy question sits at the center of banking without a branch.