Xero & MYOB Integration Repair

When an integration breaks, duplicates or quietly drops records

Repairing a broken Xero or MYOB integration

It Worked Until Something Changed

Most integrations between Xero or MYOB and the rest of the business are fine until something changes: an API permission, an app's pricing or plan, a new tax code, more transactions, or the person who built it moving on. Then records go missing or arrive twice, and someone starts fixing it by hand.

We diagnose what is actually wrong, fix it or rebuild it properly, clean up the records it missed, and make sure the next failure is noticed the same day. We have built and supported live business integrations for years, including a forestry export platform running since 2012. Looking for a new integration instead? See Xero API integration and MYOB API integration.

Signs Your Integration Needs Repair

If any of these sound familiar, it's worth a look.

  • An integration stopped after an MYOB or Xero change and nobody knows why
  • Invoices, bills or payments arrive twice, or not at all
  • Sync errors that someone clears by hand every week
  • Tracking categories, tax codes or accounts mapped wrongly
  • A Zapier, Make or n8n workflow nobody maintains any more
  • The person who built it has left
  • A connector app has become expensive for what it does

Why Integrations Break

Knowing the cause decides whether to repair, rebuild or replace.

API permission changes

MYOB has retired the broad "CompanyFile" API permission many older integrations used. Integrations need re-authorising with newer, narrower permissions, and some need code changes.

App and pricing changes

Xero introduced tiered pricing for app developers in March 2026. Connector apps change plans, limits and features, and integrations built on them change with them.

Mapping drift

New accounts, tax codes, tracking categories or item codes are added on one side and never mapped on the other, so records fail or land in the wrong place.

Fragile automations

Workflows built quickly in Zapier, Make or n8n often have no error handling, so one failed step silently drops data.

Volume and limits

What worked at 50 transactions a day fails at 500, when API rate limits, timeouts and batch sizes start to bite.

No owner

The integration works until something changes, and by then nobody remembers how it was built or where it runs.

How We Fix It

1

Diagnose

We work out what the integration does, where it runs, what is failing and why, and what records have been missed or duplicated along the way.

2

Recommend

Repair, rebuild or replace with a supported app: you get each option with its trade-offs and a fixed quote, not a push towards the biggest job.

3

Fix and clean up

We fix or rebuild the integration and correct the duplicated or missing records, so Xero or MYOB reconciles again.

4

Make it robust

We add logging, sensible retries and alerts to a named person, so a failure is noticed the same day rather than at month-end.

5

Document and hand over

You get plain-English documentation of what connects to what and how it runs, with ongoing support if you want it.

Integration Repair FAQs

Usually, yes. We start by working out what the integration does, where it runs and why it is failing, using its logs, the systems it connects and any code or automation we can access. If the original developer is still around that helps, but it is not essential.

It may be. MYOB has retired the broad "CompanyFile" API permission that many older integrations relied on. Integrations that have not moved to MYOB’s newer, narrower permissions need to be re-authorised, and some need code changes. We check which permissions your integration uses and what it needs to work again.

Xero introduced tiered pricing for app developers in March 2026, and some connector apps are passing costs on to customers. Sometimes staying with the app is still the cheapest option. Sometimes an integration built just for your business is better value over a few years. We look at what you use the app for and tell you honestly which way to go.

If a well-supported app does what you need, yes, and we will tell you so. Custom work makes sense when your process, data or combination of systems is unusual enough that apps keep breaking or need constant manual fixing.

Rebuilt integrations log every run, retry sensibly when an API is briefly unavailable, and alert a named person when something genuinely fails, instead of silently dropping records. We document how it works so you are not dependent on one person.

It depends on what is broken and how it was built. We diagnose first, then give you a fixed quote for the repair or rebuild. The first conversation is a free initial chat.

What's Broken?

Tell us what the integration connects and what it is doing wrong. We'll tell you whether it is a quick repair, a rebuild, or a case for a supported app instead.

Choosing new software? We'll check the vendor's integration and data claims against your systems before you sign. What to ask

Free initial chat. No sales pressure - if we're not the right fit, we'll say so.

Prefer to talk? Call 1300 470 091

Got a spec or files? Email [email protected]

Name, email and message are required. We'll respond within 24 hours.