Documented System Limitations and Non-Conformities in AlayaCareSummary
Summary: What AlayaCare Cannot Do (Based on Actual Use and Evidence)
1. Cannot Produce Compliant, Consolidated Invoices:
-Cannot combine billed care hours and pass-through expenses (e.g., accommodation, travel) on a single, client-ready invoice.
-Forces manual invoice splitting, reconciliation, and external workarounds.
-Creates material non-compliance risk with PHSA and other public-sector payors that require unified invoices.
Impact: Direct breach of funder invoicing expectations; invoices rejected or delayed.
2. Cannot Reliably Sync Accurate Billing Data to QuickBooks OnlineL
-Sync produces partial, misaligned, or unusable entries.
-Accommodation costs, adjustments, and non-hourly items do not flow cleanly.
-Requires external accountants to rebuild billing data manually
Impact: Increased accounting costs, delayed financial close, unreliable financial statements.
3. Cannot Generate a Complete or Decision-Grade Gross Margin Report:
-Gross margin report (eventually delivered) lacked:
-Totals at the bottom of columns
-Reconciliation to invoices
-Tie-out to payroll and expense data
-Report was analytically weak and not usable for executive or board-level decision-making.
Impact: No reliable visibility into service-level or client-level profitability.
4. Cannot Support Public Health Authority Billing Complexity:
Not fit for:
-PHSA-style contracts
-Multi-rate billing structures
-Client-specific funding rules
-Other BC nursing agencies reportedly face the same systemic limitations, indicating a product-level issue rather than configuration error.
Impact: Platform misaligned with your core payer environment.
5. Cannot Replace Core Accounting Controls
Does not enforce:
-Proper audit trails for billing changes
-Clear linkage between shifts worked, expenses incurred, and amounts billed
-Required forensic accounting review to understand historical data.
Impact: Elevated audit risk and governance exposure.
6. Cannot Deliver What Was Represented During Sales & Onboarding:
Capabilities promised during demos and early discussions were:
-Delayed
-Partially delivered
-Or delivered in a form not operationally usable
-Critical invoicing and reporting gaps persisted despite repeated escalation.
Impact: Basis for misrepresentation and failure-to-deliver arguments.
7. Cannot Reduce Administrative Burden — Instead It Increases It
Required:
-External CPA intervention
-Manual invoice rebuilding
-Parallel tracking systems
-Caused approximately $15,000+ in additional accounting and remediation costs.
Impact: Net negative ROI versus incumbent system.
8. Cannot Support Timely Dispute Resolution or Meaningful Remediation
Repeated issues raised without:
-Timely corrective action
-Clear ownership
-Practical solutions
-Responses focused narrowly on one deliverable (gross margin report) while ignoring the larger billing failure.
Impact: Loss of confidence in vendor partnership and support model.
9. Cannot Function as a Stand-Alone Source of Truth
-Billing, expenses, payroll, and reporting cannot be trusted end-to-end.
Required fallback to:
-External spreadsheets
-Legacy systems
-Manual controls
Impact: System is not enterprise-grade for regulated healthcare staffing.
Bottom Line
AlayaCare cannot:
-Produce compliant invoices
-Handle complex public-sector billing
-Sync reliably with QBO
-Deliver defensible margin reporting
-Reduce admin workload
-Support governance-grade financial controls
-As implemented, it introduced risk, cost, and operational friction rather than solving them.