AWLabs
Home / Services / Integration

Xero and MYOB Integrations That Your Bookkeeper Can Actually Reconcile

We build custom integrations between Xero or MYOB and the rest of your business: CRMs, job management, ecommerce, payroll, inventory and your own platforms. Invoices, payments and contacts flow automatically, with GST, tracking categories and failures handled properly.

What does a custom Xero or MYOB integration involve?

A custom Xero or MYOB integration is software that connects an accounting file to another system through the vendor's API, so that invoices, bills, payments, contacts and items move between them automatically, with the accounting rules, error handling and audit trail that a bookkeeper and an auditor need.

Most businesses reach for an app first, and they should. The Xero App Store and the MYOB App Marketplace list a wide range of ready made connectors, and for a common pairing, such as a popular ecommerce platform or payroll product, an existing app is usually the cheapest and quickest answer. A custom integration earns its place when the app does not exist, when it does not support the way you work, or when it gets the accounting wrong: the wrong GST code on mixed supplies, sales landing in one lump account instead of by tracking category, duplicate contacts, or a sync that silently stops and is only noticed at BAS time.

The commonest requests we see are connecting Xero or MYOB to a CRM so a won deal becomes an invoice; to job management software such as ServiceM8 or simPRO where the standard sync does not fit; to a custom portal or SaaS product so customers are invoiced automatically; to inventory and purchasing systems; and to several entities at once for consolidated reporting. The design question that matters most is direction. A one way push, where your system creates invoices in Xero, is far simpler and safer than a two way sync where both systems can change the same record, because a two way sync needs rules for which side wins, how deletions and voids are handled, and how to stop records bouncing back and forth.

Each platform sets limits that shape the design. At the time of writing (November 2026), Xero's developer pricing page lists a Starter plan of up to 5 connections at no charge with an API limit of 1,000 calls per day per organisation, and paid plans from $35 AUD a month (Core, up to 50 connections) to $1,445 AUD a month (Advanced, up to 10,000 connections), each with 5,000 calls per day per organisation and a monthly data allowance, with higher tiers requiring app certification and a security assessment. A private integration for one business usually fits comfortably in the Starter limits if it is designed to batch and cache; a product that many businesses will connect needs the plan and certification costs in its business case. MYOB's Business API serves both MYOB Business and AccountRight files, with separate APIs for MYOB Acumatica and EXO, and an AccountRight file stored locally is reached differently from one in the cloud.

The accounting has to be right, not just the data transfer. That means mapping each product or service to the correct account, tax rate and tracking category; handling GST for businesses registered for it (the ATO requires registration once GST turnover reaches $75,000, or $150,000 for non profits); rounding the way the accounting file expects; and dealing with multiple currencies and entities where they apply. We agree the mapping with your accountant or bookkeeper before we write code, and every sync writes a log they can read. Senior engineers lead every build and review every change, and you receive updates every Tuesday and Friday, Sydney time.

AWLabs is a Sydney based AI and software development company for growing businesses and enterprise. Sister company to All Webbed Up, a separate websites and marketing company.

Senior engineers lead every build and review every change
Your code and IP assigned to you on payment
Comprehensive documentation included
Care Plan support after launch
Australian company, Sydney business hours
Security built to fit your risk

Why have engineers build your accounting integration?

Right Direction, Right Rules

We decide with you which system owns each record. One way pushes where possible, two way sync only where it is genuinely needed, with explicit rules for conflicts, voids, credit notes and deletions, so nothing is overwritten by surprise.

Accounting Your Bookkeeper Signs Off

Accounts, tax rates, tracking categories, items and rounding are mapped with your accountant before build. Invoices land coded the way they would be entered by hand, so reconciliation and BAS preparation get easier, not harder.

Failures That Get Noticed

Expired connections, rejected invoices, locked periods and API limits are caught, retried where safe and reported to a named person straight away. A sync that stops quietly for three weeks is the most expensive kind of integration bug.

Reconciliation Reports

A daily or weekly report compares totals in both systems and lists anything that did not match, with a link to the record. Your bookkeeper sees the gap before month end instead of hunting for it.

Designed Around API Limits

Batching, caching, webhooks and queueing keep the integration well inside Xero and MYOB limits, including during busy periods and the first bulk import, so a sales spike does not stall your invoicing.

Secure Access to Financial Data

OAuth connections with the narrowest scopes the job needs, tokens stored encrypted, no shared logins, and a clear record of who connected which file. Financial data is hosted in Australian cloud regions where your Schedule of Work requires it.

Which APIs and tools do we build Xero and MYOB integrations with?

Xero Accounting APIXero webhooksMYOB Business APIMYOB AccountRight APIMYOB Acumatica APIOAuth 2.0Node.js / TypeScriptPythonPostgreSQLQueues and scheduled jobsn8nAWS / AzureServiceM8 APIsimPRO APIShopify APIHubSpot and GoHighLevel APIs

How do we deliver an accounting integration?

Typical timings; your Schedule of Work sets the real ones.

01
Week 1

Map the Money Flow

We trace how a sale, purchase or payment moves through your business today, who enters what, and where errors creep in. We check whether an existing app already does the job before recommending a build.

02
Weeks 1 to 2

Agree the Accounting Mapping

With your accountant or bookkeeper we agree accounts, tax rates, tracking categories, items, contacts and the rules for credit notes, refunds and voids. This mapping becomes the specification the code is tested against.

03
Weeks 2 to 5

Build Against a Demo File

We build and test against a Xero demo company or a copy of your MYOB file, never your live books, covering normal transactions, edge cases, failures and limits. You review sample invoices exactly as they will appear.

04
Weeks 5 to 6

Historical Data and Cutover

We decide with you whether to backfill history or start from a clean date, match existing contacts to avoid duplicates, and pick a cutover point that suits your reporting periods.

05
Week 6 onwards

Go Live With Monitoring

The integration goes live with alerts, retry handling and reconciliation reports switched on, and we watch the first full month end closely with your bookkeeper.

06
Ongoing

Care Plan

Vendors change their APIs, plans and limits. After the 30 day warranty, a Care Plan keeps the integration current, renews certifications where your plan needs them, and handles new account or tax mappings as your business changes.

Which businesses need a custom Xero or MYOB integration?

Trades & ConstructionRetail & EcommerceManufacturing & WholesaleAccounting & Bookkeeping FirmsProfessional ServicesSaaS & Software ProductsNot for ProfitsProperty & Real Estate

Do you need a custom integration, or will an app do?

When it is the right fit

  • No app connects your system to Xero or MYOB, or the app codes transactions wrongly
  • Staff retype invoices, bills or payments between systems every week
  • You need tracking categories, several entities or multiple currencies handled automatically
  • Your own software product needs to invoice customers through their own or your Xero file
  • You want reconciliation reports and alerts instead of finding sync problems at BAS time

When it is not the right fit

  • A well reviewed app already does exactly what you need at a modest monthly fee
  • You have a few dozen transactions a month, where manual entry costs less than any build
  • Your chart of accounts and coding rules are still in flux; settle those with your accountant first
  • You are about to change accounting platform, in which case integrate after the move
  • You want the integration to make tax decisions, which belong with your accountant

Xero and MYOB Integration: a quick glossary

Accounting Integration
Software that moves transactions and records between an accounting file, such as Xero or MYOB, and another system through the vendor's API, applying the agreed accounting rules.
One Way Push
An integration where one system creates or updates records in the other, but not the reverse. Simpler and safer than a two way sync.
Two Way Sync
An integration where both systems can change the same records and keep each other up to date. It needs explicit rules for conflicts and deletions.
Tracking Category
A Xero feature for tagging transactions by department, location, job or other dimension, so reports can be split without extra accounts.
Reconciliation Report
A scheduled comparison of totals and records between the two systems that lists anything that does not match, so errors are found early.

Common questions about Xero and MYOB integrations

Where these facts come from

  1. Xero Developer pricing and policies, Xero
  2. MYOB Business API: getting started, MYOB
  3. Registering for GST, Australian Taxation Office
Start with a conversation

Tell us what you need built.
We'll tell you straight if we're the right fit.

Book a call, and we'll show you how we would approach it.

Start with a short Development Consult
Audit fee credited to your build
Response within 1 business day
Mutual NDA sent before you share your idea