ATO Correspondence Software: 10 Questions to Ask Before You Choose a Tool

Most demos of ATO correspondence software look good. A document appears, a summary appears, an email appears. The differences that matter to a practice show up in the questions the demo doesn't answer.

If you're evaluating tools, these ten questions will tell you more than a feature list. They're written for practice owners and managers, so you don't need a technical background to use them. For a broader overview of what these tools do, see how to automate ATO correspondence processing.

How documents get in

1. How does correspondence actually arrive? Ask whether the tool connects to the ATO directly or relies on someone downloading files and uploading them. A tool that still needs a person to fetch every document has automated the easy half of the job.

2. How often does it check, and what happens when a fetch fails? Correspondence that arrives silently late is a risk in itself. Ask how failures are surfaced, and whether someone is told when a fetch doesn't complete.

3. Which document types does it handle? Notices of Assessment are the easy case. Ask about activity statements, statements of account, debt-related notices, and superannuation correspondence, because that's where practices spend their time. Our post on missed ATO correspondence and Director Penalty Notices shows why time-sensitive notices need special attention.

What it does with them

4. How accurate is classification, and how do you know? No classifier is perfect. Better tools show a confidence indicator so your team can see which documents deserve a second look, rather than presenting every result as equally certain.

5. Are due dates and amounts extracted, or only summarised? A readable summary is useful. A structured due date that can drive a deadline is more useful. Ask to see the extracted fields, not just the summary text.

6. How are Tax File Numbers handled? This is the question to press hardest. TFN information is regulated under the Privacy (Tax File Number) Rule 2015. Ask exactly when TFNs are removed (before storage? before any AI processing?), how, and whether an unredacted copy is kept anywhere. "We redact TFNs" is a different statement from "the original unredacted file is never stored". Our upcoming post on TFN redaction goes into this in detail.

What it does with the result

7. Does anything reach a client without a person approving it? For most practices, the right answer is no. Look for drafted emails that an agent previews, edits and sends themselves, rather than automatic sending.

8. Is there an audit trail, and can it be edited? You want a record of what arrived, who handled it, and what was sent to the client. Ask whether the log is append-only, how long it's retained, and whether you can export it.

Running it in a real practice

9. Where is data stored, and who can access it? Ask about data residency, encryption, multi-factor authentication, and whether team members can be given different access levels, such as read-only access for junior staff.

10. What is the vendor's position with the ATO? Software that connects to ATO services operates within the ATO's Online Services Framework. Ask where the vendor is in any registration or assessment process, and treat vague answers as a signal to dig deeper. A good vendor will tell you plainly what is complete and what is still in progress.

Scoring the answers

You don't need a formal scorecard. Give each question a simple red, amber or green after the demo. Anything red on TFN handling, client communication or audit trail is worth treating as a deal-breaker, because those are the areas where mistakes are hardest to undo.

How ATOque answers these

We built ATOque around these questions, and we'd rather you test us against them than take our word. It connects to the ATO via SBR2, redacts TFNs at the PDF binary level before storage, drafts client emails for an agent to review and send, and keeps an append-only audit log, with data hosted in Australia. ATOque is currently in the process of registering as an ATO Digital Service Provider, so that registration is not yet complete.

You can read the full feature breakdown and the security details, or join the waitlist for early access and bring your own list of questions.