MYOB workflow customisation covers user permissions, purchase order requirements, and tax code defaults across MYOB AccountRight and MYOB Business. It does not extend to multi-level approval workflows, dollar-value routing, or conditional logic based on supplier or cost centre. If your AP process requires anything beyond “who can enter bills and who can pay them,” you are working outside what MYOB was built to do.
This is not a criticism of MYOB. Accounting software records transactions. Workflow engines route decisions. They are different tools solving different problems. The issue is that many Australian industrial businesses expect their accounting platform to enforce governance rules it was never designed to handle, and the result is a policy document that sits in a shared drive while the software permits whatever any authorised user decides to do.
Here is exactly what you can configure inside MYOB, what you cannot, and how to close the gap.
What MYOB lets you customise natively
MYOB provides several configuration points that matter for AP workflows. Understanding these is the starting point before deciding what needs an external tool.
User roles and permissions. MYOB AccountRight supports role-based access control across functional areas. You can restrict users to specific modules - a data entry clerk can be limited to entering bills without access to payment processing or bank feeds. This gives you basic segregation of duties at the module level. MYOB Business offers a simpler permission model with fewer granular controls, but the core concept is the same: control who can do what inside the system.
Purchase order requirements. You can configure MYOB to require purchase orders for bill entry, creating a basic control that links expenditure to prior authorisation. When enabled, bills should reference a PO number. This does not create automated matching or block entry without a valid PO - it establishes the expectation and provides a field for tracking.
Tax code defaults. MYOB lets you assign default tax codes at the account level. When a bill is coded to a specific account, the associated tax code populates automatically. This reduces manual coding errors for straightforward transactions. The CAP tax code (Capital Acquisitions) is the one that generates the most questions - it maps to BAS label G10 and applies to capital purchases like vehicles, plant, and equipment. Setting CAP as the default on your fixed asset accounts ensures capital acquisitions are reported correctly on your BAS without the bookkeeper remembering to change the code each time.
Job and category tracking. MYOB AccountRight supports job costing and tracking categories (referred to as “categories” in MYOB Business). These let you allocate costs across projects, departments, or cost centres. For construction and wholesale businesses, this is often the reason MYOB was chosen over Xero in the first place. You can customise the category structure to match your business operations and require category allocation on transactions.
What MYOB does not support natively
The gaps become visible once invoice volume exceeds what a single person can review manually, or when your delegation of authority requires different approvers at different spend levels.
Multi-level approval workflows. MYOB has no approval routing engine. There is no way to say “invoices under AU$5,000 go to the operations manager, invoices between AU$5,000 and AU$25,000 go to the financial controller, and anything above AU$25,000 requires director sign-off.” Every user with bill access has the same approval authority regardless of the invoice amount.
Dollar-value thresholds. Without approval routing, there is no mechanism to enforce spending limits by role. A bookkeeper with bill entry access can process a AU$200 stationery order and a AU$80,000 subcontractor payment with identical permissions. The threshold policy exists as a document. MYOB does not read it.
Conditional routing by supplier or cost centre. You cannot configure rules like “all invoices from new suppliers require finance team review” or “capital expenditure above AU$10,000 routes to the CFO.” These conditional workflows require logic that MYOB’s permission system does not support.
Automated duplicate detection. MYOB flags duplicates only when the invoice reference number matches an existing entry exactly. A supplier who sends the same invoice with a slightly different reference, or the same amount and date with no reference at all, passes through without a warning. Real duplicate invoice detection requires matching across multiple fields - supplier, amount, date, and line items.
Vendor bank detail validation. When a supplier’s bank details change on an incoming invoice, MYOB does not flag the discrepancy. This is the mechanism behind payment redirection fraud. The ACCC reported AU$152.6 million in losses from business email compromise and payment redirection in 2024. An AP automation layer that compares incoming bank details against stored supplier records catches these changes before payment.
For a full comparison of MYOB’s native capabilities against external automation layers, see Accounts Payable Automation for MYOB.
MYOB tax codes explained
Tax code confusion is one of the most common sources of BAS errors. Here is a quick reference for the MYOB tax codes that apply to purchases.
| Tax Code | Rate | Meaning | When to Use | BAS Label |
|---|---|---|---|---|
| GST | 10% | Goods and Services Tax | Standard domestic purchases from GST-registered suppliers | G11 |
| FRE | 0% | GST-Free | Purchases that are GST-free under Division 38 (e.g., basic food, some medical, education) | G11 |
| INP | 0% | Input Taxed | Input taxed acquisitions (e.g., financial supplies, residential rent) | G13 |
| CAP | 10% | Capital Acquisitions | Capital purchases - vehicles, machinery, equipment, property improvements | G10 |
| N-T | 0% | Not Reportable | Non-taxable items that do not appear on the BAS (e.g., wages, bank fees, government charges) | Not reported |
The CAP code in detail. CAP stands for Capital Acquisitions. It carries the same 10% GST rate as the standard GST code, but it reports to a different BAS label - G10 instead of G11. The ATO requires capital acquisitions to be reported separately because they affect how GST credits are calculated and reported. If you buy a AU$55,000 truck (GST inclusive), the AU$5,000 GST component needs to appear at G10 on your BAS, not G11. Using the standard GST code instead of CAP means the capital acquisition credit is misreported - the total GST claimed may be correct, but the ATO’s category breakdown is wrong.
When should you use CAP? Apply it to any purchase that meets the ATO’s definition of a capital acquisition: assets acquired for use in your business that have a useful life extending beyond the current reporting period. Common examples include vehicles, plant and equipment, computer hardware above your capitalisation threshold, and building improvements. If you are unsure whether a purchase qualifies, the BAS worksheet generator can help you map your expense categories to the correct BAS labels.
Adding approval workflows to MYOB
You have two realistic options for adding approval workflows to MYOB: a dedicated AP automation platform, or a manual workaround using email and spreadsheets.
Option 1: AP automation platform (Pulsify). A purpose-built AP layer connects to MYOB via API, pulls your chart of accounts, tracking categories, tax codes, and supplier list, and creates a governed workflow between invoice receipt and ledger posting. Invoices are captured, coded (with suggestions based on supplier history), routed to the correct approver based on configurable dollar-value thresholds and category rules, and posted to MYOB only after approval. The approval workflow enforces your delegation of authority automatically. Bank detail changes are flagged. Duplicates are caught across multiple fields. The audit trail connects each approval to the authority that authorised it.
Option 2: Manual workaround. Forward invoices to the designated approver via email. Track approvals in a shared spreadsheet. Enter approved invoices into MYOB manually. This works at low volumes - perhaps 10 to 15 invoices per week with a stable supplier list. The failure mode is predictable: approvals get buried in inboxes, the spreadsheet falls behind, and the audit trail becomes a reconstruction exercise rather than a real-time record. At 40 or more invoices per week, the manual process breaks under its own weight.
| Capability | Manual Workaround | Pulsify |
|---|---|---|
| Multi-level approvals | Email chains, hope | Configurable tiers by dollar value |
| Dollar-value thresholds | Spreadsheet reference | Automated routing and enforcement |
| Duplicate detection | Manual checking | Multi-field matching (supplier, amount, date) |
| Bank detail validation | None | Automated flag on changes |
| Audit trail | Email thread reconstruction | Timestamped, role-linked record |
| MYOB sync | Manual entry after approval | Bidirectional API sync |
Step-by-step: setting up a basic MYOB workflow with external tools
If you have decided that manual workarounds are not sufficient, here is how to connect MYOB to an external AP automation layer. The steps below use Pulsify as the example, but the logic applies to any platform that offers bidirectional MYOB integration.
Step 1: Connect MYOB to Pulsify. Authenticate your MYOB AccountRight or MYOB Business account through the accounting integration settings. The platform pulls your chart of accounts, tracking categories, tax codes, job list, and supplier records. This initial sync takes a few minutes and establishes the shared data model between the two systems.
Step 2: Map your chart of accounts and configure defaults. Review the imported chart of accounts. Set default account codes for your most common suppliers based on historical coding patterns. If you process 30 invoices a week from 10 regular suppliers, most of those invoices should code themselves after the first month of training the system. Confirm that your tax code defaults (GST, FRE, CAP, N-T) align between MYOB and the AP platform.
Step 3: Configure approval tiers. Build your delegation of authority into the approval workflow engine. Define dollar-value thresholds for each approver role. Set category-specific rules where needed - for example, capital expenditure above AU$10,000 routes to the CFO regardless of the general threshold for that approver level. Add backup approvers for each tier to handle leave periods.
Step 4: Set up invoice capture. Configure a dedicated email address for supplier invoices (e.g., invoices@yourbusiness.com.au) that feeds directly into the AP platform. Invoices are extracted, matched against supplier records, coded based on history and defaults, and queued for the appropriate approver. Mobile capture is available for invoices received on site - common in construction and field services.
Step 5: Test with a batch of real invoices. Run 10 to 20 actual invoices through the workflow before going live. Verify that coding suggestions are accurate, approval routing follows your delegation matrix, and approved bills post to MYOB with the correct account codes, tax treatments, and tracking category allocations. Fix any mapping issues before switching from your manual process.
Sources: ATO - GST and record-keeping requirements · MYOB - AccountRight and MYOB Business · ACCC - Targeting Scams Report 2024
Further reading: Accounts Payable Automation for MYOB · Designing a Delegation of Authority Structure Inside MYOB · AP Approval Software Australia