Offshoring tax work and client confidentiality
Sending tax work offshore is allowed. Sending client files offshore without telling the client who gets them and where is the part the TPB's guidance is about.

The offshore team starts on a Monday. You've done the reference checks, agreed the hourly rate and
argued about which time zone the morning huddle belongs to. Somebody has set up the shared drive.
The first batch of files is sitting in a folder called To send – week 1, forty-two individual
returns, each one with a payment summary, a bank statement and a driver's licence scan in it.
Nobody in the room has asked whether those forty-two clients know.
The question belongs to nobody. The partner thinks the engagement letter probably covers it. The practice manager thinks the provider's contract does. The provider thinks it's your business, and on this one point they're right.
Offshoring is a legitimate way to buy preparation capacity. The confidentiality side is cheap to get right before the first file goes, and slow and awkward to fix afterwards, because by then you're writing to clients about something that has already happened.
The TPB treats your offshore team as a third party
The obligation is Code item 6, and the TPB's page on confidentiality of client information sets it out in a sentence. The longer guidance statement, TPB(GS) 26/2014, is where the detail sits. Its list of third parties includes an overseas or offshore entity you outsource to, cloud storage, and AI tools used in providing the services.
Three things in it matter for an offshoring arrangement.
It isn't banned. The guidance says the Tax Agent Services Act doesn't specifically prohibit outsourcing or cloud storage. Whether your clients knew is the question.
Tell them who and where. Before the disclosure, the TPB says you should tell the client what information will be disclosed, and to whom and where. "We may use third-party service providers" names nobody and no country.
Don't let the client assume otherwise. The guidance suggests you don't imply or state that all your work is done in Australia if it isn't. A practice whose website still says "your return is prepared by our local team" should read that line again.
The guidance even uses offshoring as its first worked example: a firm that sends bookkeeping and data processing to a provider in Hong Kong, discloses the arrangement in its engagement letter and gets each client's signed permission.

A signed letter can do it, but it has to say something
A reasonable test for the clause: could your client, reading it, name the country their documents are going to? If not, it doesn't say where, and where is half of what the TPB asked for.
A few things to settle before you write it:
- What goes. All source documents, or only some? Many practices send the bank statements and receipts and keep identity documents onshore. If that is your rule, say so, and then make sure the shared folder actually works that way.
- To whom. The provider's name, or at least the kind of entity and the fact that it is a separate business from yours.
- Where. The country. If the provider has staff in more than one, list them.
- Who stays responsible. Your practice, and the registered agent who signs. In the TPB's Hong Kong example the firm keeps primary responsibility for the work, and clients reasonably want to hear that.
The guidance also says inconvenience, time and cost don't excuse you from taking steps to protect information, which disposes of the usual reason the question goes unasked.
The clients you already have
None of the options is clever. Send the updated letter before the first batch goes and hold each file until it comes back signed, or start the offshore team on new clients and bring existing ones across as their letters are re-signed.
Whichever you choose, the folder has to know. A client who hasn't signed the new clause, or who said no, needs a flag that whoever prepares the batch will see before they upload. A note at the bottom of the client record is useless if the file was sent on a Tuesday by someone who never opened the record.

Some clients will say no. Decide in advance what that means, usually that their file is done locally, perhaps on a different timeline or fee. An answer made up in the client meeting is rarely one you like in May.
The Privacy Act is a separate question
The guidance statement points out that the Act's definition of an organisation excludes some small businesses, so whether it reaches your practice depends on your circumstances. It doesn't depend on how many staff you have in Manila. If it does apply, the Australian Privacy Principles include one about sending personal information overseas, and the Office of the Australian Information Commissioner is where to start reading. Don't take a blog post's word for which side of that line you sit on, including this one.
Two other pieces of guidance are worth knowing about. The TPB has a practice note on outsourcing and offshoring, TPB(PN) 2/2018, which the guidance statement refers to. And members of professional bodies that have adopted it should read APES GN 30, the APESB guidance note on outsourced services. Your professional body can tell you whether that includes you.
What to keep on file
- The provider agreement, including what it says about confidentiality, where the work is done and what happens to client files when the arrangement ends.
- The clause, with a version date. A client who signed the March version agreed to the March wording, and you should be able to show which one that was.
- Each client's signed letter, filed on the client record rather than in someone's inbox.
- A dated list of who receives client information and where. The offshore team goes on it, and so does the cloud storage and any AI tool that touches client work. The guidance treats them all as third parties, so they belong on one list.
- The opt-outs, in a place the person preparing the next batch can't miss.

It's the same list we suggested keeping for AI tools in telling clients you use AI, with one more row.
There is a quality side to offshoring as well, which is mostly about whether a stranger can follow your files. We wrote about that in why workpapers come back from review.