7 Signs Your MYOB File Is a Complete Mess

When 'It's Fine' Actually Means 'It's a Disaster'

You've been saying "it's fine" for months. The bank rec is off by $47.50, but you've got bigger problems. Payroll throws an error every second week, but you've learned to work around it. Your chart of accounts has three versions of "Office Supplies" because no one's quite sure which one to use.

Here's the thing: these aren't minor annoyances. They're symptoms of a file that's quietly sabotaging your business. Every workaround you've invented costs you time. Every error you've learned to ignore is compounding. And when tax time arrives, or you need to make an actual business decision based on your numbers, you'll discover just how much "it's fine" has cost you.

Most business owners don't realise their file is a mess until they try to do something important with it. By then, fixing it takes three times longer than it should have.

Sign #1: Your Bank Reconciliation Never Actually Balances

If your bank rec is perpetually "close enough," you're not alone. But you're also not doing yourself any favours.

What 'close enough' reconciliation actually costs you

That $23 difference you've been ignoring? It's probably masking a $450 error that's been offset by a $427 duplicate transaction. Close enough reconciliation means you have no idea what your actual cash position is. You can't trust your reports. You can't make confident decisions about spending or hiring. And when your accountant asks for your numbers, you'll spend hours trying to explain why nothing quite adds up.

The real cost isn't the missing dollars. It's the decisions you're making based on wrong information.

The rounding error trap (invoices with 3 decimal places)

Here's a specific problem that catches people out: invoices with 3 decimal places ending in 5 are rounded down, causing unbalanced transactions. You invoice someone for $127.335, expecting it to round to $127.34. It doesn't. It rounds to $127.33. Now your books are out by one cent per invoice, and if you're processing hundreds of transactions, those cents add up to real discrepancies.

This isn't a rounding preference you can change. It's how the system works. The fix is to catch it before it happens: check your invoice totals before you send them.

How to fix it without starting from scratch

Start with your most recent month. Reconcile it properly, tracking down every difference. Don't force it to balance by creating a "rounding adjustment" transaction. Find the actual problem. Once that month is clean, work backwards one month at a time. Yes, it's tedious. But it's faster than living with a permanently broken file.

Sign #2: You're Drowning in Duplicate Transactions

Duplicate transactions are the cockroaches of accounting files. You think you've got rid of them, then three more appear.

Why deleting imported statements triggers Error 01068777

You imported your bank statement twice by accident. Now you've got duplicates everywhere. You try to delete the imported statement, and Error 01068777 appears. The fix is annoyingly simple: refresh your browser. That's it. But the error message doesn't tell you that, so you waste twenty minutes trying to figure out what you've broken.

The better approach is to not import statements twice in the first place. Check what's already in your file before you import anything new.

The credit card feed mistake that creates phantom transactions

Someone set up your credit card feed and linked it to an asset account. MYOB doesn't support linking credit card feeds to asset accounts, but it doesn't stop you from trying. The result is phantom transactions that appear in your feed but don't process properly. They're not quite in your file, but they're not quite gone either.

You need to disconnect the feed, link it to a proper credit card liability account, and manually enter the transactions that got stuck in limbo. It's messy, but it's the only way to clean it up properly.

Sign #3: Your Chart of Accounts Looks Like a Junk Drawer

 Photo by Yan Krukau on Pexels

Open your chart of accounts. If you see "Office Expenses," "Office Supplies," "Office Costs," and "General Office," you've got a problem.

The duplicated account codes problem (especially after migration)

This happens most often after migrating to a new version. Duplicated account codes appear when migrating to New Essentials, and suddenly you've got two accounts with the same code but slightly different names. Transactions get split between them randomly. Your reports are useless because the data is scattered.

You can't just delete one and hope for the best. You need to identify which account has the bulk of the transactions, merge the others into it, and then archive the duplicates. It takes time, but it's the only way to get clean reports.

When to merge accounts vs when to archive them

Merge accounts when they're genuinely the same thing and you want historical reporting to be accurate. Archive accounts when they were used for a specific project or period that's now finished. Don't delete accounts unless they've literally never been used. Deleting accounts with transaction history breaks your audit trail and makes your accountant very unhappy.

Sign #4: Payroll Throws Random Errors Every Pay Run

If you dread payroll day because you know something will go wrong, your file needs attention.

Error 00706614: One wage item linked to multiple leave items

This error arises from one wage pay item being linked to multiple leave pay items. Someone set up annual leave and sick leave, both linked to the same base wage. Now the system can't figure out which leave balance to adjust when you process a pay run.

The fix requires unlinking one of the leave items, processing the pay run, then setting up the leave items properly with separate wage categories if needed. It's fiddly work, but once it's done, it stays fixed.

The timesheet Wednesday/Sunday glitch (and why it matters)

You set your timesheets to start on Wednesday. They incorrectly start on Sunday instead. There's no fix available yet, which means you're manually adjusting every timesheet or living with incorrect week boundaries. This matters because it affects how overtime is calculated and how weekly hours are reported.

Your only real option is to work around it by setting timesheets to start on Monday, or manually tracking the correct week boundaries outside the system. Neither option is good.

Sign #5: You Can't Actually Run the Reports You Need

Reports are supposed to give you answers. If yours just give you error messages, something's fundamentally wrong.

Trial balance import failures and what they reveal

Errors occur when importing trial balance files and posting journals. This usually means your chart of accounts structure doesn't match what the import expects, or you've got accounts with invalid characters in their names. The error is telling you that your file structure is non-standard enough that automated processes can't handle it.

This is a bigger problem than it seems. If your file can't handle standard imports, it probably can't handle standard exports either. That means your accountant is doing manual workarounds at year-end, which means you're paying for extra hours.

Why your P&L doesn't match your tax return

Your profit and loss says you made $85,000. Your tax return says $91,000. The difference is probably sitting in your balance sheet as unreconciled items, or you've got income coded to the wrong account type. This happens when people use asset accounts for income, or create custom account types that don't map to standard tax categories.

The fix requires going through your chart of accounts and making sure every account is the correct type, then finding the missing transactions and recoding them properly. It's detective work, and it takes time.

Sign #6: User Access Is a Guessing Game

If your team is constantly asking "can you give me access to..." or "why can't I see...", your permissions are a mess.

Error 01070189: The permission change loop

This error occurs when changing user permissions while signed in as the same user. You're trying to change your own permissions, and the system won't let you because you're already using those permissions. It's a catch-22.

The fix is to have someone else with admin access change your permissions, or sign out completely before making changes. But the real problem is that your permission structure is complicated enough that you're constantly having to adjust it.

What 'insufficient access rights' really means for your workflow

When someone gets an "insufficient access rights" error, they don't just stop working. They find a workaround. They ask someone else to process the transaction. They use a shared login. They export the data and work in a spreadsheet. Every workaround creates a gap in your audit trail and increases the chance of errors.

Proper user access isn't about security theatre. It's about making sure people can do their jobs without breaking your data integrity.

Sign #7: You're Working Around MYOB Instead of With It

The clearest sign your file is a mess is when you've invented elaborate workarounds for basic tasks.

The document upload workaround (attaching to bills instead)

Uploading documents requires a date; the workaround is to attach the document to a bill transaction instead. This seems fine until you need to find that document later. It's not where you'd logically look for it. It's buried in a bill transaction from three months ago.

If you're using workarounds like this regularly, you're not using the system properly. That's not a criticism. It's a sign that either your file needs fixing or you need training on how the system actually works.

Invoice due date gymnastics to avoid Error 01052403

Error 01052403 occurs when creating an invoice with specific payment terms. The fix is to alter and re-edit the due date terms. But if you're doing this for every invoice, you've got a systemic problem with how your payment terms are set up.

The proper fix is to review your default payment terms and set them up correctly once, rather than manually adjusting every invoice you create.

Before You Panic: Your File Isn't Beyond Saving

Most of these problems are fixable. Some require immediate attention. Others can wait.

Which signs need immediate action vs which can wait

Fix immediately: bank reconciliation problems, payroll errors, and anything that's stopping you from processing transactions. These affect your day-to-day operations and your legal obligations.

Fix soon: duplicate transactions, chart of accounts mess, and reporting failures. These won't stop you working, but they're making everything harder than it needs to be.

Fix when you have time: user access issues and workarounds. These are annoying, but they're not breaking your business.

When to call in help vs when to DIY the fix

DIY the simple stuff: cleaning up duplicate transactions, archiving old accounts, fixing obvious data entry errors. If you can see what's wrong and the fix is straightforward, do it yourself.

Call in help when: you're getting errors you don't understand, your reports are fundamentally broken, or you've tried to fix something and made it worse. Professional help costs money, but it's cheaper than spending three weeks trying to fix something yourself and potentially breaking it further.

The key is knowing the difference. If you're not sure, ask. Most bookkeepers and accountants will give you a straight answer about whether you need help or can handle it yourself.