A client signs up, agrees the fee, and then stops at the stage where he has to connect his bank. He does not reply for two weeks. When he does, he says he has been busy.
He has not been busy. He has been worrying about giving a stranger access to his money and does not want to say so out loud.
What the client is actually afraid of
Not bookkeeping. That somebody he met twice can move money out of his account, that his personal spending will be visible, and that if something goes wrong he will have authorised it himself.
Why it goes unspoken
Saying it feels like an accusation. Clients express it as being busy, as needing to check with somebody, or as a question about software. The real worry never surfaces.
Answer it before it is asked
A short, plain paragraph explaining exactly what a bank feed does. It costs a few lines and it removes the most common cause of stalled onboarding.
Explain that a feed is read only
Transaction information flows out, nothing flows in. No ability to initiate a payment, move money or change anything. This single sentence resolves most of the hesitation.
Explain what you can see
Which accounts, which transactions and over what period. Clients worry about personal accounts being visible and should hear the boundary stated.
Explain what payment authority would require
That making payments is an entirely separate arrangement, requiring separate authorisation, and that standard bookkeeping does not involve it. Naming the thing they fear and ruling it out works far better than avoiding it.
Explain how the connection is made
Through the bank's own authorisation process, with the client entering their own credentials at their bank rather than sharing them. Clients frequently assume they must hand over a password.
Say plainly never to share credentials
With you or anybody. A bookkeeper who says this proactively is demonstrating exactly the professionalism the client is trying to assess.
Explain how access is revoked
By the client, at any time, through their own banking. Knowing they hold the switch is what allows somebody to turn it on.
Explain the alternatives
Statement uploads or exports where a client will not connect a feed. It is more work and it is better than losing the client, and offering it demonstrates that you are not insisting.
Explain who else can see it
Which of your staff, whether any subcontractor is involved and how your own systems are protected. The question behind the question is about your practice, not the software.
Explain the mixed account problem
Where personal and business spending share an account, what you will see and how it is handled discreetly. This is often the real reason for hesitation.
Publish your security practices
How data is stored, who has access and what happens if a client leaves, which is the reassurance in security questions from clients worried about a breach.
Handle it at onboarding, in writing
Alongside the software conversation, as in software and handover questions when switching bookkeepers and the comparison in monthly fee questions from businesses comparing bookkeepers.
Getting started
Publish exactly what a feed does and does not allow, build the page with the AI FAQ generator, then answer access questions at any hour, which is the approach in how financial advisors use chatbots to answer client questions. SpideyChat for accountants and bookkeepers answers from your published pages, plans are on the pricing page, and the chatbot ROI calculator works through the numbers.