TCP Code – update and next steps
ACMA Feedback on the 14th December ‘TCP Code Package’
In early February, the ACMA Chair and Agency Head wrote to CA to advise that the Authority was largely comfortable with CA continuing its Code development process provided it addresses ACMA feedback on a number of identified key issues. This includes ensuring that the Code mandates that "direct debits/auto-payments are not the only payment method offered, with at least one alternative being offered fee-free to all customers with similar flexibility".
The ACMA requested that industry provide reconsidered views on the issue of payment methods by 14 March, with drafting to address the remaining matters of concern by 3 May (subsequently extended to 20 May). The letter from the ACMA is available here.
Payment Methods
CA submitted a paper on the issue of payment methods on 14 March. ACMA’s response was provided on (and include links to the two docs where underlined) (paper: please link the document called TCP-Code-payments-causes-revised,-14-March-2024) (response: please link the pdf called Correspindence from the Chair ACMA to CEO CA 9 April 2024).
Next steps
The table below outlines the proposed key steps and associated timeframes for further code development. It was developed with input from key stakeholders, with further input sought through the Review Committee (RC).
Full details, including the rationale for the proposed approach, are included in the 28 February 2024 correspondence to the RC, available here.
In line with CA’s commitment to transparency and constructive engagement, it will continue to post regular updates on its website, and welcomes constructive stakeholder engagement at any time. (email: info@commsalliance.com.au)
Consultation key steps - TCP Code development 2024
| When | What | Note |
| Ongoing | CA to seek any required clarification on issues raised in feedback to date. | Likely a bi-lateral discussion or request to the individual stakeholder (not limited to RC members). This is in line with CA’s original commitment to thorough review and consultation processes. |
| Ongoing | Test ideas and concepts with relevant stakeholders as required. | |
| 14 March | Drafting on payments to be provided to the ACMA, cc’ing the RC. | Please find the TCP Code Payment Methods Revised Drafting that was provided to the ACMA here. ACMA provided feedback on the 11 May, which you can find here. |
| 20 May | A substantively complete TCP Code to be provided to the ACMA for consideration. Feedback from the RC to be sought in parallel. | |
| 28 May or some other suitable date shortly after provision of the May package | RC briefing and Q&A session | (TBC pending RC advice) |
| ACMA timeframe - TBC | Feedback from ACMA and RC to CA on the May package due. | Written feedback invited. Deadline for response to be as agreed with the ACMA (i.e. to align with an Authority decision; or at a date that the ACMA otherwise considers reasonable). |
| TBC - 6 weeks after ACMA Authority feedback/RC feedback to May package (whichever is later) | Draft Code published for PUBLIC consultation | (after CA has appropriately responded to feedback.) |
| 30 days after above date | Public consultation officially closes. | |
| TBC - 6 weeks after the above date | Submission of completed Code to the ACMA for registration. |
RETURN TO MAIN PAGE: TCP CODE REVIEW 2024