Systems integration

The problem it solves

Most businesses run several systems that hold the same facts in different shapes. Operations live in one tool, invoicing in another, and someone retypes one into the other. The figures drift apart, the spreadsheet in the middle quietly becomes a system, and every report starts with an export.

An integration takes the record where it's created and delivers it to the system that needs it, checked and in the right form. One version of each figure, entered once.

Typical connections

• A CRM or job system to the ledger

  Quotes, jobs or orders raised in the tool your team uses, turned into contacts and invoices in Xero or QuickBooks Online without a CSV in between.

• Airtable or a spreadsheet to Xero

  Records kept in a base or a workbook posted into the ledger as contacts and invoices, so nothing is typed twice.

• Payment platforms to the ledger

  Payouts, fees and refunds landing in Xero or QuickBooks the way your accountant wants them.

• Practice tools to client files

  For accounting practices: practice management, document collection and the client's ledger kept in step.

If a system has an API, it's usually in scope. If it doesn't, we'll tell you what the workaround costs before you commit to it.

How we approach it

Your clients trust you with their books. These rules are how that trust carries through to anything we build.

• Read-only first

  An integration proves itself reading data before it's allowed to write anything to a ledger.

• Your accounts, your keys

  Connections run under accounts your firm owns, so you can revoke access in one step from inside Xero or QuickBooks.

• Only the data the job needs

  We take the fields a workflow uses and nothing else, and don't keep copies we have no reason to hold.

• A person signs off

  Anything that changes a client's numbers can be set to wait for a named person to approve it.

• Failures get noticed

  Every build alerts on a failed or stuck run, so a problem reaches us before it reaches your client.

• You own what's built

  The workflows, the code and the documentation are yours. If we stop working together, it keeps running.

Who delivers it

For firms and businesses in the UK, the US and Canada, the front door is 1-Dash. In South Africa it's Qelo Systems. Either way the work is scoped in writing, built against a sandbox first, and handed over with a runbook your team can follow.