MYOB AccountRight for Craft Commerce 5
Every order in MYOB, for what the customer paid
My turns each completed Commerce order into a MYOB sale invoice, against the customer's existing card if they have one. It applies the payment so the invoice doesn't sit unpaid, raises a credit note when you refund, and refuses to send an invoice whose total doesn't match the order.
See the invoice before MYOB does
The dry run, the Preview button on Commerce's order screen and the real push all go through one payload builder, so what you read here is what MYOB receives. It ends by adding the invoice up the way MYOB will and comparing that with the order. Looking is read-only: nothing is created in MYOB, not even a customer card.
$ php craft my/sync/order 1042 --dryRun
POST Sale/Invoice/Service
{
"Customer": { "UID": "7c1e4a90-…" },
"Date": "2026-10-02T00:00:00",
"IsTaxInclusive": true,
"Lines": [
{
"Type": "Transaction",
"Description": "2 × Linen apron (APR-01)",
"Total": 90,
"TaxCode": { "UID": "b3f0…" },
"Account": { "UID": "52d9…" }
},
…
],
"Number": "1042",
"Freight": 11,
"FreightTaxCode": { "UID": "b3f0…" },
"CustomerPurchaseOrderNumber": "1042",
"JournalMemo": "Craft order 1042",
"InvoiceDeliveryStatus": "AlreadyPrintedOrSent"
}
Would book 110.00; the order is 110.00.Features
An accounting integration has one failure it can't be forgiven: booking a different number than the customer paid. Most of My is built around not doing that, and around never doing it twice.
Totals checked twice
My never states a total. It sends the lines, adds them up the way MYOB will, and refuses to push if the sum is off from the order by more than a cent. After the push it compares what MYOB booked with what the customer paid, which catches a tax code mapped to the wrong rate.
- Line amounts come from Commerce's own totals, so a third-party surcharge isn't dropped
- Refuse, add a rounding line, or push and warn: your call
One invoice per order, however many retries
A unique key on order, document and source, claimed before the request goes out. If MYOB created the invoice but the reply was lost, the next attempt asks MYOB for that invoice number and links it instead of posting a second.
No second card for regulars
Before creating a customer card, My searches MYOB for one with the order's email address and remembers the match. A company file with ten years of customers in it stays one card per customer.
- Company or individual card, from the billing address
- Or post everything to one card, for high-volume retail
Payments and refunds follow
Each Commerce payment becomes a MYOB customer payment applied to the invoice, so nobody closes them by hand. A refund becomes a credit note and, if you want, a credit refund out of the account you name.
- Authorisations wait until they're captured
- Gateways mapped to MYOB's own payment methods
Cloud, or the server in the office
Connect a cloud company file over OAuth, or an AccountRight local server over HTTP Basic. My keeps the twenty-minute tokens fresh on its own, and copes with newer API keys that MYOB won't let list company files.
- Pin the company file per environment, so staging can't invoice production
Every request on the record
A connection log of what was sent and what MYOB said back, with tokens and company file passwords redacted before anything is written. MYOB's field-level error detail is kept, so an Invalid data tells you which field.
- Console commands for dry runs, backfill, retry and status
- Checkout never waits: every push is queued
The invoice number on your order page
craft.myob can only read. Show the MYOB invoice number on an order confirmation or account page; a template render is no place to write to the books.
{% if craft.myob.isInvoiced(order) %}
<p>Tax invoice {{ craft.myob.invoice(order).myobNumber }}</p>
{% endif %}
{% for document in craft.myob.documents(order) %}
<li>{{ document.getTypeLabel() }}: {{ document.getStatusLabel() }}</li>
{% endfor %}Frequently Asked Questions
The questions worth answering before you connect it to your books.
$99 per Craft installation, and $79 a year to keep receiving updates. There's one edition, with everything in it.
MYOB AccountRight, through the MYOB Business API: company files in the cloud (AccountRight Live and MYOB Business), and company files on an AccountRight local server your Craft site can reach. MYOB Acumatica and MYOB Exo are different products with different APIs; they're covered by the free Erpy for MYOB add-on instead.
No. Every push is a queue job. If MYOB is down or slow, the invoice goes later and the customer never knows. Failed pushes are retried, and anything still outstanding can be sent with one console command.
No. The default Service layout posts each line to a sales account. If you keep inventory in MYOB, the Item layout matches each SKU to an item for stock and cost of goods, and a SKU that isn't there goes to the sales account rather than off the invoice.
By default it isn't sent. The order shows both figures and the push is marked failed, so you can fix the cause. A wrong invoice in the books is harder to find and harder to undo than a push that stopped and told you why. You can choose a rounding line instead.
Yes. The backfill command sends every completed order that has no invoice in MYOB, oldest first. The ledger means running it twice sends nothing twice.
No. Unlinking a document, disconnecting and uninstalling all change what Craft remembers. Invoices, cards and payments in MYOB are left exactly as they are.
No. My is an independent plugin built by Justin Holt, and it talks to MYOB's public API like any other client. It is not affiliated with, endorsed by, or sponsored by MYOB.
Craft CMS 5.3+, Craft Commerce 5.0+, PHP 8.2+.
Read the invoice before it is sent
My is $99 for one Craft installation, then $79 a year for updates. Connect your company file, preview a real order, and read the invoice MYOB would receive before a single one is sent.