{"id":"F2025L01235","name":"Telecommunications (SMS Sender ID Register) Industry Standard 2025","slug":"telecommunications-sms-sender-id-register-industry-standard-2025","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":107284,"registerId":"commonwealth-F2025L01235-current","compilationNumber":null,"startDate":"2026-04-03","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"Part 1","sectionType":"part","heading":"Preliminary","content":"# Part 1—Preliminary\n\n## 1 Name\n\n  This industry standard is the Telecommunications (SMS Sender ID Register) Industry Standard 2025.\n\n## 2 Commencement\n\n> Note: Each provision of this industry standard specified in column 1 of the table commences, or is taken to have commenced, in accordance with column 2 of the table.\n\n| Column 1                                                | Column 2          |\n| ------------------------------------------------------- | ----------------- |\n| Provisions                                              | Commencement      |\n| 1. Sections 1 to 8, subsection 15(2), Part 4 and Part 6 | 15 October 2025.  |\n| 2. Sections 9 to 14, Part 7 and Schedule 1              | 30 November 2025. |\n| 3. Part 3 except subsection 15(2), and Part 5           | 1 July 2026.      |\n\nNote 1: This table relates only to the provisions of this industry standard as originally made. It will not be amended to deal with any later amendments of this industry standard.\n\nNote 2: The Federal Register of Legislation may be accessed free of charge at www.legislation.gov.au.\n\n## 3 Authority\n\n  This industry standard is made under subsection 125AA(1) of the Telecommunications Act 1997 and in accordance with sections 5, 6, 7 and 8 of the Telecommunications (SMS Sender ID Register Industry Standard) Direction 2025.\n\n## 4 Application of industry standard\n\n  Subject to subsection (2), for the purposes of subsection 125AA(1) of the Act, this industry standard:\n\n  applies to the following sections of the telecommunications industry:\n\n  carriers;\n  carriage service providers;\n  electronic messaging service providers; and\n\n  gives effect to the objectives set out in section 7 of the Telecommunications (SMS Sender ID Register Industry Standard) Direction 2025.\n\n  This industry standard does not apply to a carrier, or a carriage service provider, in its capacity as a statutory infrastructure provider.\n  An electronic messaging service provider may comply with its obligations under this industry standard by:\n\n  fulfilling the obligations itself; or\n  arranging with another person who is a participating telecommunications provider to fulfill some or all of the obligations on its behalf under subsection 13(5).\n\n## 5 Definitions\n\n  In this industry standard:\n\n> ABN (short for “Australian Business Number”) has the meaning given by section 41 of the A New Tax System (Australian Business Number) Act 1999.\n\nABN entity means an entity that has an ABN.\n\n> Act means the Telecommunications Act 1997.\n\n> Australian Business Register means the register established under section 24 of the A New Tax System (Australian Business Number) Act 1999.\n\nBusiness Names Register means the register established and maintained under section 22 of the Business Names Registration Act 2011.\n\ncertified telecommunications provider means a participating telecommunications provider that is an originating telecommunications provider that has been approved to be a certified telecommunications provider under a determination made under subsection 484L(4) of the Act.\n\n  Note 1: See paragraph 589(2)(b) of the Act.\n\nCommonwealth agency means:\n\n(a) the Commonwealth; or\n\n(b) an authority of the Commonwealth; or\n\n(c) a corporation in which the Commonwealth, or an authority of the Commonwealth, has a controlling interest;\n\nand includes the Australian Defence Force.\n\ncompany has the meaning given by section 9 of the Corporations Act 2001.\n\ncustomer, in relation to a telecommunications provider, means an entity that has a contractual arrangement with the provider relating to the sending of sender identification messages.\n\nNote: A customer can be an ABN entity or a non-ABN entity.\n\ndisrupt, in relation to a sender identification message, means where the sender identification included in the message is over-stamped by a participating telecommunications provider with a new sender identification of “Unverified”.\n\ndomain name registrar means a business that handles the reservation of domain names as well as the assignment of IP addresses for those domain names.\n\nelectronic messaging service provider has the same meaning as in section 108A of the Act.\n\nEMSP partner means an electronic messaging service provider that has a direct relationship with an entity and who has partnered with:\n\n1.  for an ABN entity or non-ABN entity – a certified telecommunications provider; or\n2.  for an ABN entity – a participating telecommunications provider that is an originating telecommunications provider, and that is not a certified telecommunications provider;\n\nand who has made a request for the provider to fulfill some or all of the partner’s obligations under this industry standard on its behalf.\n\nentity means an entity covered by subsection 484F(2) of the Act that uses or proposes to use sender identification messages.\n\nentity associate means an entity who is authorised by another entity to send sender identification messages using the sender identification registered in the Register for that other entity.\n\nexcluded satellite service means a satellite service that may be used by a consumer in an overseas location where the charge for that service is the same or lower than the charge for the same service in Australia.\n\nexisting customer, in relation to a participating telecommunications provider, means an entity who is a customer of the provider as at 30 November 2025.\n\ngovernment agency means:\n\n(a) a Commonwealth agency; or\n\n(b) a State or Territory of Australia; or\n\n(c) an authority of a State or Territory of Australia; or\n\n(d) a corporation in which a State or Territory of Australia, or an authority of a State or Territory of Australia, has a controlling interest.\n\n> identity verification service means:\n\n> an identity verification service as defined in section 5 of the Identity Verification Services Act 2023; or\n\n> a service designed to provide a high assurance level to verify an individual’s identity accurately, including through the use of government-issued identity documents, biometric or other information. This includes services that have been authorised, approved, or recognised by a foreign government.\n\ninternational mobile roaming service means a carriage service that is not an excluded satellite service and enables a consumer to automatically and seamlessly do any or all of the following when travelling overseas outside the normal coverage area without losing the connection:\n\n1.  make, send, access or receive voice calls or SMS/MMS messages;\n2.  download or upload data.\n\ninternational partner means an international telecommunications service provider that has a direct relationship with an entity and who has partnered with:\n\n1.  for an ABN entity or non-ABN entity – a certified telecommunications provider; or\n2.  for an ABN entity – a participating telecommunications provider;\n\nto make an application for registration of a sender identification and to send sender identification messages on behalf of the relevant entity.\n\ninternational telecommunications service provider means a telecommunications service provider or electronic messaging service provider based outside of Australia that is a non-ABN entity.\n\nmobile number has the meaning given by section 18 of the Telecommunications Numbering Plan 2025.\n\nNote: The Telecommunications Numbering Plan 2025 is a legislative instrument registered on the Federal Register of Legislation and may be accessed free of charge at www.legislation.gov.au.\n\nnon-ABN entity means an entity that does not have an ABN.\n\nNote: For example, a foreign company or an Australian entity that does not have an ABN will be a non-ABN entity.\n\noriginating telecommunications provider means a telecommunications provider that agrees to send sender identification messages on behalf of:\n\n1.  a customer; or\n\n1.  an international partner; or\n2.  an EMSP partner.\n\nparticipating telecommunications provider means a telecommunications provider that holds an approval under section 484F of the Act.\n\npersonal information has the same meaning as in the Privacy Act 1988.\n\nprospective customer, in relation to a participating telecommunications provider, means any entity who is not an existing customer but may become a customer of the provider.\n\nquarter means a period of 3 months beginning on 1 January, 1 April, 1 July or 1 October in any year.\n\nRegister means the SMS Sender ID Register.\n\nregister data means the list of registered sender identifications in the Register.\n\nRegister of Trade Marks means the register kept under section 207 of the Trade Marks Act 1995.\n\nregistered business name means a name that is registered under a law of a State or Territory that relates to the registration of business names and is entered on the Business Names Register.\n\nregistered domain name means a unique address or name that represents a website or other online resource on the internet that has been acquired from a domain name registrar.\n\nsatellite service means a carriage service where customer equipment used in connection with the supply of the service communicates directly with a satellite-based facility.\n\nscam message means any communication sent via SMS/MMS to a mobile number that includes a sender identification that is registered in the Register, that, based on the content of the communication, or other information available to a telecommunications provider, appears to have been sent for the purpose of dishonestly obtaining a benefit, or causing a loss, by deception or other means.\n\nsender identification match has the meaning given by subsection (2).\n\n> sender identification message means an SMS/MMS message that includes a sender identification and is sent to a mobile number issued in Australia.\n\nSMS/MMS message means a message sent using a short message service or a multimedia messaging service on a public mobile telecommunications service.\n\ntelecommunications provider means:\n\n1.  a carrier; or\n2.  a carriage service provider; or\n3.  an electronic messaging service provider.\n\nterminate, in relation to an SMS/MMS message, means to deliver the message to the message recipient.\n\nterminating telecommunications provider means a carrier that is responsible for delivering sender identification messages to message recipients who are connected to a public mobile telecommunications service owned or controlled by the carrier.\n\ntrade mark has the meaning given by section 17 of the Trade Marks Act 1995.\n\ntransit means to receive or send a sender identification message to facilitate the passing of the message between telecommunications providers over a telecommunications network.\n\ntransiting telecommunications provider means a telecommunications provider who connects with other telecommunications providers to transit sender identification messages between two telecommunications providers over a telecommunications network.\n\nvalid use case, in relation to a sender identification of an entity, means evidence that demonstrates a sender identification relates to, or is owned by, the entity.\n\n  To have a sender identification match for an entity, the sender identification:\n\n  for an ABN entity must be:\n\n    the same as; or\n    a contraction or abbreviation of; or\n    an acronym of; or\n    initialism of;\n\n  the entity’s registered business name, company name, trademark registered on the Register of Trade Marks; or registered domain name; or\n\n  for a non-ABN entity must be:\n\n    the same as; or\n    a contraction or abbreviation of; or\n    an acronym of; or\n    initialism of;\n\n  the entity’s trademark or its name entered on an official register or record in the country in which the entity is based; and\n\n  may also include one or more other words associated with the entity’s functions, location or which indicates the purpose of the sender identification message.\n\n  Note 1: For example, if an entity’s:\n  • company name is TS Pty Ltd;\n  • business name is Telservice;\n  • trade mark is TelService; and\n  • registered domain name is Zrates.com.au;\n  sender identification matches would include: “Telservice”, “TelServs”, “Telser”, “TS”, “TS\\_Track”, “TelServSale”, “Zrates” and “TS-Sydney”.\n\n> Note 2: A number of other expressions used in this industry standard are defined in the Act, including the following:\n\n    ACMA;\n    carriage service;\n    carriage service provider;\n    carrier;\n    customer equipment;\n    public mobile telecommunications service;\n    sender identification;\n    SMS Sender ID Register;\n    statutory infrastructure provider;\n    telecommunications network.\n\n  Note 3: Business day is defined in the Acts Interpretation Act 1901 to mean a day that is not a Saturday, a Sunday or a public holiday in the place concerned.\n\n## 6 References to other instruments\n\n  In this industry standard, unless the contrary intention appears:\n\n    a reference to any other legislative instrument is a reference to that other legislative instrument as in force from time to time; and\n    a reference to any other kind of instrument is a reference to that other instrument as in force or existing from time to time.\n\n> Note 1: For references to Commonwealth Acts, see section 10 of the Acts Interpretation Act 1901; and see also subsection 13(1) of the Legislation Act 2003 for the application of the Acts Interpretation Act 1901 to legislative instruments.\n\n> Note 2: For references to instruments that are not legislative instruments, see section 589 of the Act.\n\n> Note 3: All Commonwealth Acts and legislative instruments are registered on the Federal Register of Legislation. The Federal Register of Legislation may be accessed free of charge at www.legislation.gov.au.","sortOrder":0},{"sectionNumber":"1","sectionType":"part","heading":"Name","content":"## 1 Name\n\n  This industry standard is the Telecommunications (SMS Sender ID Register) Industry Standard 2025.","sortOrder":1},{"sectionNumber":"2","sectionType":"part","heading":"Commencement","content":"## 2 Commencement\n\n> Note: Each provision of this industry standard specified in column 1 of the table commences, or is taken to have commenced, in accordance with column 2 of the table.\n\n| Column 1                                                | Column 2          |\n| ------------------------------------------------------- | ----------------- |\n| Provisions                                              | Commencement      |\n| 1. Sections 1 to 8, subsection 15(2), Part 4 and Part 6 | 15 October 2025.  |\n| 2. Sections 9 to 14, Part 7 and Schedule 1              | 30 November 2025. |\n| 3. Part 3 except subsection 15(2), and Part 5           | 1 July 2026.      |\n\nNote 1: This table relates only to the provisions of this industry standard as originally made. It will not be amended to deal with any later amendments of this industry standard.\n\nNote 2: The Federal Register of Legislation may be accessed free of charge at www.legislation.gov.au.","sortOrder":2},{"sectionNumber":"3","sectionType":"part","heading":"Authority","content":"## 3 Authority\n\n  This industry standard is made under subsection 125AA(1) of the Telecommunications Act 1997 and in accordance with sections 5, 6, 7 and 8 of the Telecommunications (SMS Sender ID Register Industry Standard) Direction 2025.","sortOrder":3},{"sectionNumber":"4","sectionType":"part","heading":"Application of industry standard","content":"## 4 Application of industry standard\n\n  Subject to subsection (2), for the purposes of subsection 125AA(1) of the Act, this industry standard:\n\n  applies to the following sections of the telecommunications industry:\n\n  carriers;\n  carriage service providers;\n  electronic messaging service providers; and\n\n  gives effect to the objectives set out in section 7 of the Telecommunications (SMS Sender ID Register Industry Standard) Direction 2025.\n\n  This industry standard does not apply to a carrier, or a carriage service provider, in its capacity as a statutory infrastructure provider.\n  An electronic messaging service provider may comply with its obligations under this industry standard by:\n\n  fulfilling the obligations itself; or\n  arranging with another person who is a participating telecommunications provider to fulfill some or all of the obligations on its behalf under subsection 13(5).","sortOrder":4},{"sectionNumber":"5","sectionType":"part","heading":"Definitions","content":"## 5 Definitions\n\n  In this industry standard:\n\n> ABN (short for “Australian Business Number”) has the meaning given by section 41 of the A New Tax System (Australian Business Number) Act 1999.\n\nABN entity means an entity that has an ABN.\n\n> Act means the Telecommunications Act 1997.\n\n> Australian Business Register means the register established under section 24 of the A New Tax System (Australian Business Number) Act 1999.\n\nBusiness Names Register means the register established and maintained under section 22 of the Business Names Registration Act 2011.\n\ncertified telecommunications provider means a participating telecommunications provider that is an originating telecommunications provider that has been approved to be a certified telecommunications provider under a determination made under subsection 484L(4) of the Act.\n\n  Note 1: See paragraph 589(2)(b) of the Act.\n\nCommonwealth agency means:\n\n(a) the Commonwealth; or\n\n(b) an authority of the Commonwealth; or\n\n(c) a corporation in which the Commonwealth, or an authority of the Commonwealth, has a controlling interest;\n\nand includes the Australian Defence Force.\n\ncompany has the meaning given by section 9 of the Corporations Act 2001.\n\ncustomer, in relation to a telecommunications provider, means an entity that has a contractual arrangement with the provider relating to the sending of sender identification messages.\n\nNote: A customer can be an ABN entity or a non-ABN entity.\n\ndisrupt, in relation to a sender identification message, means where the sender identification included in the message is over-stamped by a participating telecommunications provider with a new sender identification of “Unverified”.\n\ndomain name registrar means a business that handles the reservation of domain names as well as the assignment of IP addresses for those domain names.\n\nelectronic messaging service provider has the same meaning as in section 108A of the Act.\n\nEMSP partner means an electronic messaging service provider that has a direct relationship with an entity and who has partnered with:\n\n1.  for an ABN entity or non-ABN entity – a certified telecommunications provider; or\n2.  for an ABN entity – a participating telecommunications provider that is an originating telecommunications provider, and that is not a certified telecommunications provider;\n\nand who has made a request for the provider to fulfill some or all of the partner’s obligations under this industry standard on its behalf.\n\nentity means an entity covered by subsection 484F(2) of the Act that uses or proposes to use sender identification messages.\n\nentity associate means an entity who is authorised by another entity to send sender identification messages using the sender identification registered in the Register for that other entity.\n\nexcluded satellite service means a satellite service that may be used by a consumer in an overseas location where the charge for that service is the same or lower than the charge for the same service in Australia.\n\nexisting customer, in relation to a participating telecommunications provider, means an entity who is a customer of the provider as at 30 November 2025.\n\ngovernment agency means:\n\n(a) a Commonwealth agency; or\n\n(b) a State or Territory of Australia; or\n\n(c) an authority of a State or Territory of Australia; or\n\n(d) a corporation in which a State or Territory of Australia, or an authority of a State or Territory of Australia, has a controlling interest.\n\n> identity verification service means:\n\n> an identity verification service as defined in section 5 of the Identity Verification Services Act 2023; or\n\n> a service designed to provide a high assurance level to verify an individual’s identity accurately, including through the use of government-issued identity documents, biometric or other information. This includes services that have been authorised, approved, or recognised by a foreign government.\n\ninternational mobile roaming service means a carriage service that is not an excluded satellite service and enables a consumer to automatically and seamlessly do any or all of the following when travelling overseas outside the normal coverage area without losing the connection:\n\n1.  make, send, access or receive voice calls or SMS/MMS messages;\n2.  download or upload data.\n\ninternational partner means an international telecommunications service provider that has a direct relationship with an entity and who has partnered with:\n\n1.  for an ABN entity or non-ABN entity – a certified telecommunications provider; or\n2.  for an ABN entity – a participating telecommunications provider;\n\nto make an application for registration of a sender identification and to send sender identification messages on behalf of the relevant entity.\n\ninternational telecommunications service provider means a telecommunications service provider or electronic messaging service provider based outside of Australia that is a non-ABN entity.\n\nmobile number has the meaning given by section 18 of the Telecommunications Numbering Plan 2025.\n\nNote: The Telecommunications Numbering Plan 2025 is a legislative instrument registered on the Federal Register of Legislation and may be accessed free of charge at www.legislation.gov.au.\n\nnon-ABN entity means an entity that does not have an ABN.\n\nNote: For example, a foreign company or an Australian entity that does not have an ABN will be a non-ABN entity.\n\noriginating telecommunications provider means a telecommunications provider that agrees to send sender identification messages on behalf of:\n\n1.  a customer; or\n\n1.  an international partner; or\n2.  an EMSP partner.\n\nparticipating telecommunications provider means a telecommunications provider that holds an approval under section 484F of the Act.\n\npersonal information has the same meaning as in the Privacy Act 1988.\n\nprospective customer, in relation to a participating telecommunications provider, means any entity who is not an existing customer but may become a customer of the provider.\n\nquarter means a period of 3 months beginning on 1 January, 1 April, 1 July or 1 October in any year.\n\nRegister means the SMS Sender ID Register.\n\nregister data means the list of registered sender identifications in the Register.\n\nRegister of Trade Marks means the register kept under section 207 of the Trade Marks Act 1995.\n\nregistered business name means a name that is registered under a law of a State or Territory that relates to the registration of business names and is entered on the Business Names Register.\n\nregistered domain name means a unique address or name that represents a website or other online resource on the internet that has been acquired from a domain name registrar.\n\nsatellite service means a carriage service where customer equipment used in connection with the supply of the service communicates directly with a satellite-based facility.\n\nscam message means any communication sent via SMS/MMS to a mobile number that includes a sender identification that is registered in the Register, that, based on the content of the communication, or other information available to a telecommunications provider, appears to have been sent for the purpose of dishonestly obtaining a benefit, or causing a loss, by deception or other means.\n\nsender identification match has the meaning given by subsection (2).\n\n> sender identification message means an SMS/MMS message that includes a sender identification and is sent to a mobile number issued in Australia.\n\nSMS/MMS message means a message sent using a short message service or a multimedia messaging service on a public mobile telecommunications service.\n\ntelecommunications provider means:\n\n1.  a carrier; or\n2.  a carriage service provider; or\n3.  an electronic messaging service provider.\n\nterminate, in relation to an SMS/MMS message, means to deliver the message to the message recipient.\n\nterminating telecommunications provider means a carrier that is responsible for delivering sender identification messages to message recipients who are connected to a public mobile telecommunications service owned or controlled by the carrier.\n\ntrade mark has the meaning given by section 17 of the Trade Marks Act 1995.\n\ntransit means to receive or send a sender identification message to facilitate the passing of the message between telecommunications providers over a telecommunications network.\n\ntransiting telecommunications provider means a telecommunications provider who connects with other telecommunications providers to transit sender identification messages between two telecommunications providers over a telecommunications network.\n\nvalid use case, in relation to a sender identification of an entity, means evidence that demonstrates a sender identification relates to, or is owned by, the entity.\n\n  To have a sender identification match for an entity, the sender identification:\n\n  for an ABN entity must be:\n\n    the same as; or\n    a contraction or abbreviation of; or\n    an acronym of; or\n    initialism of;\n\n  the entity’s registered business name, company name, trademark registered on the Register of Trade Marks; or registered domain name; or\n\n  for a non-ABN entity must be:\n\n    the same as; or\n    a contraction or abbreviation of; or\n    an acronym of; or\n    initialism of;\n\n  the entity’s trademark or its name entered on an official register or record in the country in which the entity is based; and\n\n  may also include one or more other words associated with the entity’s functions, location or which indicates the purpose of the sender identification message.\n\n  Note 1: For example, if an entity’s:\n  • company name is TS Pty Ltd;\n  • business name is Telservice;\n  • trade mark is TelService; and\n  • registered domain name is Zrates.com.au;\n  sender identification matches would include: “Telservice”, “TelServs”, “Telser”, “TS”, “TS\\_Track”, “TelServSale”, “Zrates” and “TS-Sydney”.\n\n> Note 2: A number of other expressions used in this industry standard are defined in the Act, including the following:\n\n    ACMA;\n    carriage service;\n    carriage service provider;\n    carrier;\n    customer equipment;\n    public mobile telecommunications service;\n    sender identification;\n    SMS Sender ID Register;\n    statutory infrastructure provider;\n    telecommunications network.\n\n  Note 3: Business day is defined in the Acts Interpretation Act 1901 to mean a day that is not a Saturday, a Sunday or a public holiday in the place concerned.","sortOrder":5},{"sectionNumber":"6","sectionType":"part","heading":"References to other instruments","content":"## 6 References to other instruments\n\n  In this industry standard, unless the contrary intention appears:\n\n    a reference to any other legislative instrument is a reference to that other legislative instrument as in force from time to time; and\n    a reference to any other kind of instrument is a reference to that other instrument as in force or existing from time to time.\n\n> Note 1: For references to Commonwealth Acts, see section 10 of the Acts Interpretation Act 1901; and see also subsection 13(1) of the Legislation Act 2003 for the application of the Acts Interpretation Act 1901 to legislative instruments.\n\n> Note 2: For references to instruments that are not legislative instruments, see section 589 of the Act.\n\n> Note 3: All Commonwealth Acts and legislative instruments are registered on the Federal Register of Legislation. The Federal Register of Legislation may be accessed free of charge at www.legislation.gov.au.","sortOrder":6},{"sectionNumber":"Part 2","sectionType":"part","heading":"Requirements relating to the Register","content":"# Part 2—Requirements relating to the Register\n\n## 7 Application for approval\n\n  A telecommunications provider that sends, transits or terminates sender identification messages must apply to the ACMA for an approval under section 484F of the Act.\n\n> Note: An entity that holds an approval under section 484F of the Act may apply to the ACMA for a sender identification to be registered in the Register under section 484G of the Act.\n\n## 8 Application to be a certified telecommunications provider\n\n  A participating telecommunications provider that wishes to:\n\n  make an application for registration of a sender identification in the Register; and\n  send sender identification messages;\n\n  on behalf of a non-ABN entity must apply to the ACMA for approval to be a certified telecommunications provider.\n  Note: A participating telecommunications provider can apply to the ACMA for approval to be a certified telecommunications provider under a determination made under section 484L of the Act.\n\n## 9 Requirements to provide information to entities\n\n  Requirements regarding existing customers – before 1 July 2026\n\n  A participating telecommunications provider that is an originating telecommunications provider must contact each of its existing customers before 1 July 2026 to:\n\n  provide to the customer, in writing, the information in Schedule 1; and\n  subject to subsection (4), offer to make an application for registration of a sender identification in the Register on behalf of the customer.\n\n  Requirements regarding prospective customers seeking to use a new sender identification\n\n  If:\n\n  a participating telecommunications provider that is an originating telecommunications provider receives a request from a prospective customer, who asks the provider to send a sender identification message on behalf of the customer; and\n  the provider agrees to provide that service; and\n  the sender identification is not registered in the Register,\n\n  the provider must:\n\n  provide to the customer, in writing, the information in Schedule 1; and\n  subject to subsection (4), offer to make an application for registration of the sender identification in the Register on behalf of the customer.\n\n  Requirements regarding existing customers using a new sender identification\n\n  If:\n\n  a participating telecommunications provider that is an originating telecommunications provider receives a request from an existing customer, who asks the provider to send a sender identification message on behalf of the customer; and\n  the sender identification is not registered in the Register,\n\n  the provider must:\n\n  provide to the customer, in writing, the information in Schedule 1; and\n  subject to subsection (4), offer to make an application for registration of the sender identification in the Register on behalf of the customer.\n\n  Where the customer is a non-ABN entity, the requirement in each of paragraphs (1)(b), (2)(e) and (3)(d) does not apply, unless the provider is a certified telecommunications provider.\n\n## 10 Requirement to publish information\n\n  All originating telecommunications providers must make available on their website the information about the Register referred to in Schedule 1.\n\n## 11 Requirements relating to the registration of sender identifications on behalf of an ABN entity\n\n  Requirements for a participating telecommunications provider that is an originating telecommunications provider\n\n  Subject to subsection (2), if:\n\n  an ABN entity requests a participating telecommunications provider that is an originating telecommunications provider to make an application for registration of a sender identification in the Register on behalf of the entity; and\n  the provider agrees to send sender identification messages on behalf of the entity;\n\n  the provider must make an application for registration of the sender identification in the Register on behalf of the entity.\n\n  Before making the application, the provider must ask the entity if it is an entity associate for another entity.\n  If the entity is an entity associate for another entity (the other entity), the provider must:\n\n  apply to the ACMA for an approval on behalf of the entity associate under section 484F of the Act; and\n  confirm with the other entity that the entity associate is authorised by the other entity to send a sender identification message that includes that other entity’s sender identification registered in the Register; and\n  subject to paragraph (b), if the sender identification is not registered in the Register – make an application for registration of the sender identification on behalf of the other entity.\n\n  Before making an application for registration of a sender identification in the Register on behalf of an ABN entity, a participating telecommunications provider that is an originating telecommunications provider must establish that the entity has a valid use case for the sender identification by:\n\n  confirming that:\n\n    there is a sender identification match for the entity in relation to the registered business name of the entity in the Business Names Register; and\n    the status of the business name of the entity is “registered”; or\n  confirming that:\n\n    there is a sender identification match for the entity in relation to the company name of the entity in the Australian Business Register; and\n    the status of the ABN relating to the entity is “active”; or\n  confirming that:\n\n    there is a sender identification match for the entity in relation to a trade mark owned by the entity and included in the Register of Trade Marks or an equivalent international register of trademarks; and\n    the status of the trademark owned by the entity is “registered”; or\n  confirming that:\n\n    there is a sender identification match for the entity in relation to a registered domain name of which the entity is the “registrant” in the whois.auda.org.au database; and\n\n  either,\n\n  the registered domain name is used for a website:\n\n  that can be accessed via the internet at the time that the valid use case is being confirmed; and\n  which the provider believes on reasonable grounds is a legitimate website; or\n\n    the registered domain name is used for an email account to which the provider has sent an email at the time that the valid use case is being confirmed and, the provider has not received a notification from the email server that the email message was not able to be delivered.\n\n  Subsection (4) does not apply where:\n\n  the ABN entity is a government agency that intends to use a sender identification in relation to which there is no sender identification match for the entity; and\n  the sender identification relates to an emergency, or a matter of public health, safety or security; and\n  the entity has provided evidence to the provider that satisfies the provider of the reason why the agency intends to use the sender identification rather than its registered business name, company name, trademark or registered domain name, as relevant.\n\n  Requirements for a certified telecommunications provider\n\n  If:\n\n  an ABN entity requests a certified telecommunications provider to make an application for registration of a sender identification in the Register on behalf of the entity; and\n  the provider agrees to send sender identification messages on behalf of the entity;\n\n  subject to subsection (7), the provider must make an application for registration of the sender identification in the Register on behalf of the entity.\n\n  Before making the application, the provider must comply with subsections 12(4) and (5), as if the ABN entity were a non-ABN entity.\n\n## 12 Requirements relating to the registration of sender identifications on behalf of a non-ABN entity\n\n  Subject to subsection (2), if:\n\n  a non-ABN entity requests a certified telecommunications provider to make an application for registration of a sender identification in the Register on behalf of the entity; and\n  the provider agrees to send sender identification messages on behalf of the entity;\n\n  the provider must make an application for registration of the sender identification in the Register on behalf of the entity.\n\n  Before making the application, the provider must ask the entity if it is an entity associate for another entity.\n  If the entity is an entity associate for another entity (the other entity), the provider must:\n\n  apply to the ACMA for an approval on behalf of the entity associate under section 484F of the Act; and\n  confirm with the other entity that the entity associate is authorised by the other entity to send sender identification messages that includes that other entity’s sender identification registered in the Register; and\n  subject to paragraph (b), if the sender identification is not registered in the Register – make an application for registration of the sender identification on behalf of the other entity.\n\n  Before making the application, the provider must do the following:\n\n  confirm the identity of the person who has requested the provider to make the application on behalf of the entity, using an identity verification service; and\n  confirm that the person is an authorised representative of the entity; and\n  confirm that the entity has been officially recognised or certified by a governing body, regulatory authority or accreditation organisation in the country in which the entity is based; and\n  establish that the entity has a valid use case for the sender identification by confirming that there is a sender identification match for the entity using a trademark register or an official register or record in the country in which the entity is based.\n\n  Note: For example, the provider may check that the entity is listed on an official business register for the country in which the entity is based, or that it has been accredited by an industry association.\n\n  Subsection (4) does not apply where:\n\n  the non-ABN entity is a government agency that intends to use a sender identification in relation to which there is no sender identification match for the entity; and\n  that sender identification relates to an emergency, or a matter of public health, safety or security; and\n  the entity has provided evidence to the provider that satisfies the provider of the reason why the agency intends to use the sender identification rather than its trademark or name on an official register or record in the country in which the entity is based, as relevant.\n\n  A certified telecommunications provider must ensure that the contact details in the Register, including email address, for a non-ABN entity on whose behalf the provider has made an application to register a sender identification, are current.\n\n  Note: The ACMA will send to a non-ABN entity notifications relating to the registration of a sender identification in the Register on behalf of the entity.\n\n## 13 Requirements relating to the registration of sender identifications for an international partner or an EMSP partner\n\n  International partners\n\n  If:\n\n  an international partner requests:\n\n    a certified telecommunications provider to make an application for registration of a sender identification in the Register, for the partner, on behalf of a non-ABN entity or an ABN entity; or\n    a participating telecommunications provider that is an originating telecommunications provider, and that is not a certified telecommunications provider, to make an application for registration of a sender identification in the Register, for the partner, on behalf of an ABN entity; and\n  the provider agrees to send sender identification messages for the partner;\n\n  the provider must make an application for registration of the entity’s sender identification in the Register, for the partner, on behalf of the ABN entity.\n\n1.  Subject to subsection (4), before making the application under subparagraph 13(1)(a)(i), the provider must have made written contractual arrangements with the international partner, which:\n\n1.  remain in force for as long as the partner is involved in the sending of sender identification messages; and\n2.  require the partner to perform the confirmations at paragraphs 12(4)(a), (b) and (c).\n\nNote: For an application made under subparagraph 13(1)(a)(ii), the confirmations in paragraph (b) will be undertaken by the ACMA via the Register system.\n\n1.  Subject to subsection (4), before making the application under subparagraph 13(1)(a)(i) or (ii), the provider must have made written contractual arrangements with the international partner which:\n\n1.  remain in force for as long as the partner is involved in the sending of sender identification messages; and\n2.  require the international partner to establish that the entity on whose behalf the sender identification is to be registered has a valid use case for the sender identification:\n\n1.  for a non-ABN entity – by confirming that there is a sender identification match for the entity by using by using one of the confirmation methods mentioned in paragraph 12(4)(d); or\n2.  for an ABN entity – by confirming that there is a sender identification match for the entity by using one of the confirmation methods mentioned in subsection 11(4).\n\n  The requirements in subsections (2) and (3) do not apply where the provider has made written contractual arrangements with the international partner to undertake the actions in subsections (2) and (3) on behalf of the international partner.\n\n  EMSP partner\n\n  A participating telecommunications provider who has partnered with an EMSP partner, must fulfill those obligations under this industry standard as agreed with the EMSP partner.\n\n  Notifications\n\n  Within 24 hours of receipt by a certified telecommunications partner of:\n\n  a notice of decision given by the ACMA under Part 24B of the Act, in relation to an application for registration of a sender identification in the Register made by a certified telecommunications provider on behalf of an international partner or an EMSP partner; or\n  a notice given by the ACMA relating to a sender identification that has been registered in response to an application made by a certified telecommunications provider on behalf of an international partner or an EMSP partner; or\n  a request from an international partner or an EMSP partner asking for the removal of a sender identification from the Register;\n\n  the provider must provide the notice to the international partner or EMSP partner or action the request, as relevant.\n\n## 14 Requirement not to mislead\n\n  A participating telecommunications provider must not, in any communication with an entity, expressly or impliedly indicate that the sender identification messages can only be sent by the telecommunications provider that made the application to register the sender identification in the Register on behalf of the entity.\n  Note: Messages containing a sender identification can be sent by more than one participating telecommunications provider.","sortOrder":7},{"sectionNumber":"7","sectionType":"part","heading":"Application for approval","content":"## 7 Application for approval\n\n  A telecommunications provider that sends, transits or terminates sender identification messages must apply to the ACMA for an approval under section 484F of the Act.\n\n> Note: An entity that holds an approval under section 484F of the Act may apply to the ACMA for a sender identification to be registered in the Register under section 484G of the Act.","sortOrder":8},{"sectionNumber":"8","sectionType":"part","heading":"Application to be a certified telecommunications provider","content":"## 8 Application to be a certified telecommunications provider\n\n  A participating telecommunications provider that wishes to:\n\n  make an application for registration of a sender identification in the Register; and\n  send sender identification messages;\n\n  on behalf of a non-ABN entity must apply to the ACMA for approval to be a certified telecommunications provider.\n  Note: A participating telecommunications provider can apply to the ACMA for approval to be a certified telecommunications provider under a determination made under section 484L of the Act.","sortOrder":9},{"sectionNumber":"9","sectionType":"part","heading":"Requirements to provide information to entities","content":"## 9 Requirements to provide information to entities\n\n  Requirements regarding existing customers – before 1 July 2026\n\n  A participating telecommunications provider that is an originating telecommunications provider must contact each of its existing customers before 1 July 2026 to:\n\n  provide to the customer, in writing, the information in Schedule 1; and\n  subject to subsection (4), offer to make an application for registration of a sender identification in the Register on behalf of the customer.\n\n  Requirements regarding prospective customers seeking to use a new sender identification\n\n  If:\n\n  a participating telecommunications provider that is an originating telecommunications provider receives a request from a prospective customer, who asks the provider to send a sender identification message on behalf of the customer; and\n  the provider agrees to provide that service; and\n  the sender identification is not registered in the Register,\n\n  the provider must:\n\n  provide to the customer, in writing, the information in Schedule 1; and\n  subject to subsection (4), offer to make an application for registration of the sender identification in the Register on behalf of the customer.\n\n  Requirements regarding existing customers using a new sender identification\n\n  If:\n\n  a participating telecommunications provider that is an originating telecommunications provider receives a request from an existing customer, who asks the provider to send a sender identification message on behalf of the customer; and\n  the sender identification is not registered in the Register,\n\n  the provider must:\n\n  provide to the customer, in writing, the information in Schedule 1; and\n  subject to subsection (4), offer to make an application for registration of the sender identification in the Register on behalf of the customer.\n\n  Where the customer is a non-ABN entity, the requirement in each of paragraphs (1)(b), (2)(e) and (3)(d) does not apply, unless the provider is a certified telecommunications provider.","sortOrder":10},{"sectionNumber":"10","sectionType":"part","heading":"Requirement to publish information","content":"## 10 Requirement to publish information\n\n  All originating telecommunications providers must make available on their website the information about the Register referred to in Schedule 1.","sortOrder":11},{"sectionNumber":"11","sectionType":"part","heading":"Requirements relating to the registration of sender identifications on behalf of an ABN entity","content":"## 11 Requirements relating to the registration of sender identifications on behalf of an ABN entity\n\n  Requirements for a participating telecommunications provider that is an originating telecommunications provider\n\n  Subject to subsection (2), if:\n\n  an ABN entity requests a participating telecommunications provider that is an originating telecommunications provider to make an application for registration of a sender identification in the Register on behalf of the entity; and\n  the provider agrees to send sender identification messages on behalf of the entity;\n\n  the provider must make an application for registration of the sender identification in the Register on behalf of the entity.\n\n  Before making the application, the provider must ask the entity if it is an entity associate for another entity.\n  If the entity is an entity associate for another entity (the other entity), the provider must:\n\n  apply to the ACMA for an approval on behalf of the entity associate under section 484F of the Act; and\n  confirm with the other entity that the entity associate is authorised by the other entity to send a sender identification message that includes that other entity’s sender identification registered in the Register; and\n  subject to paragraph (b), if the sender identification is not registered in the Register – make an application for registration of the sender identification on behalf of the other entity.\n\n  Before making an application for registration of a sender identification in the Register on behalf of an ABN entity, a participating telecommunications provider that is an originating telecommunications provider must establish that the entity has a valid use case for the sender identification by:\n\n  confirming that:\n\n    there is a sender identification match for the entity in relation to the registered business name of the entity in the Business Names Register; and\n    the status of the business name of the entity is “registered”; or\n  confirming that:\n\n    there is a sender identification match for the entity in relation to the company name of the entity in the Australian Business Register; and\n    the status of the ABN relating to the entity is “active”; or\n  confirming that:\n\n    there is a sender identification match for the entity in relation to a trade mark owned by the entity and included in the Register of Trade Marks or an equivalent international register of trademarks; and\n    the status of the trademark owned by the entity is “registered”; or\n  confirming that:\n\n    there is a sender identification match for the entity in relation to a registered domain name of which the entity is the “registrant” in the whois.auda.org.au database; and\n\n  either,\n\n  the registered domain name is used for a website:\n\n  that can be accessed via the internet at the time that the valid use case is being confirmed; and\n  which the provider believes on reasonable grounds is a legitimate website; or\n\n    the registered domain name is used for an email account to which the provider has sent an email at the time that the valid use case is being confirmed and, the provider has not received a notification from the email server that the email message was not able to be delivered.\n\n  Subsection (4) does not apply where:\n\n  the ABN entity is a government agency that intends to use a sender identification in relation to which there is no sender identification match for the entity; and\n  the sender identification relates to an emergency, or a matter of public health, safety or security; and\n  the entity has provided evidence to the provider that satisfies the provider of the reason why the agency intends to use the sender identification rather than its registered business name, company name, trademark or registered domain name, as relevant.\n\n  Requirements for a certified telecommunications provider\n\n  If:\n\n  an ABN entity requests a certified telecommunications provider to make an application for registration of a sender identification in the Register on behalf of the entity; and\n  the provider agrees to send sender identification messages on behalf of the entity;\n\n  subject to subsection (7), the provider must make an application for registration of the sender identification in the Register on behalf of the entity.\n\n  Before making the application, the provider must comply with subsections 12(4) and (5), as if the ABN entity were a non-ABN entity.","sortOrder":12},{"sectionNumber":"12","sectionType":"part","heading":"Requirements relating to the registration of sender identifications on behalf of a non-ABN entity","content":"## 12 Requirements relating to the registration of sender identifications on behalf of a non-ABN entity\n\n  Subject to subsection (2), if:\n\n  a non-ABN entity requests a certified telecommunications provider to make an application for registration of a sender identification in the Register on behalf of the entity; and\n  the provider agrees to send sender identification messages on behalf of the entity;\n\n  the provider must make an application for registration of the sender identification in the Register on behalf of the entity.\n\n  Before making the application, the provider must ask the entity if it is an entity associate for another entity.\n  If the entity is an entity associate for another entity (the other entity), the provider must:\n\n  apply to the ACMA for an approval on behalf of the entity associate under section 484F of the Act; and\n  confirm with the other entity that the entity associate is authorised by the other entity to send sender identification messages that includes that other entity’s sender identification registered in the Register; and\n  subject to paragraph (b), if the sender identification is not registered in the Register – make an application for registration of the sender identification on behalf of the other entity.\n\n  Before making the application, the provider must do the following:\n\n  confirm the identity of the person who has requested the provider to make the application on behalf of the entity, using an identity verification service; and\n  confirm that the person is an authorised representative of the entity; and\n  confirm that the entity has been officially recognised or certified by a governing body, regulatory authority or accreditation organisation in the country in which the entity is based; and\n  establish that the entity has a valid use case for the sender identification by confirming that there is a sender identification match for the entity using a trademark register or an official register or record in the country in which the entity is based.\n\n  Note: For example, the provider may check that the entity is listed on an official business register for the country in which the entity is based, or that it has been accredited by an industry association.\n\n  Subsection (4) does not apply where:\n\n  the non-ABN entity is a government agency that intends to use a sender identification in relation to which there is no sender identification match for the entity; and\n  that sender identification relates to an emergency, or a matter of public health, safety or security; and\n  the entity has provided evidence to the provider that satisfies the provider of the reason why the agency intends to use the sender identification rather than its trademark or name on an official register or record in the country in which the entity is based, as relevant.\n\n  A certified telecommunications provider must ensure that the contact details in the Register, including email address, for a non-ABN entity on whose behalf the provider has made an application to register a sender identification, are current.\n\n  Note: The ACMA will send to a non-ABN entity notifications relating to the registration of a sender identification in the Register on behalf of the entity.","sortOrder":13},{"sectionNumber":"13","sectionType":"part","heading":"Requirements relating to the registration of sender identifications for an international partner or an EMSP partner","content":"## 13 Requirements relating to the registration of sender identifications for an international partner or an EMSP partner\n\n  International partners\n\n  If:\n\n  an international partner requests:\n\n    a certified telecommunications provider to make an application for registration of a sender identification in the Register, for the partner, on behalf of a non-ABN entity or an ABN entity; or\n    a participating telecommunications provider that is an originating telecommunications provider, and that is not a certified telecommunications provider, to make an application for registration of a sender identification in the Register, for the partner, on behalf of an ABN entity; and\n  the provider agrees to send sender identification messages for the partner;\n\n  the provider must make an application for registration of the entity’s sender identification in the Register, for the partner, on behalf of the ABN entity.\n\n1.  Subject to subsection (4), before making the application under subparagraph 13(1)(a)(i), the provider must have made written contractual arrangements with the international partner, which:\n\n1.  remain in force for as long as the partner is involved in the sending of sender identification messages; and\n2.  require the partner to perform the confirmations at paragraphs 12(4)(a), (b) and (c).\n\nNote: For an application made under subparagraph 13(1)(a)(ii), the confirmations in paragraph (b) will be undertaken by the ACMA via the Register system.\n\n1.  Subject to subsection (4), before making the application under subparagraph 13(1)(a)(i) or (ii), the provider must have made written contractual arrangements with the international partner which:\n\n1.  remain in force for as long as the partner is involved in the sending of sender identification messages; and\n2.  require the international partner to establish that the entity on whose behalf the sender identification is to be registered has a valid use case for the sender identification:\n\n1.  for a non-ABN entity – by confirming that there is a sender identification match for the entity by using by using one of the confirmation methods mentioned in paragraph 12(4)(d); or\n2.  for an ABN entity – by confirming that there is a sender identification match for the entity by using one of the confirmation methods mentioned in subsection 11(4).\n\n  The requirements in subsections (2) and (3) do not apply where the provider has made written contractual arrangements with the international partner to undertake the actions in subsections (2) and (3) on behalf of the international partner.\n\n  EMSP partner\n\n  A participating telecommunications provider who has partnered with an EMSP partner, must fulfill those obligations under this industry standard as agreed with the EMSP partner.\n\n  Notifications\n\n  Within 24 hours of receipt by a certified telecommunications partner of:\n\n  a notice of decision given by the ACMA under Part 24B of the Act, in relation to an application for registration of a sender identification in the Register made by a certified telecommunications provider on behalf of an international partner or an EMSP partner; or\n  a notice given by the ACMA relating to a sender identification that has been registered in response to an application made by a certified telecommunications provider on behalf of an international partner or an EMSP partner; or\n  a request from an international partner or an EMSP partner asking for the removal of a sender identification from the Register;\n\n  the provider must provide the notice to the international partner or EMSP partner or action the request, as relevant.","sortOrder":14},{"sectionNumber":"14","sectionType":"part","heading":"Requirement not to mislead","content":"## 14 Requirement not to mislead\n\n  A participating telecommunications provider must not, in any communication with an entity, expressly or impliedly indicate that the sender identification messages can only be sent by the telecommunications provider that made the application to register the sender identification in the Register on behalf of the entity.\n  Note: Messages containing a sender identification can be sent by more than one participating telecommunications provider.","sortOrder":15},{"sectionNumber":"Part 3","sectionType":"part","heading":"Requirements relating to sending sender identification messages","content":"# Part 3—Requirements relating to sending sender identification messages\n\n## 15 Requirement on telecommunication providers\n\n  A telecommunications provider that is not a participating telecommunications provider must not send, transit or terminate a sender identification message.\n  A telecommunications provider that is not a participating telecommunications provider must not misrepresent itself as a participating telecommunications provider (including as a certified telecommunications provider).\n\n## 16 Requirements on originating telecommunications providers\n\n  This section applies to a participating telecommunications provider that is an originating telecommunications provider.\n\n  Requirements prior to sending sender identification messages\n\n  Before enabling a customer’s account to send a sender identification message on behalf of an entity, the provider must check if the sender identification included in the message is registered in the Register for that entity.\n  If the sender identification included in the message is not registered in the Register for that entity – the provider must disrupt the message.\n\n  Note: If a provider has disrupted a sender identification message under subsection (3), the provider can send the message that has been disrupted.\n\n  If the sender identification included in the sender identification message is registered in the Register for the entity, the provider must confirm:\n\n  that it is authorised by the entity to send messages that include that sender identification; and\n  that the person who has requested the provider to enable the customer’s account to send a sender identification message is authorised by the entity.\n\n  Note: Messages containing a sender identification can be sent by more than one participating telecommunications provider, if the other providers have been authorised by the entity.\n\n  The provider must not enable the customer’s account to send a sender identification message that includes the sender identification that is registered in the Register unless the provider has confirmed the matters mentioned in subsection (4).\n  If the provider receives notification from the ACMA that the provider is no longer authorised to send messages that include a sender identification for an entity, the provider must disable the customer account for the sender identification and cease sending any messages for that entity that include that sender identification immediately.\n\n  Note: The provider may receive notification from the ACMA if the entity has revoked the provider’s authorisation to send messages that include the sender identification or if the sender identification is no longer registered in the Register.\n\n  The provider must ensure that access to an account that has been enabled for an entity to send a sender identification message can only be accessed by authorised representatives of that entity.\n\n  Requirements relating to sending sender identification messages\n\n  Subject to subsection (9), the provider must not send a sender identification message to a telecommunications provider that is not a participating telecommunications provider.\n  A provider that receives a sender identification message from its EMSP partner or its international partner, as relevant, may send the message to a participating telecommunications provider that is:\n\n  a transiting telecommunications provider; or\n  a terminating telecommunications provider.\n\n  A provider that is also a terminating telecommunications provider, that receives a sender identification message from its EMSP partner or its international partner, as relevant, may terminate the message.\n\n## 17 Requirements on transiting telecommunications providers\n\n  This section applies to a participating telecommunications provider that is a transiting telecommunications provider.\n  Subject to subsections (3) and (4), the provider must not transit a sender identification message unless:\n\n  the telecommunications provider sending the message; and\n  the telecommunications provider to which the provider transits the message\n\n  are participating telecommunications providers.\n\n  Subsection (2) does not apply where a sender identification message is sent to a mobile number that is connected with a carriage service that is an international mobile roaming service.\n\n  Note: For example, subsection (3) will apply where an individual, with a mobile number that was issued in Australia, is using an international mobile roaming service. The transiting provider in this scenario will be the Australian mobile network operator of the network that the international roaming customer’s service is connected to when in Australia.\n  Messages from an international telecommunications service provider\n\n  Despite subsection (2), if a sender identification message is received by the provider from an international telecommunications service provider – the provider is permitted to transit the message if the provider has disrupted the message.\n\n## 18 Requirements on terminating telecommunications providers\n\n  This section applies to a participating telecommunications provider that is a terminating telecommunications provider.\n  Subject to subsection 16(10) and subsection (7), the provider must not terminate a sender identification message unless the message is received from a participating telecommunications provider.\n  Before terminating the message, the provider must confirm, by checking the register data, that the sender identification included in the message is registered in the Register.\n  Subject to subsection (6), if the sender identification included in the message is not registered in the Register, the provider must disrupt the message.\n  For the purposes of subsection (3), checking the register data means that the terminating telecommunications provider must have checked against the register data no more than 24 hours before terminating the sender identification message.\n  A provider is not required to disrupt the message under subsection (4) if the sender identification included in the message is “Unverified”.\n\n  Messages from an international telecommunications service provider\n\n  Despite subsection (2), if the message is received by the provider from an international telecommunications service provider – the provider is permitted to terminate the message if the provider has disrupted the message.","sortOrder":16},{"sectionNumber":"15","sectionType":"part","heading":"Requirement on telecommunication providers","content":"## 15 Requirement on telecommunication providers\n\n  A telecommunications provider that is not a participating telecommunications provider must not send, transit or terminate a sender identification message.\n  A telecommunications provider that is not a participating telecommunications provider must not misrepresent itself as a participating telecommunications provider (including as a certified telecommunications provider).","sortOrder":17},{"sectionNumber":"16","sectionType":"part","heading":"Requirements on originating telecommunications providers","content":"## 16 Requirements on originating telecommunications providers\n\n  This section applies to a participating telecommunications provider that is an originating telecommunications provider.\n\n  Requirements prior to sending sender identification messages\n\n  Before enabling a customer’s account to send a sender identification message on behalf of an entity, the provider must check if the sender identification included in the message is registered in the Register for that entity.\n  If the sender identification included in the message is not registered in the Register for that entity – the provider must disrupt the message.\n\n  Note: If a provider has disrupted a sender identification message under subsection (3), the provider can send the message that has been disrupted.\n\n  If the sender identification included in the sender identification message is registered in the Register for the entity, the provider must confirm:\n\n  that it is authorised by the entity to send messages that include that sender identification; and\n  that the person who has requested the provider to enable the customer’s account to send a sender identification message is authorised by the entity.\n\n  Note: Messages containing a sender identification can be sent by more than one participating telecommunications provider, if the other providers have been authorised by the entity.\n\n  The provider must not enable the customer’s account to send a sender identification message that includes the sender identification that is registered in the Register unless the provider has confirmed the matters mentioned in subsection (4).\n  If the provider receives notification from the ACMA that the provider is no longer authorised to send messages that include a sender identification for an entity, the provider must disable the customer account for the sender identification and cease sending any messages for that entity that include that sender identification immediately.\n\n  Note: The provider may receive notification from the ACMA if the entity has revoked the provider’s authorisation to send messages that include the sender identification or if the sender identification is no longer registered in the Register.\n\n  The provider must ensure that access to an account that has been enabled for an entity to send a sender identification message can only be accessed by authorised representatives of that entity.\n\n  Requirements relating to sending sender identification messages\n\n  Subject to subsection (9), the provider must not send a sender identification message to a telecommunications provider that is not a participating telecommunications provider.\n  A provider that receives a sender identification message from its EMSP partner or its international partner, as relevant, may send the message to a participating telecommunications provider that is:\n\n  a transiting telecommunications provider; or\n  a terminating telecommunications provider.\n\n  A provider that is also a terminating telecommunications provider, that receives a sender identification message from its EMSP partner or its international partner, as relevant, may terminate the message.","sortOrder":18},{"sectionNumber":"17","sectionType":"part","heading":"Requirements on transiting telecommunications providers","content":"## 17 Requirements on transiting telecommunications providers\n\n  This section applies to a participating telecommunications provider that is a transiting telecommunications provider.\n  Subject to subsections (3) and (4), the provider must not transit a sender identification message unless:\n\n  the telecommunications provider sending the message; and\n  the telecommunications provider to which the provider transits the message\n\n  are participating telecommunications providers.\n\n  Subsection (2) does not apply where a sender identification message is sent to a mobile number that is connected with a carriage service that is an international mobile roaming service.\n\n  Note: For example, subsection (3) will apply where an individual, with a mobile number that was issued in Australia, is using an international mobile roaming service. The transiting provider in this scenario will be the Australian mobile network operator of the network that the international roaming customer’s service is connected to when in Australia.\n  Messages from an international telecommunications service provider\n\n  Despite subsection (2), if a sender identification message is received by the provider from an international telecommunications service provider – the provider is permitted to transit the message if the provider has disrupted the message.","sortOrder":19},{"sectionNumber":"18","sectionType":"part","heading":"Requirements on terminating telecommunications providers","content":"## 18 Requirements on terminating telecommunications providers\n\n  This section applies to a participating telecommunications provider that is a terminating telecommunications provider.\n  Subject to subsection 16(10) and subsection (7), the provider must not terminate a sender identification message unless the message is received from a participating telecommunications provider.\n  Before terminating the message, the provider must confirm, by checking the register data, that the sender identification included in the message is registered in the Register.\n  Subject to subsection (6), if the sender identification included in the message is not registered in the Register, the provider must disrupt the message.\n  For the purposes of subsection (3), checking the register data means that the terminating telecommunications provider must have checked against the register data no more than 24 hours before terminating the sender identification message.\n  A provider is not required to disrupt the message under subsection (4) if the sender identification included in the message is “Unverified”.\n\n  Messages from an international telecommunications service provider\n\n  Despite subsection (2), if the message is received by the provider from an international telecommunications service provider – the provider is permitted to terminate the message if the provider has disrupted the message.","sortOrder":20},{"sectionNumber":"Part 4","sectionType":"part","heading":"Requirements relating to policies and procedures","content":"# Part 4—Requirements relating to policies and procedures\n\n## 19 Providers must implement policies and procedures\n\n  A participating telecommunications provider must implement policies and procedures to achieve compliance with this industry standard.\n\n## 20 Providers must implement complaint handling policies and procedures\n\n  A participating telecommunications provider must implement policies and procedures to deal with, record and resolve complaints from entities relating to the provider’s compliance with this industry standard.\n  Note: For example, the types of complaints might include a complaint by an entity that a sender identification has not been registered in the Register as it requested or a complaint by an entity that a participating telecommunications provider did not provide information about registration of a sender identification as required by section 9.","sortOrder":21},{"sectionNumber":"19","sectionType":"part","heading":"Providers must implement policies and procedures","content":"## 19 Providers must implement policies and procedures\n\n  A participating telecommunications provider must implement policies and procedures to achieve compliance with this industry standard.","sortOrder":22},{"sectionNumber":"20","sectionType":"part","heading":"Providers must implement complaint handling policies and procedures","content":"## 20 Providers must implement complaint handling policies and procedures\n\n  A participating telecommunications provider must implement policies and procedures to deal with, record and resolve complaints from entities relating to the provider’s compliance with this industry standard.\n  Note: For example, the types of complaints might include a complaint by an entity that a sender identification has not been registered in the Register as it requested or a complaint by an entity that a participating telecommunications provider did not provide information about registration of a sender identification as required by section 9.","sortOrder":23},{"sectionNumber":"Part 5","sectionType":"part","heading":"Reporting requirements","content":"# Part 5—Reporting requirements\n\n## 21 Traceback reporting\n\n  Where a participating telecommunications provider becomes aware that a sender identification message is a scam message:\n\n    if the provider is the originating telecommunications provider of the scam message – it must report to the ACMA in accordance with subsection (3); or\n    if the provider is not the originating telecommunications provider of the scam message – it must:\n\n    notify the telecommunications provider which sent the provider the scam message, that it is a part of the chain through which a scam message has been sent; and\n    report to the ACMA in accordance with subsection (3).\n\n  Where a participating telecommunications provider is notified by another participating telecommunications provider that it is part of the chain through which a scam message has been sent:\n\n    if the provider is the originating telecommunications provider of the scam message – it must report to the ACMA in accordance with subsection (3); or\n    if the provider is not the originating telecommunications provider of the scam message – it must comply with the obligation in paragraph (1)(b).\n\n  A report to the ACMA which is required under this section:\n\n1.  must be in writing; and\n2.  must contain the following information:\n\n    the sender identification for the scam message; and\n    the total number of recipients to whom the scam message was sent; and\n    information about the content of the scam message; and\n    if the provider preparing the report (the provider) is the originating telecommunications provider of the scam message:\n\n        that the provider is the originating telecommunications provider of the scam message; and\n        the identity of the entity which registered the sender identification, or on whose behalf the sender identification was registered, as relevant; or\n    if the provider is not the originating telecommunications provider of the scam message:\n\n(A) the identity of the telecommunications provider who sent the provider the scam message; and\n\n(B) if relevant, the identity of the international partner or EMSP partner on whose behalf the message was sent; and\n\n1.  must be given to the ACMA as soon as practicable and in any event no later than 2 business days from the date on which the provider became aware of the scam message.\n\n## 22 Quarterly reporting\n\n  Within 20 business days after the end of each quarter, a participating telecommunications provider referred to in an item of column 1 of the following table must:\n\n  prepare a written report for the relevant quarter containing the information mentioned in column 2 of the item; and\n  give the report to the ACMA.\n\n```html\n<table cellspacing=\"0\" cellpadding=\"0\" style=\"margin-bottom:0pt; border-collapse:collapse\"><tbody><tr><td colspan=\"3\" style=\"width:383.25pt; border-top:2.25pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\">Information to be reported</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\">Item</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\">Column 1</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:16.15pt; text-indent:0pt\"><span style=\"font-weight:bold\">Column 2</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:2.25pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\"></span></p></td><td style=\"width:173.5pt; border-top:2.25pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\">Participating telecommunications provider who must provide information</span></p></td><td style=\"width:163.25pt; border-top:2.25pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:16.15pt; text-indent:0pt\"><span style=\"font-weight:bold\">Information</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:2.25pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>1</span></p></td><td style=\"width:173.5pt; border-top:2.25pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Originating telecommunications providers</span></p><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Transiting telecommunications providers</span></p><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Terminating telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:2.25pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:16.15pt; text-indent:0pt\"><span>The number and type of complaints the telecommunications provider has received from other telecommunications providers, entities and message recipients relating to the Register.</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>2</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Originating telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><ol class=\"awlist95\" style=\"margin:0pt; padding-left:0pt\"><li class=\"subsection\" style=\"margin-left:36pt; text-indent:-18pt\"><span style=\"width:5.79pt; font:7pt 'Times New Roman'; display:inline-block\"></span><span>The total number of sender identification messages sent by the originating telecommunications provider which included sender identifications registered in the Register.</span></li><li class=\"subsection\" style=\"margin-left:36pt; text-indent:-18pt\"><span style=\"width:5.17pt; font:7pt 'Times New Roman'; display:inline-block\"></span><span>The total number of sender identification messages which included sender identifications that were not registered in the Register and were disrupted by the originating telecommunications provider.</span></li></ol></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>3</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Transiting telecommunications providers</span></p><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Terminating telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:16.15pt; text-indent:0pt\"><span>The identity of any telecommunications providers that are not participating telecommunications providers that have attempted to send sender identification messages.</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>4</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Terminating telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><ol class=\"awlist96\" style=\"margin:0pt; padding-left:0pt\"><li class=\"subsection\" style=\"margin-left:36pt; text-indent:-18pt\"><span style=\"width:5.79pt; font:7pt 'Times New Roman'; display:inline-block\"></span><span>The number of sender identification messages received from participating telecommunications providers.</span></li><li class=\"subsection\" style=\"margin-left:36pt; text-indent:-18pt\"><span style=\"width:5.17pt; font:7pt 'Times New Roman'; display:inline-block\"></span><span>The number of sender identification messages which included sender identifications that were not registered in the Register and were disrupted by the terminating telecommunications provider.</span></li></ol></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>5</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Transiting telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:8.95pt; text-indent:0pt\"><span>The number of sender identification messages sent by international telecommunications service providers that were disrupted by the transiting telecommunications provider.</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>6</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Certified telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:8.95pt; text-indent:0pt\"><span>The number of requests received from a non-ABN entity (directly to the certified telecommunications provider or via an international partner or EMSP partner for the provider) to make an application for registration of a sender identification in the Register on behalf of the entity under subsection 12(1) but the application was not made because the provider was unable to confirm or establish one or more of the matters in subsection 12(4).</span></p></td></tr></tbody></table>\n```","sortOrder":24},{"sectionNumber":"21","sectionType":"part","heading":"Traceback reporting","content":"## 21 Traceback reporting\n\n  Where a participating telecommunications provider becomes aware that a sender identification message is a scam message:\n\n    if the provider is the originating telecommunications provider of the scam message – it must report to the ACMA in accordance with subsection (3); or\n    if the provider is not the originating telecommunications provider of the scam message – it must:\n\n    notify the telecommunications provider which sent the provider the scam message, that it is a part of the chain through which a scam message has been sent; and\n    report to the ACMA in accordance with subsection (3).\n\n  Where a participating telecommunications provider is notified by another participating telecommunications provider that it is part of the chain through which a scam message has been sent:\n\n    if the provider is the originating telecommunications provider of the scam message – it must report to the ACMA in accordance with subsection (3); or\n    if the provider is not the originating telecommunications provider of the scam message – it must comply with the obligation in paragraph (1)(b).\n\n  A report to the ACMA which is required under this section:\n\n1.  must be in writing; and\n2.  must contain the following information:\n\n    the sender identification for the scam message; and\n    the total number of recipients to whom the scam message was sent; and\n    information about the content of the scam message; and\n    if the provider preparing the report (the provider) is the originating telecommunications provider of the scam message:\n\n        that the provider is the originating telecommunications provider of the scam message; and\n        the identity of the entity which registered the sender identification, or on whose behalf the sender identification was registered, as relevant; or\n    if the provider is not the originating telecommunications provider of the scam message:\n\n(A) the identity of the telecommunications provider who sent the provider the scam message; and\n\n(B) if relevant, the identity of the international partner or EMSP partner on whose behalf the message was sent; and\n\n1.  must be given to the ACMA as soon as practicable and in any event no later than 2 business days from the date on which the provider became aware of the scam message.","sortOrder":25},{"sectionNumber":"22","sectionType":"part","heading":"Quarterly reporting","content":"## 22 Quarterly reporting\n\n  Within 20 business days after the end of each quarter, a participating telecommunications provider referred to in an item of column 1 of the following table must:\n\n  prepare a written report for the relevant quarter containing the information mentioned in column 2 of the item; and\n  give the report to the ACMA.\n\n```html\n<table cellspacing=\"0\" cellpadding=\"0\" style=\"margin-bottom:0pt; border-collapse:collapse\"><tbody><tr><td colspan=\"3\" style=\"width:383.25pt; border-top:2.25pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\">Information to be reported</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\">Item</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\">Column 1</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:16.15pt; text-indent:0pt\"><span style=\"font-weight:bold\">Column 2</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:2.25pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\"></span></p></td><td style=\"width:173.5pt; border-top:2.25pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span style=\"font-weight:bold\">Participating telecommunications provider who must provide information</span></p></td><td style=\"width:163.25pt; border-top:2.25pt solid #000000; border-bottom:2.25pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:16.15pt; text-indent:0pt\"><span style=\"font-weight:bold\">Information</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:2.25pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>1</span></p></td><td style=\"width:173.5pt; border-top:2.25pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Originating telecommunications providers</span></p><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Transiting telecommunications providers</span></p><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Terminating telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:2.25pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:16.15pt; text-indent:0pt\"><span>The number and type of complaints the telecommunications provider has received from other telecommunications providers, entities and message recipients relating to the Register.</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>2</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Originating telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><ol class=\"awlist95\" style=\"margin:0pt; padding-left:0pt\"><li class=\"subsection\" style=\"margin-left:36pt; text-indent:-18pt\"><span style=\"width:5.79pt; font:7pt 'Times New Roman'; display:inline-block\"></span><span>The total number of sender identification messages sent by the originating telecommunications provider which included sender identifications registered in the Register.</span></li><li class=\"subsection\" style=\"margin-left:36pt; text-indent:-18pt\"><span style=\"width:5.17pt; font:7pt 'Times New Roman'; display:inline-block\"></span><span>The total number of sender identification messages which included sender identifications that were not registered in the Register and were disrupted by the originating telecommunications provider.</span></li></ol></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>3</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Transiting telecommunications providers</span></p><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Terminating telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:16.15pt; text-indent:0pt\"><span>The identity of any telecommunications providers that are not participating telecommunications providers that have attempted to send sender identification messages.</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>4</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Terminating telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><ol class=\"awlist96\" style=\"margin:0pt; padding-left:0pt\"><li class=\"subsection\" style=\"margin-left:36pt; text-indent:-18pt\"><span style=\"width:5.79pt; font:7pt 'Times New Roman'; display:inline-block\"></span><span>The number of sender identification messages received from participating telecommunications providers.</span></li><li class=\"subsection\" style=\"margin-left:36pt; text-indent:-18pt\"><span style=\"width:5.17pt; font:7pt 'Times New Roman'; display:inline-block\"></span><span>The number of sender identification messages which included sender identifications that were not registered in the Register and were disrupted by the terminating telecommunications provider.</span></li></ol></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>5</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Transiting telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:8.95pt; text-indent:0pt\"><span>The number of sender identification messages sent by international telecommunications service providers that were disrupted by the transiting telecommunications provider.</span></p></td></tr><tr><td style=\"width:24.9pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>6</span></p></td><td style=\"width:173.5pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:0pt; text-indent:0pt\"><span>Certified telecommunications providers</span></p></td><td style=\"width:163.25pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"subsection\" style=\"margin-left:8.95pt; text-indent:0pt\"><span>The number of requests received from a non-ABN entity (directly to the certified telecommunications provider or via an international partner or EMSP partner for the provider) to make an application for registration of a sender identification in the Register on behalf of the entity under subsection 12(1) but the application was not made because the provider was unable to confirm or establish one or more of the matters in subsection 12(4).</span></p></td></tr></tbody></table>\n```","sortOrder":26},{"sectionNumber":"Part 6","sectionType":"part","heading":"System security, record keeping and privacy","content":"# Part 6—System security, record keeping and privacy\n\n## 23 Requirement to keep records\n\n  A telecommunications provider must keep records to demonstrate its compliance with this industry standard.\n  Where a telecommunications provider keeps records under subsection (1) it must take all reasonable steps in the circumstances:\n\n> Note: to protect any such record from misuse, interference and loss and from unauthorised access, modification or disclosure; and\n\n> Note: to ensure that any such record is destroyed or otherwise disposed of in a secure manner where the record is no longer required to be retained under this industry standard or any other applicable law.\n\n## 24 Record retention\n\n> Note: A telecommunications provider must:\n\n> Note: retain any record required to be kept under subsection 23(1) for 2 years from the date of creating the record; and\n\n> Note: make any such record available to the ACMA within 5 business days after receiving a written request from the ACMA.\n\n## 25 System security\n\n    A participating telecommunications provider must take all reasonable steps to ensure that its information technology systems and processes relating to the sending of sender identification messages and its interactions with the Register are secure.\n    Where a participating telecommunications provider becomes aware of a breach or suspected breach of the security of any of its information technology systems or processes referred to in subsection (1), it must notify the ACMA, as soon as practicable, of what has occurred and what steps have been taken to rectify the matter.\n\n## 26 Privacy\n\n> Note: Where a participating telecommunications provider is not subject to the requirements of the Privacy Act 1988, it must ensure that personal information it collects for a particular purpose in connection with this industry standard:\n\n  is not used or disclosed for some other purpose except:\n\n  as required to manage a complaint made by the person to whom the information relates; or\n  with the express consent of the person to whom the information relates; or\n  where the use or disclosure is required or authorised by or under an Australian law or a court or tribunal order; and\n\n  is destroyed or otherwise disposed of in a secure manner where it is no longer required to be retained under this industry standard or any other applicable law.\n\n  Note: Where a provider is subject to the Privacy Act 1988, Australian Privacy Principle 6 in Schedule 1 to that Act will apply to the use or disclosure of personal information it collects in connection with this industry standard.","sortOrder":27},{"sectionNumber":"23","sectionType":"part","heading":"Requirement to keep records","content":"## 23 Requirement to keep records\n\n  A telecommunications provider must keep records to demonstrate its compliance with this industry standard.\n  Where a telecommunications provider keeps records under subsection (1) it must take all reasonable steps in the circumstances:\n\n> Note: to protect any such record from misuse, interference and loss and from unauthorised access, modification or disclosure; and\n\n> Note: to ensure that any such record is destroyed or otherwise disposed of in a secure manner where the record is no longer required to be retained under this industry standard or any other applicable law.","sortOrder":28},{"sectionNumber":"24","sectionType":"part","heading":"Record retention","content":"## 24 Record retention\n\n> Note: A telecommunications provider must:\n\n> Note: retain any record required to be kept under subsection 23(1) for 2 years from the date of creating the record; and\n\n> Note: make any such record available to the ACMA within 5 business days after receiving a written request from the ACMA.","sortOrder":29},{"sectionNumber":"25","sectionType":"part","heading":"System security","content":"## 25 System security\n\n    A participating telecommunications provider must take all reasonable steps to ensure that its information technology systems and processes relating to the sending of sender identification messages and its interactions with the Register are secure.\n    Where a participating telecommunications provider becomes aware of a breach or suspected breach of the security of any of its information technology systems or processes referred to in subsection (1), it must notify the ACMA, as soon as practicable, of what has occurred and what steps have been taken to rectify the matter.","sortOrder":30},{"sectionNumber":"26","sectionType":"part","heading":"Privacy","content":"## 26 Privacy\n\n> Note: Where a participating telecommunications provider is not subject to the requirements of the Privacy Act 1988, it must ensure that personal information it collects for a particular purpose in connection with this industry standard:\n\n  is not used or disclosed for some other purpose except:\n\n  as required to manage a complaint made by the person to whom the information relates; or\n  with the express consent of the person to whom the information relates; or\n  where the use or disclosure is required or authorised by or under an Australian law or a court or tribunal order; and\n\n  is destroyed or otherwise disposed of in a secure manner where it is no longer required to be retained under this industry standard or any other applicable law.\n\n  Note: Where a provider is subject to the Privacy Act 1988, Australian Privacy Principle 6 in Schedule 1 to that Act will apply to the use or disclosure of personal information it collects in connection with this industry standard.","sortOrder":31},{"sectionNumber":"Part 7","sectionType":"part","heading":"Notification to message recipients","content":"# Part 7 – Notification to message recipients\n\n## 27 Requirements on carriage service providers\n\n  This section applies to a carriage service provider that supplies a public mobile telecommunications service.\n\n  Regular notifications\n\n    For each public mobile telecommunication services supplied by a provider under a contract, the provider must provide information about how the following will be dealt with under this industry standard:\n\n  a sender identification message that includes a sender identification registered in the Register; and\n  a sender identification message that includes a sender identification that is not registered in the Register,\n\n    to either:\n\n  the end-user of the service; or\n  the account holder for the service.\n\n    For subsection (2), the information must be:\n\n    published on the provider’s website from 30 November 2025; and\n    provided to the end-user or the account holder, as relevant, by SMS, via a mobile application or by email or any other direct communication with the end-user or account holder:\n\n    upon entering into or renewing a contract with the account holder; and\n    at least once every quarter, starting from the quarter commencing 1 October 2026.\n\n  One-off notifications around 1 July 2026\n\n    For each public mobile telecommunication services supplied by a provider under a contract, the provider must provide the following information:\n\n    how the following will be dealt with under this industry standard:\n\n    a sender identification message that includes a sender identification registered in the Register; and\n    a sender identification message that includes a sender identification not registered in the Register; and\n\n    that the Register will commence on 1 July 2026,\n\nto either:\n\n    the end-user of the service; or\n    the account holder for the service.\n\n    For subsection (4), the information must be provided to the end-user or account holder, as relevant, by SMS, via a mobile application or by email or any other direct communication with the end-user or account holder:\n\n    between 18-20 June 2026; and\n    between 28-30 June 2026; and\n    between 8-10 July 2026.","sortOrder":32},{"sectionNumber":"27","sectionType":"part","heading":"Requirements on carriage service providers","content":"## 27 Requirements on carriage service providers\n\n  This section applies to a carriage service provider that supplies a public mobile telecommunications service.\n\n  Regular notifications\n\n    For each public mobile telecommunication services supplied by a provider under a contract, the provider must provide information about how the following will be dealt with under this industry standard:\n\n  a sender identification message that includes a sender identification registered in the Register; and\n  a sender identification message that includes a sender identification that is not registered in the Register,\n\n    to either:\n\n  the end-user of the service; or\n  the account holder for the service.\n\n    For subsection (2), the information must be:\n\n    published on the provider’s website from 30 November 2025; and\n    provided to the end-user or the account holder, as relevant, by SMS, via a mobile application or by email or any other direct communication with the end-user or account holder:\n\n    upon entering into or renewing a contract with the account holder; and\n    at least once every quarter, starting from the quarter commencing 1 October 2026.\n\n  One-off notifications around 1 July 2026\n\n    For each public mobile telecommunication services supplied by a provider under a contract, the provider must provide the following information:\n\n    how the following will be dealt with under this industry standard:\n\n    a sender identification message that includes a sender identification registered in the Register; and\n    a sender identification message that includes a sender identification not registered in the Register; and\n\n    that the Register will commence on 1 July 2026,\n\nto either:\n\n    the end-user of the service; or\n    the account holder for the service.\n\n    For subsection (4), the information must be provided to the end-user or account holder, as relevant, by SMS, via a mobile application or by email or any other direct communication with the end-user or account holder:\n\n    between 18-20 June 2026; and\n    between 28-30 June 2026; and\n    between 8-10 July 2026.","sortOrder":33},{"sectionNumber":"Schedule 1","sectionType":"part","heading":"Information to be provided to customers","content":"# Schedule 1 – Information to be provided to customers\n\n(Paragraph 9(1)(a), paragraph 9(2)(d), paragraph 9(3)(c), and section 10)\n\n  The following information must be provided to customers by a participating telecommunications provider that is an originating telecommunications provider under paragraphs 9(1)(a), 9(2)(d) and 9(3)(c) and by an originating telecommunications provider under section 10:\n\n  Part 24B of the Act provides for the establishment of the SMS Sender ID Register (the Register);\n  From 1 July 2026, if a sender identification message is sent which includes a sender identification that is not registered in the Register, the sender identification message will be labelled as ‘Unverified’;\n  If an entity wishes to send sender identification messages, it must register its sender identification in the Register and ensure that it uses one or more participating telecommunications providers to send the sender identification messages;\n  The following types of entities can be approved to make applications to register sender identifications in the Register:\n\n    an individual;\n    a body corporate;\n    a corporation sole;\n    a body politic;\n    a government entity (within the meaning of the A New Tax System (Australian Business Number) Act 1999);\n    a partnership;\n    any other unincorporated association or body of persons;\n    a trust;\n    a superannuation fund (within the meaning of the Superannuation Industry (Supervision) Act 1993);\n  For an entity to be able to have its sender identification registered in the Register, the entity must demonstrate that it has a valid use case for the sender identification;\n  An entity can make an application to register its sender identification in the Register through a participating telecommunications provider that is an originating telecommunications provider. A list of all participating telecommunications providers that are originating telecommunications providers will be made available on the ACMA’s website;\n\n  Entities with an ABN\n\n  An entity with an ABN can make an application to register its sender identification through any participating telecommunications provider that is an originating telecommunications provider, or a partner of a participating telecommunications provider. In order to obtain approval to make such an application:\n\n    the person making the request for the entity must be listed as an authorised contact for the entity on the Australian Business Register, or be otherwise authorised by that entity; and\n    the person making the request must pass an identification check; and\n    the person making the request must agree to the Register’s terms of use;\n\n  Note: These requirements will be included in a determination made under section 484L of the Act.\n\n  Once the provider has made the application for registration of the sender identification on behalf of an entity, the person making the request for the entity will receive instructions from the ACMA about how to access the Register;\n  Once the entity is approved by the ACMA, the entity will be able to confirm the registration of the sender identification;\n\nNote: The requirements in paragraphs (h) and (i) will be included in a determination made under section 484L of the Act.\n\n  Any cost for registering a sender identification, including any ongoing annual charge;\n  Once the entity’s sender identification is registered, the entity can authorise other participating telecommunications providers to send messages using that sender identification;\n  An entity with an ABN can also register its sender identification through an originating telecommunications provider that is a certified telecommunications provider;\n\n  Entities without an ABN\n\n  An entity without an ABN can only make an application to register its sender identification through an originating telecommunications provider that is a certified telecommunications provider or a partner of a certified telecommunications provider. That provider or partner will conduct similar checks to those outlined in paragraph (g);\n  An entity without an ABN that makes an application to register its sender identification through a provider or partner of the kind referred to in paragraph (m) will not be able to gain access to the Register.","sortOrder":34}],"analysis":{"flash_summary":{"complexity_score":8,"scope_assessment":{"changed":false,"description":"This industry standard implements and operationalises the SMS Sender ID Register established under the Telecommunications Act and the associated Direction (see s3, s4, Schedule 1). It sets detailed procedures and obligations for verifying and registering sender identifications, for provider approvals and for operational handling of unregistered sender IDs. The measures are consistent with that stated purpose (give effect to the objectives in the Direction) rather than expanding the scheme beyond the Register’s core intent. The instrument does, however, add significant operational detail (verification pathways, certified provider gatekeeping for non‑ABN entities, reporting and notification regimes) that concretely defines how the Register will operate in practice; that is an implementation elaboration rather than a material scope expansion."},"complexity_factors":["Extensive interpretation/definitions section (section 5) with many defined terms and cross‑references (ABN entity, certified telecommunications provider, EMSP partner, international partner, sender identification match, valid use case, etc.)","Multiple actor categories and roles (originating, transiting, terminating, participating, certified, EMSP partner, international partner) with different obligations (Parts 2–3 and s15–18)","Differentiated procedures and proof standards for ABN entities vs non‑ABN entities (sections 11–12) including different evidence sources (Australian registers v overseas registers)","Numerous cross‑references to the Telecommunications Act (sections 484F, 484G, 484L, Part 24B) and to other statutes (Identity Verification Services Act, ABN Act, Trade Marks Act), adding legal layering (see s3, s5, notes)","Staged commencement dates for different parts (three separate commencement dates with transitional obligations) increasing implementation complexity (Commencement table)","Conditional exceptions (government agencies; emergency/public health/security usages) that require evidentiary assessments (s11(6), s12(6))","Detailed reporting obligations with both urgent (2 business days) and periodic (quarterly) reports containing many specific data points (s21–22 and table in s22)","Operational timing constraints (e.g. terminating provider must check register data no more than 24 hours before termination — s18(5)) and retention/production timelines (2 year retention; 5 business day production — s24)","Security, privacy and record‑keeping obligations layered on top of operational checks (s23–26) and complaint handling requirements (s19–20)","Multiple notification schedules for consumers and account holders (regular quarterly notices plus several specific pre/post commencement notices — s9, s10, s27)","Repetition and duplicated text in the instrument as presented (repeated sections) which complicates authoritative reading and may create ambiguity"],"plain_english_summary":"**What this instrument does (mechanics)\n\n- Establishes operational rules for the SMS Sender ID Register (the Register). It sets who must register sender identifications (the names or labels shown on SMS/MMS), how telecommunications providers must check and handle those sender IDs, and reporting, record-keeping, security and notification requirements. (See: sections 4, 5, 7–14, 15–18, 21–27, Schedule 1.)\n\n- Only providers approved by the Australian Communications and Media Authority (ACMA) as \"participating telecommunications providers\" may send, transit or terminate messages with sender identifications (s7; s15). Providers must apply to ACMA for approvals under the Telecommunications Act (s7, s8). A further approval category, \"certified telecommunications provider\", is required to register sender IDs on behalf of entities without an Australian Business Number (ABN) (s8; s12).\n\n- Entities that wish to use a sender identification must have that sender ID registered in the Register (Schedule 1). Where a sender ID is not registered, providers must over‑stamp or label messages as “Unverified” (Schedule 1; s16(3); s18(4)). Originating, transiting and terminating providers must check the Register and disrupt (i.e. over‑stamp) unregistered sender IDs in many circumstances (s16–18).\n\n- Processes differ for ABN entities and non‑ABN entities. For ABN entities, providers must verify a valid use case by checking Australian registers (Australian Business Register, Business Names Register, Trade Marks Register or whois for registered domains) before applying to register a sender ID on the entity’s behalf (s11). For non‑ABN entities, a certified provider must perform identity checks, show the entity is officially recognised in its home country and confirm a valid use case using official overseas registers (s12).\n\n- International providers and electronic messaging service providers (EMSP partners) may participate through local partners; the local provider must have contractual arrangements requiring the overseas partner to perform identity and use‑case confirmations (s13).\n\n- Providers must give customers specified information about the Register (Schedule 1) and publish that information online (s9, s10). Carriage service providers must notify mobile end‑users/account holders about how registered and unregistered sender IDs will be handled and must issue specific notices around the Register commencement (s27).\n\n- Reporting and record‑keeping: providers must report scams (traceback reporting) to ACMA within 2 business days and provide quarterly operational statistics to ACMA (s21–22). Providers must retain compliance records for 2 years and make them available to ACMA on request (s23–24).\n\n- Security and privacy: providers must take reasonable steps to secure systems that interact with the Register and notify ACMA of security breaches (s25). Personal information collected under this standard must be used only for the specified purposes and handled consistently with the Privacy Act or the privacy rules set out in this standard (s26).\n\n\nWho this affects and how (actors and behaviour changes)\n\n- Entities that send SMS/MMS using a sender identification: must register that sender identification (Schedule 1). ABN entities face an Australian verification route (s11); non‑ABN entities must use a certified provider and meet identity and foreign‑registry checks (s12).\n\n- Participating telecommunications providers (originating, transiting, terminating): must obtain ACMA approval (s7), implement operational checks against the Register before enabling and sending sender ID messages (s16–18), disrupt unregistered messages (label as \"Unverified\") (s16(3); s18(4); Schedule 1), keep records and meet reporting obligations (s21–24), implement complaints handling and policies (s19–20) and meet IT security and privacy requirements (s25–26).\n\n- Certified providers: bear additional responsibilities to accept and verify non‑ABN entity applications and to keep contact details for those entities up to date (s8; s12).\n\n- International messaging partners and overseas providers: must work through local certified or participating providers; local partners must have contractual obligations to perform specified checks (s13).\n\n- Carriage service providers who supply public mobile services: must notify end‑users/account holders about how registered and unregistered sender IDs will be handled, and provide timed notices around commencement (s27).\n\n\nWhy it matters (claimed purpose and operational consequences)\n\n- The instrument operationalises the Register and creates a verification and provider‑accountability framework intended to reduce SMS/MMS spoofing and scam messages by tying sender identifications to verified entities (see s4; Schedule 1). It does so by:\n  - restricting who may send/relay/terminate sender ID messages (s15–18);\n  - requiring identity and ownership/use‑case checks before registering a sender ID (s11–13); and\n  - requiring providers to label or disrupt unregistered sender IDs as \"Unverified\" (s16(3); s18(4); Schedule 1).\n\n\nCosts, incentives, trade‑offs and implementation details to note\n\n- Compliance and operational costs fall mainly on participating telecommunications providers (approval process, IT checks, system security, record retention, reporting, customer communications) (s7; s19–26; s21–22). Certified providers incur extra costs to onboard and verify non‑ABN entities (s8; s12).\n\n- Entities (especially non‑ABN or small overseas senders) face additional friction and potential cost to get a sender ID registered because they must use a certified provider and undergo stronger identity and foreign‑registry checks (s12; s13). ABN entities have a clearer, lower‑friction route using Australian registers (s11).\n\n- There is a concentration risk: certified providers (who can register non‑ABN entities) and those participating providers who win ACMA approvals may capture more business from overseas or small senders. The standard establishes a gatekeeper role for certified providers (s8; s12), which can create concentrated benefits for those providers.\n\n- Effects on competition and market entry: the requirement that only participating providers may carry sender ID messages (s15) and the verification steps before enabling sending (s16) raise the compliance bar for smaller or overseas messaging providers. That may reduce the number of suppliers able to provide sender‑ID SMS, or incentivise businesses to switch to other channels (e.g. OTT messaging, email) where registration is not required.\n\n- Risk of false positives and service disruption: operational checks and mandatory disruption of unregistered sender IDs (s16–18) could cause legitimate messages to be labeled \"Unverified\" or blocked if register checks fail or authorisations are not tracked properly. Terminating providers check register data within 24 hours before termination (s18(5)), which creates a tight operational window and an implementation risk for providers with legacy systems.\n\n- Administrative discretion and centralisation: many actions require ACMA approvals, determinations or notifications (approval to be a participating or certified provider, ACMA registration decisions, and ACMA notifications that a provider is no longer authorised) (s7–8; s11–13; s16(8)). That centralises key decision points with the regulator.\n\n- Privacy and data handling: providers must maintain records and handle personal information for identification and audit purposes; smaller providers not covered by the Privacy Act must still follow the instrument’s privacy limits (s23–26). Record retention (2 years) and 5‑business‑day production on ACMA request are specific operational obligations (s24).\n\n- Reporting and compliance monitoring: the instrument mandates quick scam traceback reporting (as soon as practicable, no later than 2 business days) and detailed quarterly reports (s21–22). That generates ongoing compliance and monitoring costs and provides ACMA with operational data to enforce the scheme.\n\n\nNet operational picture (who pays, who decides, what changes)\n\n- Who pays: participating and certified providers bear most direct costs (IT, identity checks, security, records, reporting); entities (especially non‑ABN) may face higher onboarding costs or fees charged by certified providers; carriage service providers must also implement customer notifications.\n\n- Who decides: ACMA decides approvals, registration outcomes and can notify providers about authorisations and removal of registrations (s7; s11–13; s16(8)). Participating providers implement verification and disruption rules.\n\n- Behavioural change: providers will add pre‑send register checks, disrupt/label unregistered messages, and deny sending until registration and authorisation are confirmed; some senders (particularly overseas/non‑ABN) will need certified provider intermediaries; some traffic may divert to other channels if registering sender IDs is infeasible or costly.\n\n\nReferences to key sections (examples)\n\n- Applicability and purpose: s4; Schedule 1.\n- Provider approvals and certified providers: s7–8; s11–13.\n- Sending/transiting/terminating rules and \"Unverified\" labelling: s15–18; Schedule 1.\n- Customer information and notifications: s9–10; s27; Schedule 1.\n- Reporting and traceback: s21–22.\n- Records, retention, security and privacy: s23–26.\n\nThis summary describes the instrument’s structure and practical implications. It attributes the instrument’s stated objective (to give effect to the Register and reduce spoofing/scams) to the text (s4; Schedule 1) and then identifies the principal operational trade‑offs: compliance costs concentrated on providers, higher friction for non‑ABN/overseas senders, centralised ACMA approvals, and operational risks around over‑stamping or disruption of legitimate traffic (see the cited sections)."},"kimi_summary":{"_metrics":{"provider":"moonshot","completionTokens":2487},"content_quality":"ok","complexity_score":8,"scope_assessment":{"changed":false,"description":"This instrument establishes the original scope of the SMS Sender ID Register regime as directed by the Telecommunications (SMS Sender ID Register Industry Standard) Direction 2025. It covers registration, verification, message handling restrictions, scam reporting, consumer notification, and data retention—which appears consistent with establishing a comprehensive sender verification system rather than representing scope creep beyond the original intent."},"complexity_factors":["Over 40 defined terms including distinct categories for 'originating', 'transiting', 'terminating', and 'certified' telecommunications providers","Bifurcated compliance regime with different verification pathways for ABN entities (Australian businesses) versus non-ABN entities (international/foreign organisations)","Three-stage staggered commencement (15 October 2025, 30 November 2025, and 1 July 2026) creating different obligation start dates","Complex verification requirements requiring cross-checking against multiple external registers (Business Names Register, Australian Business Register, Trade Marks Register, WHOIS database)","Nested conditional logic and exceptions, including specific carve-outs for government agencies dealing with emergencies or public safety","Multi-layered relationship management requirements for 'entity associates', 'international partners', and 'EMSP partners' with distinct contractual and notification obligations","Extensive cross-referencing to primary legislation (Telecommunications Act 1997) and other statutes (Privacy Act 1988, Corporations Act 2001, Identity Verification Services Act 2023)","Detailed reporting tables requiring specific data collection on complaints, message volumes, disruption counts, and scam traceback information"],"plain_english_summary":"**What this does:**\n\nThis law creates a national **SMS Sender ID Register**—a verified database of the names that appear when businesses and organisations send you text messages (like when your bank texts you and it shows up as \"MyBank\" instead of a phone number). The goal is to make it harder for scammers to impersonate legitimate organisations.\n\n**Who it affects:**\n\n*   **Telecommunications providers** (telcos, messaging services): Must register as \"participating providers\" to send, carry, or deliver SMS messages with sender IDs. They face strict rules about checking registrations and must \"disrupt\" (replace with \"Unverified\") any message using an unregistered sender ID.\n*   **Businesses and organisations** (called \"entities\"): Any business, government agency, or other organisation that wants to send SMS with a custom sender name (like \"Telservice\" or \"ATO\") must register that name in the Register and prove they own it or have a right to use it.\n*   **Consumers**: Will see \"Unverified\" labels on text messages from unregistered sender IDs, helping them spot potential scams.\n\n**How it works:**\n\n*   **For Australian businesses (ABN entities):** Must prove their sender ID matches their registered business name, company name, trademark, or domain name. They can register through any participating provider.\n*   **For international/foreign entities (non-ABN entities):** Must use a specially approved \"certified telecommunications provider\" and undergo additional identity verification checks using government-issued documents.\n*   **The process:** Before sending a message, providers must check if the sender ID is registered. If not, they must replace it with \"Unverified\" before delivering the message.\n*   **Scam reporting:** Providers must trace back and report scam messages to the ACMA (Australian Communications and Media Authority) within 2 business days.\n*   **Rollout:** The Register operates in phases—provider approvals start October 2025, customer notifications begin November 2025, and the full registration and verification system starts **1 July 2026**.\n\n**Why it matters:**\n\nThis creates a \"verified sender\" system for text messages, similar to blue checkmarks on social media. It helps prevent \"spoofing\" (where scammers fake sender names to trick you into thinking they are your bank or the government) by ensuring only legitimate entities can use specific sender IDs."},"flash_summary_failed":{"failed":true,"reason":"Unauthenticated. Configure AI_GATEWAY_API_KEY or use a provider module. Learn more: https://ai-sdk.dev/unauthenticated-ai-gateway","source":"analysis-cron"}},"importantCases":[],"_links":{"self":"/api/acts/telecommunications-sms-sender-id-register-industry-standard-2025","history":"/api/acts/telecommunications-sms-sender-id-register-industry-standard-2025/history","analysis":"/api/acts/telecommunications-sms-sender-id-register-industry-standard-2025/analysis","conflicts":"/api/acts/telecommunications-sms-sender-id-register-industry-standard-2025/conflicts","importantCases":"/api/acts/telecommunications-sms-sender-id-register-industry-standard-2025/important-cases","documents":"/api/acts/telecommunications-sms-sender-id-register-industry-standard-2025/documents"}}