This support note applies to:
- AO Corporate Compliance (AU)
- AE Corporate Compliance (AU)
When importing an RA72 into Corporate Compliance (CC), the import may fail at the end, displaying an error "failed to update corporation data". There are a number of causes for this error occurring. Following is an explanation of some of the different causes and the resolution where applicable.
A person is both an officer and a member
The import may fail when selecting both officer and member to one existing person in CC, where the ASIC records reflect different names in CC for officers and shareholders.
An example of this is where on the RA72, the officer might be Jane Mary Brown, and member might be Jane Brown. The CC person selected for both is Jane Mary Brown.
To complete this process, in the upload process, select the appropriate member or officer where the name matches, and for the member or officer whose name is slightly different, leave the contact field blank in the upload window. This allows CC to create the person as a contact, subsequently you need to amend the data after the import is complete. For example, in the above scenario, you find Jane Brown as a contact on the members tab.
- Open the corporation and click the Capital tab. The capital classes display.
- Highlight the capital class and select Change Share issue.The change Share issue window opens.
- Click the Allotment details tab, highlight the contact and click Edit.The allotment details for the holder displays.
- Note all the details, click Cancel. The holder information window closes and the Change Share issue window displays.
- Highlight the holder and click Delete then click Yes to confirm. The holding is removed from the allotment details page.
- Click Add, then use the ellipsis to choose Mary Jane Brown from your existing officer/shareholder list and complete the allotment details. The details are selected.
- Click OK. The correct holder appears on the allotment details tab.
- Click OK and save as a database correction only. The Capital tab displays.
Missing Fixed/Floating/Both and or description fields in the Charges
If the RA72 shows charges listed then they type of charge is required, for example, fixed charge, floating chart or both. If the RA72 shows no charges listed then there is no need for a type and therefore this is not cause of the upload failure.
If there are charges showing on the RA72, and the type is missing, then ASIC's records need to be updated. You can contact ASIC to have the missing Chargee details updated over the phone. If ASIC are unable to update the records over the phone, they can advise you on how to request for these details to be changed.
Once ASIC's charge details have been updated, lodge a new RA71 request and upload the resulting RA72. Provided there are no other causes for the failure, the subsequent upload is successful.
Ultimate Holding company
If there is an Ultimate Holding Company (UHC) which does not exist in Corporate Compliance prior to the import, this can cause the upload to fail. In this situation manually create the UHC before importing the RA72.
Share class discrepancies
Share capital issued shows a different capital class to the capital held by the member. For example "A" with quotes compared to the shareholders details which may show A without quotes.
In this scenario, enter the data manually into CC and then lodge a correction to ASIC.
Once the issue details are updated by ASIC, lodge a new RA71 request and upload the resulting RA72. Provided there are no other causes for the failure, the subsequent upload is successful.
Data corruption in the RA72
There can also be issues with the RA72 data itself. Delete the existing RA72 and request another copy of the corporation data and attempt import of the updated data.