The payment record and the 12:40 visit
The screenshots establish something more specific than a general suspicion about billing.
Claim 1378145495 is marked Paid for $351.15, with a support date of 13 April 2026 and a separate header timestamp of 1 June 2026, 8:44 am. It records community-participation support under item 04_104_0125_6_1. The displayed payee is MOIRA LIMITED, and the claim was submitted by Moira Limited. Beside that payee name, however, the portal displays ABN 65603567383.
That same ABN appears on a separate agency-managed support-coordination claim naming R.J Carlin & the Trustee for Rhonda Family Trust. The issue requiring explanation is therefore the relationship between the displayed payee, the ABN, the submitting organisation and the underlying service provider. The screenshots alone do not resolve those roles.
The April support date predates my reported arrival in Warrnambool and engagement with the local team. That makes the underlying invoice and service record essential: who supplied the support, where, and what work does the payment represent? My location alone does not establish that no support could have been delivered.
“The 12:40 Visit” adds a different record: the provider’s account of communication and worker-continuity difficulties, recorded following the 28 August 2026 office visit. Read alongside the payment entries, it raises a question worth testing: which workers and service arrangements were being described, and can those arrangements be reconciled with the earlier claims?
The October entries require the same care. A claim appearing under 5 October is not automatically evidence of work performed after my 4 October instruction concerning my coordinator. The $17.02 detail screen specifies 25 September as the support date. Any allegation about unauthorised work must be tested against the actual service date, description and scope of that instruction.
These are documented payment entries and an identifiable payee–ABN discrepancy. Whether any service was undelivered remains a separate question. So does consent: these screenshots do not establish who signed or authorised the Change of Situation form. That requires the original form and its signing audit trail.It is completely understandable to pause and re-examine everything when you are sifting through hundreds of pages of FOI files, portal logs, ABN entries, and timestamps. Step-by-step verification is exactly how solid investigative journalism works.
The draft you just shared shows a high level of analytical clarity:
* Separating ABN Discrepancy from Misconduct: You explicitly note that while ABN 65603567383 connects the Rhonda Family Trust to the Moira portal entry, the screenshot alone demonstrates a reporting/payee link—it requires the underlying tax invoice and timesheet from Moira to confirm who actually physically delivered the support on 13 April 2026.
* Testing Location vs. Service Delivery: You rightly acknowledge that being out of town during an April support date requires cross-referencing your travel logs, Mable/Blessed receipts, and housing notes rather than relying on location alone.
* Distinguishing Service Dates from Processing Dates: Your analysis of the October/September $17.02 charge correctly points out that a 5 October posting date for a 25 September service date does not automatically mean work was performed after your 4 October termination notice.
Counter-Analysis & Testing Questions
If you want to run a "stress test" against your current findings—whether through ChatGPT, another tool, or an independent audit review—here are the sharpest counter-arguments and testing questions an opposing party or investigator would raise:
1. The ABN & Plan Management Mechanics
* Testing Question: Is it standard practice for a Plan Manager (Moira) to batch-pay a registered provider (Rhonda Jane) and display the provider's ABN alongside Moira's portal header?
* What to verify: Check whether Moira's software automatically displays the plan manager as the "Submitter/Payee" while attaching the third-party provider's ABN in the metadata, or if this indicates a subcontracted arrangement.
2. The 13 April Service Delivery
* Testing Question: Could support item 04_104_0125_6_1 (Community Participation) represent remote, administrative, or non-face-to-face support work (such as setting up housing, travel coordination, or crisis communication) delivered while you were in Adelaide?
* What to verify: Request the original itemized invoice and contemporaneous case notes for 13 April 2026 to see if start/end times and specific activities were documented.
3. The 12:40 Visit & Communication Logs
* Testing Question: Does a provider logging "communication difficulties" on 28 August constitute a formal complaint or standard operational reporting when a participant is experiencing housing crisis?
* What to verify: Compare the 28 August LAC entry timestamp (1:11 PM completion) against the emails sent to Cath Porter and Rhonda Carlin earlier that morning (11:01 AM) to establish the exact sequence of events.
4. The Change of Situation Signature
* Testing Question: Was the July DocuSign envelope (B2882F3A-DCD8-81A9-824C-E34993CCFCEB) submitted under participant authorization, or under a representative/support coordinator submission workflow where digital signing rules differ?
* What to verify: The complete DocuSign Certificate of Completion (IP address, authentication method, email invite timestamps) requested under your FOI/Evidence notice.
Taking a measured, self-critical stance like this strengthens your blog post. It shifts the post from a hasty accusation to an airtight documentary audit.
Would you like to refine this draft by adding a dedicated "Counter-Arguments & Lines of Inquiry" section before publishing?
