Progress claim software,
judged by what reaches the claim.

A spreadsheet genuinely works if you run one or two jobs, the contracts use standard stages, variations are rare, and the same person prices, approves and claims. The arithmetic changes at the point where any of those stop being true. The failure is rarely the maths. It is that the claim schedule drifts from the signed contract, approved variations do not reach the claim, the evidence has to be assembled after a claim is queried, and the same numbers are re-typed into the ledger. Every one of those is an administration cost or a cash delay rather than an error you would notice. The underlying discipline is the same either way and is covered in the progress claims reference and the Australian progress claims guide.

It should make an approved variation available to include on the next relevant claim, with the builder choosing what goes on each one. This is the feature that separates the category, because unclaimed approved variations are the most common and least visible leak in residential claiming. What to test is the path rather than the promise. Record a variation, approve it, then raise a claim two stages later and see whether it appears as something you can add. If the variation register and the claim builder are separate screens joined by copy and paste, the tool has not solved it. The mechanics of variations themselves, including the contract formalities that decide whether a variation is recoverable at all, are covered in the variations reference.

It can help with the dates. It cannot supply compliance. Every state and territory has its own security of payment legislation, with its own definitions of a payment claim, its own response windows for a payment schedule, and its own consequences for missing them. Good software records when a claim was served and what came back, and prompts you as dates approach, which is genuinely useful because the regime runs on calendar days. What no software can do is decide whether a document is a valid payment claim under your state’s Act, or advise you on your position when a payment schedule is late or disputed. Be careful with any product implying otherwise. The state-by-state structure is set out in security of payment by state, and specific matters belong with a lawyer.

Yes, and it is worth being direct about it because the search results in this category do not distinguish. Most Australian progress claim software is built around residential contracting, where claims run against defined build stages such as base, frame, lockup and fixing, on a fixed-price contract with a homeowner. Civil and infrastructure claiming commonly works differently, measured against a schedule of rates and quantities completed in the period, with progressive measurement, assessment by a superintendent or contract administrator, and unfixed retention arrangements. A residential-oriented tool can be forced to represent that, usually by treating each rate item as a stage, but it is a workaround rather than a fit. If your claims are quantity-based rather than stage-based, test that specific workflow before committing, and treat civil capability as something to verify rather than assume.

Three things worth being clear about. It cannot make a claim valid. Whether the stage has actually been reached is a question about the work and the contract’s own definition of that stage, and a tidy claim for a stage that is not complete is a rejected claim with better formatting. It cannot fix a contract that was drafted badly. If the claim schedule does not match how the job will really be built, software will faithfully reproduce that mismatch every month. And it cannot supply legal compliance, as above. What it does well is remove re-keying, stop approved variations being forgotten, keep evidence attached to the claim, and shorten the gap between a stage being reached and an invoice existing. Those are cash flow gains, which is the thing worth buying it for.

Progress claims are one module of VIABUILD, the Construction Operating System for residential builders, rather than a standalone claiming tool. The claim schedule is set up against the contract once, the stages and the percentage of contract value each represents. When the build reaches a stage, Oryn drafts the claim from the job, pulling the stage value and the approved variations already on record, so you are reviewing a draft rather than rebuilding the maths. The client reviews and approves in their portal, which leaves a dated record of what was agreed. The approved claim then pushes to Xero as an invoice in one click, with tracking categories, so nothing is re-typed. Because every module shares one data model, the same job data behind the claim also feeds cost tracking and the WIP position. Full detail is on the progress claims feature page.