Most small businesses in the UK run on more than one piece of software: the accounting package, a spreadsheet for jobs or orders, email, and perhaps a booking or invoicing app added later. Each one works. None of them speak to each other, and that gap is where things go wrong.
This article sets out what breaks, in plain terms, so you can see whether the friction your business feels has a name.
Key PointDisconnected systems rarely announce themselves. They show up as time nobody budgeted for and numbers nobody quite trusts.
The double-entry problem
When two systems do not share data, someone enters the same information twice. An order goes into one system and someone types it into the accounts. A customer record is updated in one place and stays out of date everywhere else.
Every re-keying step is a chance of a mistake, and it costs time that produces no value. For VAT records it can also be a compliance issue: HMRC's VAT Notice 700/22 says it does not consider copy and paste to be a digital link between software.
Decisions made on yesterday's numbers
When systems are disconnected, a report is only as current as the last manual export. Figures pulled on Monday morning are already days old by Wednesday afternoon.
Where cash flow matters, and for most small businesses it does, that lag means decisions made on a picture of the business that no longer exists.
The version problem
A spreadsheet exported from one system and imported into another becomes a separate copy the moment it leaves. Within days there are two versions of the same data, and nobody is sure which is current.
This is not a discipline problem. It is a structural one, and it keeps happening until the systems are connected. Where the data is about people, it matters legally too: the ICO's accuracy principle requires personal data to be accurate and, where necessary, kept up to date.
Watch OutIf VAT figures move between systems by copy and paste, check them against HMRC's digital links rules.
The staff time that disappears into the gap
Some tasks exist only because systems do not connect:
- downloading a report from one system and uploading it to another;
- chasing a colleague for a figure that should be visible in the software;
- cross-referencing two spreadsheets to find a discrepancy;
- reconciling an invoice in the accounts against an order in the job system.
Each is short on its own. Together they can take a real share of someone's week, which is time not spent on the business itself.
What integration actually fixes
When systems share data directly, a record entered once appears everywhere it needs to. An order raised in the CRM updates the accounts, and a contact updated in one place is current in every system.
A good connection also expects failure. Microsoft's guidance on the retry pattern describes how an application can handle short-lived faults rather than losing the data. Our article on API-first integration explains how we build connections.
How to measure how bad it is
Before deciding whether to fix this, measure what it costs. Three measurements need no consultant:
- Count the re-keys. For one normal week, note every time someone types information that already exists in another system.
- Time the reconciliation. How long does it take each week or month to establish what is true? Include the checking, not just the correcting.
- Count the escapes. Over the last quarter, how often did something reach a customer wrong because two systems disagreed?
Those three numbers are the honest size of the problem. If they are small, you do not have an integration problem, and nobody should sell you one.
Pro TipRun the three counts for one normal week before you talk to anyone about integration. The numbers will tell you whether you need it.
Why it gets worse rather than levelling off
Manual reconciliation grows with volume. Twice the orders means roughly twice the checking, and more chances for two systems to drift apart before anyone notices.
It also gets more expensive to fix. Every month on disconnected systems adds history that will one day need reconciling or migrating. Our article on what an integration actually costs covers the budget side.
Is integration right for your business?
It is worth considering when at least one of these is true:
- staff regularly enter the same information in more than one place;
- reports are routinely late because data has to be exported or compiled by hand;
- you are not confident that the numbers in different systems match;
- a data entry mistake has cost the business money or a customer.
The fix is not always integration. Sometimes it is dropping a system, or agreeing which one is authoritative. Our guide to choosing a systems integration company helps if you do go ahead.
If you recognise these problems, see our integration service and business systems work, or get in touch.