AI Bookkeeping Albury-Wodonga
The Border problem nobody else in Australia has to solve twice
Albury-Wodonga is the only place in the country where a genuine city of around 100,000 people is cut in half by a state border. Roughly 56,000 live on the Albury side in New South Wales and a little over 45,000 on the Wodonga side in Victoria, with a regional catchment closer to 200,000 once you take in Corowa, Howlong, Jindera, Culcairn and Holbrook to the north and Beechworth, Yackandandah, Chiltern, Rutherglen, Tallangatta and the Kiewa Valley to the south. People cross the Lincoln Causeway to get to work without thinking about it. The two councils between them carry something over 8,000 actively trading businesses, and a large share of the employers among them have staff living on the other side of the river from where the payroll is run.
That is a small geographic detail with an outsized compliance consequence, and it lands squarely on the bookkeeper. One employer, one roster, one pay run, and then two of nearly everything downstream. Wages have to be apportioned between two payroll tax regimes with different rates, different thresholds and a Victorian regional employer concession that only applies while enough of the wage bill stays regional. Workers compensation means an icare New South Wales policy and a WorkSafe Victoria policy, with two classification systems, two definitions of rateable remuneration and two declaration cycles. Long service leave runs on two statutes with different qualifying periods. Even the public holiday calendar splits: the Wodonga half of the workforce gets the Melbourne Cup and the Friday before the AFL Grand Final, the Albury half does not.
Layer the local industry mix on top and the reason this is a bookkeeping problem rather than an advisory one becomes obvious. The Hume Highway carries the freight task between Australia's two largest cities straight through the middle of town, and the region has built around it: the rail hub and industrial estates north of Albury at Ettamogah, refrigerated and general linehaul operators, warehousing, and the owner-drivers who subcontract to all of them. Add food and beverage manufacturing on the Wodonga side, Bandiana's defence logistics presence, two university campuses, a cross-border health service, and the vineyards, dairies and timber businesses in the hills behind. Almost none of these clients are simple, and a striking number of them employ across the river.
Practices here do not get the compliance wrong because they do not know the rules. They get caught because the rules only bite once the ledger is current, and the ledger is usually three weeks behind. A dedicated AI attacks that end of it. It codes and reconciles Xero and MYOB nightly, tags every employee to the jurisdiction that actually governs them, and keeps both sets of numbers assembled as the year runs rather than reconstructed in a panic when a declaration falls due. It runs single-tenant in the AWS Sydney region, so payroll records for both states stay in Australia.
Bring us your worst cross-border payroll client
Pick the Albury-Wodonga employer whose wages you split by hand every month. In 30 minutes we will run a dedicated AI over their real Xero or MYOB file and show you the two-state wage totals, the icare and WorkSafe figures and the leave provision coming back already separated. Live on your files within 1 hour.
Book a 30-min demoOne employer, two rulebooks
What actually diverges the moment a client employs on both sides of the river, and what the dedicated AI keeps assembled underneath it. Your registered agent still makes every call.
| Obligation | Albury side, NSW | Wodonga side, VIC | What the AI keeps current |
|---|---|---|---|
| Payroll tax | Revenue NSW registration, its own rate and threshold | State Revenue Office Victoria, different rate, plus the regional employer concession | Monthly wages totalled per state on the nexus rules, with the threshold apportioned once a client is liable in both |
| Which state gets the wages | Decided by the employee's usual place of residence for the month, before the tests fall through to where the work was done and where the pay was made | Every employee tagged to a jurisdiction, re-tested when an address changes mid-year | |
| Workers compensation | icare NSW policy, NSW industry classification | WorkSafe Victoria policy through an authorised agent, Victorian industry rate | Two rateable remuneration figures built from live pay runs, not reconstructed at declaration time |
| Long service leave | Long Service Leave Act 1955, ten-year entitlement | Long Service Leave Act 2018, accessible from seven years | Parallel accrual per employee and a split provision, with each person's first entitlement date visible |
| Portable leave schemes | Construction and contract cleaning levies | Community services, contract cleaning and security levies | Levies coded to their own accounts per scheme rather than absorbed into wages |
| Public holidays | No Melbourne Cup Day, no Grand Final Friday, Labour Day in October | Cup Day and Grand Final Friday are public holidays, Labour Day in March | The right calendar applied per employee, and split-calendar pay runs flagged before processing |
| Grouping and entity structure | Related entities on either side can be grouped, so a second company does not buy a second threshold | Common control and shared employees surfaced across the client group before a registration decision is made | |
| BAS, GST and STP | Federal, and mercifully the same on both banks of the Murray | Working papers drafted from a ledger that is already current, with coding anomalies flagged for review | |
An Olive Street practice and a cold-chain carrier in Wodonga
Picture a three-person bookkeeping and BAS practice on Olive Street in central Albury: the principal, a full-time bookkeeper and a part-time payroll officer three days a week. Sixty-eight clients, of which thirty-one are on payroll, about 640 employees between them. Most files are in Xero. A block of older manufacturing and transport clients is still on MYOB and has been getting moved across a few at a time for two years, and two clients arrived on QuickBooks Online and stayed there. Roughly twenty of the sixty-eight employ people on both sides of the Murray, which is the number that shapes the whole practice.
The client that hurts is a refrigerated linehaul operator working out of a yard off Melrose Drive in Wodonga: 38 employees, nine subcontracted owner-drivers, a small fleet running produce and chilled freight up the Hume to Sydney and down to the Melbourne markets. Fourteen of the 38 live on the New South Wales side, in Lavington, Thurgoona, Springdale Heights and out at Jindera, because that is simply where the housing was when they were hired. The company is Victorian. Its payroll is not.
The old month went like this. The payroll officer ran the fortnightly pays, then exported them to a spreadsheet and hand-sorted employees by home postcode to get a New South Wales wage figure and a Victorian one for payroll tax. Anyone who had moved during the year was wrong until somebody noticed. Twice a year the same spreadsheet got cut a second and third way, once for the icare declaration and once for WorkSafe, using two different definitions of rateable remuneration and no shared source. Long service leave sat as one blended provision, so the principal could not say which of the fourteen NSW drivers were near ten years and which of the Victorian staff had already passed seven. The fuel card CSV was coded in a single evening each month, with the refrigeration unit fuel claimed at the on-road rate because splitting it properly took longer than anyone had. And in the first week of November, half the workforce was paid a public holiday they were not entitled to.
With a dedicated AI running, the month reshapes. Every night it codes the bank feeds and the fuel card imports across all sixty-eight files, in Xero and in MYOB, and reconciles. For the carrier it holds a jurisdiction tag against every employee, sourced from the payroll record and re-tested when an address changes, so the New South Wales and Victorian wage totals exist as a by-product of running the pays rather than as a monthly chore. It maintains the icare and WorkSafe remuneration figures continuously against their own definitions. It accrues long service leave under the 1955 Act for the Lavington and Jindera drivers and the 2018 Act for the Wodonga staff, and shows the principal a dated list rather than one number. It applies each employee's public holiday calendar and raises the Cup Day pay run before it is processed, not after a payslip query.
The freight detail gets handled too, which is where the recoverable money was hiding. Fuel is split by vehicle and by use, so the diesel burned in the reefer units and the yard forklift is claimed at the off-road rate instead of the road-user-charge-reduced one, and the rate applied is the one that was in force for that quarter. Owner-driver settlements are decoded so linehaul rate, fuel levy, tolls and deductions each sit in their own account, and the AI flags two of the nine subcontractors whose arrangements look substantially like labour, which is a superannuation guarantee question and a payroll tax contractor question the principal now gets to consider deliberately rather than discover later.
The practice did not hire. It took on eleven new clients over the following year, most of them referred precisely because word gets around the Border about who can actually handle a two-state payroll, and the principal finally started charging for the cross-border work as advisory rather than absorbing it as bookkeeping. The same shape holds whether the practice sits on Olive Street, above a shopfront on High Street in Wodonga, or at a desk in Thurgoona.
Thirty minutes on a real Hume corridor file
Bring a transport or manufacturing client and we will code a month of fuel card data, split the on-road and off-road claims and reconcile an owner-driver settlement in front of you, in your own Xero or MYOB file. No migration, no new ledger.
See it on your Xero fileWhat your dedicated AI takes on
The work that makes a Border book heavier than it looks, done continuously and left review-ready for a registered BAS agent.
Cross-border wage apportionment
Tags every employee to New South Wales or Victoria on the nexus rules, totals wages per state per month, tracks the apportioned threshold and watches the Victorian regional employer test.
icare and WorkSafe declarations
Keeps two rateable remuneration figures current against two policies, two classification systems and two renewal cycles, with deemed-worker contractor payments flagged for a decision.
Dual leave and holiday calendars
Accrues long service leave under the statute that governs each employee, splits the provision, and applies the right public holiday calendar so Cup Day does not quietly get paid twice.
Nightly coding and reconciliation
Codes bank feeds from each client's own history, matches invoices to payments and reconciles Xero, MYOB and QuickBooks Online overnight, so no file sits a month behind while you are on the road.
BAS, GST and STP working papers
Drafts the working papers with the odd items surfaced, a permit or registration coded to repairs, a private vehicle expense in cost of sales, for a registered BAS agent to review and lodge.
Document capture and chasing
Reads supplier invoices, weighbridge dockets, fuel statements and bank documents from email, Dext or Hubdoc, then keeps nudging the clients who never answer the first request, in your practice's own tone.
The Hume corridor client
Freight and logistics is the industry the Border was built on, and it is the file type that eats the most bookkeeping hours per dollar of fee.
Fuel tax credits, split properly
Fuel card data imported and coded by vehicle, with diesel burned in refrigeration units, auxiliary equipment and yard machinery separated from on-road use, and the rate that applied to the period used rather than today's.
Owner-driver settlements
Settlement statements decoded so linehaul rate, fuel levy, tolls, insurance recoveries and deductions each land in their own account, and arrangements that look substantially like labour are flagged for a super and payroll tax decision.
Driver allowances and STP
Overnight travel allowances reported in their own Single Touch Payroll category instead of being folded into gross wages, with the substantiation position noted so a later query is answerable.
Live within 1 hour, not next financial year
Connect
We link the dedicated AI to your Xero and MYOB files, your practice inbox, your capture tool and whichever fuel card portals your transport clients use.
Map the border
For each employing client we set the jurisdiction rules, the two workers compensation policies and the leave statutes that apply, once, so they hold for every pay run after it.
Prove it on one file
Start with your hardest cross-border client and check its output against your own working for a cycle or two. You decide what it posts alone and what waits for sign-off.
Roll it out
As trust builds it takes the rest of the book, and the cross-border work stops being the thing that caps how many employing clients you can carry.
Dedicated AI versus the usual options
How a Border practice normally tries to add payroll capacity, and what each option actually gives you.
| Dedicated AI | Offshore VA | Local payroll officer | |
|---|---|---|---|
| Time to start | Within 1 hour | 2-4 weeks | 1-3 months in a thin regional market |
| Knows both state regimes | Configured per client, both | Rarely, and never confidently | Only if they have worked the Border before |
| Hours worked | 24/7, codes overnight | Business hours, time-shifted | Business hours |
| Relative cost | ~70% less than a VA | Baseline | $5,000+/mo plus on-costs |
| Xero and MYOB native | Yes, both, at once | Manual | Manual |
| Data location | Onshore, AWS Sydney | Overseas | Local |
| Audit trail on jurisdiction calls | Logged with evidence, timestamped | A spreadsheet, if you are lucky | Depends who is on leave |
Built for Australian compliance
Your registration is untouched
The AI prepares and a registered BAS or tax agent reviews and lodges. Tax Practitioners Board registration, the Code of Professional Conduct and your supervisory arrangements all stay exactly where they are.
Both states' records stay onshore
Single-tenant on AWS in the Sydney region. Employee addresses, tax file numbers, claim histories and leave records for your New South Wales and Victorian clients alike stay in Australia, in your own isolated environment, never used to train models.
Evidence behind every call
Each jurisdiction decision is logged with the address evidence and the date it was applied, so a question about which state should have received a month of wages is answerable years later, not reconstructed from memory.
Border practices, frequently asked questions
We have clients with staff on both sides of the Murray. Can it split wages between the NSW and Victorian payroll tax regimes?+
Yes, and this is the single most common reason Border practices call us. Under the harmonised nexus rules the state that gets a month's wages is decided by where the employee usually lives, and only if that is unclear does the test fall through to where the work was done and where the wages were paid. So a Wodonga employer with drivers living in Lavington, Thurgoona and Jindera is a New South Wales taxpayer for those people and a Victorian taxpayer for the rest, in the same pay run. The dedicated AI tags every employee to a jurisdiction and re-tests it when an address changes, totals wages per state per month, and tracks the tax-free threshold in each state on the apportioned basis that applies once a client is liable in more than one. It also watches the Victorian regional employer test, where a client that loses the required share of regional wages moves off the reduced rate, and it flags grouping risk when the same family controls entities registered on either side. Rates and thresholds move most budgets, so the AI keeps current values in its configuration and your registered agent confirms them at lodgement.
What about workers compensation, with icare New South Wales on one side and WorkSafe Victoria on the other?+
A cross-border employer carries two policies, and almost nothing about them lines up. The classification systems are different, so the same business is described by a New South Wales workers compensation industry classification on one policy and a Victorian industry rate on the other. The definitions of rateable remuneration differ around allowances, apprentices and deemed workers. The renewal and declaration cycles do not fall in the same month. The result, in most practices, is that the same payroll report gets pulled twice a year and hand-cut two different ways under time pressure. The dedicated AI keeps a continuously updated remuneration figure per policy, built from the actual pay runs rather than reconstructed afterwards, with contractor payments flagged where a deemed worker question exists. When each declaration falls due, the numbers are already assembled and your bookkeeper is checking rather than rebuilding.
Long service leave works differently in New South Wales and Victoria. Can it run both in one payroll file?+
It can, and it needs to, because two people doing the same job in the same depot can have genuinely different entitlements. Victorian employees accrue under the Long Service Leave Act 2018 and can request leave once they reach seven years of continuous service. New South Wales employees sit under the 1955 Act with its ten-year entitlement and its narrower pro-rata rules before then. The dedicated AI accrues each employee under the rulebook that applies to them, keeps the provision on the balance sheet split so the number means something, and gives you the date each employee first becomes entitled rather than a single blended figure. Portable schemes get their own treatment too: a contract cleaning or community services client operating on both sides can be levied under a Victorian portable scheme and a New South Wales one for different parts of the same workforce, and those levies are coded to their own accounts instead of being buried in wages.
Albury and Wodonga do not share a public holiday calendar. Does that break the pay run?+
It breaks it every year, usually twice. The Victorian side has public holidays the New South Wales side does not, the Melbourne Cup and the Friday before the AFL Grand Final being the two that catch people out, and Labour Day falls in a different month in each state. For a business running one roster across the Lincoln Causeway that means two sets of penalty rates, two sets of public holiday pay entitlements and two views of what a leave day costs, inside a single pay period. The dedicated AI applies the calendar that belongs to each employee's jurisdiction, checks the award interpretation for that day rather than assuming a normal shift, and flags the pay runs that fall on split calendars before they are processed. Most practices only discover a Cup Day mistake when an employee queries a payslip in December.
A lot of our book is Hume corridor freight and logistics. Can it handle fuel tax credits and owner-drivers?+
Yes, and transport files are where the coding effort really sits in this region. The dedicated AI imports fuel card data and codes it by vehicle, keeps the on-road claim separate from the higher off-road rate for fuel burned in yard equipment, auxiliary power and refrigeration units, and applies the rate that was in force for the period rather than the current one, which is what usually breaks a retrospective claim. It reconciles owner-driver settlement statements, separating linehaul rates from fuel levy, tolls, insurance recoveries and deductions, and it flags subcontractors who are being paid substantially for their own labour, where a superannuation guarantee obligation and a payroll tax contractor question both need a decision from you. Driver allowances are treated properly for Single Touch Payroll, with overnight travel allowances reported in their own category instead of being folded into gross wages.
Does it work with Xero and MYOB, and can it help us while we are mid-migration?+
It connects directly to Xero and MYOB, and to QuickBooks Online, and it reads from the capture tools most practices already run, including Dext and Hubdoc. Mid-migration is a normal state for a Border practice, because the older manufacturing and transport clients have often been on MYOB since before either of us started, and moving them is a project nobody has a spare month for. The dedicated AI works both platforms at once, so a client can sit in MYOB while their sister entity is already in Xero and the cross-border payroll picture still consolidates across the group. When a file does move, it carries the coding history forward instead of leaving the new file to learn the client's chart of accounts from scratch.
We hold payroll for both New South Wales and Victorian entities. Where does that data physically sit?+
In Australia, in the AWS Sydney region, on infrastructure dedicated to your practice alone. That matters more than usual for a cross-border book: you are holding employee addresses that determine a client's payroll tax liability, tax file numbers, workers compensation claim histories and long service leave records for people in two jurisdictions. None of it is pooled with another practice's data, none of it is shared, and none of it is used to train models. When a client asks where their staff records are kept, the answer is a single sentence, which is a materially easier conversation than describing an offshore contractor's arrangements.
Does running a dedicated AI change our BAS agent registration or Tax Practitioners Board position?+
No. The registered agent still reviews and lodges, so registration, the Code of Professional Conduct and your supervisory arrangements are unchanged. What does change is the quality of the file behind each lodgement. Cross-border work is the kind that gets queried years later, when a client is reviewed on which state should have received a month of wages or whether a subcontractor should have been treated as an employee. The dedicated AI logs every transaction it coded, every jurisdiction call it made and the address evidence behind it, with a timestamp, so the reasoning is recoverable long after the person who did the work has moved on.
Keep reading
The national picture for bookkeepers
The pillar page this Albury-Wodonga page sits under.
If you also do the tax work
The companion pillar written for registered tax agents.
Deadline by deadline
How BAS, GST and the compliance calendar get prepared.
Two hours up the Hume
Riverina firms, farm concessions and defence returns in Wagga Wagga.
Down on the Victorian coast
Seasonal payroll and BAS work for Barwon bookkeepers.
Where the 70% figure comes from
The cost arithmetic against another hire, set out properly.
Stop running two rulebooks by hand
See a dedicated AI work your own Xero or MYOB files: wages split between New South Wales and Victoria, icare and WorkSafe kept apart, leave accrued under the right statute and the Hume corridor coding done overnight. Live within 1 hour, with client data kept onshore in the AWS Sydney region.
[email protected] · Serving bookkeepers and BAS agents across Albury, Wodonga, the Riverina and North East Victoria