Australia’s Sharing Economy Reporting Regime: Scope, Data and Lodgment

Table item 15 in section 396-55 of Schedule 1 to the Taxation Administration Act 1953 requires the operator of an electronic distribution platform to report to the Commissioner of Taxation when consideration flows to a supplier for a supply made through the platform. Australia’s Sharing Economy Reporting Regime (SERR) turns that one table item into a twice-yearly XML lodgment with the Australian Taxation Office (ATO).

The next report covers payments from 1 July to 31 December 2026. Its standard due date is 31 January 2027, which falls on a Sunday, so approved-form lodgment is permitted on Monday 1 February 2027. The following report covers 1 January to 30 June 2027. Its standard due date is Saturday 31 July 2027; applying the ATO’s next-business-day rule and the Northern Territory public holiday on 2 August, the permissible lodgment date is Tuesday 3 August 2027.

The regime reached taxi travel and short-term accommodation from 1 July 2023 and every other reportable supply from 1 July 2024. What a platform actually reports is decided by three legal layers: the statutory item, a 2023 Commissioner’s instrument that fixed six-monthly reporting periods, and an exemption determination that was remade from 1 July 2025 with one new exemption for platforms the GST law treats as the supplier. The ATO’s web guidance sits on top of those layers and carries the operational rules for the file itself, from quarterly aggregation to the reference-ID rules that trigger rejections.

Offshore operators lodging without an Australian business number (ABN) have one more date to plan around: the ATO has said that from early 2027 a Digital ID such as myID will be needed to access Online services for non-residents, the channel they use for SERR files, as AUSid is replaced.

Related reading: DAC7 reporting for Luxembourg platform operators

SERR dates that matter for the January 2027 report

The standard due dates repeat every year; the statutory start dates and instrument dates sit alongside them.

Date What happens Source
1 July 2023 SERR applies to transactions relating to taxi travel and short-term accommodation 2022 amending Act, Schedule 2 item 2; 2023 instrument, section 5
1 July 2024 SERR applies to all other reportable transactions Same provisions
1 July 2025 2025 exemption determination commences and repeals the 2024 determination F2025L00517, section 2 and Schedule 1
31 January, each year Report due for payments from 1 July to 31 December ATO SERR guidance
31 July, each year Report due for payments from 1 January to 30 June ATO SERR guidance
31 January 2027 Standard statutory due date for the July to December 2026 report; approved-form lodgment can occur on the next business day, 1 February 2027. The separate section 6 written-notification condition is tied to the day the report would otherwise be required, or a later day agreed in writing by the Commissioner. ATO SERR guidance; F2025L00517, section 6(d)
Early 2027 Digital ID (such as myID) needed for Online services for non-residents ATO lodgment guidance

The start-date rows describe the application of the law, so they still matter for one reason: a transaction completed and paid before the SERR applied to that type of supply is outside the regime, and the ATO lists that as a standing exclusion.

The obligation was inserted by Schedule 2 to the Treasury Laws Amendment (2022 Measures No. 2) Act 2022 (No. 84, 2022), which received the Royal Assent on 12 December 2022. Schedule 2 added item 15 at the end of the table in section 396-55 of Schedule 1 to the Taxation Administration Act 1953. Under the Act’s commencement table the schedule started on 1 January 2023, while its application provision tied the obligation to transactions entered into on or after 1 July 2023 for taxi travel and short-term accommodation, and 1 July 2024 in any other case.

Column 1 of item 15 names the reporting entity: an operator of an electronic distribution platform within the meaning of the GST Act, but disregarding paragraph 84-70(1)(c) of that Act. Column 2 describes the reportable transaction as the provision of consideration by an entity to another entity (the supplier), wholly or partly for a supply made by the supplier through the platform, if four conditions hold:

  • the supply is connected with the indirect tax zone, or would be if that zone included the external Territories;
  • no amount is required by Division 12 to be withheld from the payment;
  • the operator and the supplier are not members of the same consolidated group or MEC group;
  • the supply is not a transfer of ownership of goods, a transfer of ownership of real property, or a financial supply.

Read plainly, the reportable event is the provision of consideration by any entity to the supplier, wholly or partly for a supply made through the platform, so a payment that never passes through the platform can still be a column 2 transaction. In Example 6 of the 2025 explanatory statement, a taxi booking paid directly to the driver drops out of the report through the mere-booking exemption in section 8(c), which applies only when all three of its conditions hold.

Two Commissioner’s instruments then shape the obligation. The Taxation Administration (Reporting by Electronic Distribution Platform Operators) Legislative Instrument 2023, made by the Commissioner under subparagraph 396-55(a)(ii) and dated 8 June 2023, requires a report in the approved form for each six-month period beginning on 1 January and 1 July. The explanatory statement to the 2025 exemption determination describes that instrument as substituting the default annual reporting period with a six-monthly one. The Federal Register of Legislation lists the 2023 instrument as in force, with a sunset date of 1 October 2033.

The second is the Taxation Administration (Reporting Exemptions for Electronic Distribution Platform Operators) Determination 2025, registered as F2025L00517 and referred to by the ATO as LI 2025/5. A Deputy Commissioner made it on 6 March 2025 under subsection 396-70(4), which lets the Commissioner determine by legislative instrument that classes of entities, or classes of transactions, need not be reported. It commenced on 1 July 2025, repealed the 2024 determination, kept every 2024 exemption and added the exemption in subsection 7(3). Public consultation ran from 28 November 2024 to 17 January 2025 and, according to the explanatory statement, produced no substantive feedback and no changes.

The definitions in the 2025 determination point back to the Act for timing. “Reporting period” means the period set under paragraph 396-55(a), and the multiple-platform exemption’s notice deadline is the day the report would otherwise be due under paragraph 396-55(b). The ATO publishes those due days as 31 January and 31 July. The report itself has to be in the approved form, which the ATO sets as its SETP XML Schema; the rest of the ATO’s SERR pages is administrative guidance, and where that wording and the instrument differ, the instrument text governs.

Which platforms the Sharing Economy Reporting Regime catches

The ATO treats a platform as an electronic distribution platform (EDP) when merchants use it to offer their supplies to customers through electronic communication, such as a website, app, internet portal, gateway, online store or online marketplace. The ATO describes the EDP operator as the entity responsible for operating the platform.

The test turns on who operates the platform, whoever built it. The ATO’s Kevin’s Cabs example describes a taxi business that licenses a third-party booking and dispatch suite, including an app passengers use to book and pay. Because the business operates the app under its own branding, the ATO treats it as the EDP operator with the reporting obligation, even though a software vendor built the platform.

The ATO also lists what does not make a platform an EDP. A platform is outside the definition if it only:

  • provides a carriage service transmitting electronic communications;
  • acts solely as a payment system or payment processing service;
  • offers advertising, acts as a directory or redirects users to external supplier websites;
  • provides channel management services.

The word “only” carries the weight. The ATO’s directory example is Plumb Match, a website that introduces customers to plumbers while the quoting, work arrangements and payment occur outside the platform. The ATO contrasts this with a colour analysis booking website where customers book and pay for appointments through the site and the operator can see when the supplier is paid. The ATO treats that website as an EDP. Adding booking and payment functionality to a directory would require a fresh assessment under the statutory EDP test.

Whether a platform acting as an agent for suppliers must report depends on whether it operates an electronic distribution platform within the statutory definition, facilitates transactions falling within table item 15 of section 396-55, and qualifies for an applicable exemption. Contracts and terms of service alone do not remove SERR reporting obligations.

When more than one platform sits in the chain

Where a supply passes through several platforms, the explanatory statement to the 2025 determination says section 6 places the reporting obligation on the platform that provides all or part of the consideration directly to the supplier. Section 6 of the 2025 determination gives the first platform an exemption only when all four of its conditions hold: the supply was made through the first platform and at least one other EDP interposed between it and the supplier; the first platform provided no consideration directly to the supplier; another EDP operator provided all or part of the consideration and has its own item 15 obligation for the transaction; and the first platform notified the Commissioner in writing, on or before the report due date or a later day the Commissioner agreed in writing.

Written notification is a condition for relying on section 6, and the operator must satisfy the timing requirement in paragraph 6(d). The determination does not expressly state that a fresh notice must be submitted for every subsequent reporting period. On the question of certainty, the explanatory statement says a first platform that is unsure whether the other operator reports should take reasonable steps to confirm it; the ATO’s web guidance puts it more firmly, telling operators to seek and receive confirmation before relying on the exemption.

Reportable transactions: what item 15 covers and what it leaves out

The ATO’s guidance groups reportable supplies into services and intangible goods. On the services side it lists ride-sourcing, taxi travel and other transport; accommodation and fixed-location assets such as holiday rentals, office or parking spaces and storage units; hire of movable assets such as vehicles, equipment, tools and clothing; and task-based services, from trades and delivery to health, beauty, education, tour guiding and freelance digital work. On the intangible side it lists digital products, subscriptions and virtual items, together with tips or gratuities paid through a platform in connection with a supply.

A pipeline built around priced bookings can miss tips, which are voluntary. The ATO’s Content4Fans example covers a streamer whose viewers make one-off or recurring contributions, including digital tokens converted into currency, and concludes that the platform reports all tips and gratuities it passes to the creator.

The exclusions come from two places. The statute removes payments subject to Division 12 withholding (the ATO gives salary and wages as the example), transactions within the same consolidated or MEC group, transfers of ownership of goods or real property, and financial supplies. The ATO’s own list of non-reportable transactions adds three categories, and points readers to Law Companion Ruling LCR 2018/2 (paragraphs 19 to 47) for background:

  • the sale of vouchers, such as gift cards, with a stated monetary value redeemable for goods or services;
  • supplies where the EDP operator is itself the supplier, so there is no third-party supplier;
  • transactions completed, including payment to the supplier, before the SERR applied to that type of supply.

The ATO’s ExperiencesRus example shows the voucher line in a single supplier’s catalogue: the adventure bookings the platform takes and sees paid are reportable, while the same supplier’s rock-climbing vouchers sold through the platform are not.

The Australian connection and the payment-date rule

The ATO summarises the connection test in three limbs: the service is provided in Australia, the supplier is in Australia, or the supply of real property relates to property located in Australia. Real property abroad drops out regardless of who owns it. The 2025 explanatory statement’s example of a Tokyo apartment owned by an Australian resident and booked through an EDP concludes that the transaction is not reportable at all, because it concerns real property outside the indirect tax zone.

Timing follows the payment to the supplier. The ATO’s ABC Holiday Co example has a family book and pay on 1 December 2023 for a stay from 10 to 15 January 2024, with the supplier paid on 16 January 2024 under the platform’s terms. The transaction belongs in the 1 January to 30 June 2024 report, because that is when the supplier was paid; the booking date and the stay dates do not move it. A platform that pays suppliers only after the stay or service can therefore see late-December bookings land in the following half-year’s file.

The 2025 exemption determination, test by test

Most of the scoping decisions sit in the 2025 determination. Section 7 exempts transactions by reference to the supplier; section 8 exempts transactions by reference to the supply; section 6 covers multiple platforms. The explanatory statement adds that once a supplier’s transactions fall within section 7, the operator need not test them against section 8.

Exemption Condition Provision
Listed entity supplier Supplier is a listed entity or a wholly owned subsidiary of one Section 7(1)(a)
Government supplier Government department, agency or authority at any level, or an entity wholly owned by a government Section 7(1)(b)
Substantial supplier At least $1,000,000 (including GST) of supplies through that platform in the 12 months ending on the last day of the period, prorated for a supplier that started on the platform within that window Section 7(2)
Platform treated as GST supplier Operator treated as the supplier under section 84-55 of the GST Act, disregarding section 84-60 Section 7(3)
Substantial property At least 2,000 transactions for the property in the 12 months ending on the last day of the period, prorated if first listed within that window Section 8(a)
Offshore supplier and service All four: the supplier has given at least one address and none is in the indirect tax zone; the service was not provided there; payment did not go to an account with a financial institution there; and no other information indicates the supplier resides there Section 8(b)
Mere booking Price not specified at booking, consideration not provided via the platform, and no operator visibility of the supply or payment Section 8(c)
Scheduled passenger travel At least 10 places available for the service; charter services and taxi travel excluded Section 8(d)
Scheduled event At least 200 places made available for the event Section 8(e)
Permanent attraction or experience At least 50 places available each day it was open in the period Section 8(f)
Rental of assets other than real property Not a specific asset, and at least 50 assets available each day of the period Section 8(g)
Multiple platforms The four section 6 conditions, including written notice by the due date Section 6

Thresholds run on a rolling 12 months, per platform

Both value and volume thresholds look back over the 12 months ending on the last day of the reporting period, which is longer than the six-month period being reported. The ATO’s summary page shortens the substantial-supplier test to supplies made during the reporting period; the instrument’s definition uses the 12-month window, and the explanatory statement’s Example 12 applies the same window to the property threshold. The proration formulas follow the same window: for a newer supplier, the days it had supplies available on the platform divided by 365, multiplied by $1,000,000; for a newer property, the days listed divided by 365, multiplied by 2,000.

The explanatory statement’s Example 12 shows why the window matters. A resort with 2,100 hotel-room transactions on a platform in one period and 900 in the next stays exempt in both, because each 12-month look-back exceeds 2,000. The explanatory statement (paragraphs 22, 34 and 35) also sets two counting rules. Thresholds are assessed platform by platform, so a supplier’s sales on two separate platforms are never added together. Properties are counted by distinct address, so rooms in one hotel are one property while apartments at separate addresses in one building are separate properties.

The explanatory statement also says the exemptions apply transaction by transaction and period by period. A platform can owe no report in one half-year and a partial report in the next as suppliers cross thresholds in either direction, which is a reason to compute exemption status inside the reporting pipeline each period instead of keeping a static supplier flag.

The new section 7(3) exemption has a narrow edge

Subsection 7(3), the 2025 addition, removes transactions where the operator is treated as the supplier under section 84-55 of the GST Act. The explanatory statement describes the target as a digital product or service supplied through an enterprise carried on outside Australia to an Australian resident buyer, with the platform liable for the GST. Two neighbouring cases stay reportable. Where a platform is treated as the supplier only because of an agreement under section 84-60 with an Australian supplier, the subsection disregards that agreement, so the domestic sale stays in the file. Offshore supplies that are not digital supplies, such as live online tutoring or legal services performed by a person, also stay reportable because the platform is not liable for the GST on them.

The other definitions reward a careful read. A scheduled passenger travel service runs on a pre-defined route with price and terms set by the supplier and open to public booking; a charter, where the customer hires an entire aircraft, vehicle or vessel and can negotiate terms, never qualifies. The event and attraction exemptions likewise require the supplier to set the time or opening hours, price and terms, with any member of the public able to book. For the asset-rental test, assets already booked for a day or temporarily unavailable, for example under maintenance, still count as available. The explanatory statement’s car-hire examples draw the line on specificity: hiring one owner’s particular car is reportable, while booking whichever sedan a hire company with more than 50 listed cars has available at collection is exempt.

Inside the SERR file: seller, transaction and property data

The approved form is an XML file valid against the ATO’s SETP XML Schema. The ATO’s report page splits the content into four blocks, and the SERR Business Implementation Guide uses its own vocabulary for them: suppliers appear as “sellers” and the EDP operator as the “Reporter Platform”.

  • Platform details: the operator’s business information, such as ABN and contact details, and any intermediary involved in reporting, such as a software provider or agent.
  • Supplier details for individuals: first name, surname and date of birth; address, email and phone number; bank account information or identifiers; and activity details covering start and end dates, activity code, transactions and amounts.
  • Supplier details for non-individuals: ABN, ATO reference number (ARN), tax identification number (TIN), business or trading name, plus the same contact, financial and activity details.
  • Transaction details (amounts paid, GST, fees and commissions) and, where the supply involves short-term accommodation or a fixed-location asset, property details.

Each transaction carries an activity code, and some need a sub-code. The ATO lists the current codes as ride-sourcing or taxi services, short-term accommodation, movable asset, food delivery, fixed-location asset, service and other, with the full code and sub-code lists held in the Business Implementation Guide.

Aggregation and amount rules that decide acceptance

The ATO’s common-mistakes page sets the amount basis. Report the supplier’s gross income, meaning the total paid for bookings, digital goods or services in the period including GST and commissions, and exclude refunds for cancelled transactions. Instead of individual transactions, the file carries aggregated totals per supplier, activity type and quarter, with all monetary amounts reported in Australian dollars (AUD), foreign-currency payments converted into AUD and the mandatory SETPP52 transaction currency field set to AUD. The quarters are Australian financial-year quarters: in the ATO’s example, a supplier paid $30, $120 and $10 between 1 January and 31 March is reported as a Quarter 3 total of $160, and $20 and $50 between 1 April and 30 June as a Quarter 4 total of $70. The “number of activities” counts only completed bookings, goods or services, leaving out anything cancelled or unpaid.

The same page lists the format errors that cause rejections:

  • Characters outside the schema’s English character set. Character conversion that some ATO systems apply after lodgment does not apply to SERR reports, so names in Chinese, Japanese or Korean script, and accented characters, have to be converted before the file is built.
  • Titles and suffixes left in names. MR, MRS, ESQ and JNR come out; “Exec for John Smith” is reported as John Smith, while “The Trustee for Smith Family Trust” is reported as a non-individual supplier.
  • A file creation timestamp outside the ISO 8601 UTC format specified for element SETP4.
  • Reused document reference IDs. SETP1 (message reference), SETP30 (reporter platform document reference) and SETPP1 (document reference, different for every supplier) must each be unique within the report and never reused in a report for another period, following the pattern receiving country, report calendar year, the platform’s ABN or ARN, then a unique string.
  • A missing or malformed Bulk Business Document Message (BBDM) wrapper on files sent by File transfer, which produces the error “The version of this file type cannot be sent by this channel”.

The current SERR Business Implementation Guide specifies a maximum report size of 5 GB, inclusive. The ATO’s general SERR guidance also provides instructions on compressing larger files. The reference-ID pattern uses the calendar year, while the amount breakdown uses financial-year quarters; a January to June file therefore carries Quarter 3 and Quarter 4 amounts under a reference ID stamped with the calendar year.

The ATO’s current software-developer materials include the SERR Business Implementation Guide (version 4.5, March 2026) and the Sharing Economy Taxable Payments (SHRNGECONTXBLPMT) technical specification at the version the ATO software-developer page shows as current. The associated SHRNGECONTXBLPMT.0001 package provides message structure tables, validation rules and XSD files, while separate Bulk Data Exchange materials address the BBDM wrapper and XML BDE implementation. Operators should validate builds against the applicable published package. The ATO runs its Common Reporting Standard statements through a separate XML specification and lodgment process; our guide to Australian CRS reporting under the ATO specification covers that regime’s file rules for comparison.

Testing and lodging through ATO Online services

The ATO offers two test routes. The File transfer test facility validates the structure of a file built with dummy data against the XML schema and returns an error report; access requires a registration form, with separate facilities for businesses and agents and for software developers. Inside ATO Online services, the File transfer function has a “Test” option that validates a file containing real data. After a successful test the operator still has to use the “Lodge” option to submit the report formally, according to the ATO.

The lodgment channel depends on how the operator is registered:

  • Operators or intermediaries with an ABN lodge through Online services for business, using a Digital ID such as myID and authorisation through Relationship Authorisation Manager (RAM), then File transfer under the Lodgments menu.
  • Operators or intermediaries without an ABN lodge with an ARN through Online services for non-residents. First-time lodgers receive an ARN once their registration is processed. The channel currently uses AUSid, which the ATO says will give way to a Digital ID requirement in early 2027.
  • Tax agents lodge through Online services for agents, using File transfer under the Reports and Forms menu.

Operators can build files themselves or use third-party software, and they can authorise an intermediary to lodge. After submission the operator receives a receipt number and a validation report, and can opt into email notifications on the report’s status. A report that is incomplete or incorrectly formatted may be rejected; errors must be corrected before re-lodging, and the ATO says a relationship officer will contact the operator with guidance on fixing and resubmitting where needed.

Corrections are governed by both the Taxation Administration Act 1953 and the SETP schema. Under section 396-75 of Schedule 1 to the Act, an operator that becomes aware of a material error in a lodged SERR report must provide a corrected report in the approved form within 28 days of becoming aware of the error. Section 388-55 allows the Commissioner to defer an approved-form lodgment deadline.

The correction procedure must therefore address both the statutory timing requirement and the applicable XML requirements. Section 5 of the ATO’s Business Implementation Guide (cancelling and relodging reports) sets out the Message Type and Document Type combinations that cancel a whole report or selected seller records, and both are available only for the most recent report sent. For changes to an earlier report, the guide directs operators to contact sharingeconomyreporting@ato.gov.au for assistance. The ATO says a combination outside the guide’s tables is not processed and needs a resubmission.

Deferrals, exemptions on request and penalties

Separate from the determination’s class exemptions, an operator can ask the ATO for a lodgment deferral or an exemption, assessed case by case. The ATO’s examples of when it may grant one include an operator that has only just learned of its obligation and cannot change systems in time, one that needs more time to produce the SETP format, one that will have all data but needs more time, and one changing systems that will be unable to retrieve historic data afterwards. Where all required data is held except one mandatory field that blocks lodgment, the ATO says an interim solution may be available. The written request goes to sharingeconomyreporting@ato.gov.au and has to include the organisation’s name, ABN or ARN, the reporting periods, the proposed lodgment date and the reason.

The ATO’s guidance names two penalty triggers: not lodging by the due date when an obligation exists, and giving false or misleading information, including by omission, and states that reporting false or misleading information is an offence under tax law. It points to its general interest and penalties guidance for how penalties may apply.

Over-reporting carries its own risk. The ATO asks operators to report only what tax law requires, to take reasonable steps to keep out-of-scope transactions out of the file, and to keep their privacy obligations in mind; where an operator over-reports, the ATO says it will work with the operator so that only required data is provided.

Where a DAC7 build will mislead an Australian SERR file

A group that already reports under the EU’s DAC7 rules may be tempted to start from that pipeline, and several design choices do not carry over. Our DAC7 reporting guide for Denmark shows how the EU model works at national level; set against Council Directive (EU) 2021/514 and the Australian sources, five differences stand out.

  • Goods: DAC7’s relevant activities include the sale of goods, while item 15 excludes supplies by way of transfer of ownership of goods. On a reading of the statute, a marketplace’s physical-goods sales can be in DAC7 scope and outside SERR.
  • Amount basis: DAC7 consideration is net of fees, commissions or taxes withheld or charged by the platform operator. The SERR gross-income figure includes GST and commissions, with amounts paid, GST, fees and commissions reported as separate transaction details.
  • Calendar: DAC7 reports a calendar year by 31 January of the following year, broken down by the quarter in which consideration was paid or credited. SERR runs two reports a year and breaks amounts down by Australian financial-year quarter.
  • Property threshold: DAC7 excludes an entity seller for which the platform facilitated more than 2,000 rentals of a property listing in the reporting period. The SERR test counts at least 2,000 transactions per property over a rolling 12 months, prorated for newer listings, and the determination does not limit it to entity suppliers.
  • Small sellers: DAC7 excludes sellers with fewer than 30 sales of goods and total consideration of no more than EUR 2,000. The 2025 determination contains no low-value or low-volume seller exemption.

Two exclusions do line up. Both regimes leave out governmental entities and listed entities, with DAC7 extending to related entities of a listed company and the SERR determination to wholly owned subsidiaries of a listed entity. File formats differ completely: the ATO accepts a SERR report only as a valid file under its SETP XML Schema, carried in a BBDM wrapper when sent by File transfer.

Frequently Asked Questions

Our platform collects a booking deposit and the customer pays the balance to the supplier directly. Is that a mere booking?

The mere-booking exemption in section 8(c) of the 2025 determination needs all three conditions: no price specified at booking, consideration not provided via the platform, and no operator visibility of the supply or payment. A deposit taken through the platform fails the second condition. My reading is that the transaction stays reportable. The 2025 explanatory statement adds that the exemption does not apply where payment for a reportable supply is made through a payment system linked to the platform that processes it at the time of booking.

We use an external payment provider to pay suppliers. Does that make the payment provider the reporting entity?

A business that acts solely as a payment system or payment processing service is outside the ATO’s EDP definition, so the obligation stays with the platform that arranged the supply. In Example 7 of the 2025 explanatory statement, a taxi platform processes the fare through a third-party payment provider; because the operator knows the service was delivered and the amount actually paid, the mere-booking exemption does not apply and the platform reports the transaction.

A supplier crossed $1,000,000 on our platform in October. Do we drop them from the January 2027 report?

The substantial-supplier test is measured at the last day of the reporting period over the preceding 12 months, so for the period ending 31 December 2026 the question is whether the supplier’s supplies through your platform from 1 January 2026 to 31 December 2026 reached $1,000,000 including GST, prorated if the supplier joined within that window. If they did, the exemption covers the supplier’s transactions for that period; the test is run again for the period ending 30 June 2027.

A local council and a foreign tourism agency list paid tours on our platform. Does the government-supplier exemption cover them?

Paragraph 7(1)(b) of the 2025 determination covers a government department, agency or authority, however described and at any level of government, and an entity wholly owned by a government. The explanatory statement says it is intended to capture government bodies, including foreign bodies, at all levels of government, including local government. A tour operator that is only licensed or funded by a government, and not wholly owned by one, falls outside the paragraph and needs another exemption to drop out of the file.

One mandatory field, such as a supplier’s date of birth, is missing for part of our population. Should we lodge without it?

Incomplete files may be rejected. The ATO’s deferral guidance says that where an operator has collected all required data except one mandatory field that is preventing lodgment, it will work with the operator on its circumstances and an interim solution may be available. The route is a written request to sharingeconomyreporting@ato.gov.au.

An offshore app developer sells an app to an Australian customer through our store, and we account for the GST. Do we report it?

Where your platform is treated as the supplier under section 84-55 of the GST Act for that sale, subsection 7(3) of the 2025 determination exempts it. If you collect GST on a sale by an Australian developer only because of a section 84-60 agreement, the agreement is disregarded and the sale remains reportable.

Key Takeaways

  • Diarise the standard SERR due dates of 31 January and 31 July. For the two 2027 reports, the approved-form next-business-day rule permits lodgment on 1 February 2027 and 3 August 2027, respectively, based on the currently published public holidays.
  • Section 6 relief for an upstream platform requires written notification to the Commissioner in accordance with paragraph 6(d), by the applicable reporting deadline or a later day agreed in writing. The ATO’s guidance says to submit the notification by the due date for the relevant reporting period, so an operator relying on section 6 should give the Commissioner written notice for each period it intends to rely on the exemption.
  • Recompute supplier and property exemption status at each period end from a 12-month look-back held separately for each platform.
  • Allocate amounts by the date the supplier is paid; booking and service dates do not decide the period.
  • Build amounts gross of GST and commissions, net of cancellation refunds, and aggregate them by supplier, activity type and Australian financial-year quarter, with all monetary amounts reported in AUD.
  • Generate SETP1, SETP30 and SETPP1 reference IDs from a sequence that is never reused across periods.
  • Operators lodging with an ARN need a Digital ID route into Online services for non-residents ready for early 2027.

Sources and References

Preparing the 31 January 2027 SERR lodgment

The report for 1 July to 31 December 2026 covers consideration provided to suppliers during that period only where the transactions fall within table item 15 of section 396-55 and no applicable statutory or 2025-determination exemption applies. The payment ledger establishes the relevant payment dates, while the scoping exercise determines which transactions belong in the report. What remains open is the scoping run against the 2025 determination with 12-month look-backs ending 31 December 2026, any section 6 notices to the Commissioner for upstream platforms, and a file that passes the File transfer test facility or the Online services Test option before it is lodged. For offshore operators lodging with an ARN, each authorised user will need their own Digital ID, such as myID, at the required identity strength when the ATO replaces AUSid in early 2027. Operators should prepare individual access arrangements before the January to June 2027 lodgment, for which the standard due date is 31 July 2027 and the next-business-day date is 3 August 2027.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts