ASIC's Specification
Agent not authorised by Form 362 to access this company
Cause
The V456 error indicates that you are not currently recorded as the ASIC agent for the company with ASIC.
When this occurs, ASIC will reject the lodgement because you are not registered against the company on ASIC’s records.
This can occur even if you believe you are the appointed agent and there is no record in CAS 360 of a Form 362 being lodged to cease your agency.
Form(s) Affected
- All electronic Forms
Why This Error Occurs
The V456 error may occur in the following situations:
1. No Form 362 Has Been Lodged
You have not previously lodged a Form 362 to appoint your agency for the company.
Until ASIC has processed a Form 362 appointing you as agent, you cannot lodge documents on behalf of the company.
2. Your Agency Was Ceased
A Form 362 may have been lodged to cease your appointment as an ASIC agent.
This may have been:
- Lodged through CAS 360, or
- Lodged directly with ASIC outside of CAS 360.
Once processed, ASIC removes your agency from the company record, preventing further lodgements.
3. Another Agent Has Appointed Themselves
In some cases, there is no record in CAS 360 of a Form 362 ceasing your agency, however you still receive the V456 error.
This may occur if another party has lodged a Form 362 directly with ASIC to appoint themselves as the new agent.
When a new Form 362 is lodged appointing a different ASIC agent, ASIC will automatically cease the previous agent on their records.
In this scenario, your agency is removed from ASIC even though no cessation form was lodged through CAS 360.
4. Timing Delay After Lodging Form 362
If you are attempting to lodge a form shortly after lodging a Form 362, the V456 error may be due to a timing delay while ASIC updates its records.
Even if the Form 362 has been successfully accepted, ASIC’s systems may take time to recognise you as the registered agent for the company.
In some cases, if ASIC is experiencing issues with their online services or EDGE Mailboxes, processing times may be longer than usual. During this period, you may temporarily receive the V456 error when attempting to lodge documents.
How to Resolve the V456 Error
If you receive the V456 error after lodging Form 362:
Confirm the form has been successfully processed by ASIC.
Check that you are using the correct corporate key.
Allow sufficient processing time if the form was recently lodged.
Confirm With the Client
Confirm with your client that:
- You are still the authorised ASIC agent for the company.
- They have not intentionally appointed another agent.
You should ensure you have written authority to act before proceeding.
Lodge a New Form 362
If the client confirms you are still the appointed agent:
Prepare a new Form 362 in CAS 360.
Appoint your agency as the ASIC agent for the company.
Lodge the Form 362 with ASIC.
Once ASIC processes the Form 362 and reinstates your agency, you will be able to proceed with document lodgements.
RA71 Rejected After Lodging Form 362
If you receive a RA71 rejection immediately after lodging a Form 362, this is usually caused by timing issues between CAS 360 and ASIC’s systems.
When a Form 362 is lodged, CAS 360 automatically submits a RA71 in the background. Sometimes, ASIC’s database has not yet updated the ASIC Agent information, which can cause the RA71 to be rejected.
Recommended Action
Wait 30–60 minutes after lodging Form 362 before attempting the RA71 Data Download again.
This allows sufficient time for ASIC’s database to update the ASIC Agent on record, reducing the likelihood of rejection.