An explanation about the delays that some have faced when dealing with the ATO

[vc_row][vc_column][dfd_spacer screen_wide_spacer_size=”60″ screen_normal_resolution=”1024″ screen_tablet_resolution=”800″ screen_mobile_resolution=”480″ screen_normal_spacer_size=”50″ screen_tablet_spacer_size=”20″ screen_mobile_spacer_size=”10″ tutorials=””][vc_column_text]

Why the ATO is hardening its API environment

An “exponential” growth rate in the number and take-up of the Australian Taxation Office’s application programming interfaces (APIs) has prompted a hard rethink of how this environment is secured.

The number of APIs in production for third-party providers has boomed from 70 in July 2014 to 237 at current count, according to ATO chief digital officer John Dardo.

And the number of developers taking advantage of this ecosystem has jumped from 17 service providers three years ago to 346 today.

Adoption of the ATO’s standard business reporting (SBR2) APIs – an environment that has been criticised as not particularly easy to traverse – is nonetheless skyrocketing: from handling ten million transactions last year, to an expected one billion in 2017, and a predicted 10 billion next year, according to Dardo.

Read the full article here.[/vc_column_text][/vc_column][/vc_row]