Checking your Blogger archive records and formal notices provides the exact chronology and foundational context for the early April and May entries under MOIRA plan management.

Here is the focused breakdown connecting those early entries to the broader audit trail:

The MOIRA Period: Early April to June Invoicing Audit

  1. 6 April 2026 ($245.81) — Paid 21 May 2026
    • The Issue: A substantial delay of over six weeks between the recorded service date and the eventual payout date. This lag forms part of the core question regarding when invoices were actually received, processed, and validated by MOIRA.
  2. 17 April 2026 ($210.69)
    • The Issue: Logged under community participation. This entry requires cross-referencing against contemporaneous personal travel logs, Mable records, or support worker confirmation to verify physical presence and service delivery.
  3. 6–12 May 2026 ($561.84) — Paid 16 May 2026
    • The "Ghost Invoicing" / Block-Billing Flag: This multi-day span ($561.84) was lumped into a single block claim. Lacking itemized daily hours or contemporaneous case notes, it exemplifies the type of billing structure that obscures whether supports were delivered on each individual day within that week.
  4. 1–2 June 2026 ($561.84)
    • The Duplicate Pattern: Repeating the exact financial amount ($561.84) seen in the May block entry, pointing to recurring batch-billing mechanisms rather than individualized, date-specific service reporting.
  5. Unconfirmed Date ($286.72)
    • The Missing Documentation: A MOIRA-submitted entry where the original supplier invoices and supporting records were not visible or accessible within the participant portal view.

How This Ties Into the Wider Archive

As documented across your formal notices and Blogger revision logs, these entries are not isolated anomalies—they represent the structural friction of the MOIRA management period before transitioning to subsequent plan managers. The central investigative question remains: Did these lump-sum, delayed, and block-billed claims correspond to verified, on-the-ground support delivery, or did administrative automation manufacture a paper trail detached from actual service?

Let's work backward or forward from here—how would you like to refine this specific block of entries for the next post or ledger update?

This post brings the core puzzle pieces directly into focus.

Looking at the text and the exhibits on the Truth Sequences blog post:

  1. The Nine Booked Nights: Breaking down the chronological anchor across consecutive blocks (13–17 April 2026 and 17–22 April 2026) to separate reservations from actual occupancy, payment authority, and final itemized billing.
  2. The Four Separate Dates: Emphasizing that a service date, invoice date, submission/processing date, and payment date must never be conflated or treated as interchangeable.
  3. Figure 3 (The Cash Receipt): The handwritten cash receipt issued by Brett McKean (brettmkean6@gmail.com, Supplier ABN: 51 824 753 96) documenting transport costs ("adelaide-warrnambool Return") for client Ivan Brecevic (Participant #567168465), routing to BSB 063-767, Account 1166 1548, with a total noted as $214.

This post ties together the exact friction points we've been mapping across the MOIRA management period, the accommodation trail, and the transport expense logs.

Keeping this framework clear—separating booking confirmations from occupancy, and distinct dates from processing milestones—is essential as we audit the rest of the ledger. Where would you like to take the review next?



Popular Posts