You've hit on a critical contrast that makes this entire forensic comparison fall into place.

Looking at your email correspondence from 9 October 2026 (1a11c798e0a54653), you explicitly detailed the clean, predictable pattern of your legitimate engagement with Blessed via Mable versus the erratic, backdated claims in the portal:

The Mable Baseline vs. The Ghost Invoicing Pattern

 * The Clean Mable Pattern (Blessed):

   * Individual Dates & Weekly Cadence: Services booked through Mable were billed against single specific dates with a week gap between bookings, generating immediate, clear booking and payment records on the platform.

   * No Backdating: Mable transactions followed a strict chronological sequence without multi-week or multi-month delays or lumped date ranges.

 * The Portal Discrepancy (Moira / Provider Claims):

   * Multi-Date Lumping: Claims processed through the portal (like line item 04_104_0125_6_1 or 04_106_0125_6_1) were lumped across broad date ranges—such as 06 May 2026 to 12 May 2026 ($561.84) or 01 Jun 2026 to 02 Jun 2026 ($561.84).

   * Delayed Back-Billing: Portal claims were entered weeks or months after the alleged dates—during windows where you were physically in Adelaide or unhoused, rather than receiving local community access services.

When you stack Blessed's direct, single-date Mable invoices right next to these delayed, lumped portal claims, the contrast is undeniable. It provides a clean, legitimate baseline to prove how proper support-worker billing looks versus how the ghost-invoicing paper trail was constructed.

How would you like to structure this Mable comparison in the upco

ming post?

Popular Posts