Skip to content
Cross-Hub HubThought Leadership

What Happens When Your Accountant, HR, and IT Don't Talk to Each Other

Here's something we've been thinking about a lot lately. It's one of those topics that comes up in almost every conversation we have with business owners — but.

By Andrew Northcott·3 April 2026·5 min read·Last reviewed 8 July 2026

The short answer

When your accountant, HR and IT operate in isolation, work falls through the gaps between them: a new hire is set up in payroll but not in systems, a departing staffer keeps access they should lose, and the same information gets re-entered and mismatched across functions. This coordination tax shows up as errors, compliance risk and wasted time. The fix is shared information and joined-up processes so finance, people and operations run as one connected back office rather than three disconnected silos.

Most growing businesses assemble their back office one supplier at a time — an accountant here, an IT provider there, an HR advisor or bookkeeper somewhere else. Each is competent in their lane. The trouble is that the interesting problems in a business almost never sit neatly inside one lane, and when your advisors don't talk to each other, the gaps between them quietly become your problem.

The work that falls between the desks

Consider onboarding a new employee. HR handles the contract and the award classification. IT sets up the laptop, the email account and system access. Finance adds them to payroll and sorts superannuation. On paper, three tidy jobs. In practice, this is a single workflow that hands off between three parties who each assume someone else is watching the seams.

So the contract gets signed but IT isn't told the start date, and the new starter sits for two days without a login. Or payroll is set up but nobody flags that the role should have been classified under a different award, and you've underpaid from day one. Nobody did anything wrong inside their own scope. The failure lives in the coordination — which is precisely the thing no single supplier is being paid to own.

What the disconnection actually costs

The cost rarely shows up as a line item, which is why it's easy to miss. It shows up as:

  • Rework and double handling — the same information re-entered into three systems, each slightly differently, so none of them agree.
  • Compliance exposure — an offboarded employee whose system access was never revoked because IT didn't hear they'd left; a payroll error that surfaces months later; a tax position your accountant would have flagged had they known about a decision made elsewhere.
  • Slow decisions — you become the human router, forwarding emails between advisors and translating one discipline's answer into another's question.
  • Contradictory advice — your accountant optimises for tax, your HR advisor for compliance, your IT provider for security, and no one is optimising for the business as a whole.

That last point is the quiet one. Each specialist gives you a locally correct answer. Nobody is responsible for whether those answers add up to a coherent whole.

Why you become the integration layer

When suppliers don't connect, the connective tissue defaults to the owner. You hold the context that lives in nobody else's head — that the new hire is really a contractor-to-permanent, that the office move affects both the lease and the network, that a customer dispute has tax, legal and reputational threads. You end up spending your scarcest resource, attention, on stitching other people's work together. This is a classic form of founder dependency: the business can't run a routine process without you sitting in the middle of it.

Closing the gaps without hiring an army

You don't need to bring everything in-house. You need the handoffs to be deliberate rather than accidental.

  • Map the cross-functional workflows. Onboarding, offboarding, a new client, an office move, a system change. For each, write down every party involved and every handoff between them. The gaps become obvious once they're on paper.
  • Assign an owner to each end-to-end process, not just to each task. Someone should be accountable for the whole of onboarding, with authority to chase the parts that live with external suppliers.
  • Give your advisors shared context. A single source of truth — even a simple shared document or system they can all see — beats you relaying information by email. When your accountant, HR advisor and IT provider can see the same picture, they stop working blind.
  • Put the handoffs in a checklist. The point of a checklist is precisely to catch the step that everyone assumed someone else would do.

The case for a joined-up back office

The alternative to endless coordination isn't necessarily one supplier who does everything. It's treating the back office as a single connected system rather than a collection of parts — one where information flows between finance, people and operations without you carrying it. That's the idea behind a connected back office: the specialists can stay specialists, but the seams between them are owned and designed, not left to chance.

You'll know you have the balance right when a new employee starts and everything — contract, laptop, payroll, super, access — simply happens, without you sending a single email to make it so.

About the author

Andrew Northcott

Founder & Chairman, Valont

Andrew is the founder and chairman of Valont and the parent group Wattlestone. He has spent two decades building and running Australian SMEs, and writes about the realities of ownership — cash, people, systems, and the decisions that compound.

LinkedIn →

Want to know where your business stands?

Take our free Business Health Check — it takes 5 minutes and gives you a clear picture across finance, people, operations, and growth.