Press a button on the job, get a MYOB invoice, and a reason if it fails
Staff press a button on a job in monday.com and a Make scenario creates the invoice in MYOB, with or without an installation line, then writes the result back to the job. A four-module sub-scenario keeps the connection to MYOB authorised.
Where this applies
Trades, installers and any Australian or New Zealand business that runs jobs on monday.com and invoices in MYOB.
- runs, 34 successful
- 35
- routes: with install, without, or a reason
- 3
- modules in the token tool
- 4
The problem
When jobs run on a board and invoices are raised in the accounting system, every invoice is typed twice: once as the job and once as the invoice. Whoever invoices has to know which jobs are finished, what was installed and what has already been billed.
The usual automation fails quietly. If the accounting system rejects an invoice, or the job is missing something it needs, the person who asked for it finds out days later, if at all. The answer has to come back to the place where they asked.
What we built
A button, not a status
The trigger is a button column on the job. Pressing it is a deliberate act, so an invoice is raised when someone decides it should be, not whenever a status happens to change.
The token as a tool
Before it talks to MYOB, the scenario calls a sub-scenario that reads the stored refresh token from a data store, exchanges it for a fresh access token, saves the new refresh token back and returns the access token. Any scenario that needs MYOB can call it, and none of them carries the sign-in logic itself.
Three routes, decided by the job
A router checks the job first. A valid job with an installation gets an invoice with an install line; a valid job without one gets an invoice without it; a job missing what the invoice needs goes down a third route that marks the item and posts an update saying what is wrong.
Straight to the API
The scenario looks up what it needs in MYOB and posts the invoice to the AccountRight API with Make's HTTP module, building the request itself, so the invoice has exactly the lines the route calls for.
Success and failure both written back
When MYOB accepts the invoice, the job's columns are stamped with the result. When it rejects it, an error route marks the job and posts an update explaining the failure, so the person who pressed the button sees the reason on the item.
The outcome
Between 18 and 22 September 2026 the scenario ran 35 times, 33 from the button and two by hand, with 34 successes and one error, using 172 credits.
In the current billing period the invoice scenario has used 135 credits and the token tool 81. Both are switched on.
Where it stops
The flow raises the invoice and stops there: payment is not brought back from MYOB to the job. It knows two invoice shapes, with and without an installation line, and anything else needs another route. It is built against one business's MYOB company file and its item and account choices.
Built with
- Make.com
- monday.com
- MYOB AccountRight
- HTTP API
- Make data store
Patterns used
- Button as trigger
- Token refresh as a sub-scenario
- Error route writes back
- Validate before posting
Page copy drafted with AI assistance. Skofi is accountable for it. Editorial policy
Have something shaped like this?
If any part of the above resembles a problem you are living with, a short call is the fastest way to find out whether it is the same problem underneath.
What happens on the call
- 15 minutes, no deck
- We map the process on the call
- A written scope, or an honest no