WorkflowMax was Xero’s project and job management platform, retired on 26 June 2024, leaving thousands of Australian construction, trades, and professional services businesses to find a new home for their job management workflows. What most migrations missed is that WorkflowMax wasn’t just a project management tool: it was also the place where purchase order approval steps and invoice coding logic lived, often embedded in the job record itself. This guide covers how to identify what was lost in the AP layer, what needs to be rebuilt, and how to structure an approval workflow that actually holds up at invoice volume.
Why WorkflowMax Users Have a Hidden AP Problem
When Xero announced in March 2023 that WorkflowMax would be retired on 26 June 2024, the immediate response from most businesses was to find a replacement for the project management side: job tracking, time recording, quoting, progress claims. BuildXact, ServiceM8, Fergus, monday.com, and WorkflowMax by BlueRock all saw interest from businesses looking for a like-for-like alternative.
Most of that planning focused on what was visible. The job board. The client timeline. The quoting module.
What got less attention was the invoice approval logic that had been running quietly inside WorkflowMax for years. Purchase orders raised against a job. Approval steps before a subcontractor invoice was passed to Xero. Invoice coding tied to job codes, cost centres, and project budgets. These weren’t features most users consciously designed. They evolved over time as the business grew, and they worked because all the information about a job was in one place.
Once WorkflowMax was gone, that information was split across the new project management tool and the accounting platform. The approval layer in the middle went with it.
What Was Actually in WorkflowMax That You’ve Now Lost
Not every WorkflowMax user ran the same configuration. But across construction firms, trades businesses, and professional services practices, the platform typically held some version of the following:
Purchase orders tied to job records. Subcontractor POs were raised against a specific job, which meant the invoice that came in later could be matched back to the original commitment. That matching happened in context, with the job record visible.
Invoice routing tied to job ownership. Because each job had a designated manager or supervisor, invoice approval often followed the job structure. The person who owned the job reviewed the invoice. There was no separate approval system; the job record was the approval record.
Line-item coding informed by job categories. When an invoice arrived, the job code and cost type told you where to allocate each line. Labour, materials, equipment hire each had a corresponding category in WorkflowMax, and that structure fed into how invoices were coded before hitting Xero.
Progress claim history. For construction businesses managing staged projects, WorkflowMax held the progress claim record: what had been approved, what percentage of the contract had been billed, what was outstanding. Comparing an incoming invoice against that record was straightforward because everything was in the same system.
All of this is now either sitting in the new project management tool, in a spreadsheet, in someone’s inbox, or it’s simply gone. The approval workflow that was embedded in WorkflowMax’s job structure has no direct equivalent in Xero or MYOB by default.
Where the WorkflowMax Gap Shows Up in Practice
Consider a building contractor based in Adelaide, South Australia. Their office manager handles AP for around 40 invoices a week, mostly from subbies and materials suppliers. Before the migration, each invoice arrived, was matched to a WorkflowMax job record, and the job supervisor reviewed it before it was pushed to Xero.
After migrating to a new project management platform, the job records moved across. The invoices kept arriving. But the approval step vanished because it had never been a formal process, it had been the job record itself that acted as the check. Now invoices arrive by email, get processed without a job-level review, and go straight into Xero. The coding is done from memory or from a rough internal guide. Some invoices land in the right account. Others don’t.
The issue isn’t that anyone is being careless. It’s that the structural check that WorkflowMax provided passively is no longer there. The approval workflow has to be rebuilt deliberately, because it no longer lives in the job management system by default.
The AP Rebuild Checklist After a WorkflowMax Migration
This checklist covers what needs to be addressed in the accounts payable layer. It assumes you have already completed the project management migration and are now focused on the invoice approval gap.
1. Map where your purchase orders now live
If you raised POs inside WorkflowMax, they were tied to job records. In a new system, POs may live in the project management tool, in Xero (if you’ve set up purchase order management there), or nowhere at all.
Before rebuilding the approval layer, you need to know where the PO commitment sits so that incoming invoices can be matched against it. Two-way PO matching means an invoice is compared against the purchase order before it reaches the approval step. If the amounts align, the invoice moves forward. If they don’t, it’s flagged for review. That check can’t happen if the PO record and the invoice are in different systems with no connection.
2. Identify who owns invoice approval for each job type
WorkflowMax’s job ownership structure gave you an implied approval chain. Without it, you need to make the approval chain explicit. For most construction and trades businesses, this breaks into two tiers: invoices under a threshold can be approved by the office manager or bookkeeper, and invoices above a threshold need a director or project manager to sign off.
Write this down. The threshold, the role, the escalation path if the primary approver is unavailable. If you don’t have an explicit approval workflow documented, you don’t have an approval workflow: you have a process that depends on the right person being available and remembering the informal rule.
3. Rebuild your line-item coding logic
This is the part that takes longest to recover. WorkflowMax’s job categories gave you a structure for allocating invoice line items to the right accounts. Labour to one account. Materials to another. Plant hire to a third. Each cost type had a corresponding code.
In Xero or MYOB, that structure still exists in the chart of accounts, but the link between incoming invoice lines and the correct account code has to be made manually for every invoice, unless you have a tool that applies coding rules automatically based on supplier history.
The practical consequence of losing this: the same supplier gets coded differently in different months depending on who processes the invoice that week. Reporting becomes inconsistent. Job costing figures stop being reliable. GST treatment errors compound over time.
4. Re-establish your duplicate detection process
WorkflowMax’s job records made it relatively obvious when a subcontractor had already billed for a particular milestone, because the job record showed the billing history. Without that context, duplicate invoices become harder to catch. Two invoices from the same supplier for the same amount, a few weeks apart, can both make it to Xero before anyone notices.
This is not a hypothetical problem. It’s one of the most common AP errors in businesses managing construction invoices across a high volume of subcontractors.
5. Set up vendor validation for bank detail changes
This one matters more in construction than almost any other industry. The ACCC identified construction, real estate, and legal as the sectors most frequently targeted by fake invoice scams due to large transaction values and frequent invoicing. Payment redirection scams cost Australian businesses $152.6 million in 2024, up 66% year-on-year, and construction is specifically identified by the AFP as a prime target.
A Victorian construction company was defrauded of AU$900,000 in 2024 when attackers compromised a supplier’s email and sent a fake invoice with altered bank details. The email came from the supplier’s genuine address.
When WorkflowMax was live, the job record gave you historical context for a supplier’s payment details. Now, without a system that flags when a bank account number appears on an invoice for the first time, bank detail changes move through unchecked.
Vendor validation means comparing the bank details on an incoming invoice against the history in the system. If they don’t match, the invoice is held and reviewed before payment. This is a control that needs to be built into the approval layer explicitly after migration.
6. Document the exception handling process
When something doesn’t match, what happens? Who reviews it, what information do they need, and how is the outcome recorded? Exception handling is the part of an approval workflow that most businesses never formalise, because the informal version works until it doesn’t.
After a WorkflowMax migration, the informal version has often been disrupted. Document the exception path now: what triggers a hold, who reviews it, what the resolution looks like, and how the audit trail records the outcome.
What the Rebuilt AP Layer Should Look Like
The approval workflow that was embedded in WorkflowMax’s job structure needs to be a standalone layer now. That layer has four components:
Intake. All invoices come through a single point of entry, not scattered across email inboxes, WhatsApp messages, and paper documents sitting in the ute. This sounds obvious, but for trades businesses managing multiple job sites it’s often the first thing to fix.
Matching. Incoming invoices are compared against purchase orders before they reach the approval step. The PO sets the commitment. The invoice claims against it. If the amounts, quantities, or line items don’t align, the invoice is held. This is two-way purchase order matching, and it’s the control that most directly replaces what WorkflowMax’s job record used to provide.
Approval routing. Invoices are routed to the right approver based on the approval thresholds you’ve defined. The approval workflow should enforce the route automatically, not rely on someone remembering to forward an email to the right person.
Coding and publication. Once approved, invoices need to be coded accurately and pushed to Xero or MYOB. Automated line-item coding reduces the inconsistency that comes from manual decisions: the system applies the same coding logic for the same supplier every time, based on historical patterns, rather than depending on whoever is processing that invoice that week. Pulsify handles this as part of its automated line-item coding layer, which is particularly relevant for construction invoices that split across labour, materials, and equipment hire on a single bill.
The Cost of Not Rebuilding
Processing an emailed PDF invoice costs Australian businesses an average of AU$27.67 per invoice, according to ATO and Deloitte Access Economics research. For a business processing 40 invoices a week, that’s over AU$57,000 a year in processing cost alone, before accounting for errors.
The cost of errors is harder to quantify but easier to feel. A single job with miscoded materials invoices distorts the cost report for that project. A duplicate payment to a subcontractor may not be recovered. A fraudulent invoice with altered bank details that makes it through an unchecked approval process can represent months of margin from a single project.
Before Pulsify, finance teams managing 50 invoices a week were typically spending around four hours a week on coding, PO matching, and chasing GST errors. After implementing structured AP automation, that same volume takes around 15 minutes of exception review. The difference is the control layer, not the speed layer.
What Most WorkflowMax Migrations Get Wrong
Most businesses migrated the project management layer and assumed the AP process would follow. It didn’t, because the AP process was never a separate system in WorkflowMax. It was a function of the job record itself.
The result is that many businesses that completed their WorkflowMax migration in late 2023 or early 2024 are now running AP on a combination of email, manual Xero entry, and institutional memory. The approval step, where it exists, is informal. The coding is inconsistent. The audit trail is incomplete.
This isn’t a criticism of the migration decision. The project management migration was urgent because the shutdown had a hard deadline: 26 June 2024. The AP layer was not urgent because it didn’t stop working on that date. It just got worse, gradually, in ways that are hard to see until you’re looking at a reconciliation problem or an unexpected payment.
The right time to fix this was at migration. The second-best time is now.
Frequently Asked Questions
What did WorkflowMax do for invoice approvals?
WorkflowMax handled invoice approvals implicitly through its job management structure. Purchase orders were tied to job records, invoices were matched to those jobs before being pushed to Xero, and approval typically followed the job ownership chain. When WorkflowMax was retired in June 2024, that implicit approval layer went with it. Businesses that didn’t replace it explicitly are now running invoice approval on informal processes, often without a clear audit trail.
What are the best WorkflowMax alternatives for the AP layer in Australia?
The project management alternatives to WorkflowMax (ServiceM8, BuildXact, Fergus, WorkflowMax by BlueRock) replace the job management functions but not the AP approval layer. For the AP layer specifically, you need a tool that handles purchase order matching, approval routing, line-item coding, and vendor validation. These are separate to the project management tool and integrate directly with Xero or MYOB. Pulsify, ApprovalMax, and Dext are among the tools used by Australian construction and trades businesses for this layer.
Why does job costing break after a WorkflowMax migration?
Job costing relies on invoice line items being coded consistently to the right accounts: labour to the correct code, materials to another, plant hire to a third. In WorkflowMax, the job category structure informed this coding. After migration, that structure is gone, and line-item coding happens manually. Manual coding introduces inconsistency: the same supplier gets coded differently depending on who processes the invoice. Over time this distorts cost reports, makes project profitability reporting unreliable, and creates reconciliation problems at month end. Rebuilding a consistent coding layer, whether through coding rules or automated line-item coding based on supplier history, is the most important step in recovering accurate job costing after migration.
How do I handle subcontractor progress claims after WorkflowMax?
In WorkflowMax, the progress claim history was visible within the job record, which made it straightforward to compare an incoming claim against what had already been approved and what remained outstanding. After migration, that history lives in the new project management tool, but the invoice approval layer in Xero or MYOB has no direct visibility into it. The practical fix is to document the progress claim schedule for each job separately and make it available to whoever is approving invoices, or to use a tool that can pull in job context when routing invoices for approval. This is a known gap in most post-migration setups.
Is construction specifically targeted by invoice fraud in Australia?
Yes. The ACCC identifies construction, real estate, and legal as the sectors most frequently targeted by payment redirection scams due to high transaction values and frequent invoicing. The AFP notes that construction businesses are a prime BEC target because of high-value transactions, frequent invoicing, and often limited cybersecurity resources, particularly in smaller, family-run firms. Payment redirection scams cost Australian businesses AU$152.6 million in 2024, a 66% increase on 2023. A Victorian construction firm lost AU$900,000 in a single incident in 2024 when attackers altered bank details on a supplier invoice that came from a genuine email address.
What should a WorkflowMax replacement actually include for AP?
A WorkflowMax replacement for the AP layer needs: purchase order matching so incoming invoices can be compared against committed spend before approval; structured approval routing with documented thresholds; vendor validation that flags changes to supplier bank details before payment; line-item coding rules that apply consistent account allocations across invoices from the same supplier; and an audit trail that records who approved what and when. The project management tool you’ve migrated to handles the job management side. The AP layer is a separate tool that sits between invoice receipt and your accounting platform.
Related Guides
- WorkflowMax vs Modern Approval Tools in Construction Accounting
- Expense Management Software: Where Purchase Order Matching Breaks in Real Construction Environments
- What a Modern Accounts Payable System Actually Needs to Do in Australia in 2026