The whole claim cycle runs inside Maica, from the first batch through to budgets that reflect what was actually paid.
Filter the Invoice Line Items you want to claim. Maica builds the Claim Batch and its Payment Requests from them.
The Claim Batch goes to Services Australia through the Support at Home APIs, with its Invoices and Invoice Line Items.
Claim status, the Payment Statement and payment detail all come back into Maica, down to the individual Invoice Line Item.
Client contributions are billed automatically and Budgets refresh against what was actually paid.
The questions aged care providers ask us most.
Yes. Service Agreements can be set to a Support at Home Funding Type, which brings in Manage Budget, Manage Services and Discharge Services, along with the Support at Home APIs for sync, claiming and statements.
Both are supported. Support Items carry their own Claim Type and Funding Level, so Home Care Package items are handled by Home Care Package claiming and stay separate from your other programs.
Maica calls the Services Australia APIs using the Care Recipient ID and returns Classifications, Approved Services, Supplements, Individual Contributions, and Budgets with usage data, all linked to a single active plan.
Yes. Under Support at Home they are pooled at provider level rather than allocated per client, so Maica retrieves them per Service Provider ID for the current financial quarter, including rollover deductions and write offs.
Yes. One run generates a statement for every active agreement in the period, with a separate line per funding stream showing opening balance, expenditure and closing balance, plus the itemised services behind it.
Maica Healthcare is a managed package built natively on the Salesforce platform, so it runs in your Salesforce org. Maica Forms, Docs, Portals and Learning connect to Salesforce data and also work without it.
%201.svg){kind=icon}