Skip to main content

Input of Distribution Tax Automation data

Comments

2 comments

  • Andre Jones

    Hello Neil, 

    Thank you for reaching out to the Community. 

    Unfortunately, the CSV file can't be directly uploaded into the Distribution Tax Automation screen. However, there are a couple of different ways to automate this process. 

    As the ETFs you've mentioned are commonly held, there's a good chance System Tax Data is already available in Simple Fund 360. To check, go to the Distribution Tax Automation screen and look to the far left of each ETF. A blue lightning icon means System Tax Data is available for that ETF, which will automate the process for you. 

    If they're not supported yet, SmartDocs is the next best option. You can email your tax statements to the fund's SmartDocs address or upload them in the Documents screen, then use the SmartDocs Review button in Distribution Tax Automation to attach each statement to the right investment code.

    It's difficult to say exactly when System Tax Data will be available for these ETFs. As we don't yet have the tax data for the 2026 financial year, it may take a little longer while we make sure the figures are accurate.

    To see the all options in detail, please refer to this help article - Distribution Tax Automation

    You're also correct that the Wrap Statement Extractor isn't suitable here, as it can only be used if your Betashares portfolio was consolidated into one account in Simple Fund 360.

    Please let me know if you have any further questions.

     

    0
  • Neil Stewart

    Thanks for the response. I have used the System Tax Data before, which has been good when its present.  

    The core issue is that Betashares only provide a "rolled up/sum of all" tax components in their tax statement. If you want individual etf statements then you ask them and they provide a csv.  The additional problem is that the csv column headers bear little, or no, relation to the labels in BGL's DTA forms. This might not be an issue for tax professionals, but I am not one of them ...

    I solved the issue by using Google Gemini to do the mapping for me. Then I entered the values in the DTA. Job done.

    I raised the issue with Betashares and it might have gone into some pool of future feature requests ...

    0

Please sign in to leave a comment.