📣 3.1M+ views · 330K investor views · Analysts cut TPG's price target · Stock down ~8% after Investor Day · A CEO call that reached inside the complainant's workplace · Vodafone leaked employment records · Portal shut down mid-investigation · Now in legal channels

📂 Case Files

This page documents the full evidence trail – every call, every transcript, every reversal, every false flag – in the order it happened. The receipts are all here.

What began as a $50 billing error in May 2024 is now an active whistleblower matter under s1317AC of the Corporations Act, with legal representation engaged and active cases open with the TIO, OAIC, with the ACMA separately engaged.

TPG initially denied whistleblower protections. Then reversed that position. Then appointed an external independent investigator. The CEO’s contact with the complainant’s current employer has been confirmed in writing. Vodafone’s disclosure of confidential employment records to a journalist has been independently corroborated by a named email identifying Vodafone as the source.

📍 Case Overview (TL;DR)

What began as a routine billing dispute over a $50 refund has escalated into a complex dispute involving alleged billing errors, privacy breaches, internal account flags, and whistleblower disclosures concerning the conduct of TPG Telecom and Vodafone Australia.

In May 2024, Vodafone promised a $50 credit on a customer’s bill. When the credit did not appear after numerous follow ups, the customer lodged a complaint and initiated a partial chargeback for $50 through their bank. Vodafone’s internal billing system then incorrectly reversed the entire $2,088.51 bill, creating the appearance that the full payment had been refunded.

Despite confirmation from the customer’s bank that only $50 had been disputed, Vodafone continued to pursue the customer for the full $2,088 balance. Over the following months, the account was treated as overdue, and internal records were altered in ways that later prevented the customer from obtaining Vodafone services.

Despite Vodafone’s position that no adverse flags exist and no balance is owing, service eligibility remains blocked. The central unresolved issue is simple: if no negative markers exist, why is access still denied?

What should have been a simple correction became a prolonged dispute involving multiple regulators and internal escalation within Vodafone’s parent company, TPG Telecom.

During the course of the dispute:

The dispute subsequently escalated beyond a typical telecommunications complaint.

In October 2025, the Chief Executive Officer of TPG Telecom contacted a board member at the complainant’s workplace during the ongoing dispute. This contact has been confirmed in written correspondence.

In December 2025, a journalist provided an email identifying Vodafone as the source of information relating to the complainant’s employment history, raising concerns about the disclosure of confidential personal information.

As a result of these events, formal protected disclosures were submitted through KPMG FairCall, the external whistleblower service used by TPG Telecom. After initially denying that whistleblower protections applied, TPG Telecom later confirmed that the disclosures fall within the scope of the Corporations Act 2001 (Cth) whistleblower provisions.

An independent external investigator has since been appointed under TPG Telecom’s whistleblower framework to review the matter.

Separate complaints and referrals have also been made to several regulatory bodies, including the Telecommunications Industry Ombudsman (TIO), the Office of the Australian Information Commissioner (OAIC), and other regulatory agencies responsible for telecommunications and consumer protection.

This page documents the full chronology of events – including billing records, correspondence, call transcripts, and regulatory complaints – to provide a transparent record of how a minor billing dispute developed into a broader dispute involving consumer protections, privacy obligations, and corporate governance.

All factual claims referenced on this page are supported by documentary evidence, which is available to regulators, journalists, and legal representatives upon request.

🔍 Why This Case Matters

This case raises broader questions about how telecommunications providers:

– Handle billing disputes and chargebacks
– Apply internal credit and eligibility flags
– Respond to privacy access requests
– Interact with regulators during active complaints
– Comply with the TCP Code, RG 96 Debt Collection Guidelines, and legislation

It also highlights a potential accountability gap: even where errors are admitted, there may be no mechanism requiring providers to correct internal records that continue to affect customers.

Table of Contents

Personal vs Business Accounts

This case involves two Vodafone accounts:  

– A personal (Consumer) account – where a $50 refund dispute escalated into a $2,088 billing error, leading to incorrect reversals, adverse flags, and service denial.  

– A Business (LRC) account – which experienced a similar mishandled chargeback, was referred to debt collection during an active TIO complaint, and later linked to my personal account, contaminating my records with a false “write-off” flag.  

Both accounts demonstrate the same systemic failures – inaccurate billing, misuse of internal credit flags, and unlawful complaint handling. This is not just my story: other Vodafone customers are also submitting their experiences.

📅 Timeline of Events

🚦 The Start (May – June 2024)

  • I purchased an iPhone 15 Pro Max 256GB. The charge appeared on the bill with billing cycle ending 14 June 2024, amongst standard monthly charges.
  • Vodafone had promised a $50 credit off the total bill, due to incorrect charges.
  • Despite several follow ups, they stated a refund of $50 had been issued however no refund had been received.

👉 Had the same issue? Share your story here.

  • Despite awaiting this $50 credit, I paid the bill promptly on the 26th June 2024
  • Vodafone’s own systems (Siebel and invoice) showed this payment as received.

⚖️ TIO Complaint and Chargeback (July 2024)

  • On 5 July 2024, I lodged a TIO complaint regarding the missing $50 refund.
  • On 6–9 July 2024, Westpac processed a $50 chargeback, crediting the amount back to my card by 16 July.
  • Instead of reversing only $50, Vodafone incorrectly reversed the entire $2,088.51 in their Siebel CRM billing system.

💸 The Foundational Error ($50 → $2,088)

This is where it all started: a $50 dispute that ballooned into a $2,088 ‘debt’ because Vodafone’s system mishandled a partial refund. If this can happen from a small billing error, it shows how fragile their systems are.

  • 19 July: Vodafone’s Siebel system shows a reversal of the full balance. This error is the foundational issue that triggered everything that followed.
  • This is what the incorrect reversal looked like on the bill:

Vodafone’s incorrect reversal, as displayed on my bill.

  • And in Vodafone’s Siebel CRM records, this is what it looked like:

Siebel CRM entries showing full reversal (incorrect).

  • The same day: I receive an SMS demanding payment.

5 August 2024: Vodafone issues an overdue balance email for $2,080.52.

🔍 TIO Investigation (August – November 2024)

  • Despite clear evidence from Westpac, Vodafone continued to bill for $2,088.51.
  • The TIO outcome on 7 November 2024 relied only on Vodafone’s Siebel records and accepted Vodafone’s claim that the payment was reversed.
  • Vodafone did not check with their Banking & Finance Team, despite assurances on the contrary and a letter from Westpac.
  • Evidence from Westpac confirming only $50.00 was disputed was not considered. Vodafone failed to check their banking records and relied on internal Siebel CRM records alone.

👉 Need to push back on Vodafone? See Resources & Templates.

This was the formal correspondence and confirmation from Westpac, supplied to Vodafone however it was ignored:

🔁 The Double Reversal (August – November 2024)

While the personal account dispute was unfolding, the business account was mishandled in almost identical ways:

  • A chargeback was processed after I disputed billed charges, but Vodafone support provided no resolution.

Vodafone reversed the full payment amount despite a chargeback win

A chargeback for disputed fees was reversed, then re-applied on the next bill – a double charge of the same amount.

  • I escalated the matter to the TIO in December 2024. Vodafone’s own correspondence confirmed in writing that I was not required to pay disputed charges while the complaint was active.

📞 The Debt Collection Saga (January 2025)

  • Despite this, Vodafone referred the account to an external debt collection agency (DCA).
  • This in breach of the TIO’s Complaint Handling Process:

2.5.3 Ceasing credit management on disputed charges.

The member must stop all credit management for disputed charges while we are handling the complaint. When the TIO refers a complaint to the member, it must stop credit management action on disputed charges for the duration of the Referral period, and while the TIO complaint is open.

  • The DCA then harassed me with repeated calls, SMS messages, and emails, demanding payment of charges that were still under TIO investigation.

This wasn’t just poor complaint handling – it was a direct breach of the TCP Code & TIO Complaint Handling Procedures, which prohibits referral to collections while a complaint is open, and is also a breach of ACCC/ASIC debt collection guidelines (RG96).

⚖️ What this means for you:

If your account is in dispute with the TIO, Vodafone cannot legally send you to collections. If they do, cite TCP Code 2.5.3 and ACCC/ASIC RG96.

❌ Vodafone’s Response & “Resolution”

Despite clear evidence of duplicate charges, Vodafone’s Resolutions team repeatedly denied any error:

  • The Resolutions Team member insisted no duplication existed, even as invoices showed the same $152.47 appearing twice – once as a reversal and again as a “Credit Card Chargeback.”
  • I rebutted this multiple times, simply going off the bills, but Vodafone refused to acknowledg their error and adjust the bill, asking for my bank statements (which were unrelated).

📝 The ‘Waiver’ That Wasn’t (March 2025)

Eventually, Vodafone offered to “waive” the full $793.12 balance.

On the surface this looked like a resolution, but internally Vodafone did not treat it as a waiver/credit. Instead, they processed it as a write-off, leaving a collections flag attached to the account.

This matters because:

  • A true waiver/credit = balance cancelled, no adverse markers.
  • A write-off = balance treated as uncollectable, internally flagged like a bad debt.

Vodafone told the TIO it had “resolved” the matter – but in reality, it left behind a blacklisting flag that later contaminated my personal account and prevented new services.

The business account was closed with a $0 balance, but Vodafone refused to confirm in writing that the adverse ‘write-off’ flag was removed, or provide a “reapply without prejudice” letter, in the least that their billing errors would not form part of future assessments.

👉 Think your account has hidden flags? Use the correction request template in Resources to force Vodafone to confirm and fix internal markers.

⛔ The Constructive Obstruction (March 2025)

When I pressed Vodafone on why I was still being barred despite a $0 balance, the Case Manager simply fobbed me off. His response was dismissive, hiding behind vague “internal checks” and suggesting I “seek alternate options,” rather than acknowledging or correcting the false blacklist that Vodafone itself created and maintained.

👉 Don’t let them stonewall you – here’s how to escalate properly.

🏛️ Escalations to Executive Resolutions (January – March 2025)

  • 28 January 2025: I contacted Vodafone’s Executive Resolutions team.
  • 4 February 2025: I followed up with Vodafone CEO, Iñaki Berroeta. No response:
  • 17 March 2025: I escalated to the CEO, Head of Credit/Collections, Finance, and Executive Resolutions, outlining breaches of the TCP Code and the Privacy Act, seeking an amicable and timely resolution:
  • Vodafone responded only by restating the TIO outcome, ignoring both the evidence and the clear breaches of Privacy and the APPs.
  • Most concerningly, they stated that they would not correspond with me further on this matter, despite the ongoing inaccuracies and documented evidence to the contrary.
  • They also stated their position “has been made clear and will not change” & that this was their “final response”.

👉 Fighting Vodafone’s execs? Get the templates here.

🚩 The Overdue Flag (Business Account) (March 2025)

The Collections agent confirmed my balance was $0 and attempted to remove the “overdue” flag that was blocking new services. Mid-call, the Case Manager instructed her to stop and said he would “handle it by email.” He never did. The incorrect flag remained, continuing to block eligibility.

A full recording of this call was obtained via a Privacy Request.

Recording available to regulators and journalists on request.

👉 Has Vodafone breached your privacy? Share your story and get free support to fight back.

💥 Westpac Calls It, Again: Vodafone Got It Wrong

I lodged a second, formal complaint with Westpac to double check and provide Vodafone new, fresh evidence of their error.

Westpac responded with an official confirmation of Vodafone’s error, providing a detailed letter confirming the Acquirer Reference Number (ARN) via the Mastercard Portal for Vodafone to check with their Banking & Finance Team:

This confirms Vodafone’s error squarely. Additionally, Vodafone did not reply to the chargeback request (supplied with evidence to the Bank), hence it was found in my favour, yet they still processed a reversal, and for an incorrect amount.

🎭 The “Goodwill Gesture”

Despite Executive Resolutions previously declaring their position “final” and refusing further correspondence, once I escalated my evidence again – this time including Vodafone’s executives, CEO Iñaki Berroeta, and others – along with Westpac’s second formal confirmation of their error, Vodafone quietly shifted.

They offered to close the account at a $0 balance, presenting it as a “goodwill” gesture. But crucially, they did not admit fault, nor did they address the ongoing internal adverse flags that continue to block service eligibility.

👉 Gaslit by Vodafone’s ‘resolutions’? Join others fighting back.

My Response:

I acknowledged Vodafone’s “goodwill” gesture to close the balance at $0, but made it clear this alone did not resolve the dispute. I provided them with Westpac’s second formal confirmation that the $2,088.51 payment remained with Vodafone, attaching the evidence for their records.

I requested that Vodafone also restore my credit status and service eligibility – ideally through a fresh account with proper credit approval, as had existed before their error. I explained that while I was open to closure on this basis, without addressing the internal flags and service denial, the matter would remain before the TIO, who may ultimately recommend restoration of eligibility and order compensation for stress, inconvenience, and poor complaint handling.

To date, I have not received any reply despite multiple follow-ups.

🏳️ The Blacklist Flags

  • Although Vodafone eventually corrected the billing (likely from my email of the above Westpac letter to their Executives + Executive Resolutions), they failed to correct adverse flags from the dispute that acted as internal bans, preventing me from accessing Vodafone services.
  • Vodafone’s credit team gave contradictory reasons:
    • “Internal credit decision.” – vague
    • “External credit decision.” – false
    • “Credit bureau has not lifted the ban yet.” – false
    • Unproven allegations of misconduct, later dropped – not substantiated
  • All three major credit bureaus (Equifax, illion, Experian) confirmed I have a clean credit report. There was never a ban placed.
  • Vodafone Collections staff admitted my old business account, wrongly referred to debt collection during an active TIO dispute, is now linked to my personal account and blocking eligibility.

See Blog Post: From Error to “Gesture” – Vodafone’s Playbook for Avoiding Blame for a deeper look.)

⚖️ What this means for you:

Even if Vodafone gives you a “Paid in Full” letter, check for hidden write-off/overdue flags that may still block you, or mean you may be referred to Collections (like a debt collection agency).

Waived vs Written-Off – the blacklist trick [Business Account]

Vodafone told the TIO my balance was “waived” – but internally processed it as a write-off.

I had only found out after talking to Sales, they had asked me to speak to Collections. At no point should this have been referred to Collections given the account was waived/credited in full by Vodafone.

Upon following up, at least 4 times, Vodafone provided a ‘paid in full’ letter. I also requested for Collections to raise a backend ticket to remove the ‘write-off’ flag, as it was incorrect.

After several follow ups, the Vodafone Collections Admin team provided a paid in full letter, however there was no word on the correction for the ‘write-off flag’.

After following up with a Collections Supervisor, he did indeed raise a request to remove the ‘write-off’ flag.

The next day he called back, advising the ‘write-off’ flag could not be removed, no specific reason provided, however he did quote the TIO case.

• Waived/Credited: the charge is cancelled; no negative flag should remain.

• Written-off: treated as a bad/dead debt (internal adverse marker) that can block future eligibility.

Vodafone’s own accounting policy says receivables are written off when there is no reasonable expectation of recovery (e.g., long-overdue, no repayment plan). That did not reflect my situation.

Result: The account showed $0 publicly, but a write-off/overdue flag persisted internally – the very reason new applications were refused. Calling this a “goodwill” waiver while keeping a write-off flag is misleading and corrosive.

⚠️ The False & Defamatory Accusations

Vodafone introduced new claims to the TIO – alleging I’d made “hundreds of applications” and used “altered ID.” These serious accusations were never raised previously, no evidence was provided, and they were quietly dropped when challenged.

If Vodafone genuinely believed “altered ID” was used, that would imply KYC failures on Vodafone’s part (which they did not assert elsewhere). The allegation appeared retaliatory and were abandoned without explanation, confirmation or correction.

When I had later followed up with the TIO Case Manager on this, several months later, she had no idea about it. Further, she had advised me Vodafone provided evidence of only 3-5 applications that had been made.

See Blog Post: False Allegations – “Altered ID” & “Hundreds of Applications” for more detail.

🔒 Privacy Act Breaches (2024–2025) – Obstruction, Delays, and Excessive Fees

August 2024 – Privacy Request Lodged

On 21 August 2024, I lodged a formal request under the Privacy Act 1988 (Cth) for access to all personal and credit information Vodafone holds about me.

  • Vodafone’s own policy promises a response within 30 days.
  • APP 12.4 also requires organisations to respond within 30 days.

August – September 2024 – Silence and Delays

For over two weeks, I received no acknowledgement. On 5 September, I chased them. Only then did Vodafone finally reply – not with information, but with a new digital ID hurdle. I responded the same day.

  • On 10 September, Vodafone admitted they had located five accounts linked to me, but demanded $20 per account, payable up front.
  • After I clarified further account numbers, Vodafone went silent again.
  • By 18 September, after more chasing, they admitted they had eight accounts and increased the fee to $160.
  • This back-and-forth continued, with Vodafone drip-feeding responses only after repeated follow-ups.

Vodafone then went completely silent and did not respond to multiple follow ups for access to credit-held information on myself:

September 2024 – Escalation to TIO

By mid-September, after almost a month of obstruction and silence, I lodged a complaint with the TIO. Only then did Vodafone begin processing the request.

January 2025 – Access Finally Provided

After five months of chasing, Vodafone finally delivered partial account notes in January 2025 – five times longer than the legal 30-day deadline.

Vodafone had already breached APP 12 and its own Privacy Policy.

This was only the first half of Vodafone’s Privacy Act breaches. What began in 2024 with delays, stonewalling, and partial access escalated further in 2025 into even more serious obstruction, excessive fees, and misuse of legal exemptions.

Early 2025 – Second Access Request and $5,088 Quote

  • I submitted a formal APP 12 request for everything relevant – complete account history, records of the chargeback, internal emails/notes and account remarks, credit assessments, any overdue/write-off/collections flags, internal communications between complaint managers, plus any related call recordings and chat logs. Vodafone’s reply was a $5,088 quote to access my own data, alongside misapplied APP 12.3 exemptions.
  • Vodafone demanded $5,088.44 for access to my own personal information – nearly $4,000 for 197 web chats and over $1,000 for 36 call recordings.
  • Vodafone quoted $5,088 to access my own records – an excessive fee that functioned as a barrier to access (contrary to APP 12.8).
  • Under the Privacy Act 1988, APP 12 requires access fees to be reasonable. Vodafone’s charges were grossly disproportionate to the actual cost of retrieving digital records and created a constructive barrier to access – obstructing my legal right to review and correct the very records they were relying on against me.

I challenged Vodafone’s $5,088 quote. The Privacy Act says they can’t overcharge, must explain any refusals, and should at least give a redacted copy. They ignored all of that.

⚖️ What this means for you:

If Vodafone ever quotes you a massive fee for your own records, remember APP 12.8 – charges must be reasonable. Anything excessive may be a constructive denial of access.

📌 What I Raised as Breaches

  • APP 12 (Access) – right to access my personal information.
  • APP 12.8 (Reasonable fees) – charges must not be excessive or punitive.
  • APP 12.9 (Summary access) – if full access isn’t possible, organisations must provide summaries or redacted versions.

📧 Vodafone’s Response

Vodafone’s Privacy Team replied by:

  • Citing APP 12.3(h) – suggesting “unlawful activity” or “misconduct” could justify refusal.
  • Citing APP 12.3(j) – claiming disclosure could reveal “commercially sensitive decision-making.”

They used these provisions to block access entirely – while still demanding thousands of dollars.

❌ Why This Was a Breach

  • Exemptions Misapplied: APP 12.3(h) & (j) are for fraud investigations or genuinely sensitive evaluations. Routine chat logs and call recordings do not fall under these categories.
  • No Redacted Access: Even if exemptions applied, APP 12.9 requires Vodafone to provide partial or redacted access. They refused.
  • Barrier to Access: $5,088 for digital records already stored in their systems is punitive and disproportionate, breaching APP 12.8.

In short: Vodafone priced me out of my rights, misused legal exemptions, and ignored their duty to provide redacted access. What should have been a straightforward privacy request became another layer of breach and obstruction.

See Blog Post: The $5,088 Price Tag on My Privacy for the full breakdown.

👉 Quoted an excessive privacy fee? Use the OAIC complaint template in Resources to escalate – APP 12.8 requires fees to be reasonable.

🚧 The TIO Stonewalling (June – August 2025)

Following repeated escalation, Vodafone quietly acknowledged an “administrative error” in its billing system.

Despite this admission, Vodafone has refused to issue any correction letter, apology, or confirmation that adverse flags will not affect future eligibility.

Through the TIO, Vodafone claimed no adverse flags exist, yet refuses to confirm this in writing, contradicting evidence from their own staff and internal records obtained under Privacy Requests.

📞🕵️‍♂️📢 Weeks of chasing just to get the Case Manager on the phone – only to be told Vodafone’s was not aware of an ‘error.’

At no stage of this TIO case did Vodafone proactively contact me by phone, and I only ever received a single email. Out of curiosity, I began chasing the Case Manager, the new case manager assigned at that time:

  • Mon 18 Aug 2025 – Told he was unavailable, call-back requested.
  • Tue 19 Aug 2025 – Again told he was unavailable, no other case manager could assist. Call-back ETA given as 24–48 hours.
  • Thu 21 Aug 2025 – No call-back received. I called again; after a hold, the Case Manager finally picked up. We spoke for ~15 minutes, but he refused to discuss specifics, claiming he did not “ID me” – even while speaking as though he knew the case in detail.

The Case Manager confirmed that an apology letter could be issued if Vodafone had made an error, but added that he did not believe Vodafone had – contradicting Vodafone’s own written admission of an “administrative error.” He also admitted that many of the “applications” Vodafone used against me were automated system outcomes, not repeated manual re-applications, undermining Vodafone’s scapegoat narrative.

Vodafone meanwhile proposed a token sum above the TIO’s guidance for non-economic loss, but the TIO continues to characterise it merely as a refund. This framing strips the payment of its true context.

The fact that Vodafone paid significantly above the Ombudsman’s cap raises the obvious question – are they tacitly acknowledging the seriousness of their error, while avoiding any formal admission of liability?

An ex-gratia settlement for systemic mishandling, poor complaint handling, breaches (not including privacy), and more than a year of detriment.

Vodafone’s position, even after all this, remains unchanged: the billing error is admitted, but the conduct that appear retaliatory through blacklisting continues. No apology letter. No written confirmation that no adverse flags exist. No acknowledgement of staff admissions that the flags were still active. No ‘re-apply without prejudice’ assurance. Nothing.

👉 Felt stonewalled or gaslit by Vodafone? You’re not alone – share your story.

🚩 Did Vodafone Mislead the TIO and Mischaracterise Compensation?

Vodafone eventually made a payment above the Telecommunications Industry Ombudsman’s usual cap for non-economic loss. However, instead of acknowledging this as ex-gratia compensation for stress, poor complaint handling, and systemic breaches, Vodafone characterised the payment as a simple refund – a framing that, in my view, does not reflect the true nature of the payment.

This is misleading for two reasons:

  1. The charges were already paid for in full, back in June 2024. There was no “refund” owing. The funds Vodafone paid were not a refund of money I had paid in error – they were damages for Vodafone’s admitted administrative error and the harm it caused.
  2. It conceals liability. By calling the payment a “refund,” Vodafone attempted to disguise the fact that it had exceeded the TIO’s compensation cap, effectively paying a settlement while refusing to admit wrongdoing in writing.

At the same time, Vodafone’s representations to the TIO were inconsistent with information provided by its Collections Team on 5 September 2025. They assured the TIO that all flags were cleared and the balance resolved. Yet when I checked directly with Vodafone’s own Collections team, the account was still flagged with an internal “write-off” marker and even treated as owing. Agents asked me for payment of a balance that was supposed to have been fully credited under the TIO case resolution.

Plainly put: Vodafone told the TIO the business account was cleared; Collections told me the opposite on 5 Sept 2025.

Call Transcript – 5 Sept 2025 (Vodafone Collections)

“This account is no longer with Vodafone Collection, but it is with the Commercial Credit Control… it was referred a few months back.”

“As of today… there is a write-off flag present on the account. Once you complete the payment, you need to go to the store and they will speak to the credit team who can help to remove that flag.”

“The balance is $793.12.”

This directly contradicts Vodafone’s representations to the TIO, where they claimed there were no amount owing and no adverse flags on my accounts. The transcript proves:

  • The business account was referred to a debt collector (Commercial Credit Control).
  • A write-off flag is still active under my account, name, and details.
  • Vodafone’s statements to the TIO were inconsistent with Collections’ advice to me on 5 Sept 2025. I believe they continue to hold false records that block service eligibility.

This demonstrates:

  • Potentially misleading the Ombudsman – providing false assurances about account status.
  • Failure to correct inaccurate records – contrary to APP 10 (accuracy) and APP 13 (correction).
  • Constructive obstruction and retaliation – continuing to hold and act on false data after admitting liability.

Vodafone paid above the TIO’s cap, disguised it as a “refund,” and Vodafone’s statements to the TIO were inconsistent with Collections’ advice to me on 5 September 2025. I believe they may have misled the TIO about account corrections. The underlying systemic breaches – false records, denial of service, and misrepresentation – all remain unresolved.

⚠️ Why this matters:

  • There was nothing to refund – I had already paid in full in June 2024.
  • The payment was made as a direct credit to my CBA account, not as a card refund, proving it was fresh compensation.
  • Vodafone may have misled the TIO by claiming all adverse flags were cleared; staff and transcripts show the opposite.
  • Both Vodafone and the TIO have used this framing to conceal liability, while refusing to confirm in writing that records were corrected or that I could reapply without prejudice.

👉 In short: Vodafone hid behind the TIO, and the TIO hid behind Vodafone. The result is no apology, no written correction, inaccurate flags still remaining in place, and ongoing service denial despite admitted errors.

🧨 TIO Catches Vodafone’s Write-Off Flag (September 2025)

This week (September 2025), the TIO phoned me directly in response to my previous submission that Vodafone Collections was stating a balance was still owing, along with confirmation of a write-off flag present, despite previous assurances. In that call, she confirmed:

  • ✅ The disputed balance is not owing.
  • ⚠️ A “write-off” flag does remain on my Vodafone business account.
  • ❌ The TIO cannot compel Vodafone to remove it or revisit the prior complaint outcome.

The contradictions:

  • In March 2025, Vodafone (Case Manager, Resolutions) told me the balance was waived/credited.
  • Vodafone later issued a “paid in full” letter.
  • Vodafone assured the TIO there were no flags.
  • Collections later told me the opposite.
  • Finally, the TIO confirmed the flag exists – but won’t require Vodafone to remove it.

The accountability gap: Vodafone acknowledges the errors privately but refuses to own them publicly or correct them in writing.

  • Vodafone refuses to reply to follow-up emails or put anything in writing.
    ‎
  • No apology letter, despite the Case Manager (Vodafone Resolutions) admitting it was within his remit and two separate follow-ups from me.
    ‎
  • Instead, Vodafone staff have quietly clicked through to this blog but continue to ignore all requests for confirmation.
    ‎
  • More importantly, Vodafone has formally acknowledged that it is retaining a false “write-off” flag on my account, constituting a potential breach of its obligations under the Privacy Act 1988 (Australian Privacy Principles).

⚠️ Why this matters

  • It signals Vodafone may have misled the Ombudsman. They claimed no flags existed when one did.
    ‎
  • It highlights a regulatory gap. The TIO admits it lacks power to compel Vodafone to correct inaccurate records – even after admitting fault.
    ‎
  • It leaves consumers blacklisted. Customers can walk away from a “resolved” TIO case but still carry internal write-off flags that deny them service, effectively marking them as bad debtors. In any such event of a CRM/billing system migration or update, customers could go through the same ordeal of debt collection, defaults and more all over again.

👉 In short: Vodafone hid behind the TIO, and the TIO hid behind Vodafone. The false records remain in place.

📋 Write-Off Flag Dispute Continues (ongoing)

Following the TIO’s September 2025 confirmation that a write-off flag remained on the account, Vodafone subsequently provided a screenshot, as part of the Fair Offer Assessment, purporting to show no write-off flag and no outstanding balance. Despite this, service eligibility remains barred.

Vodafone’s position on the write-off flag has been contradictory throughout. Across multiple interactions, staff have alternately confirmed the flag’s existence, denied it, and provided inconsistent explanations for the continued service bar. A screenshot showing a clean account does not reconcile with an eligibility block that remains in place – and Vodafone has provided no explanation for that gap.

The matter has been escalated to the TIO’s senior appeals team and is currently at desktop review stage. As part of that review, a full audit trail has been requested – including an examination of whether Vodafone misled the Ombudsman and the complainant regarding the true status of the account and the presence of adverse flags.

The core question is straightforward: if there is no write-off flag and no balance owing, why is eligibility still barred? Vodafone has not answered it.

📞 TPG CEO Contacts Complainant’s Employer (October 2025)

TPG’s CEO personally contacted a board member of the complainant’s current employer during the active dispute. This has been confirmed in written correspondence. TPG has not denied it at any point.

🔒 First Protected Disclosure via TPG & KPMG FairCall (October 2025)

First and second formal protected disclosures submitted through TPG’s external whistleblower service (KPMG FairCall) under the Corporations Act 2001 (Cth).

⚖️ TPG Reverses Whistleblower Denial (November 2025)

TPG initially denied that the matter qualified for whistleblower protections under Part 9.4AAA of the Corporations Act. TPG subsequently reversed that position, formally acknowledging coverage under s1317AC and referring the matter for independent review via KPMG FairCall. At no point has TPG denied the CEO contact incident itself.

📧 The Journalist Email (December 2025)

A named journalist email independently corroborates that Vodafone disclosed the complainant’s employment history to a member of the media in an apparent attempt to discredit the complainant. The email identifies Vodafone as the source by name. This evidence is produced and documented for regulatory and legal purposes.

🔒 Second Protected Disclosure via KPMG FairCall (December 2025)

Second formal protected disclosure submitted.

🔍 External Independent Investigator Appointed (December 2025)

TPG appoints a Band 1 external investigator to conduct an independent investigation under TPG’s whistleblower framework. The appointment of a senior independent investigator of this calibre signals the matter has been escalated to the highest internal governance level.

📋 TIO Appeal at Senior Officer Desktop Review (Early 2026)

TIO appeal progresses to senior officer desktop review stage. The appeal involves the admitted billing error, the write-off flag incorrectly applied to business account, and TCP Code breaches.

👨‍⚖️ Legal Representation Engaged (2026)

Legal representation engaged.

What began as a $50 billing error. What it became is now a matter for the Federal Court if necessary.

Vodafone’s conduct is not a one-off billing error: it demonstrates potential systemic breaches across multiple regulatory frameworks.

📑 Telecommunications Consumer Protections (TCP) Code

  • Clause 8.2 & 8.3.1 (Complaint handling): failure to engage transparently, failure to provide clear reasons, and constructive obstruction (e.g. Case Manager preventing removal of an overdue flag despite $0 balance).
  • Clause 8.5 (Escalation to external resolution): improper referral of an account to debt collection while a TIO complaint was active.
  • Clause 8.6 (Timeliness): multiple missed deadlines, including over 4 months of non-contact during an active TIO complaint, and missed call-back commitments.
  • Clause 4.1 (Accuracy of billing): reversal of a full $2,088.51 instead of the disputed $50, followed by pursuit of an invalid debt.
  • Clause 2.5.3 (Collections during TIO complaints): Vodafone repeatedly engaged in credit management action while complaints were open with the TIO, in direct breach of the Code. Both personal and business accounts were pursued – including referral of the business account to an external DCA (Commercial Credit Control) and issuing 21D/6Q default notices – while the charges were still under TIO dispute. This is one of the clearest and most serious breaches, as clause 2.5.3 explicitly prohibits any debt collection while the Ombudsman is investigating.
  • Constructive service denial: maintaining internal “write-off” or overdue flags to block re-application for services.
  • Retaliatory conduct: service ineligibility imposed after Vodafone admitted its billing error, despite prior approvals.

👉 What this means for you:

If you lodge a complaint with the TIO, your telco must stop all debt collection and credit management on the disputed charges until the TIO process is finished. Vodafone ignored this rule by still sending accounts to collections, issuing default notices, and demanding payment. This is a serious breach of consumer protections – if it happens to you, cite TCP Code clause 2.5.3 and escalate immediately.

🔒 Privacy Act 1988 (Cth) – Australian Privacy Principles (APPs)

  • APP 1 (Transparency): shifting and inconsistent reasons for service refusal (external bans, internal credit decisions, fraud allegations), without clarity or disclosure.
  • APP 10 (Accuracy): retention of inaccurate personal data (overdue and write-off flags) despite “paid in full” letters and evidence.
  • APP 12 (Access): refusal to provide internal records underpinning service denial unless excessive fees ($5,088.44) were paid.
  • APP 12.8 (Reasonable fees): grossly disproportionate charges for basic digital records (chat logs, call recordings).
  • APP 12.9 (Summary access): refusal to provide redacted/summary versions where full disclosure not feasible.
  • APP 13 (Correction): ignoring at least four separate requests to remove incorrect backend flags.
  • Misapplication of exemptions (APP 12.3(h), 12.3(j)): claiming “commercial sensitivity” and “unlawful activity” exemptions to obstruct legitimate access requests.

📘 ACCC & ASIC Debt Collection Guidelines (RG 96)

  • Pursuing recovery of a disputed debt during an active TIO process.
  • Linking an unrelated business account (already disputed) to a personal account, blocking eligibility.
  • Providing contradictory reasons for refusal, misleading the consumer.
  • Harassment via repeated overdue notices and demands despite $0 balance.
  • Unsubstantiated allegations later withdrawn (“altered IDs”, “hundreds of applications”) made to the TIO without substantiation, later abandoned.

⚖️ Australian Consumer Law (ACL)

  • s18 (Misleading or deceptive conduct): repeatedly claiming external credit bans existed when Equifax, illion, and Experian confirmed clean files.
    • Misrepresenting the nature of compensation: Vodafone proposed a sum of money consistent with the TIO’s guidance for non-economic loss, but the TIO repeatedly positioned it as a refund. This reframing conceals the fact that Vodafone’s payment relates to its administrative error and non-economic detriment, not a simple billing correction.
  • s29 (False or misleading representations): misrepresenting the effect of internal “flags” and telling the TIO issues were resolved when they weren’t.
  • s21 (Unconscionable conduct): retaliatory refusal to provide services after admitting an “administrative error”. Power imbalance exacerbated by telco being an essential service.
  • s23 (Unfair contract terms): reliance on vague “commercial discretion” to deny services after Vodafone’s error, applied inconsistently and without transparency.
  • s60–62 (Consumer guarantees): services not provided with due care and skill in maintaining accurate account records.

📡 Telecommunications Act 1997 & ACMA oversight

  • Potential breaches of licence conditions requiring accurate billing and fair complaint handling.
  • Non-compliance with ACMA-enforceable industry codes (TCP Code).
  • Possible breach of ACMA’s Know Your Customer (KYC) requirements: allegations of “altered ID” would, if true, mean Vodafone failed its regulatory obligation to reject invalid ID – but no such breach existed, meaning allegations were false and improperly raised.

🏛️ TIO Terms of Reference & Procedures

  • Failure to engage with the consumer during a live complaint (no call-backs, no updates for >4 months).
  • Failure to meet TIO deadlines for substantive responses.
  • Providing inconsistent, misleading, or potentially defamatory information to the TIO (“hundreds of applications”, “altered IDs”), not supported by evidence.
  • Ignoring good-faith settlement offers (Calderbank letters), undermining conciliation.
  • Denial of procedural fairness: refusing to disclose the data used to justify service denial.

🚫 Pattern: Obstruction, Retaliation, Denial of Service

  • Constructive obstruction: Case Manager preventing staff from removing an overdue flag, maintaining false adverse records despite $0 balance.
  • Constructive denial of service: using backend write-off/overdue flags as pretext to reject applications, even after Collections staff admitted they were wrong.
  • Retaliation: timing of refusal of service immediately after Vodafone admitted its billing error, inconsistent with years of prior approvals.
  • False and unsubstantiated allegations of misconduct (‘altered ID’) raised before the TIO, then abandoned without explanation or correction.
  • Retaliatory denial of service (expanded): Even after confirming the account balance was $0 and collections had been withdrawn, Vodafone refused to remove the internal blacklist. Applications were blocked without any external credit check – proving it was their own false records, not my credit file. When pressed, Executive Resolutions Manager Case Manager dismissed the issue with vague references to “internal checks” and told me to “seek alternate options.” This is consistent with a pattern of retaliation: instead of correcting their errors, Vodafone continued to deny service despite admitting the underlying error.

💥 Why This Case Surpasses Prior Telco Precedents (e.g. D’v Telstra)

  • Broader APP breaches (1, 10, 12, 13 vs limited scope in D’v Telstra).
  • Ongoing detriment – denial of service access for >12 months, despite clean credit reports and no money owing.
  • Ongoing systemic neglect – false flags maintained even after “paid in full” letters, and record corrections requested multiple times.
  • Cross-code non-compliance – Privacy Act, TCP Code, ACL, RG96 simultaneously.
  • Retaliatory element – discretionary denial of service applied only after consumer complaint success, showing bad faith and retaliatory conduct.

📞 TIO Complaint Handling Failures

Vodafone’s conduct was compounded by failures in the TIO’s handling of the dispute. Under the TIO’s Terms of Reference, service providers must keep accurate records, respond in a timely way, and ensure fairness in external resolution. In this case:

  • Vodafone did not initiate any contact during the active complaint, except for a single email that introduced unsubstantiated allegations.
  • The TIO did not respond to those allegations, did not verify them, and missed multiple deadlines for call-backs and updates.
  • Despite repeated follow-ups, the TIO failed to confirm or address the presence of Vodafone’s internal credit flags, continuing to deny any wrongdoing.
  • The TIO refused to discuss case specifics when pressed, citing identification requirements, yet relied on Vodafone’s submissions without scrutiny.

This lack of oversight enabled Vodafone to stonewall, escalate untested allegations, and prolong the dispute well beyond reasonable timelines.

🚫 False Allegations, and Constructive Obstruction

Vodafone repeatedly introduced contradictory, false, and defamatory claims as the basis for denying services:

  • Alleged “hundreds of applications” and “altered ID methods” – serious accusations of misconduct – raised only late in the dispute, never mentioned in prior complaints or Privacy Act responses.
  • These allegations were quietly abandoned after being challenged, without apology or correction.
  • If Vodafone genuinely believed “altered ID” was used, this would amount to an admission that Vodafone’s KYC process is inadequate and a failure to comply with ACMA’s regulatory obligations. Having failed to substantiate the claim, Vodafone later dropped it.
  • Vodafone’s own staff encouraged and facilitated multiple applications (via live chat, Collections, and Executive Resolutions) while backend “write-off” flags remained in place. The volume of applications was then used against me as a scapegoat.
  • The true cause was always the incorrect account flags. If Vodafone had corrected its data, the repeated applications would never have been necessary. Instead, Vodafone is now using the volume of applications as a convenient scapegoat to justify service denial, rather than addressing the underlying record errors.
  • In May 2025, a credit application was forced through: it was not auto-declined, was referred based on positive bureau data, but ultimately rejected due to the presence of write-off flags.
  • Multiple emails from Vodafone’s credit team gave inconsistent reasons for denial:
    • “External credit bureau data” (false).
    • “Internal credit decision” (vague).
    • “Ban not lifted” (false – all credit agencies confirmed no such ban).
    • Allegations of misconduct (unsubstantiated, later withdrawn).
  • This pattern shows constructive obstruction: using false allegations and incorrect flags to deny service, while preventing correction of records.

😡 Consequences and Impact

The ongoing harm caused by Vodafone’s conduct is significant:

  • Over 350+ hours spent attempting to chase a promised credit, correct records (across calls, emails, live chats, and escalations).
  • Loss of service eligibility despite years of prior approvals and a clean credit history.
  • Forced to switch to another provider at higher cost, with the loss of continuity of service.
  • Reputational harm – Vodafone’s unsubstantiated allegations of misconduct (‘altered ID’) raised with the TIO were damaging and were subsequently abandoned without explanation or correction.
  • Emotional stress and exhaustion from prolonged stonewalling, contradictory responses, and refusal to correct clear errors.
  • Denial of a basic consumer right: to apply for services on fair and accurate terms.
  • Retaliatory timing: service eligibility was blocked only after Vodafone admitted its “administrative error,” despite years of prior approvals and clean external credit reports.

Even after admitting no balances were owing, and providing this in writing from their Executive Resolutions team, Vodafone has kept backend write-off and overdue flags in place, ensuring continued denial of services. Their “commercial discretion” was exercised inconsistently and appears retaliatory, applied only after their billing error was admitted.

📊 Investor Impact: TPG Telecom’s results Q&A (Thursday 28 August 2025) saw an analyst press management on billing accuracy – the very heart of the systemic issues documented here. While Voda.fail was not mentioned directly, it’s clear institutional investors are taking note. Voda.fail has been in touch with analysts and provided briefings.

👉🏻 See Blog Post: Analysts Briefed, Billing Accuracy Raised at TPG Q&A

⚡ Why It Matters

If Vodafone can deny one customer service based on false records, they can do it to thousands. This page shows how a $50 dispute turned into systemic billing, credit, and privacy failures.

👉 Don’t let it be dismissed as “an error.” Share your story.