Menu

INTEGRATION · MYOB

MYOB integrations that handle the cases the connectors miss.

MYOB AccountRight and MYOB Business are workhorse accounting systems for Australian SMBs. The off-the-shelf connectors handle simple cases. When your operations include refunds, gift cards, multi-channel sales, or anything beyond the basics, you need integration built for the way your business actually works.
Myob Integration Services Banner

MYOB connected to WooCommerce, Shopify, Zenoti, custom POS, and operational systems. Real-time sales sync, full reconciliation, audit-ready.

The case for proper MYOB integration

MYOB has been the default accounting system for a generation of Australian businesses, particularly mid-market SMBs that have been operating since before Xero became dominant. If you are on MYOB, you are probably on it for good reasons (compliance requirements, payroll handling, established workflows, accountant familiarity) and you are not looking to migrate. That is the right call. Switching accounting systems mid-flight is one of the most disruptive things a business can do to itself.

What MYOB needs to do well is be the system of record for your finances. What it does not need to do (and what causes most of the integration pain) is be the source of truth for your sales, your inventory, or your operational data. Those sit in other systems, and the integration between them and MYOB is where the work happens. The MYOB API is the right way to do that integration; the bookkeeper manually re-keying figures from Shopify reports into MYOB is not.

The MYOB add-on marketplace has connectors for common platforms, but the same pattern applies as with Xero: the connectors handle the happy path, but break on refunds, gift cards, multi-channel reconciliation, and anything outside the most common transaction types. Bookkeepers maintain manual adjustment spreadsheets to fix the variance. The variance is small in any individual month. The cost of fixing it adds up to a part-time bookkeeping role across the year.

Proper MYOB integration removes that manual work. Every sale, every refund, every payment, every credit note flows into MYOB with correct accounting treatment, correct GST, and correct categorisation. The bookkeeper stops finding mystery variances and starts doing actual advisory work.

The honest moment most agencies skip: most MYOB stacks do not need custom middleware. If you are under $1M in revenue with a single sales channel, the off-the-shelf MYOB add-on is genuinely the right answer. We will tell you that directly. About one in four MYOB discoveries we run ends with our recommendation to stick with the existing add-on and fix the chart of accounts setup instead. The discovery cost is the audit deliverable. The answer “you do not need us” is just as valid as “you do.”

If your MYOB month-end requires manual fix-ups, call 0431 000 062.

Symptoms to look for

You probably need proper MYOB integration when one or more of the following are true.

  • Your bookkeeper makes manual MYOB adjustments every month. The off-the-shelf connector mostly works, but has variance that needs reconciling. The adjustment journals follow a predictable pattern, which means the connector has a predictable blind spot.
  • Refunds and partial refunds break the integration. Sales flow correctly, but refunds either fail, duplicate, or land in the wrong account. The credit notes in MYOB are reconstructed manually each month from the source system’s refund report.
  • You sell across multiple channels. Online, in-store, marketplace, and B2B each have their own sales channels, but they all need to reconcile in MYOB. Each channel has its own connector. The connectors do not know about each other and sometimes produce conflicting entries.
  • Inventory and stock movements do not flow correctly. Cost of goods sold, stock-on-hand adjustments, and stocktake variances are manual. The accountant has to ask the warehouse manager what really happened before posting the month-end inventory journal.
  • You are on MYOB AccountRight Classic and want to modernise the integration. Many MYOB businesses still run desktop or older versions. The integration story for these is different from cloud MYOB. The cloud-only add-ons cannot reach the data; the desktop has its own API that needs handling differently.
  • Multi-currency or international sales add complications. Exchange rate handling, realised gains and losses, and foreign-currency invoices all require treatment the off-the-shelf connectors do not handle. The accountant has manual journals waiting at month-end for every overseas transaction.
  • You run multiple MYOB company files. Separate entities, separate trading names, or separate trust structures. Inter-entity transactions and group consolidation require manual data entry across files. The CFO has a spreadsheet that consolidates the lot, and it lags two days behind reality.

DIAGNOSTIC

If three or more describe your situation, the MYOB integration layer is the bottleneck. Replacing brittle connectors with proper middleware pays back in bookkeeper time alone.

The architecture we deploy

Myob Integration Services Content

Every MYOB integration we build on Nexus uses the same pattern. The components are deliberately boring. Boring is the point.

Source system event capture

Events from your operational systems (Shopify, WooCommerce, Zenoti, custom POS, custom ERP) are captured as they happen. Every state change is preserved, not just the final state. If an order was placed, then partially refunded, then cancelled, all three events make it through. The MYOB-side accounting treatment reflects the full sequence, not just the latest snapshot.

Accounting transformation

Each event is transformed into the correct MYOB transaction type. Sales become invoices or sales receipts. Refunds become credit notes. Payments become applied payments. Inventory movements become inventory adjustments. GST treatment is correct for each transaction type. The transformation rules are written down, version-controlled, and reviewed by your accountant before going live. They are not magic.

MYOB API writes

Transactions are written to MYOB through the official MYOB API. Rate limits are respected. Failed writes are retried with backoff. Duplicate prevention through idempotency keys. When MYOB has scheduled maintenance overnight, your transactions queue and drain when MYOB comes back. Nothing is lost.

Reconciliation reports

Daily reconciliation reports show source system totals versus MYOB totals. Variance, if any, is visible immediately. The bookkeeper opens the dashboard on Tuesday morning and sees Monday’s discrepancies, while the data is still fresh and the cause is still findable. Month-end stops being a forensic exercise and becomes a confidence exercise.

Full audit trail

Every event, every transformation, every MYOB write is logged. Investigation is a query, not a forensic exercise. When the auditor asks for evidence of how a specific transaction was treated for GST, you hand them the calculation log. When the bookkeeper asks why a credit note posted to a specific revenue account, the answer is two clicks away.

Three engagement shapes

We structure MYOB integration engagements one of three ways. All three start with discovery.

  • Single source integration. From $8,000. One operational system to MYOB. Examples: Shopify to MYOB, WooCommerce to MYOB, Zenoti to MYOB. 3 to 5 weeks. Best when one specific integration is the source of most of the month-end pain.
  • Multi-source integration. From $20,000. Multiple operational systems unified into MYOB, with one set of accounting rules. 5 to 8 weeks. Best when sales come from multiple channels and the current connectors are pulling against each other.
  • Run With Us retainer. From $6,500 per month. Ongoing monitoring, continuous additions, security patching, quarterly review. Best when your stack continues to evolve and you want a team that knows your MYOB rules already.

Call 0431 000 062 to talk through which fits.

MYOB integrations we have built

Three MYOB integration projects. All three names confidential at client request (accounting integrations tend to involve commercially sensitive structures). Reference calls available under NDA.

Multi-channel retail, Shopify and POS into MYOB

  • Problem: Retail business with Shopify online, custom POS in stores, MYOB AccountRight for accounting. Two add-on connectors running. Monthly reconciliation took 2 to 3 days due to variance from both sources. The bookkeeper had a private Excel sheet that tracked the recurring variance patterns.
  • Built: Replaced both connectors with Nexus middleware. Both Shopify and POS events flow through a unified transformation layer, write to MYOB with consistent treatment. Job tracking applied to separate online from in-store revenue. Built over six weeks.
  • Result: Month-end reconciliation reduced from days to hours. Variance reduced to near zero. Cross-channel reporting available inside MYOB. The bookkeeper’s private Excel sheet retired.
  • Stack: Shopify Admin API, custom POS API, Nexus middleware, MYOB AccountRight API, MariaDB, AWS Sydney.

Subscription billing to MYOB

  • Problem: Subscription business with WooCommerce Subscriptions, needing recurring revenue, upgrades, downgrades, and refunds reflected correctly in MYOB. Annual prepaid subscriptions were being booked as full revenue on day one, distorting monthly figures and creating an audit finding around revenue recognition.
  • Built: Custom WooCommerce-to-MYOB pipeline on Nexus. Subscription lifecycle events (new, renewal, upgrade, downgrade, refund, cancellation) each mapped to the correct MYOB transaction with correct deferred revenue treatment. Monthly revenue recognition automated. Failed payment recovery automated through a configurable retry sequence.
  • Result: Recurring revenue now reconciles in MYOB on the day of the renewal. Failed payment handling automated. Deferred revenue balance reconciles without manual adjustment. Audit finding closed at the next review.
  • Stack: WooCommerce, WooCommerce Subscriptions, Nexus middleware, MYOB AccountRight API, MariaDB, AWS Sydney.

Legacy AccountRight Classic, modernised

  • Problem: Specialty wholesaler running MYOB AccountRight Classic on a desktop server with a Windows VPN providing remote access. Cloud-only add-on connectors could not reach the data. All Shopify orders were being re-keyed manually by the bookkeeper, who was about to retire. The business could not migrate off Classic in the short term due to a custom inventory module.
  • Built: Nexus middleware using the MYOB AccountRight desktop API via a local sync agent. Shopify events flow to Nexus in real time, then push to AccountRight Classic on the next sync cycle. Custom inventory module data preserved. Bookkeeper retired with the system stable.
  • Result: Manual re-keying eliminated. The Classic system kept running while the business plans a Business or Advanced migration over the next 12 months. The migration is now an option, not an emergency.
  • Stack: Shopify Admin API, Nexus middleware, MYOB AccountRight Classic local API, Windows sync agent, AWS Sydney.

Who you will work with

No account managers, no offshore teams, no juniors learning on your project. The two engineers below scope, build, and ship the work. The bookkeeper or accountant is part of the discovery session and the rules review. The transformation rules are written down in language they recognise, not engineering jargon. They tell us how the chart of accounts should be used; we write the code that uses it correctly.

  • Image 3

    Nicolas Wendell

    MANAGING DIRECTOR

    Nicolas has been building custom software since leaving school, bringing a lifelong passion for development to every project. Before founding Paladine Systems, he ran his own video game studio and earned multiple accolades in network engineering. Known as a driving force in the custom software world, Nicolas combines deep technical expertise with visionary leadership – guiding Paladine in delivering innovative, enterprise-grade solutions.

  • Image 4 (1)

    Mark Morcom

    SENIOR SYSTEMS ENGINEER

    Mark is a young prodigy in software development, bringing 5 years of experience to Paladine. Equally at home on the front end and back end, he crafts clean, scalable solutions that power complex applications. Mark’s sharp problem-solving skills and passion for innovation make him a driving force behind Paladine’s most advanced projects.

How we ship it

MYOB integration projects run in three phases. Each phase is fixed scope and fixed price.

  1. DISCOVERY

    1 to 2 weeks. Map current accounting flows, identify edge cases, map MYOB chart of accounts and job tracking, produce a written scope and fixed quote.

  2. BUILD

    2 to 5 weeks. Stand up Nexus, integrate source systems and MYOB, build transformation rules, validate against historical data.

  3. CUTOVER

    1 to 2 weeks. Disable the old connector, turn on the new middleware, monitor and reconcile the first weeks.

For most stores, total project time is 4 to 8 weeks. Multi-entity, multi-source, or AccountRight Classic deployments run longer.

MYOB integration FAQs

  • Which MYOB products do you integrate with?

    MYOB AccountRight Live (cloud) is the most common. MYOB Business (the newer cloud product) is also supported. MYOB Advanced (for larger businesses) is supported. MYOB AccountRight Classic (desktop) requires a different approach involving the local API, but we have done this work. If you are on a legacy desktop version, mention it in discovery and we will scope the sync agent separately.

  • Are you MYOB partners?

    We are MYOB API integration specialists. We build custom integrations using the official MYOB APIs. For MYOB advisory and bookkeeping, work with a certified MYOB partner in parallel. The two roles are complementary, not competitive.

  • Will this conflict with our MYOB bookkeeper or accountant?

    No. Proper integration makes their job easier. The variance they currently fix manually disappears, which frees them for actual advisory work. The bookkeeper is part of discovery; they tell us the rules, we write the code that enforces them.

  • Can you handle MYOB across multiple companies?

    Yes. Multi-company MYOB (separate MYOB files for separate entities) is a common pattern. Nexus routes events to the correct MYOB file based on rules. Inter-entity transactions can be automatically posted to both sides. Group consolidation logic can be codified.

  • What about MYOB payroll integration?

    We have done payroll integration work, but it is less common than accounting integration. If your operational systems generate timesheets, commissions, or other payroll-relevant data that needs to flow into MYOB Payroll, this can be scoped. For most businesses, payroll stays as-is and only the accounting side is integrated.

  • Can you replace our existing MYOB add-on connector?

    Yes. The most common request. We turn off the existing connector, route events through Nexus, validate against historical data before going live. No data gap during cutover. The new middleware runs in parallel with the old connector for the first month so any final variance can be investigated.

  • What about migrating from MYOB to Xero, or vice versa?

    We do not do MYOB-to-Xero migrations directly. Work with a certified accountant for the migration itself. We come in for the operational system integration before or after the migration is complete. If you are on the fence about migrating, the discovery conversation can include input on which platform suits your operational stack better, but the final accounting call belongs to your advisor.

  • How do we get started?

    Call 0431 000 062 or book a discovery call through the form below. The first conversation is free and is run by an engineer. Bring your bookkeeper or accountant to the call if you can. We will tell you whether middleware is the right next step. Sometimes the answer is to stick with the off-the-shelf add-on and fix the chart of accounts, and we will say so.

GET STARTED

Your MYOB month-end needs manual fix-ups every month. Get an integration that closes the books cleanly.