Winding up an SMSF in BGL 360

We are in the process of winding up a fund today, 09-1-18 and the proceeds will be paid out on Monday 12-11-18.

We have followed the instructions in help menu but step two is not clear, it states that to determine the funds final tax position you need to complete Create Entries up to until 30 June for the Financial Year, the Create Entries will make the necessary adjustments for tax purposes. Should this be done as part of determining the members balances? It then goes on to say, to create entries for the day before you pay out the benefit?

Then in Step 5 is states to do a create entries for a day the fund is winding up, but is this not the same as doing the CE to the end of the financial year?

As a result we have done the following:

  1. Create Entries as at yesterday (01-07-18 to 08-11-18)
  2. Input wind up date 09-11-18
  3. Create Entries 09-11-18 to 09-11-18
  4. Process payments (in this case commute pensions to accumulation and rollover the accumulation accounts on 09-11-18.

Is this correct? the instructions are confusing and the tax and expenses are not allocating correctly when we just perform the create entries to 08-11-18?

Has any one else had the same problem?


Hi Sarah,

With reference to the article, we apologise that the information under step 2 is incorrect. The steps you have completed are correct.

The outdated information to create entries until 30 June to determine the final tax position is incorrect. The article has been updated to remove this information.

Kind regards,


1 Like

Hi Sam,
I have been doing a wind up similar to Sarah above & downloaded the BGL instructions but they still say in Step 2 to prepare the Create Entries to the end of the year first to determine the tax amount owing on the final tax return. I have done the whole process over and again several times and each time my tax balance is out. I just found this post as I was about to log a support call to help sort it out.
Please update the instructions as they are very confusing.

Hi @JoColles,

Thank you for letting us know about that, we’ve updated the knowledge base article below: