Accounting · Xero
Construction software for Xero,
chosen on the integration, not the badge.
Most Australian builders already run Xero and are not looking to leave it. The real question is what sits on top and how well the two are joined. This page is the buying guide, what a genuine two-way sync has to do, how to judge an integration without taking a marketplace listing at face value, the questions to ask before you connect your organisation, the limits of running two systems, and how VIABUILD works with Xero as the ledger.
01 / The direct answer
What you are actually choosing
You are choosing a construction system to sit on top of Xero, not a replacement for it. Xero stays the ledger, the statutory record and the place your bookkeeper and accountant work. The construction system holds what a general ledger has no concept of, the job budget, purchase orders and committed cost, progress claims, retentions, variations, the programme and the site record. The integration between them is what decides whether that arrangement removes work or adds it, which is why the integration deserves more of your evaluation than it usually gets.
If you have not yet worked out why a builder needs a layer on top of Xero at all, read Xero for construction first. It covers what Xero does well, where general-ledger accounting stops short of a construction business, and what the layer has to do. That is the explainer. This page assumes you have reached the buying decision and are comparing the options.
If the prior question is still open, whether to keep your ledger and add a layer at all or move to a system that carries its own accounting, that comparison is set out on construction accounting software. This page assumes you are keeping Xero.
02 / The standard
What a genuine two-way sync has to do
Six behaviours. Every one of them is describable in plain words by a vendor who has built the integration, and every one is checkable in a demo on a connected test organisation.
Contacts that stay one list
Your suppliers and subcontractors exist in both systems the moment you connect them. If the two lists are maintained separately you will end up with duplicates, near-duplicates and bills coded to the wrong entity. Ask how contacts are matched on first connection and what happens when a new supplier is created on either side.
Tracking categories applied on the way through
Job-level reporting in Xero depends on tracking categories, and they are only useful if something applies them consistently. A construction system that pushes bills without setting the tracking category has moved the coding problem rather than solved it. Confirm which category and option is applied and whether you control the mapping.
Bills and invoices treated as different things
Cost flows one way, revenue flows the other. Approved supplier bills should reach Xero as bills, and approved progress claims should reach it as sales invoices. A connector that only handles one direction leaves half the double entry in place, which is usually the half you notice at BAS time.
GST handled once, not twice
The tax treatment on a line has to be the same in both systems, or your BAS becomes a reconciliation exercise. Ask specifically how GST codes map, what happens with a mixed-treatment invoice, and whether rounding is done in the construction system or the ledger.
No double entry in either direction
The test is simple and worth running literally. Enter a supplier bill once and count how many places a human touches it before it is posted. If the answer is more than one, the integration is a file transfer with a nicer name, and your bookkeeper will keep working the way they do now.
A clear rule about which system owns what
Two-way does not mean everything is editable everywhere. Good integrations state plainly which system is authoritative for each object, and what happens when something is changed on the other side. Vagueness here is where reconciliation work is created, so ask for the rule in words before you connect anything.
The word to be careful with is integration, because it covers a range from a nightly one-way export of totals through to a native two-way sync of individual bills and invoices with job coding applied. Both are described using the same vocabulary, and a listing in an app marketplace tells you a connection exists rather than what it does. Ask for the object-by-object list, then watch a bill and a claim actually go across. Four minutes of demonstration settles more than any amount of integration copy.
03 / The conversation
Questions worth asking before you connect anything
Six questions, and the second one is the one to insist on. Bring your bookkeeper to the demo, because they will find the friction faster than you will.
- 01
Which objects sync, in which direction, and on what trigger
Ask for the actual list. Contacts, bills, sales invoices, payments, tracking categories, chart of accounts. Then ask which direction each moves and what causes it to move, approval, a schedule, or a manual push. A vendor who can answer this crisply has built an integration. A vendor who answers with the word seamless has built a badge.
- 02
Show me a bill and a claim go across, live
In a demo, on a connected test organisation, watch a supplier bill land in Xero with the tracking category on it, and watch an approved claim land as a sales invoice. This takes four minutes and it is the single most informative thing you can ask for in this evaluation.
- 03
What does my bookkeeper have to change
Bring the person who does your books to this conversation, because they will find the friction before you do. Where do they code bills now, where will they code them after, and which of their existing month-end steps disappears. If nothing about their week changes, nothing about your double entry has changed either.
- 04
What happens to my existing Xero data on connection
Whether historic bills and invoices are imported, ignored or duplicated, and whether the connection can be run on a trial organisation first. Ask what a disconnection does. You want to know that you can unplug the construction system and leave Xero intact and correct.
- 05
How are Australian GST and BAS handled specifically
This is worth asking directly of any product with an international origin, without assuming the answer either way. Whether GST codes map, how a mixed-treatment invoice behaves, and whether the product is used by Australian builders lodging BAS today. Ask for a customer reference in Australia rather than a claim about localisation.
- 06
What is not synced, and what is on a roadmap rather than shipped
Ask what does not sync today. Every integration has a boundary, and a vendor willing to name theirs is easier to trust on the rest. Treat roadmap answers as not shipped, and if a feature is load-bearing for your decision, ask to see it working before you sign rather than after.
04 / Comparing options
How to compare platforms on Xero fit
A common version of this search is a specific pairing, a builder wondering how a particular construction platform works with Xero. It is a fair question and it has a frustrating answer, which is that integration behaviour is exactly the kind of thing that changes between releases and between regions, so anything written about a competitor’s current sync goes out of date quickly and confidently repeating it would be doing you a disservice. What we will not do on this page is characterise how any other vendor’s Xero integration behaves today.
What holds up instead is a scoring sheet of capability categories you take to each vendor. Which objects sync and in which direction. Whether tracking categories are applied automatically or set manually afterwards. Whether progress claims become Xero invoices or have to be raised separately in Xero. How GST is mapped and what happens on a mixed-treatment invoice. Whether the sync is native or runs through a third-party connector, and who supports it when it breaks. And whether the product is in daily use by Australian builders lodging BAS. Score those per product from the vendor’s own demonstration, and treat anything you cannot see working as unverified.
Where we can be specific is about ourselves. If you are weighing VIABUILD against a particular platform, the differences we do claim are set out on our comparison pages, for example VIABUILD vs Buildertrend, and even there the right move is to confirm the other product’s current integration behaviour with that vendor rather than with us. The wider evaluation process, beyond accounting fit, is in the guide to choosing construction software.
05 / Honest limits
What running two systems actually costs you
Four things nobody puts in the integration copy, and all four are manageable if you plan for them.
You are running two systems. That is two subscriptions and one connection that can fail, so ask how a sync error surfaces and who is expected to notice it. The integration is only as good as your Xero setup, and a chart of accounts and tracking category structure that has grown organically for six years usually needs tidying before it will carry job coding cleanly. That work is real, it belongs to your bookkeeper, and it is almost never scoped in an implementation quote.
Job cost structure and account structure are different shapes. Tracking categories give you job-level reporting inside the ledger, which is useful, but cost code level detail, committed cost and forecast final cost live in the construction system, and you should expect to read job cost there. Trying to make Xero the place you read job cost is the thing the layer exists to avoid, and the distinction is set out in job cost reporting. And an integration does not fix coding discipline, it accelerates it. Bills coded inconsistently today will arrive in Xero inconsistently and sooner, which is an argument for tightening accounts payable alongside the software change rather than expecting the software to do it.
06 / How VIABUILD does it
The build in VIABUILD, the ledger in Xero
VIABUILD does not try to replace Xero. It is the Construction Operating System for the build, jobs, budgets, purchase orders, accounts payable, cost tracking and claims on one data model, and Xero stays your accounting ledger. The integration is native and two-way. Approved supplier bills push to Xero as draft bills with tracking categories applied, so cost lands against the right job in your accounts rather than as a lump. Approved progress claims and variations push to Xero as invoices. Contacts and the data that should match stay aligned across the two systems.
It is built around Australian GST and BAS workflows rather than adapted from an overseas connector, and because VIABUILD runs on one data model the same coded actuals that reach Xero also feed cost tracking, so budget against committed against actual stays current as bills land. Your bookkeeper keeps working in Xero and nothing is re-typed between the two.
One thing to be straight about. The accounting integration is Xero only. There is no MYOB integration today, so if your ledger lives in MYOB, talk to us before you switch and we will tell you honestly where that stands rather than sell you a roadmap. Full detail on what syncs is on the Xero integration page.
07 / FAQ
Common questions.
It is a construction system that runs the build side of a building business and connects to Xero rather than replacing it. Xero stays the accounting ledger, the statutory record and the place your accountant works. The construction system holds the things a general ledger has no concept of, the job budget, purchase orders and committed cost, progress claims and retentions, variations, the schedule and the site record. The two are joined by an integration so that supplier bills and progress claims move between them without being typed twice. Xero construction software, construction Xero add on and Xero for construction company all describe the same arrangement. What Xero itself does well and where general-ledger accounting stops short is explained in full in the Xero for construction reference, which is the better starting point if you have not made that distinction yet.
For most Australian residential builders, no, and it is worth understanding why the question keeps coming up. Xero is doing a job that is genuinely well suited to it, the general ledger, bank reconciliation, payroll, GST and BAS, and it is the system your accountant and bookkeeper already know. Replacing it means retraining them, migrating history and taking on a compliance-critical migration for no gain on the build side. The problem builders actually have is not that Xero is bad at accounting, it is that accounting is not job cost control. The sensible arrangement is to add the construction layer and keep the ledger. The exception is a builder whose accounting needs have genuinely outgrown a small-business ledger, and that is a conversation with your accountant rather than a software comparison.
Six things, and they are all checkable in a demo. Keep contacts as one list rather than two drifting ones. Apply tracking categories on the way through, so cost lands against the right job in Xero rather than as a lump. Treat bills and sales invoices as different objects moving in different directions, cost out of the construction system into Xero as bills, revenue out as invoices. Handle GST once, with a stated mapping, so the BAS is not a reconciliation exercise. Remove double entry rather than relocate it, which you test by entering a bill once and counting how many humans touch it. And state clearly which system owns which object, so it is defined what happens when something is edited on the other side. An integration that cannot describe all six in plain words is worth testing harder rather than trusting.
Compare capability categories rather than marketing claims, and verify the specifics with each vendor directly, because integration behaviour changes between versions and between regions and anything written about it goes out of date quickly. The categories worth scoring are the objects synced and their direction, whether tracking categories are applied automatically, whether progress claims become Xero invoices or have to be raised in Xero separately, how GST is mapped, whether the sync is native or runs through a third-party connector, and whether the product is in daily use by Australian builders. Score those on a page for each shortlisted product, then ask each vendor to demonstrate the two or three that decide your choice. If you are weighing us against a specific product, our comparison pages set out where we differ, and you should still confirm the other vendor’s current behaviour with them rather than with us.
No, and this is the most common misreading in the category. A listing in an app marketplace tells you a connection exists. It does not tell you which objects move, in which direction, whether tracking categories are applied, or whether your bookkeeper still has to touch each bill. Integrations range from a nightly one-way export of totals through to a native two-way sync of individual bills and invoices with job coding applied, and every one of them can be described using the same words. The only reliable way through this is to ask for the object-by-object list and then watch a bill and a claim actually go across on a connected test organisation. Four minutes of demonstration is worth more than any amount of integration copy.
Four worth knowing before you commit. You still run two systems, which means two subscriptions and a connection that can break, so ask how sync failures are surfaced and who notices. The integration can only be as good as your Xero setup, and a chart of accounts and tracking category structure that has grown organically for six years will need tidying, which is real work that is rarely scoped. Job cost structure and account structure are different shapes, so tracking categories give you job-level reporting in the ledger but the cost code detail lives in the construction system, and you should expect to read job cost there rather than in Xero. And an integration does not fix bad coding discipline, it moves it faster. If bills are coded inconsistently today, they will arrive in Xero inconsistently and sooner.
VIABUILD is the Construction Operating System for the build and does not try to replace Xero, which stays your accounting ledger. The integration is native and two-way. Approved supplier bills push to Xero as draft bills with tracking categories applied, so cost lands against the right job in your accounts. Approved progress claims and variations push to Xero as invoices. Contacts and the data that should match stay aligned across the two systems, and it is built around Australian GST and BAS workflows rather than adapted from an overseas connector. Because VIABUILD runs on one data model, the same coded actuals that go to Xero also feed cost tracking, so budget against committed against actual stays current as bills land, with no double entry along the way. One thing to be straight about, the accounting integration is Xero only. There is no MYOB integration today, so if your ledger lives in MYOB the honest answer is to talk to us before you switch rather than take a roadmap promise.
08 / Keep reading
Keep reading on Xero and the build
The explainer behind the decision, the accounting references, the product pages and the comparison.
Keep the ledger. Add the build.
VIABUILD runs the build on one data model and syncs natively with Xero, bills across with tracking categories, approved claims across as invoices, GST and BAS handled the Australian way. Your accountant never leaves Xero.