How to Open a Business Bank Account: A Practical UK Checklist
Practical planning guide
This is a practical guide to opening a first business account for sole traders and small limited-company directors who want clear business records.
Quick summary
Start with the real work already happening, make a decision from evidence, and set a date to review whether the approach is helping.
- Define the decision before comparing options.
- Use a typical working example rather than an ideal case.
- Keep ownership and the next review visible.
Before you start
Set aside a short working session with the records, calendar entries and people who understand the day-to-day process. The aim is a useful decision, not a perfect document.
- Write the problem in one sentence.
- Collect one normal cycle of examples.
- Decide who owns the next action.
Step-by-step instructions
Confirm the business details a provider will ask for
Gather your company number or trading name, registered address, identification, ownership details and a clear description of the business. Match the information to your formal records before applying.
Map normal money movements
List incoming payments, regular bills, staff reimbursements, cash deposits, international transfers and cards. A low monthly fee is less useful when transaction charges dominate a normal month.
Compare features against your working routine
Check invoice links, payment approvals, accounting integrations, card controls and customer support. Keep the comparison short and select features that remove a real admin problem.
Apply with one prepared set of information
Use consistent names, addresses and trading descriptions. Save each confirmation and respond promptly if the provider requests additional evidence.
Create separation rules as soon as the account opens
Route business income into the account, pay business expenses from it, and label owner draws or salary transfers. Consistency makes later records understandable.
Schedule a weekly reconciliation
Match transactions to receipts and invoices, flag unclear items and maintain any tax reserve. A short weekly review is easier than repairing a whole quarter later.
Decision table
| Check | Question to answer | Evidence to keep |
|---|---|---|
| 01 | the account supports your legal structure | Record a short answer using a normal working example. |
| 02 | the payment and card costs you will actually use | Record a short answer using a normal working example. |
| 03 | how it connects to bookkeeping | Record a short answer using a normal working example. |
Common issues and how to avoid them
Starting with a generic answer
Keep the focus on the account supports your legal structure. Use a small documented check and revisit it after real use instead of building a one-off process.
Choosing a headline feature
Keep the focus on the payment and card costs you will actually use. Use a small documented check and revisit it after real use instead of building a one-off process.
Skipping the review date
Keep the focus on how it connects to bookkeeping. Use a small documented check and revisit it after real use instead of building a one-off process.
Advanced tips
- Keep the supporting note short enough that another person can follow it.
- Use recurring questions as signals that one part of the process needs clearer language.
- Change one constraint at a time so you can see what made a difference.
Final checklist
- The decision is recorded in plain language.
- The process has an owner and a review date.
- Any exception route is clear before it is needed.
Frequently asked questions
How detailed should this process be?
Only detailed enough for a person who did not create it to follow the next action without guessing.
When should it be reviewed?
Review after one normal cycle, then at a sensible recurring interval or when the underlying work changes.
What evidence matters most?
Use the records, costs, timing and outcomes that are actually connected to the decision rather than a generic score.
