Invoice approval software is built around a straightforward model: invoice arrives, gets coded, gets approved, gets paid. Contract-based billing breaks this model in ways that most approval workflows were not designed to handle. When a supplier bills against a contract rather than a discrete purchase order, reconciliation is no longer a matching problem - it is an interpretation problem. And interpretation problems do not resolve themselves through faster processing.
How manual and automated contract reconciliation compare
Element | Manual reconciliation | Automated with invoice approval software |
|---|---|---|
Contract terms tracked | Spreadsheet or memory | System-level with invoice matching |
Progress claim validation | Checked against contract manually | Flagged when invoice exceeds contract value |
Variation invoices | Processed like standard invoices | Separated and routed for additional approval |
Cumulative billing tracking | Recalculated each month | Running total maintained automatically |
Retention amount tracking | Manual deduction | Calculated at line level |
Dispute resolution record | Email trail | Full audit trail linked to invoice |
Coding consistency | Depends on who’s processing | Applied from supplier history |
What contract-based billing actually looks like in practice
Standard invoice processing has a clear reference point: a purchase order. The invoice either matches the PO or it does not. Either way, the check is binary. Contract-based billing - common in construction, consulting, and facilities management - replaces that binary check with a series of judgement calls.
A progress claim from a subcontractor might reference a lump-sum contract valued at $380,000. The claim might be for 35% completion, which should equate to $133,000. But the contract specifies milestone-based payment rather than percentage-based, so the 35% figure requires verification against the actual milestone schedule. The invoice might also include a variation that was verbally approved on site but not yet documented. The retention percentage might have changed from the initial contract terms.
A bookkeeper at a Sydney construction company managing five active subcontractors described the process as ‘reading four documents simultaneously and hoping they all say the same thing.’ The invoice, the contract, the variation log, and the payment schedule each contain a piece of the answer. None of them are in the same system.
This is what contract reconciliation actually looks like before any workflow tool gets involved.
Where invoice approval workflows break under contract complexity
Most AP automation tools, including native Xero and MYOB approvals, route bills through a standard approval path. The approver sees an invoice value and a supplier name. They may see a cost code if someone has entered it. What they do not see:
Whether this invoice is within the remaining contract value
Whether the claimed percentage of completion matches what was certified on site
Whether the variation amount has formal approval documentation attached
What the cumulative payments to this supplier total relative to the contract ceiling
The approval step happens after reconciliation is supposed to have occurred. In practice, for contract-based billing, reconciliation often happens after approval - or not at all.
Three workflow failures are particularly common in Australian construction and project-based businesses:
The variation bypass. A subcontractor submits a variation as a line item on a regular progress claim. The approver sees the total invoice amount, not the variation component. Without a separate approval path for variations, additional scope gets approved at the same threshold as routine work.
The cumulative billing gap. Nothing in a standard AP workflow tracks how much has been paid to a particular supplier against a contract total. Each invoice is treated as standalone. When cumulative payments exceed the contract value, the AP system does not flag it. The next payment run catches it if someone checks manually.
The retention timing problem. Contracts often specify that a retention percentage is withheld until practical completion. This deduction needs to happen at line level on each invoice. If it is applied manually, it is applied inconsistently. If it is not applied at all, the business overpays on every progress claim until someone notices.
Why these failures persist even after automation is introduced
The optimistic assumption about AP automation is that it reduces the amount of manual decision-making in AP. For standard purchase order workflows, this holds. For contract-based billing, automation can actually obscure the problem by making the process look controlled while the underlying reconciliation remains manual.
When an invoice is auto-coded and routed to an approver in four minutes rather than 40, the speed creates an impression of control. The approver approves quickly because the process appears clean. But the question of whether this bill accurately reflects contract entitlement was never part of the workflow at all.
The ACCC identifies construction as one of the sectors most frequently targeted by false billing scams, in part because invoice values are high and the reconciliation process is complex enough that discrepancies are hard to spot. High-value invoices processed through fast workflows with no contract validation layer represent a specific risk profile.
What invoice approval software should actually do for contract-based billing
For businesses with contract-based supplier relationships, an effective approval workflow needs to handle:
Contract value tracking: Maintain a running total of payments against each contract so the approver can see remaining contract value at the point of approval
Milestone and variation flags: Route invoices claiming against unapproved variations to a separate approval path with documentation requirements
Retention calculation: Apply retention deductions at line level based on contract terms, not as a manual adjustment after the fact
Cumulative billing alerts: Flag any invoice that would cause cumulative payments to exceed the contract ceiling before it is approved
Coded approval history: Maintain an audit trail that links each payment to the specific contract line or milestone it relates to
Most standard AP automation tools do not address these functions natively. The gap is not a failing of the tools - contract management is a specialised domain. The gap is relevant to any Australian finance team that has adopted AP automation and assumed it covers contract reconciliation.
What finance teams actually do to manage this
In practice, Australian finance teams running contract-heavy AP workflows use a combination of approaches:
Spreadsheet tracking alongside the AP system. A separate spreadsheet maintains contract values, cumulative payments, and retention schedules. The AP system handles routing and approval. The spreadsheet handles reconciliation. The risk is that the two are maintained by different people and updated at different times.
Job costing tools as the reconciliation layer. Construction businesses often run a project management or job costing tool - ProCore, Buildxact, or CoConstruct - alongside Xero or MYOB. Contract reconciliation happens in the project tool; the approved amount is then entered into the accounting system. The gap is that these two systems rarely talk to each other in real time.
Approval process workarounds. Approvers add notes to invoices indicating contract status: ‘within contract,’ ‘variation approved separately,’ ‘retention adjusted.’ These notes exist as comments in the approval record. They are not enforced by the system.
None of these approaches create the closed-loop reconciliation that contract-based billing actually requires. They create a paper trail that looks like reconciliation from the outside.
Practical steps for closing the gap
Finance teams managing contract-based AP workflows can reduce reconciliation risk with these specific actions:
Maintain a contract register that records supplier name, contract value, payment schedule, variation log, and retention terms - kept by someone who is not processing invoices
Add a reconciliation step before approval that requires the person submitting the bill to confirm: (a) this invoice is within the remaining contract value, (b) any variation amounts have documented approval
Set approval routing rules by supplier type - contract suppliers should route to a separate approver from standard purchase order suppliers, with a higher review threshold
Require variation documentation as an attachment to any invoice containing a variation line item
Review cumulative payments monthly rather than per invoice - a monthly total check against each contract ceiling catches drift that individual invoice reviews miss
For teams where the volume of contract-based invoices is high enough to make manual reconciliation impractical, the question is whether the AP automation platform in use can be configured to track contract values, or whether a separate contract management layer needs to be added to the workflow.
The PO matching function in more advanced AP tools offers a partial solution - flagging when invoice values exceed purchase order amounts. For contract billing, the equivalent function is contract value tracking, which is available in some purpose-built platforms.
FAQ
What is contract reconciliation in accounts payable?
Contract reconciliation is the process of verifying that invoices from contract-based suppliers match the entitlement specified in the contract - including milestone progress, variation approvals, and retention terms. Unlike standard invoice processing against a purchase order, contract reconciliation requires tracking cumulative payments and interpreting whether claimed amounts accurately reflect work completed or delivered under the contract terms.
Why does invoice approval software struggle with contract-based billing?
Standard invoice approval software is built around purchase order matching - an invoice either matches the PO or it does not. Contract billing replaces that binary check with ongoing entitlement tracking across multiple payments. Most AP tools do not maintain contract values, track cumulative billing totals, or separate variation amounts for additional approval. These functions are typically managed outside the AP system.
How do Australian construction businesses handle subcontractor invoice reconciliation?
Most construction businesses use a combination of their project management tool (for contract tracking) and their accounting system (for payment processing). The reconciliation step happens between these two systems, often manually. The gap between them - where contract status is checked informally or not at all - is where reconciliation errors and fraud most commonly occur.
What is a progress claim and how does it differ from a standard invoice?
A progress claim is an invoice submitted by a subcontractor for work completed to a certain stage rather than for a discrete product or service. Progress claims reference a contract value and claim a percentage of completion or a specific milestone. Unlike a standard invoice, a progress claim requires validation against the contract schedule, the payment claim register, and any approved variations before it can be correctly reconciled.
What controls should be in place for variation invoices?
Variation invoices - billing for scope outside the original contract - should follow a separate approval path from routine progress claims. At minimum, approval should require: documented evidence that the variation was authorised (written instructions or a signed variation order), confirmation of the agreed variation amount, and sign-off from someone with appropriate authority. Variations processed through a standard invoice approval path without additional documentation requirements are a consistent source of overpayment and dispute.
Sources: ATO record-keeping for business · ASIC financial reporting obligations