AI for MYOB

No. We are an independent Australian product, we are not affiliated with, endorsed by, certified by or partnered with MYOB, and MYOB is their trademark. Our software works alongside an MYOB file with your authorisation, and nothing more should be read into it than that. We are deliberate about this wording because the add-on marketplace habit of implying official blessing leaves firms unclear about who is accountable when something breaks — and the answer, in our case, is us. What our software can actually do against your particular MYOB products, versions and hosting arrangement is something we confirm with you during onboarding, on your real setup, rather than assert generically here.

It matters for how we connect, not for what your team experiences. MYOB’s product line has more than one lineage, and firms with long-established client bases usually have a genuine mix — some clients on newer cloud-based products, others on AccountRight files that have been running for years, sometimes with different hosting arrangements behind them. Rather than make a blanket claim across all of that, we check your actual estate at the consultation and tell you which files we can work with, in what way, and which ones would need a different approach. Where a file cannot be connected in the way you would want, you hear it before you buy something, not after.

Genuinely useful — it is the single biggest advantage a long-established MYOB book has, and it is usually underrated. Coding accuracy comes almost entirely from history: how this supplier has actually been treated in this file, over years, through different bookkeepers. A file with a decade of consistent treatment gives the AI a far stronger reference than a pristine new one, which is the opposite of what most people assume about legacy data. The caveat is that consistency is what matters, not age. A decade of a supplier coded four different ways by four different people is a decade of noise — and the AI’s correct response to that is to flag the inconsistency for a person rather than pick a fifth treatment. That surfacing is often the first real value a long-running file gets from this.

No, and we would be suspicious of anyone whose automation pitch quietly requires a ledger migration. MYOB stays the ledger. We do not want to be your ledger, we are not building one, and a forced migration is one of the most disruptive and expensive things you can do to a client — particularly one with years of history, established reporting and staff who know the software. The AI works upstream of the ledger: reading documents, deciding what they are, chasing what is missing, and proposing transactions for your team to approve into the file that already exists. If a client should move ledgers, that should be a decision made on its own merits, not smuggled in as a precondition for automating data entry.

This is the right question, and it is usually the deciding one. Firms with long MYOB histories often have clients who are older, less digital and quite content with the way things are — and the honest position is that the AI changes very little for them, by design. The client still emails a bill or photographs a receipt; there is no new app they must adopt, no portal to log into, no habit to relearn. What changes is on your side. The one place they will notice is document chasing: they will get more reminders than before, because the reminders will actually be sent. In our experience that lands better than firms fear, provided the reminders are polite, specific and not relentless — which is exactly why the cadence is yours to set.

Strict isolation, enforced structurally rather than as a policy. Each client file is its own context with its own chart of accounts, supplier history and rules, and a document captured for one client cannot be posted to another. That is not merely a data hygiene nicety for a firm — you are handling other people’s financial records, and under the Privacy Act 1988 you are accountable for keeping them separate and secure. Access on our side is per staff member, and every action is logged: what the AI proposed, who reviewed it, what they changed and when. Above the individual files, the practice view shows where exceptions are waiting and which clients are not responding, without mixing any of their data together.