Fund Can No Longer Receive Contributions Using Pay Super

This is the screen shot for the fund I am having issues with

Below is the error message being displayed

Hey Julz79,

I've spot on this Community Forum thread where another user hit the same “fund can no longer receive contributions using Pay Super” message and was able to clear it by updating the super fund details in their file. If you could also follow the same steps shown in that post and refresh the fund details, you should be able to super payment.

Cheers,

Doreen

HI Doreen,

Thank you for the response.  I have double checked all of the fund details, which haven't changed from last time.  I rang the fund and confirmed I have the correct USI and ABN.  I tried selecting a different fund for the employee, and then reselecting the MLC fund, but still get the same error message. 

I had read the previous post you mentioned, but their issue seemed to have been a change of fund name, which resulted in a new ABN and USI being required.  

Hi Julz79,

You’ve done a great job working through this already, especially double checking all the fund details and calling the fund to confirm the USI and ABN. From here, the best move is to reach out to our team so we they check what seems to be happening and what triggers the error message. You can contact them on Live Chat via our virtual assistant, MOCA, or by submitting a support case via My Account.

Cheers,

Doreen

Thanks Doreen.  I will try to reach out to them this afternoon.

Hi Julz79.

Just wondering if you ever had a resolution to this issue?

Colonial First State 26 458 289 557 is giving me the same issue today.

Went to process it it gives us the error - This fund can no longer receive contributions using Pay Superannuation. Please edit the fund from the Superannuation Fund List window and select a valid Fund Name for it.

I've checked the Colonial First State website - it is showing the same information (Name & SPIN) that we have currently used.

(Initial set-up using Employee onboarding)

Keen to hear what you had to do to resolve this issue.

Thanks

(PS. Discovered they had a different name registered in MYOB - all fixed)