Skip to content
Australia

Automation for Australian operations teams, built around GST, STP and Xero or MYOB

Australian operations builds are shaped by GST and the BAS cycle, payroll that reports to the ATO on every pay run, Xero or MYOB as the ledger, the Privacy Act's rules on offshore data, and a calendar of public holidays that differs by state.

Four things set the terms for an Australian build. GST at ten per cent and the BAS that reports it. Payroll that reports to the ATO each time employees are paid, through Single Touch Payroll. A ledger that is often Xero or MYOB. And the Privacy Act 1988, which cares about personal information that leaves the country, as it does whenever an automation or AI provider is hosted offshore.

This page is about those four, and about two practical things that catch Australian builds out: public holidays that vary by state and territory, and the spread of time zones across the country. It is not tax or legal advice, and it links to the ATO and the OAIC rather than restating their rules.

Three case studies have an Australian connection. The evidence section is precise about how far they go, which is not as far as GST, BAS, STP, Xero or MYOB.

Australia, specifically

What is different about building here

Six things that change the design of an Australian finance or operations build.

GST and the BAS

GST is ten per cent on most goods and services, and businesses report it, with PAYG withholding and instalments, on a Business Activity Statement, usually on a monthly or quarterly cycle. For automation the point is at the line level: taxable, GST-free and input-taxed supplies are different things, and an automation that posts a transaction with the wrong one creates work at BAS time. Your BAS agent or accountant, and the ATO, decide how each supply is treated.

Single Touch Payroll

Employers report salary and wages, PAYG withholding and super information to the ATO each time they pay employees, through STP-enabled software. The consequence for builds is simple: read from the payroll system or write through it, and never keep a second payroll record in a side system that is not reporting.

Xero, MYOB and the ABN

Xero and MYOB are two of the accounting packages Australian small businesses use, and QuickBooks is also available. MYOB has been consolidating its AccountRight and Essentials products into MYOB Business, and its Business API covers all three, but features can differ between products, so the product and plan are confirmed before anything is scoped. Australian businesses are identified by an ABN, which can be checked against the ABN Lookup service at the point a supplier or customer is created.

The Privacy Act and offshore data

The Privacy Act 1988 and its Australian Privacy Principles are regulated by the OAIC. APP 8 covers disclosing personal information overseas, which is exactly what happens when an automation platform or AI provider processes it offshore. Many small businesses, those with an annual turnover of $3 million or less, are outside the Act unless an exception applies, and the exceptions are the OAIC's to explain. The Notifiable Data Breaches scheme applies to entities covered by the Act. Take advice on whether and how the Act applies to you.

Public holidays by state

There is no single national calendar. States and territories set their own public holidays, and some are regional. Melbourne Cup Day is a Victorian public holiday (some regional councils arrange a local day instead), for example, and Labour Day falls on different dates in different states. A business-day clock for a team operating in more than one state needs the right calendar per job, not one list. The fleet order automation case study runs its SLA against a real Australian public holiday calendar.

Peppol e-invoicing

Australia uses the Peppol e-invoicing network, with the ATO acting as the Australian Peppol Authority, which means some suppliers can send invoices as structured data rather than PDFs. Whether it applies to you is for the ATO to say, but it is a reason not to build invoice intake that only reads images. The ATO publishes e-invoicing guidance; start there.

The buyer's problem

What an Australian operations team is usually stuck with

These come from the shape of the rules and tools, not from a client list.

Deadlines that arrive whether the data is ready or not

The BAS has a lodgement date for its monthly or quarterly cycle, and each pay run has to be reported through STP. Approvals, timesheets and supplier bills that land late get rushed into the books by hand, and the rushed entries are where the errors are.

Field jobs in one system, invoices in another

Jobs, installs or deliveries are tracked on a board or in a spreadsheet, and the invoice is raised in the ledger afterwards, by hand, when someone remembers. Revenue is late and the two records disagree.

Commitments measured in business days across states

A service commitment of a number of business days is easy to promise and hard to track when the holiday calendar differs by state and the clock is in someone's memory.

What Skofi would build

The Australian shape of each build

Order intake and a state-aware SLA clock

Orders parsed onto monday.com boards, installers allocated and notified, and a business-day clock that survives reallocation and escalates by itself. The fleet order automation case study did this against an Australian public holiday calendar, with a shadow-mode cutover. A multi-state build would make the calendar per state and editable as data.

A GST check before a bill reaches the ledger

Supplier bills are read and proposed, and a person confirms them. On a fully taxable line the GST is one eleventh of the GST-inclusive total, so a figure that does not reconcile is held for review instead of posted. A cut-off view lists what is still unconfirmed ahead of each BAS date. The trading ERP case study is the capture-and-confirm pattern on a different ledger; the BAS view and the GST check are what we would add here.

Marketplaces and portals, with prices held as data

The materials marketplace case study is a public site and a signed-in marketplace in one codebase, with prices in the database so page copy cannot drift from what is charged. A trade audience tends to read prices ex-GST while a consumer one expects GST-inclusive, so a build like this would store the tax basis beside every price. The case study does not say that it does.

Timesheets and approvals that feed payroll, not replace it

Hours captured and approved in an ops platform, then exported to the STP-enabled payroll software. Payroll stays where it reports to the ATO.

Time zones and calendars

Working across the Australian day

Australia has three main time zones, and daylight saving applies in some states and not others. Eastern time moves between UTC+10 and UTC+11, Queensland stays on UTC+10, central Australia is UTC+9:30 (UTC+10:30 in South Australia during daylight saving) and Western Australia is UTC+8.

Overlap depends on the city and the other zone

We work from Pakistan, on UTC+5 with no daylight saving. Australian Eastern Standard Time (UTC+10) is 5 hours ahead of us and Australian Eastern Daylight Time (UTC+11) is 6 hours ahead, so the gap changes when New South Wales, Victoria, the ACT and Tasmania move their clocks. Working hours are arranged to overlap with Australian eastern business hours.

Schedulers in UTC, businesses in local time

Many automation schedulers run in UTC. A job set for nine o'clock in the morning silently moves an hour when daylight saving starts in Sydney and does not in Brisbane. We store the zone with each schedule, and keep date-only fields as dates so they do not slip a day in conversion.

Failure modes

Where Australian builds go wrong

  • 01

    GST-free and input-taxed treated as the same thing

    Both carry no GST on the invoice, but they are not the same. GST-free supplies, such as exports and some basic food, still allow credits on related costs; input-taxed supplies, such as residential rent and many financial supplies, do not. A code table that collapses them gives a BAS that is wrong in a way the invoice does not show. Your BAS agent specifies the mapping.

  • 02

    One holiday list for the whole country

    A single list counts Melbourne Cup Day as a working day in Victoria, or treats Labour Day as the same date everywhere. An SLA due date computed from it is wrong for the job in that state. The calendar is held per state, as data.

  • 03

    Writing to payroll outside the STP flow

    A change made in a side system never reaches the ATO. Edits go through the STP-enabled payroll software, and the automation reads back what the payroll system holds.

  • 04

    Posting to the wrong Xero organisation

    A Xero connection can reach more than one organisation, and a flow that assumes the first one posts to the wrong set of books. The target organisation is chosen explicitly and checked on every write.

  • 05

    MYOB product assumed, not checked

    One API serves AccountRight, Essentials and MYOB Business, but features can differ between products. A flow proven on a test file from one product can fail on the client's. The product and plan are confirmed before scoping.

  • 06

    Schedules that drift with daylight saving

    A UTC schedule moves relative to local time twice a year in the states that observe it. The schedule is stored with its zone and tested across a changeover.

The honest limit

Where we are the wrong answer

Do not build payroll. Choose STP-enabled payroll software and integrate with it. Do not use us as your BAS agent: lodgement and the tax judgement behind it belong to your registered BAS agent or accountant. If a ready-made Xero or MYOB feature already does what you need, use it first. We are useful where jobs, approvals and the ledger have to work together, or where a state-aware business-day commitment has to be tracked reliably.

Evidence

What we can and cannot point to in Australia

Three case studies connect to Australia. The materials marketplace was built for an Australian construction-materials marketplace. The estimating assistant is a working demo for an Australian AV integrator. The fleet order automation runs its service clock against an Australian public holiday calendar.

None was GST, BAS, Single Touch Payroll, Xero or MYOB work, and we have no published case study for any of those. We do not claim an Australian office, ABN-based presence or partner status with Xero, MYOB or the ATO.

Not advice

Check the rules with the people who own them

GST, BAS and STP obligations depend on your registration, reporting cycle and software. Your registered BAS agent or accountant is the right person to specify codes and reports. We build to what they set and write it down. Start from the ATO and the OAIC.

Platforms we would build on

Questions

Australia, specifically

Three case studies, with limits. The materials marketplace was built for an Australian construction-materials marketplace, the estimating assistant is a working demo for an Australian AV integrator, and the fleet order automation runs its service clock against an Australian public holiday calendar. None involved GST, BAS, STP, Xero or MYOB.

Sources

Statements about what a platform, regulator or provider says come from their own pages. Rules and limits change, so check the current page before you rely on one.

Page copy drafted with AI assistance. Skofi is accountable for it. Editorial policy

Start here

Tell us about the process that keeps costing you.

A 15-minute call is usually enough to say whether this is an automation, an integration, or something that should be built, and whether we are the right people for it.

Book a 15-minute callsaveez@skofi.tech

What happens on the call

  • 15 minutes, no deck
  • We map the process on the call
  • A written scope, or an honest no
Book a call