Construction Software for Australian Builders: Job Costing, Claims and Retention.
Custom and Odoo-based software that shows job margin early, handles GST, progress claims, retention, variations and subcontractors, and links to your accounting system.
A builder in Australia can win a job at a good margin and still lose money on it. The estimate sits in one file, costs arrive through the accounting package weeks late, variations are agreed on site and never priced, and the retention owed to you is a figure someone remembers. Construction software closes those gaps while the job is still running.
Devvista is a software development company that builds custom construction software for Australian builders and contractors: job costing, progress claims, retention, variations, subcontractor records and links to your accounting system. We also build on Odoo where an all-in-one system suits, and we say when a ready-made product is the cheaper answer. This page covers what the software must do, the Australian rules that shape it (GST, security of payment, retention) and how a build runs. To start, tell us how a job is run today.
What Construction Software Includes
Most contractors need four or five of these, added in an order that follows where money leaks today.
| Module | What it does | What goes wrong without it |
|---|---|---|
| Estimating | Builds a bid from your own rates and assemblies | Rates drift from real costs; old bids are copied with old numbers |
| Job costing | Compares labour, materials, plant and subcontract cost with budget by cost code | The loss is found after handover |
| Variations | Records the instruction, the pricing, the approval and the effect on the claim | Extra work is built and never claimed |
| Progress claims | Produces the claim from percentage complete and approved variations, and tracks what was served and paid | Claims go out late or short |
| Retention and security | Holds what is withheld from you and from your subcontractors, with release dates | Money owed sits unclaimed |
| Subcontractors | Contracts, licences, insurances, claims received, payments | A lapsed certificate found at the wrong moment |
| Site capture | Daily diaries, hours, photos and defects from a phone | Paper retyped days later |
| Accounting link | Sends costs and tax invoices to your ledger | Double entry and reports that disagree |
This is a workflow and data problem, the same kind we solve on our custom software development page. Where the main pain is retyping between tools, AI automation may be enough, and for a joined-up back office see business management software.
GST, Tax Invoices and Your Ledger
Every claim and supplier invoice in the system is also a tax document, so GST has to sit in the data model, not in a spreadsheet beside it. The facts we opened on 12 November 2026 are short.
| Rule | What the government source says | What the software does with it |
|---|---|---|
| Rate | GST is "a tax of 10% on most goods, services and other items sold or consumed in Australia" (business.gov.au) | Stores the tax code on every claim line, variation and bill, with room for lines that are not standard |
| Registration | A business must register if its GST turnover is "$75,000 or more" (same page) | Not a software matter, but the invoice template depends on whether you are registered |
| Tax invoice | Required for a taxable sale of more than $82.50 including GST, or on request; it shows the words "tax invoice", your business name, ABN, issue date, a description and the GST amount (business.gov.au, how to invoice) | Builds the claim or invoice with those fields filled from the job and company record, and blocks issue when one is missing |
Two more points. First, a claim is a legal document under the state Act as well as a tax invoice, and the rules are not the same thing. Second, subcontractor payment reporting to the ATO is a reporting task your accountant owns. We have not been able to open the ATO's own guidance for this page, so we do not state who must report or when; we build the supplier record (name, ABN, amounts) so the report can be run from it. Odoo's Australian localisation, described below, includes a report of this kind.
Security of Payment: What It Means for Your Software
Each state has its own security of payment law, and a contractor working across borders meets more than one. The time limits for claims, payment schedules and adjudication in New South Wales, Victoria and Queensland are set out, with sources, on our payment claim deadlines page. We do not repeat them here. What matters for software is what the law implies for the data you hold.
| Law implies | The system needs |
|---|---|
| A claim must be served in a set way and its date matters | A service log: who, when, how, and a copy of what was sent |
| Clocks run in business days, which differ by state | A holiday calendar per state, versioned, and the state recorded on each job |
| Rules change: Victoria's regime was overhauled in April 2026 | Rules held as dated settings so an old claim is judged by the rule in force then |
| A late or missing response can have serious consequences | Alerts that reach a named person, with an acknowledgement |
On Victoria, Baker McKenzie reported in April 2026 that "a majority of the proposed amendments to the SOP Act have now commenced", that reference dates were replaced with a statutory monthly entitlement and that performance security, including retention money, can now be claimed for release (Baker McKenzie). The article gives no timetable for the remaining parts, so we treat any later change as something to check at scoping. This is general information, not legal advice.
Retention: What We Read by State
Retention is the money a head contractor holds back from a subcontractor, and the subcontractor's own claim against it later. It is easy to lose track of, and the rules are different by state. What we read:
| State | What the source says | Source |
|---|---|---|
| New South Wales | Head contractors must hold retention money in trust on projects valued over $20 million, in an account with an authorised deposit-taking institution. The ledger goes to the subcontractor at least every 3 months or as agreed in writing, and no less than every 6 months. The page describes retention as "Usually up to 5% of the total contract value", as common practice and not a cap. Fines of up to $22,000 apply for breaches. | NSW Government |
| Queensland | Project trust accounts apply by contract price: $1 million or more excluding GST (Group 1) and $10 million or more (Group 2). If project trust work is 50% or less of the contract price, no project trust account is needed. Retention trust accounts are needed only where the head contract needs a project trust account and cash retentions are withheld. The page was last reviewed on 16 May 2022, so confirm current thresholds. | QBCC trust account rollout |
| Victoria | Retention money counts as performance security that can be claimed for release under the amended Act. The summary we read does not mention a trust scheme. | Baker McKenzie |
We have not verified retention rules for Western Australia, South Australia, Tasmania, the ACT or the Northern Territory, so a project there starts with research, not a guess. Software cannot decide whether a trust applies to your contract. It can hold the contract value, the retention terms and the release dates, produce the ledger a subcontractor is owed and warn you when a release is near.
Job Costing That Shows the Loss Early
The job cost report is the point of the whole system, so it is worth being exact about what it needs. Our usual design:
- Cost codes shared across estimate, budget and ledger, so a figure means the same thing in all three.
- Commitments, not only actuals. A signed subcontract or purchase order is cost you will pay. Showing committed cost beside paid cost is what lets you act early.
- Forecast to complete, entered by the project manager and compared with the budget each month.
- Variations linked to cost. Approved variations adjust the contract value; unapproved ones show as exposure.
- One lock date. After month end the figures freeze, so reports do not change under you.
The part that most often disappoints is the timesheet. If the crew's hours arrive a fortnight late, labour is always behind, and the report is wrong in the same direction every time. That is why site capture on a phone is usually early in the plan, not last.
Variations Without Lost Revenue
A variation is a small contract inside the contract, and it needs the same discipline: an instruction, a price, an approval and a claim. A workable flow:
- The instruction is logged with who gave it, the date and a photo or document.
- A price is built from your rates and sent for approval, with the time effect if any.
- Approval, rejection or a dispute is recorded against the variation.
- Approved variations flow into the next progress claim; unapproved ones stay in an exposure list the project manager sees each week.
- Closed variations appear on the final account with their trail.
We do not interpret your contract. The approval rules (who may approve, by when) are entered from the contract at set-up and checked by a person. The system makes the step visible so that it is not skipped.
Subcontractor Records and Compliance
Subcontractors are where cost, compliance and cash flow meet. A good subcontractor record holds the contract and its retention terms, the licence and insurance documents with expiry dates, the claims received and their status, and what has been paid. Expiry alerts are the simplest win: a certificate that lapses on a Tuesday should be on someone's list before Tuesday. If you also receive claims from subcontractors, the same service log used for your own claims applies; see the deadline tracker design for how we propose to approach it.
The Odoo Option and the Australian Localisation
Some contractors want one system for jobs, purchasing, accounting and payroll instead of several connected tools. Odoo is one option we build on. We build Odoo systems for clients under NDA, so we do not name them or show them. Our Odoo implementation for Australia page covers that work in general.
What the Odoo documentation (version 18, opened 12 November 2026) says about the Australian localisation, and what it means for a contractor:
| Odoo documentation says | Why a contractor cares |
|---|---|
| Standard GST rate of 10%, with tax variants for cases such as exports, capital purchases and imports | Claims and bills carry the right tax code from the start |
| A BAS report built from pre-configured tax grids | The activity statement figures come from the same ledger as the jobs |
| A Taxable Payments Annual Report that "can be exported to multiple formats: PDF, XLSX, and TPAR" | Subcontractor payments reportable from the records; whether you must report is for your accountant |
| A payroll module with PAYG withholding components | Wages for site staff in the same system |
| "Odoo is compliant with Australia's Peppol requirements"; the invoice XML must be uploaded manually to a Peppol network | Useful if your clients ask for e-invoices; plan the upload step |
| ABA files for batch payments | Pay a run of subcontractors from the bank file the system produces |
Odoo's Project app is described in its documentation as "a tool to manage your ongoing projects", able to schedule tasks and track each project's profitability (Odoo Project documentation). The localisation details are on the Australian localisation page. Whether Odoo covers your estimating, progress claims by schedule of values or retention ledger as it comes, or needs custom modules, is the first thing we test at scoping. Often the answer is a mix: Odoo for the ledger and purchasing, custom screens for claims and retention.
Custom, Odoo or Ready-Made: How to Decide
We would rather tell you now when a ready-made platform is the better buy. The usual dividing line:
| Situation | We would suggest |
|---|---|
| Your process matches a mainstream construction product and you only need a licence and set-up | Buy it. Custom work costs more than the gap it closes |
| Your claims, retention or variation rules do not fit a standard product | Custom screens on top of your ledger, or Odoo with modules |
| The pain is retyping between two tools that already work | An integration or automation, not a new system |
| You want one system for jobs, purchasing, accounts and payroll | Odoo, with local set-up and a staged roll-out |
| You need only a phone app for site diaries and defects | A focused mobile app that sends data to your existing system |
We have no published construction case study, so we do not show one. Delivered work in other areas is on the case studies page.
How a Build Runs and What Moves the Quote
We usually begin with the one module that hurts most, often job costing or progress claims, and add others once it is trusted.
- Discovery. On video we follow one job from bid to final account with the estimator, project manager, site supervisor and bookkeeper.
- Written scope and quote. The first module, the states in scope, integrations, data to bring across and what waits.
- Prototype. Screens for office and site, plus the rules tables for tax and retention, reviewed with your accountant or adviser.
- Build and test on a finished job. We usually propose a staging copy loaded with a closed job, so the report can be checked against what you know happened.
- Pilot on one live job beside the old method.
- Roll-out and handover. Training, documentation and accounts in your name.
The proposal sets out a dated plan. We do not publish prices. What moves a quote:
| Driver | Why it matters |
|---|---|
| Modules in the first release | Each adds screens, rules and tests |
| States and rule sets | Each state adds calendars, retention and claim rules to configure |
| Accounting system and integration | Cost codes, suppliers and tax codes must map both ways |
| Data migration | Old jobs and supplier records need cleaning before loading |
| Offline site capture | Needs sync and conflict handling where signal is poor |
| Third-party fees | Hosting and licences are set by those vendors and listed separately |
After a short call we scope the build with you, starting from the budget range you have in mind. We do not promise a profit improvement. We aim to show job margin earlier so you can act.
Who This Suits and Your Next Step
We suit Australian builders, trades and civil contractors who know which part of the job runs on paper or memory and want to own the fix.
| A good fit | Probably not |
|---|---|
| Your process does not fit a standard product | A ready-made platform already covers it |
| You work across states and need rules by date | You want legal advice on a claim, which only a construction lawyer can give |
| A project manager and your bookkeeper will help test | You want every module on day one |
| You welcome hearing that a bought product would do | The lowest quote alone will decide |
Related Australia pages: warehouse software for yards and supply stores, fleet management for vehicles and plant, manufacturing ERP for prefab and joinery, POS software for trade counters and the Australia home page. Ready to talk? Use the contact form or book a call.
Straight Answers.
Tell us how a job runs today
Describe your jobs, the states you work in and the tools you use now. Book a call and we will say what to build, what to buy and what to leave alone.
- 30-minute online call
- Honest feedback on fit
- No obligation
- Book a call30 minutes online. Tell us what you want to build.
- Get a straight answerHonest feedback on fit and scope.
- DecideYou choose the next step once the scope is clear.