Systems we've worked with

We're not tied to any vendor. If a system has an API, a database or even just an export, we can connect it. Here are some of the systems we've integrated for New Zealand businesses.

Accounting and ERP

Ledgers, invoices, bills and payments, including write-backs such as planned payment dates.

  • Xero
  • NetSuite

Inventory and warehousing

Stock levels, orders, purchasing and warehouse movements.

  • Cin7
  • Consignly

Freight, logistics and ports

Consignments, tracking, freight costs and container information.

  • Mainfreight
  • DHL
  • 360 Logistics
  • PortConnect

Agriculture

Farm financials, farm management and dairy supply data.

  • Figured
  • Farm Focus
  • Farm Source

Payroll and rostering

Pay runs, payroll journals, leave, rosters and timesheets.

  • Employment Hero
  • When I Work

Jobs, projects and CRM

Quotes, jobs, time and costs, customers and the sales pipeline.

  • Simpro
  • WorkflowMax
  • HubSpot

Government and public registers

Tax, company and ownership records, business numbers, security interests and property data.

  • Inland Revenue (IRD)
  • Companies Office
  • NZBN (MBIE)
  • PPSR (MBIE)
  • LINZ

Proprietary and in-house systems

Vendor-specific APIs, in-house databases and older systems that only offer file exports.

  • Proprietary APIs
  • In-house databases
  • File and email exports

Product names are trademarks of their owners. Listing a system shows we've integrated with it, not a partnership or endorsement.

Connecting is the start. Insight is the point.

Once your operational and financial data is joined up, it can answer the questions that matter: where cash is tied up, which customers and products make money, which assets are sitting idle, and where work gets held up between quote, order, invoice and payment.

See insight and reporting

How we connect systems

The connector is the easy part. What makes an integration run for years is the design around it. More on integration and automation.

  1. Map how data moves

    Who exports what, who re-keys it where, and which spreadsheet holds it all together. The map shows which link to fix first.

  2. Agree who owns what

    Each field gets one source of truth, with a rule for what happens when two systems disagree.

  3. Build it to last

    Retries, safe re-runs, a log of every outcome and alerts that reach a person, running in your own accounts.

Using something that isn't listed? Ask us.

Tell us about the report nobody trusts or the process that eats a day a week. We'll tell you straight whether we can help, and what it would take.