Skip to content
Pylon Digital

Build · Quoted per job

Xero and Actionstep integrations, plus custom tools for professional firms

Pylon Digital builds Xero and Actionstep integrations, connects other practice-management, accounting and CRM systems, and builds small internal tools, so client and job data is entered once and reaches every system that needs it. It suits law, accounting and advisory firms whose systems do not talk to each other.

Illustration: systems connected, with exceptions sent to a person.

Is it right for you

Who it's for

Integrations suit 10–100 person firms running several systems that each hold part of the picture: matters or jobs in one, invoices in another, contacts in a CRM. Common triggers are a reconciliation error, a report nobody trusts, or staff typing the same client into three systems.

What integration options do Xero, MYOB, Actionstep, LEAP and Clio offer?

Each of these vendors offers an API, but access rules differ, and those rules shape the timeline and cost of an integration. The summary below reflects each vendor’s own documentation as at September 2026.

SystemHow third-party integrations connect
XeroA public API with tiered developer pricing, based on connections and data volume, since 2 March 2026. For a single organisation, Xero also offers Custom Connections for a monthly subscription. (Xero pricing, Custom Connections)
Xero Practice Manager (now part of Xero Partner Hub)A premium API: access needs a security assessment, repeated annually, and use-case approval from Xero. Custom Connections cannot be used with it. (Xero Developer)
MYOBAPIs for MYOB Business and AccountRight, with access through MYOB’s paid developer program. (MYOB Developer Centre)
ActionstepAPI access by request, with a sandbox for testing and an API review before production credentials are issued. (Actionstep documentation)
LEAPREST APIs through the LEAP Developer Console, with published apps listed in the LEAP App Marketplace. (LEAP)
ClioA documented API using OAuth 2.0, with a separate Australian data region (au.app.clio.com) and its own regional developer portal. (Clio Developer Documentation)

How do integrations support practice reporting?

Integrations are often the first step towards partner reporting that people trust. Once practice-management and accounting data line up, a weekly report can be built on top without anyone exporting spreadsheets.

That report is our automated practice reporting service. Our guide to automating WIP and utilisation reporting shows the steps, and Power BI vs Xero reporting for accounting firms compares the reporting options.

How it fits together

One record, every system

We map where each piece of client data lives, connect the systems that need it, and report any failed sync to a named person instead of letting it fail silently.

A diagram connecting practice-management, accounting, CRM and email systems through one connection layer, which keeps client records in sync and sends mismatches to a person.
Illustration: an integration map, where data is entered once and exceptions go to a person.

Deliverables

What you get

You get working connections and tools, documented so your firm knows exactly what data moves where.

  • An integration map

    A written list of which data moves between which systems, in which direction and how often, agreed before the build.

  • System connections

    Scheduled or event-driven links between your practice-management, accounting and CRM systems, built on each vendor's API.

  • Custom internal tools

    Small web tools for gaps your systems leave, such as a new-client form that writes to several systems at once.

  • Error alerts

    Failed syncs are reported to a named person with the record and the reason, instead of failing silently.

  • Vendor access

    We handle the API access requests and vendor reviews each connection needs, such as Actionstep's API review.

  • Handover documentation

    A plain-English guide to each connection and tool, what it touches and how to pause it.

Process

How it works

Every job starts by confirming what each vendor's API allows, so the quote reflects what is actually possible.

  1. Step 0145 minutes, free

    Discovery call

    We map your systems, where data is re-keyed today and what should flow automatically.

  2. Step 02Agreed in writing

    Scope and quote

    We check each vendor's API and access rules, then give you a written quote for the agreed scope.

  3. Step 03Timeline in your proposal

    Build and test

    We build against sandbox or test accounts where the vendor offers them, then test with your own data before go-live.

  4. Step 04Timeline in your proposal

    Go live and handover

    We switch the connection on, watch the first runs closely and hand over the documentation.

  5. Step 05Terms in your proposal

    Support

    We monitor connections and update them when a vendor changes its API or access rules.

Integrations

Systems we work with

We work with the systems professional firms rely on. Where a workflow needs AI to read documents or emails between systems, it sits under AI automation.

  • Xero
  • Xero Practice Manager
  • MYOB
  • Actionstep
  • LEAP
  • Clio
  • Microsoft 365
  • Power BI

Security & data residency

Where your data goes, and who can see it

Integrations move client, billing and contact data between systems, so each connection gets only the permissions it needs and every sync is logged. Internal tools we build store client data in fully GDPR-compliant data centres.

Narrow permissions
Each connection uses the narrowest scopes the vendor offers, and is read-only wherever the job allows.
Sync log
Every sync records what changed, in which system and when, so any record can be traced.
Where data is stored
Integration data we keep is stored in fully GDPR-compliant data centres. Our security and data residency page explains how we protect it.
Vendor terms
We build to each vendor's developer terms. Xero's, for example, prohibit using data from its APIs to train AI models.
Privacy
Each system's handover documentation records what personal information it holds, where it is kept and who can see it, so your firm can answer privacy questions from clients and regulators.
Read our security and data residency page

Pricing

Pricing guidance

Pricing model: Quoted

Quoted per job after scoping, with the price in writing before any work starts. The quote depends on how many systems we connect, how much data moves and whether a custom tool is included. Vendor charges for API access, such as a Xero Custom Connection subscription, are listed separately.

Illustrative example

Example: an accounting firm with a separate CRM

Talk through a similar build

Illustrative scenario: a 25-person accounting firm re-keys every new client from its CRM into Xero Practice Manager, and phone numbers and addresses soon differ between the two. With an integration, a client marked as signed in the CRM is created in Xero Practice Manager with the agreed fields, later contact changes flow across, and conflicts are flagged for the practice manager.

Commitments

What you can hold us to

These are the working rules behind every engagement, from the first discovery call to the monthly Run service. Ask us on the call how each one works for the system you have in mind.

  • Scope and price in writing first

    Every build is scoped and priced in writing before work starts, so there are no open-ended hours.

  • A person approves what agents send

    Our AI agents draft; a person at your firm approves what they send. The After-hours Receptionist answers live only from wording your firm approves in advance.

  • Every agent action logged

    Every action an agent takes is recorded in an audit log, so you can see exactly what it did.

  • GDPR-compliant data centres

    Client data in the systems we build and run is stored in fully GDPR-compliant data centres.

  • Accessible, fast websites

    Websites are designed and tested against WCAG 2.2 level AA and Google’s Core Web Vitals “good” thresholds.

  • Built and run under one roof

    A build can move straight onto a monthly Run service with us, so it is not handed over and forgotten.

Melbourne and Victoria

Areas we serve

We are based in Melbourne and work with businesses across Melbourne, Geelong and Victoria, on site by arrangement or remotely.

Questions

Frequently asked questions

Can you connect Xero Practice Manager to our other systems?

Yes, subject to Xero's approval. As at September 2026, Xero lists the Xero Practice Manager API as a premium feature: access needs a security assessment, repeated annually, and use-case approval, and Xero's developer pricing may apply. That adds time before a build can start, so we confirm the access route and any Xero charges for your firm before we quote.

Do you build Actionstep integrations?

Yes. Actionstep offers an API for custom integrations. Access starts with a request to Actionstep, which sets up a sandbox for development and testing, and each integration passes Actionstep's API review before production credentials are issued. We plan the build around that review, so your live system is connected only once Actionstep has approved it.

What if one of our systems has no API?

We look for the next most reliable option. Many systems offer scheduled exports, emailed reports or a vendor-supported connector that can be read automatically. Where none of these exist, we tell you in scoping rather than build something fragile, and suggest whether a small internal tool or a process change is the better investment.

What kind of custom tools do you build?

Small, focused internal tools that fill gaps between your systems. For example, a tool might be a new-client form that creates the record in several systems at once, a partner approval screen for write-offs, or a single search across matters, jobs and contacts. Each tool is documented at handover, so your firm knows what it does and where it runs.

How much does an integration cost?

Integrations are quoted per job after scoping, with the price in writing before any work starts. The price depends on how many systems we connect, the direction and volume of data, and whether a custom tool is included. Vendor charges for API access, such as a Xero Custom Connection subscription, are listed separately so you see the full cost before approving.

Who looks after an integration once it is live?

We can, and we recommend it. Vendors change their APIs and access rules: Xero, for example, is replacing broad API scopes with granular scopes, and broad scopes remain available only until September 2027. Unmonitored integrations eventually break. We watch each connection, fix failures and make updates. Your proposal sets out how ongoing support is charged.

Secure by design. Set up correctly. Fully managed.

Talk to us before you commit to anything

Start with a free 45-minute discovery call. We look at your systems and priorities, then recommend a first step with a fixed scope, or tell you if we are not the right fit.

Book a free 45-minute discovery call

Keep exploring