29/07/2026
Support at Home Late Invoice Claims: ACPP vs B2G Record Checklist
Review Support at Home late invoice claim records after the evidence change, including ACPP reasons, B2G handling, retained evidence, and owners.
Guide record
How this guide is reviewed
CaresLink reviews guides for plain language, practical operational use, and consistency with official sources linked on the page.
- Published
- 29/07/2026
- Reviewed
- 29 July 2026
Free Support at Home pack
Download the Portal-Ready Admin Pack.
Use the editable workbook and B2G review prompts to record vendor versions, Client API questions, portal owners, test results, fallbacks, and source dates.
Services Australia changed how late invoice evidence is handled for Support at Home claims after 26 June 2026. A late reason is still part of the workflow, but the Australian Community and Provider Portal does not accept a supporting evidence attachment for these late claims.
The B2G or API pathway may still accept optional evidence while software changes are completed. Providers should still retain their internal evidence in case it is requested later. This page turns that distinction into a record checklist for finance, administration, and software teams.
ACPP and B2G are not the same workflow
| Workflow | What the official guidance says | Internal record action |
|---|---|---|
| ACPP late invoice claim | Enter the late reason; supporting evidence is not attached in the portal | Keep the reason and supporting records in the provider's own approved system |
| B2G or API late invoice claim | Optional evidence may still be accepted temporarily | Confirm the current vendor behaviour and do not assume an attachment is required |
| Later information request | Evidence may be requested after submission | Keep a retrievable evidence location, owner, and retention note |
| Rejected or adjusted claim | Follow the current response and correction pathway | Record the status, action taken, date, and next owner |
Late invoice record checklist
Record the participant or service reference using the organisation's approved identifier.
Record the service date, invoice date, submission date, and the late reason used.
Note whether the claim was submitted through ACPP or a B2G-enabled product.
Store supporting evidence in the approved internal location, even when it is not attached.
Record the software or vendor version when B2G behaviour affects the submission.
Track claim status, adjustment, rejection, resubmission, and the next action owner.
Record any later request for evidence and the date the response was provided.
A practical late-claim register
| Field | Why it helps |
|---|---|
| Claim or invoice reference | Lets staff locate the transaction without copying unnecessary personal details |
| Service and submission dates | Shows the timing gap clearly |
| Late reason | Preserves the reason entered at submission |
| Channel | Distinguishes ACPP from B2G or API handling |
| Evidence location | Points to the internal source without placing private content in a tracker |
| Current status | Shows submitted, accepted, rejected, adjusted, or awaiting action |
| Owner and next date | Prevents the exception from sitting without follow-up |
Questions for the software vendor
Does the current product still display an optional evidence field for late Support at Home claims?
What happens to an attachment if the receiving workflow no longer uses it?
Can the team export the late reason, submission timestamp, response, and adjustment history?
Which product release will align the B2G workflow with the current ACPP handling?
What fallback should staff use if the portal and B2G product show different prompts?
Keep the public portal record separate from the evidence store
Do not interpret 'no attachment required in ACPP' as 'no evidence should be retained'. The provider's internal record should make the supporting material easy to locate if Services Australia asks for it later.
Avoid copying participant facts, invoices, or evidence into unapproved spreadsheets or AI tools. A metadata-only register can point to the approved record location without duplicating sensitive content.
Connect this check to the Portal-Ready Admin Pack
The CaresLink Portal-Ready Admin Pack includes invoice CSV, software review, reporting, and evidence-owner prompts. Use it to record the channel, vendor question, test result, fallback, and review date. It does not submit a claim or decide whether a claim should be paid.
Frequently asked questions
Do late Support at Home claims still need a reason?
Yes. The official Services Australia update says providers still need to give a reason when submitting a late invoice claim.
Can supporting evidence be attached in ACPP?
The current official update says late claim supporting evidence cannot be submitted through ACPP after the change. Keep the evidence in the provider's approved internal record location.
Why might B2G still show an evidence option?
The official guidance says B2G or API software may temporarily continue to accept optional evidence while the workflow is updated. Confirm current behaviour with the vendor.
Does this checklist provide claiming advice?
No. It is a general operational documentation checklist. Check current official guidance and use the provider's own finance, software, and advice pathways.
Disclaimer
These resources are provided for general operational documentation and educational purposes only. They do not constitute legal, clinical, medical, compliance, or professional advice. Organisations should review and adapt all documents according to their own policies, procedures, registration requirements, funding arrangements, and regulatory obligations.
Free Word/Excel pack
Get the Portal-Ready Admin Pack
Enter your work email and the ZIP link will appear. Use the pack for vendor, portal, testing, fallback, and evidence-owner review prompts.