
Telling Clients You Use an Offshore Team: A Confidentiality Guide
Here's the question that keeps firm owners quiet about offshoring: do I have to tell my clients? The honest answer is that disclosing offshore accounting to clients is sometimes legally required and almost always the smart move. At BusAcTa Advisors, we work behind US CPA firms, and we've seen that the firms who handle this conversation well keep clients, while the ones who hide it risk losing trust the moment a client finds out. This guide covers when disclosure is required, how to frame it so it builds confidence, and the confidentiality safeguards that should sit behind the conversation.
The goal isn't to script you into a corner. It's to give you clear rules and language so disclosing offshore accounting to clients feels routine, not awkward. This article is general information, not legal advice, so confirm your own obligations with your state board and counsel.
When Disclosing Offshore Accounting to Clients Is Required
Answer first: for tax work, written client consent is required before you send returns offshore. For other work, you generally need either a confidentiality agreement with your provider or client consent. So do you have to tell clients you outsource? It depends entirely on the type of work, and client consent for offshore work ranges from legally mandatory to strongly recommended.
Start with tax. Under IRC section 7216, a preparer must obtain the client's written consent before disclosing tax return information to a third party, including an offshore preparer, and the IRS spells this out. There's no gray area here: for tax returns, consent is mandatory and must come before the disclosure.
For non-tax confidential information, like bookkeeping or advisory work, the AICPA Code of Professional Conduct governs. Rule 1.700.001 says you can't disclose confidential client information without specific consent. Its interpretation 1.700.040 then gives you a path for using a third-party service provider: before disclosing, you should either enter a contractual confidentiality agreement with the provider, or get the client's specific consent. So strict client consent isn't always mandatory for non-tax work if you have the right agreement in place.
One more layer: your state board may impose its own disclosure rules, and some do. When you're weighing whether disclosing offshore accounting to clients is required, check the work type, the AICPA rules, and your state. When in doubt, disclose. Whatever the rules technically demand, treat disclosing offshore accounting to clients as your default posture, not the exception you make only when forced.
For tax returns, client consent is mandatory before you offshore. For everything else, it's either a confidentiality agreement or consent. When unsure, disclose.
Why Disclose Even When You Don't Have To
Answer first: because the downside of being caught hiding it dwarfs the discomfort of saying it. A client who discovers an undisclosed offshore team feels deceived, even if you broke no rule. A client who hears it from you, framed well, usually doesn't blink.
Think about it from their side. Wouldn't you rather hear "we use a vetted, secure team to handle preparation so our senior staff can focus on your strategy" from your advisor, than discover it by accident? Proactive disclosure turns a potential liability into a sign of confidence. It says you have nothing to hide and a process you're proud of. That's the quiet power of disclosing offshore accounting to clients before they ever think to ask the question themselves.
There's a practical upside too. Once disclosure is routine, your whole firm stops tiptoeing around it. Client confidentiality and outsourcing stop feeling like a conflict, because you've already shown clients the safeguards. That's why the firms most comfortable disclosing offshore accounting to clients tend to be the ones scaling fastest.
Proactive offshore outsourcing disclosure also protects you if a client ever asks pointed questions later. You can point to the consent on file, the engagement-letter language, and the safeguards, instead of scrambling to explain. Disclosing offshore accounting to clients up front means there's never an uncomfortable "why didn't you tell me" moment to manage.
How to Frame It: Scripts That Build Trust
So how do you actually say it? The framing matters more than the fact. Knowing how to tell clients you outsource accounting comes down to leading with the client's benefit and your safeguards, not with the word "offshore" in isolation. When disclosing offshore staff to clients, the order of the message does most of the work. Here are three ways to handle disclosing offshore accounting to clients, depending on the channel.
In the engagement letter (written consent or notice): "To deliver timely, cost-effective service, our firm uses trusted third-party professionals, including a dedicated offshore team, to assist with preparation and bookkeeping. Your information is protected by strict confidentiality agreements and security controls, and our firm remains fully responsible for all work and signs every return."
In a conversation, if a client asks: "Great question. We use a dedicated, vetted team that works inside our secure systems, under our review. It lets our senior people spend more time on your planning instead of data entry. We stay responsible for everything, and we sign every return."
If a client is uneasy: "I understand the concern, so let me show you the safeguards: confidentiality agreements, encrypted systems, named staff, and our own review on every file. Nothing leaves our control, and your data is handled to the same standard as in our office."
Notice the pattern. Benefit first, safeguards second, and your firm's responsibility always front and center. That framing makes disclosing offshore accounting to clients a trust-builder instead of a confession. Practiced a few times, disclosing offshore accounting to clients stops feeling like a script and starts sounding like the confident, ordinary thing it should be.
Lead with the client's benefit and your safeguards, not the word "offshore." Framing turns disclosure from a confession into a sign of confidence.
The Confidentiality Safeguards Behind the Conversation
Answer first: a disclosure is only as good as the safeguards behind it. Before you talk to clients, make sure the protections you're describing are actually in place. Confidentiality when outsourcing accounting rests on a few concrete controls.
A confidentiality agreement with your provider, the contractual backbone the AICPA interpretation calls for.
Section 7216 consents on file for every tax client before any return goes offshore.
Encryption and access controls, so data is protected in transit and at rest. See our data security approach.
Named, accountable staff working under your firm's review, with a documented quality control process.
Your firm as the responsible party, signing every return and owning every client relationship.
Your firm always carries responsibility for the work done on its behalf, the standard the AICPA sets for firm management. With these safeguards in place, disclosing offshore accounting to clients is simply describing a process you've already made secure.
Build these controls before the first client conversation, not after. When a client asks a hard question, you want to answer with specifics already in place, not promises you're still working on. That readiness is what makes disclosing offshore accounting to clients feel calm instead of defensive.
A disclosure is only as strong as the safeguards behind it. Build the controls first, and the conversation answers itself.
Mistakes to Avoid When You Disclose
A few missteps can turn a routine disclosure into a problem. Steer clear of these.
Burying it in fine print. A ยง7216 consent is a distinct document with required language; don't hide it in an engagement letter clause.
Disclosing after the fact. For tax work, consent must come before the file moves, not after.
Apologizing for it. If you frame offshore work as something to be sorry about, clients will treat it that way. Frame it as a strength.
Overpromising secrecy you can't guarantee. Describe real safeguards, not absolutes.
Skipping the confidentiality agreement. For non-tax work, that agreement is what lets you proceed without separate consent under the AICPA rule.
Get the substance right and the conversation gets easy. Most clients care that their data is safe and that you own the result, and disclosing offshore accounting to clients well proves both. Avoid these missteps and the disclosure becomes a non-event, which is exactly what you want it to be.
The Bottom Line for Your Firm
Disclosing offshore accounting to clients isn't a risk to manage; it's a trust signal to use. Get written consent where the law requires it, keep a confidentiality agreement with your provider, lead your framing with the client's benefit and your safeguards, and never forget that your firm signs and owns the work. Do that, and the conversation that once felt scary becomes one more reason clients trust you. Handled with the right safeguards and framing, disclosing offshore accounting to clients quietly strengthens the relationship instead of straining it.
This article is general information, not legal advice. Confirm your specific obligations under IRC section 7216, the AICPA Code, and your state board with qualified counsel.
Want help building the safeguards behind a confident disclosure? Contact BusAcTa Advisors for a no-obligation scoping call, or see how our how it works process and offshore tax preparation workflow keep your clients' data protected.
FAQ
Frequently Asked Questions
Put these insights to work in your firm.
Book a 30-minute consultation. A CPA, not a salesperson, will walk through your workflow.

Written by
Viral Patel, CPAViral Patel, CPA, CA, is co-founder of BusAcTa, where he leads operations and quality assurance. With 10+ years in U.S. individual, corporate, and partnership tax, he built BusAcTa's delivery model around one standard: offshore work that holds up to the same review a domestic senior would apply. He holds credentials in both the U.S. (CPA) and India (CA).









