MYOB AccountRight ecommerce integration without re-keying invoices

The store already takes orders. The company file already holds the customers. The gap is Sale/Invoice, Customer, and inventory items — and whether this file is cloud AccountRight, a local desktop, or a file MYOB now steers away from. We will tell you what will post, and what the UI will not show.

Book a free 30-minute discovery callTalk through your MYOB AccountRight connection

Australian ecommerce team. We look at the store and the company file before anyone talks about a connector.

Still running a store that needs MYOB AccountRight?

The store still takes orders. The MYOB file still does GST. That is why the two have been left talking through a CSV, or through a desktop add-on the last developer stopped answering.

MYOB AccountRight is the SME company-file product — desktop and online. MYOB is an Australian business-software company (since 1991) built for AU and NZ, with ATO-oriented compliance. MYOB’s own wording says it has helped “hundreds of thousands of organisations” across AU and NZ, and the AU homepage says “more than a million people in Australia and New Zealand who trust their business with MYOB”. Those are vendor phrases, not an install-base we will restate as a company count.

MYOB’s developer docs also say MYOB Business will replace MYOB Essentials and MYOB AccountRight for new customers in Australia. Existing company files are still common. New AU buyers are being steered elsewhere. That is a scoping fact, not a reason to panic-migrate the file on the first call.

You might recognise one of these:

  • Web orders are re-typed as item invoices in AccountRight
  • Customers on the site are not the Customer contacts in the company file
  • The file is still on a desktop with the API on localhost:8080, not on api.myob.com
  • Someone said “just use the MYOB API” without saying AccountRight or Acumatica
  • Inventory items in MYOB do not match SKUs on the store
  • You were told new customers cannot buy AccountRight, and you are not sure what that means for a live file

You do not need a new brand, or an ERP pitch. You need a clear read on the company file you already have.

Why these connections stall

AccountRight has a documented API. The stall is rarely “MYOB has no API”. It is the company-file shape, the cloud versus desktop endpoint, and the fields the UI will actually show.

Cloud vs desktop

Business API v2

UIAccessFlags

Not Acumatica

Cloud and desktop are not the same door.

The official surface is MYOB Business API v2 — REST + JSON — the same endpoint family for AccountRight, Essentials, and MYOB Business. Cloud base: https://api.myob.com/accountright/. Local desktop: http://localhost:8080/accountright/ (or a LAN IP). Cloud auth is OAuth plus x-myobapi-key, x-myobapi-version: v2, and x-myobapi-cftoken (Base64 company-file user:pass). A connector written for the cloud headers will not just “point at localhost”. A desktop file behind a locked office PC is a hosting problem before it is a mapping problem.

The sales scope is specific.

Ecommerce work uses /Sale/Invoice (Item, Service, and related types), /Sale/Order, /Sale/Quote, /Sale/CustomerPayment, /Contact/Customer, and inventory items. “Post the order into MYOB” has to name the resource. An item invoice is not a service invoice. A Sale/Order is not a Sale/Invoice. CustomerPayment is a separate call. Guessing that from a generic “MYOB plugin” is how half-posted invoices sit in the file.

UIAccessFlags decide what the bookkeeper sees.

Not every AccountRight-only field appears in Essentials or MYOB Business UI. An API write can succeed and still be invisible, or invalid, in the product the client actually opens. Confirm the product line and the flags before promising a field the UI does not have.

AccountRight is not Acumatica, and it is not “the MYOB API”.

Acumatica (formerly MYOB Advanced) is a different product with a contract-based REST API. AccountRight clients do not work unchanged against it. Calling both “MYOB” in a statement of work is how you buy the wrong build. Opteon Sydney is a published CoSource valuation app that integrated into MYOB. It is not an ecommerce or nopCommerce case, and we will not cite it as one.

None of that makes the store or the company file worthless. It does mean “drop in the MYOB module on Monday” is usually the wrong first move.

How we work

We start with the company file and the store, not with a product name on a slide.

1

Look at what you have

Store platform, whether the file is cloud AccountRight or a local company file, which MYOB product the UI actually is, existing add-ons, and what already creates invoices. We will tell you which Sales resource to use, and whether the desktop endpoint is even reachable.

2

Decide the job

There are three honest outcomes. We recommend one, not all three.

3

Do the work in stages

Customer contacts and item mapping first, then Sale/Invoice (or Sale/Order), then CustomerPayment. A cloud sandbox or a copy of the file beats a Friday post into the live company file.

4

Hand it back so the next person can run it

Source, the API key and company-file identity pattern, and a short record of which resource creates which document.

Three honest outcomes

  • Connect the store to AccountRight: create or update Customer contacts, map Inventory/Item, create Sale/Invoice/Item (or Service) from web orders, optionally Sale/Order, and apply CustomerPayment. Custom API work. No published CoSource App Store connector.
  • Fix a broken connector when an add-on still almost works: move it onto API v2 headers, stop posting the wrong invoice type, or get a desktop listener off a machine that sleeps.
  • Decide not to connect when the file is the wrong MYOB product (Acumatica / Advanced, or a Business file that should be treated as Business), when a desktop file cannot be reached safely, or when MYOB’s own path for new AU customers means the job is a product change, not a store sync.

We will not tell you AccountRight and Acumatica share an API. We will not tell you new Australian customers will still be sold AccountRight. If you already know you want a MYOB-branded app and nothing custom, that channel may be a better fit. If you want an honest fork in the road, talk to us.

What we need for the first call

A store URL and which company file is enough to start.

  • Which store: nopCommerce, AbleCommerce, Shopify, or another CMS
  • Cloud AccountRight, local desktop, or you are not sure
  • Whether the UI is AccountRight, Essentials, or MYOB Business
  • What should land: item invoices, orders, customer payments, contacts, inventory items
  • Whether anyone already posts into this file (add-on, accountant tool, inventory product)
  • What “done” looks like: a working sync, a repaired add-on, or a clear picture first

The first call is 30 minutes. You leave with a recommendation you can take to a manager, not a MYOB estimate pulled from thin air.

Related work

We have not published a MYOB AccountRight ecommerce case. Opteon Sydney integrated into MYOB for a property valuation application. That is not a store, and we will not use it as one.

CoSource is a Sydney software firm and a nopCommerce Gold Partner. Services include custom development and CRM & ERP integration on nopCommerce, AbleCommerce, and Shopify. That is a capability, not an AccountRight case study. An AccountRight company file still starts with its own assessment.

FAQ

Can web orders become MYOB invoices?
Yes, on API v2, typically as /Sale/Invoice Item (or Service). Decide that versus /Sale/Order up front. Then map /Contact/Customer and inventory items so the file does not fill with unmatched cards.
Is the file in the cloud or on a PC?
Ask that first. Cloud uses api.myob.com and OAuth plus MYOB headers. Desktop uses localhost:8080 (or LAN) on the machine that holds the file. The code is not interchangeable without a hosting decision.
Are AccountRight and MYOB Acumatica the same integration?
No. Different products, different APIs. Do not reuse an AccountRight client against Acumatica.
Will new Australian customers still get AccountRight?
MYOB’s own developer docs say MYOB Business replaces Essentials and AccountRight for new customers in Australia. Existing files are a different conversation. We will not pretend the vendor is still selling AccountRight as the default new-AU SKU.
Do you have an AccountRight ecommerce case we can read?
No named store case. Opteon is MYOB, not ecommerce. We will not invent one.

Talk through the AccountRight connection you already need

Thirty minutes. Bring a store URL and whether the company file is cloud or desktop. We will tell you whether to connect, fix the add-on, or leave this file alone.

Book a free 30-minute discovery call