A client agrees to a security awareness programme at renewal, the agreement is signed and the schedule is set - and the billing step still starts with a person: create the client in MYOB, invoice the first period, remember it every month. Connecting MYOB to Cyber Aware turns client billing into an event rather than a checklist item.
TL;DR
- MYOB has not yet built an official Zapier integration - the Zapier page for MYOB says "Not Yet Supported".
- Cyber Aware connects to Zapier and exposes a direct API, so the connection can be built with Zapier's Webhooks, Custom Actions or Code steps on the MYOB side plus MYOB's own public API.
- MYOB's public API connects to AccountRight and MYOB Business files and is registered through MYOB's API support channel.
- The practical route: Cyber Aware billing-cycle event (webhook or API) to MYOB contact and invoice creation.
- Test one synthetic client before switching on live billing.
Why this matters
Billing is the last manual step on most white-label awareness programmes. The white-label platform comparison in this workspace's own guide set covers why partners stay on the platform for margin reasons - recapturing per-seat spend under their own brand - yet invoices are often still typed by hand into the accounting package every month. One missed invoice cycle is a lost month of recurring revenue, and a manual step is exactly where that happens.
There is no official MYOB connector on Zapier - MYOB's own account is marked "Not Yet Supported" - but the route still exists. Zapier's Webhooks, Custom Actions and Code tools let a self-built connection call MYOB's public API directly, and MYOB's developer platform documents the endpoints for creating contacts and invoices in AccountRight and MYOB Business files. Because Cyber Aware exposes both a webhook and a direct API, either side can be the trigger point.
Who this is for
Australian MSPs and service providers billing security awareness training through MYOB - especially partners who already run the programme hands-off through security awareness training automation on Cyber Aware but still re-invoice clients by hand each period.
Before you start
- A MYOB file with API access. MYOB's developer documentation covers the AccountRight and MYOB Business APIs; registration runs through MYOB's developer API support page.
- A Zapier account or a small server-side script if Zapier isn't the bridge of choice - the same pattern works with a Webhooks by Zapier trigger plus a Custom Action or Code step calling MYOB's API.
- A Cyber Aware partner account with API or webhook access.
- The gotcha: because the MYOB side of the connection is self-built rather than off-the-shelf, every field mapping - contact name, invoice line items, tax and terms - is a field you define yourself. Test one synthetic invoice before pointing anything at a live client ledger.
Step 1 - Set up the Cyber Aware billing trigger
- On the client record in Cyber Aware, note the reporting cadence - monthly courses, monthly reminders, monthly human risk reports.
- Point Cyber Aware's outbound webhook at Zapier's webhook trigger (or schedule a script that calls Cyber Aware's API on the same cadence as the report cycle).
- Send one test payload and confirm the Zap (or script) receives it: client name, subscription period, quantity.
Expected result: a test payload arrives with the client's billing identifiers present. If fields are missing, add them to the webhook payload in Cyber Aware before mapping further.
Step 2 - Create the client as a MYOB contact
- In the same Zap, add a Custom Action or Code step that calls MYOB's public API to create a contact.
- Map the client name, email and address fields from Cyber Aware into MYOB's contact fields.
- Test the step with the sample payload.
Expected result: a test contact appears in MYOB against your sandbox or test client file.
Step 3 - Create the invoice
- Add a second API call (Custom Action or Code step) that creates the sales invoice against that contact.
- Map the recurring service item - user count from the Cyber Aware payload - to the invoice line, and let MYOB apply the tax rules from the sales settings as it does on invoices raised manually in the app.
- Map the due date and email template so the first invoice reaches the client without a manual follow-up.
Expected result: a test invoice lands in MYOB, tax-inclusive and ready to send.
Step 4 - Reconcile and report
- Raise invoices on the same date the branded client report exports, so the client sees the invoice and the Human Risk Score in the same week.
- Keep the per-seat basis consistent between Cyber Aware's enrolment count and MYOB's invoice line - a one-seat drift every month is the most common reconciliation headache on MSP-side billing.
- If you only want the invoice raised once the programme has actually started, gate the webhook on the learner's activation rather than the start date.
Verification and a clean rollout
- Use one internal test client end-to-end: Cyber Aware event, MYOB contact, MYOB invoice, confirmation email.
- Run one real client's invoice in manual-review mode before enabling auto-send.
- Switch the remaining clients across over one billing cycle, not all at once.
Troubleshooting
- No contact appears in MYOB. Test payloads need a real API call - check that the client file is open and connected and that the mapped name matches a new record.
- 403 or registration error from MYOB's API. The application registration runs through MYOB's developer platform; the connection has to be registered before it can create records in your file.
- Duplicate invoices. The client was invoiced manually once and then again from the webhook. Turn off the manual step for that client before switching the webhook on.
- Wrong seat count. Map the learner count field from Cyber Aware's payload, not a static value - static values are the most common source of one-seat drift.
- Nothing sends at all. Webhook triggers are event-driven; the first payload has to arrive after the connection is live to be picked up.
What to do next
Billing is the commercial frame; the programme behind the invoice is security awareness training - auto-added monthly courses, due and overdue reminders and branded certificates, so every seat the invoice lists has a real, scheduled activity attached to it.
FAQ
Does MYOB have an official Zapier integration?
No - MYOB's own page on Zapier is marked "Not Yet Supported": MYOB has not yet built an integration on Zapier. The connection has to be built yourself using Zapier's Webhooks, Custom Actions or Code steps pointing at MYOB's public API.
Can Cyber Aware connect to MYOB directly?
No native MYOB connector appears in Cyber Aware's published integration list - Google Workspace, Microsoft 365, Zapier and a direct API. Because Cyber Aware exposes both Zapier webhooks and a direct API, either can be one side while MYOB's public API is the other.
Does the invoice carry the MSP's brand or MYOB's?
MYOB invoices carry your business's own template and settings - that is what the client sees. The training itself is white-labelled on Cyber Aware, which is what earns the margin between the platform cost and what you charge.
Is the training itself billed per seat or per client?
Per-seat is the norm on white-label awareness programmes - Human Risk Reporting exports a per-client view that maps directly to an invoice line.
Is this just invoicing automation, or can it handle the whole revenue cycle?
This pattern covers one recurring thing safely: contact and invoice creation on a cadence your code path calls MYOB's API correctly. Quotes, deposits, and mid-cycle changes are left for follow-ups - do not assume auto-proration is handled.
One last thing
Check before you switch on the webhook: does every client on the awareness programme actually have a valid MYOB contact? Reconciliation is easiest to fix before month one goes out rather than after month three has drifted.