# Aust localisation inconsistent with ATO requirements

**URL:** <https://forum.manager.io/t/aust-localisation-inconsistent-with-ato-requirements/35545>\
**Category:** Uncategorized\
**Created:** [June 15, 2021, 12:43pm UTC](https://forum.manager.io/t/aust-localisation-inconsistent-with-ato-requirements/35545 "2021-06-15T12:43:35Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![lubos](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/lubos/32/62798_2.png) [@lubos](https://forum.manager.io/u/lubos)\
**Post date:** [June 16, 2021, 1:43am UTC](https://forum.manager.io/t/aust-localisation-inconsistent-with-ato-requirements/35545/4 "2021-06-16T01:43:08Z")

</div>

I’m currently experimenting if I can replicate these report transformations using no-coding approach. So rather than writing Liquid markup and HTML, you could define these reports in visual way like custom reports are implemented now.

---

_[View the full topic](https://forum.manager.io/t/aust-localisation-inconsistent-with-ato-requirements/35545)._