The consulting partner at a mid-tier engineering firm in Brisbane opens a subcontractor invoice for AU$18,400. It covers structural design work across three client projects, billed at blended hourly rates for two different engineers. There is no purchase order to match it against. There is no delivery docket. There is no physical goods receipt. There is a brief scope description, a timesheet summary, and a total.
The partner knows the work happened. She is fairly sure the rates are correct. She is less sure whether the hours on the invoice match the hours her project managers authorised, or whether the allocation across the three projects is right. She approves it anyway, because the alternative is spending 40 minutes pulling project records, and she has client work to do.
This scene plays out daily in consulting firms, law practices, accounting businesses, and IT services companies across Australia. Professional services AP is structurally different from the manufacturing and wholesale workflows that most AP systems were designed to handle — and the gap between what these firms need and what their tools provide is where errors accumulate quietly.
Why professional services AP does not follow the standard model
The textbook AP workflow assumes a purchase order, a goods receipt, and an invoice. You match the three, resolve any variances, code the expense, and approve payment. This three-way matching model works well when you are buying steel, chemicals, or stock.
Professional services firms buy very little that fits this model. The largest cost lines in a consulting or legal practice are people costs — salaries, subcontractor fees, and specialist engagement costs — followed by software subscriptions, office expenses, and travel. None of these involve physical goods. None generate a goods receipt. Most do not have a purchase order in any formal sense.
The result is that standard AP controls do not apply in their original form. There is nothing to three-way match. There is no goods receipt confirmation to trigger payment approval. The validation that matters in professional services — did this work actually happen, was it authorised, and is it allocated to the right project — requires a different kind of evidence and a different process to collect it.
This does not mean professional services firms need fewer controls. If anything, they need more. The absence of physical evidence makes it easier for incorrect invoices to pass through undetected. A manufacturer notices when raw materials do not arrive. A consulting firm may not notice when a subcontractor invoices for hours that were never worked or allocates time to the wrong project.
The subcontractor invoice problem
Subcontractor costs are the single largest source of AP complexity in professional services. A mid-sized consulting firm with 30 to 50 staff might engage 10 to 15 subcontractors at any given time, each invoicing monthly or fortnightly. The invoices arrive in varied formats — some with detailed timesheets attached, some with a single line item and a total.
The verification challenge is straightforward to describe and difficult to execute: does the invoiced work match what was authorised and what was actually delivered?
In a law firm, a barrister’s invoice for AU$6,500 covers three days of court preparation and one day of appearance. The managing partner needs to confirm those days against the matter file. In an engineering consultancy, a specialist subconsultant invoices AU$22,000 for geotechnical analysis across two project sites. The project engineer needs to confirm the scope was completed and that the time allocation between the two sites is accurate.
Neither of these checks can be automated in the way that a PO-to-invoice match can be automated. They require someone with project knowledge to review the invoice against internal records. The question is whether the AP process makes that review easy or hard.
In most professional services firms, the process makes it hard. The subcontractor invoice arrives as a PDF. The project records sit in a separate system — a practice management tool, a project management platform, or a spreadsheet. The approver has to manually cross-reference the two. When the invoice covers multiple projects, the cross-referencing multiplies.
The practical effect is that subcontractor invoices are either approved without adequate verification (fast but risky) or held up while project managers find time to check them (safe but slow). Neither outcome is acceptable when subcontractor costs represent 20 to 35 percent of a firm’s total expenditure.
Multi-project cost allocation
A single subcontractor invoice that needs to be split across multiple projects is one of the most common and most poorly handled scenarios in professional services AP.
Consider an IT consulting firm that engages a cybersecurity specialist. The specialist works across three client engagements in a month and submits one invoice for AU$14,000, with a breakdown showing 40 hours on Client A, 25 hours on Client B, and 15 hours on Client C. The total is correct. The rates are correct. The problem is making sure the cost allocation flows through to the right client projects in the accounting system.
In Xero, this requires creating three separate line items on the bill, each coded to a different tracking category. If the firm also needs to allocate by cost type — distinguishing between technical work and project management, for example — and Xero’s two tracking category dimensions are already used for client and project, there is nowhere to put the third dimension. The allocation either loses detail or gets tracked in a spreadsheet outside the accounting system.
MYOB’s job costing module provides more allocation flexibility. A single bill can be split across multiple jobs at the line level. But the allocation still requires manual entry. When a firm processes 60 to 80 subcontractor invoices per month and a third of them require multi-project splits, that manual allocation work is substantial — and the risk of miscoding is proportional to the volume.
The downstream consequences of incorrect project allocation are not just accounting problems. They affect client profitability analysis, project budget tracking, and — in firms that bill costs through to clients — the accuracy of client invoices. An engineering consultancy that allocates AU$5,000 of subconsultant costs to the wrong project is not just misstating its internal reports. It is potentially under-billing one client and over-billing another.
Retainer management and drawdown tracking
Many professional services firms work on retainer arrangements — a client pays a fixed monthly or quarterly amount, and the firm draws down against that balance as work is performed. From an AP perspective, the challenge is symmetrical: when the firm itself pays a subcontractor or specialist on a retainer basis, it needs to track cumulative charges against the retainer balance.
The typical scenario: a law firm engages a forensic accountant on a six-month retainer of AU$60,000. The forensic accountant invoices monthly against the retainer. After four months, AU$48,000 has been drawn down. The remaining AU$12,000 will not cover the expected work in months five and six.
In a well-structured process, someone notices this at month four and either renegotiates the retainer or seeks client approval for additional costs. In a poorly structured process, nobody notices until the forensic accountant’s month-five invoice pushes the total past AU$60,000, the client queries the overage, and the firm discovers it has been absorbing costs it cannot recover.
Neither Xero nor MYOB provides native retainer drawdown tracking in the AP workflow. Retainers are typically recorded as prepaid expenses or liabilities, but the accounting system does not monitor the cumulative position against the original balance. Monitoring happens in spreadsheets, practice management systems, or — most commonly — in the memory of the partner managing the engagement.
Approval complexity in partnerships
Professional services firms — particularly law firms, accounting practices, and engineering consultancies — often operate as partnerships or have partnership-style governance. This creates approval structures that do not map neatly to a standard hierarchical workflow.
A subcontractor invoice might require approval from the cost owner (the partner managing the project), the practice group head (who manages the group’s budget), and the finance team (who checks coding and compliance). These are not sequential approvals in a simple chain. The cost owner and the practice group head may be the same person on some invoices and different people on others. The finance review may happen before or after partner approval depending on the invoice value.
In a firm with 8 to 12 partners, each managing different matters, the approval routing for a single invoice depends on which project it relates to, which partner owns that project, and whether the invoice exceeds the partner’s individual approval threshold. A flat approval workflow — where invoices above AU$5,000 go to a senior partner — does not reflect the reality that the relevant senior partner changes depending on the matter.
This is why professional services firms often default to email-based approvals. Email is flexible enough to route invoices to whoever needs to see them. But email provides no tracking, no audit trail, and no enforcement of approval thresholds. Invoices get lost in inboxes, approved by the wrong person, or approved twice by two people who each assumed the other had not yet reviewed it.
The timesheet reconciliation challenge
For firms that track internal time — which includes most law firms, many consulting firms, and a growing number of engineering practices — subcontractor invoices create a reconciliation problem that sits outside the standard AP workflow.
The subcontractor’s timesheet says they worked 120 hours on a project in March. The firm’s internal resource plan allocated 100 hours of subcontractor time to that project in March. The variance is 20 hours. Is it legitimate scope growth, or did the subcontractor overstate their hours?
Answering that question requires comparing the subcontractor’s invoice against the firm’s project records — which sit in a practice management system, not in the accounting system. The AP team can verify the arithmetic on the invoice, but they cannot verify the underlying hours without input from the project manager.
In firms where this reconciliation happens consistently, it typically adds 15 to 30 minutes per subcontractor invoice. For a firm processing 40 subcontractor invoices per month, that is 10 to 20 hours of reconciliation work — performed by project managers whose billable time is worth AU$250 to AU$400 per hour. The cost of the reconciliation process itself is significant.
In firms where the reconciliation does not happen consistently — which is most firms — the variance between authorised and invoiced hours accumulates silently. It surfaces at project completion, when the final margin analysis shows costs that exceed the budget by 10 to 15 percent and nobody can explain exactly where the overrun occurred.
GST traps in professional services
Professional services firms encounter several GST scenarios that differ from goods-based businesses and that create specific AP coding risks.
International consulting fees. When an Australian firm receives services from an overseas consultant, the reverse charge mechanism under Division 84 of the GST Act may apply. The firm must self-assess GST on the imported service and can generally claim the input tax credit on the same BAS — but only if the coding is correct. Getting this wrong does not create a net tax liability in most cases, but it does create an incorrect BAS that the ATO may query on review.
Travel recharges. Subcontractors and employees incur travel costs that are recharged to clients. The GST treatment of the recharge depends on whether the firm is acting as agent (passing through the supplier’s tax invoice) or principal (issuing its own tax invoice for the recharged amount). Many firms treat all travel recharges the same way, which is incorrect when the mix includes GST-free items like international airfares alongside GST-inclusive items like domestic accommodation.
Disbursements. Law firms and accounting practices regularly incur disbursements on behalf of clients — court filing fees, search fees, government charges. Some of these carry GST; some are GST-free. The firm’s AP coding of the original expense needs to reflect the correct treatment, and the subsequent recharge to the client needs to carry the corresponding GST treatment. When the original expense is miscoded, the error propagates to the client invoice and ultimately to the BAS.
Software subscriptions with overseas suppliers. Professional services firms are heavy users of cloud software — project management tools, design software, collaboration platforms. Many of these are supplied by overseas vendors. The GST treatment depends on whether the supplier is registered for Australian GST (most large vendors are, since the 2017 changes to the GST Act) and whether the supply is a B2B or B2C transaction.
These are not unusual scenarios. They are the normal operating environment for a mid-sized professional services firm. A practice with 30 staff might process 15 to 20 invoices per month that require non-standard GST treatment. If the AP process does not flag these for review, the errors accumulate and surface at BAS lodgement — or worse, at ATO audit.
The high-volume, low-value problem
Professional services firms also deal with a steady flow of recurring invoices that are individually small but collectively significant: software subscriptions, office supplies, printing, telecommunications, insurance, professional memberships. A firm with 40 staff might have 50 to 70 recurring supplier invoices per month, each under AU$500.
These invoices still need to be coded, approved, and allocated. They still carry GST that needs to be treated correctly. They still need to be matched to the right cost centre or project if the firm allocates overheads.
The temptation is to process these on autopilot — same coding as last month, same approval, same account. That works until the software vendor changes its pricing, the telecommunications provider adds a new charge, or a subscription auto-renews that should have been cancelled. At AU$200 to AU$500 per invoice, these individual errors are small. Across 50 to 70 invoices per month, they add up.
The challenge is building an AP process that handles high-volume, low-value invoices efficiently without sacrificing the oversight needed to catch changes. Automated coding rules that replicate the previous month’s treatment, combined with exception flags for invoices that differ from the expected amount by more than a set threshold, are the practical solution.
Where Xero and MYOB fall short for professional services
Both Xero and MYOB are capable general ledger systems. They handle bill entry, payment processing, and financial reporting well. But their AP workflows were designed around the assumption that invoices relate to purchased goods or clearly defined services with purchase orders behind them.
For professional services firms, the gaps are specific:
- Xero’s tracking categories are limited to two dimensions, which is insufficient for firms that need to track by client, project, cost type, and office.
- MYOB’s job costing requires manual line-level allocation and does not connect to external practice management or time tracking systems.
- Neither system provides retainer balance monitoring or cumulative drawdown alerts.
- Neither system supports the kind of conditional approval routing that partnership structures require — where the approver depends on the project, not just the invoice amount.
- Neither system connects subcontractor invoices to internal time or resource records for verification.
These are not criticisms of Xero or MYOB. They are accounting systems, not practice management systems. The gap exists because professional services AP requires information that lives outside the accounting system — in project records, timesheets, engagement letters, and resource plans. Bridging that gap is the specific challenge.
Structuring AP for professional services
Connect invoices to project records at the point of capture
When a subcontractor invoice is received, the first step should be linking it to the relevant project or matter — before coding, before approval routing, before anything else. That link determines who approves it, how it is coded, and which budget it draws from.
Build approval routing around project ownership
Approval workflows should route invoices based on the project they relate to, not just the dollar amount. A AU$3,000 subcontractor invoice on Partner A’s matter should go to Partner A, regardless of whether AU$3,000 is above or below a general approval threshold.
Track retainer balances proactively
Retainer drawdown tracking should be automated at the AP level. When a new invoice is processed against a retainer, the system should compare the cumulative charged amount to the retainer balance and alert the responsible partner when the balance falls below a defined threshold — typically enough to cover one more month of expected work.
Automate recurring invoice verification
For high-volume, low-value recurring invoices, set expected amounts based on historical patterns. Flag invoices that deviate from the expected amount by more than a defined percentage. Auto-code invoices that match expectations and route exceptions for review.
Enforce GST rules at the coding stage
For invoices from overseas suppliers, travel recharges, and disbursements, apply GST coding rules at the point of invoice entry rather than relying on the person processing the invoice to remember the correct treatment. Rules-based coding is not a guarantee of accuracy, but it catches the most common errors before they reach the ledger.
Signs your professional services AP process needs attention
- Subcontractor invoices are routinely approved without cross-referencing project records or timesheets
- Project profitability reports are not trusted because cost allocation is inconsistent
- Retainer overruns are discovered after the fact rather than flagged proactively
- The same recurring invoices are manually coded and approved every month
- GST treatment on international services or disbursements varies depending on who processes the invoice
- Month-end close involves correcting project cost allocations that were wrong at the point of entry
- Partners approve invoices by email with no audit trail
If several of these describe your firm, the cost is not just processing time. It is margin leakage on projects, inaccurate client billing, and GST risk that compounds with every BAS period.
For more on how Pulsify handles AP automation for services businesses, including approval workflows and automated line-item coding, see the feature overviews.
Sources: ATO - GST and Imported Services · ASBFEO - Small Business Counts · ATO - E-invoicing and Invoice Processing · Law Council of Australia - Regulatory Framework
Further reading: BAS Preparation and AP: How Coding Errors Create GST Risk · Automated Line-Item Coding for Mixed GST and Split Invoices · How Subcontractor Invoice Approvals Differ From Standard SMB Workflows