Working with firms as a subcontractor

What AICPA Code 1.150.040, 1.300.040 and 1.700.040 require of a firm that uses an outside accountant, and what that means for you before and during a file.

US rule; elsewhere, check your own regulator · Updated November 20, 2026

What subcontracting for a firm means

When an accounting firm passes part of an engagement to you, the firm remains the one with the client. In AICPA Code terms you are a third-party service provider to the firm. The Code, in section 1.300.040, lists bookkeeping, tax preparation, consulting or attest services, including related clerical or data entry functions, as examples of work a member may have a third-party service provider assist with. The firm's duties come first, and yours follow from the way the firm has to meet them.

US rule applies to the AICPA material cited here. Check your own regulator for local rules if you are licensed outside the US. Country-neutral points are marked as such.

What the firm must do before it uses you

Three sections of the Code put duties on a member who uses a provider like you.

Competence and supervision (section 1.300.040). Before using you, the member should ensure that you have the required professional qualifications, technical skills and other resources. The Code lists things that help the member judge this: references from banks, other CPAs and other customers, professional reputation, published materials, and the member's own evaluation. The member must also plan and supervise your work so that it is performed with competence and due professional care, and obtain sufficient relevant data to support the work product. Section 1.300.040 adds that this supervision duty does not go beyond what the applicable professional standards require for the engagement.

Telling the client (section 1.150.040). Clients might not expect that a member uses a provider. Before disclosing confidential client information to one, the member should inform the client, preferably in writing, that a provider may be used. If the client objects, the member should either not use the provider or decline the engagement. A member need not tell the client about providers of administrative support such as record storage, software hosting or authorised e-file transmission.

Protecting the information (section 1.700.040). Before disclosing confidential client information to a provider, the member should either enter into a contract with the provider to keep the information confidential and obtain reasonable assurance that the provider has procedures to prevent unauthorised release, or obtain the client's specific consent. The Code says the extent of procedures depends on the facts, including how much is publicly known about the provider's controls.

None of these sections says what exact clause or document to use. They set the outcomes. A firm may choose a contract term, a questionnaire, a call, or a mix.

What this means for you

  • Expect questions about your credentials and your setup. A careful firm will ask what you hold, which standards you have worked under, which software you use and how you protect files. Answer with facts and be ready to document them.
  • Expect a confidentiality commitment. It may be in the subcontract or a separate acknowledgement. Read it for the scope of information covered, the period it lasts, what you must do with files at the end, and what you must report.
  • Expect supervision. The firm must plan and supervise your work. Review notes from a manager are part of the arrangement, not a criticism.
  • You may be told not to start. If the client objects to a provider, the firm may withdraw the work from you.

Mark-up and payment

Section 1.520.070 says that if a member subcontracts services for a client, any mark-up of the cost of those services is not a commission. So a firm may bill the client at a rate that exceeds what it pays you without that being a commission under the Code. Other rules, such as any state board rules on fees, may still apply to the firm. What you are paid, and when, is set by your agreement.

Two things the contract should settle

Independence (country-neutral good practice). If the firm performs attest services for the client, your own independence with respect to that client matters for the file. The firm will usually ask for a statement per engagement. The ethics cluster explains what independence means for a subcontractor. A per-file statement is more exact than a general one made once.

Work product and workpapers. Who owns the workpapers and what you may retain are questions for the agreement and for professional standards. See the page on workpaper ownership. Do not keep copies of client files outside the firm's systems unless the agreement says you may.

Two scenarios

Scenario 1: a new firm asks for a call (illustrative)

A firm that has not used you before asks to talk before sending a file. The partner asks about your licence, the standards you have worked under, how you store data, and whether you have any relationship with the client.

This is the firm meeting the competence and confidentiality duties above. A good answer states your credentials exactly, describes your setup in plain terms, names any relationship with the client or says there is none, and says you will sign a confidentiality agreement. A poor answer promises everything and gives no facts.

Scenario 2: the client objects (illustrative)

A firm tells you a client has refused to let any outside provider see its data, after the firm sent the disclosure. The firm withdraws the file you were about to start.

Section 1.150.040 says that in that case the firm either does not use a provider or declines the engagement. The firm has done what the Code requires. Delete or return anything you received, and confirm in writing that you did. Do not argue the client's choice.

What to do

  1. Prepare a one-page fact sheet: credentials, licence status, work types, software, data handling.
  2. Ask the firm how it will document your confidentiality commitment.
  3. Complete a per-file independence statement if asked, and say so promptly if you have a conflict.
  4. Work only inside the systems the firm authorises.
  5. Keep your own record of scope, dates and instructions.
  6. At the end, return or delete files as the agreement says and confirm in writing.

Frequently asked questions

Do I need professional liability insurance to subcontract?

Some firms ask. Whether you need cover depends on the contract and your own risk. See the insurance cluster.

Does the firm have to tell its client about me?

Under section 1.150.040 the member should inform the client, preferably in writing, that it may use a provider, before disclosing confidential information to one. Administrative support providers are carved out.

Can I contact the client directly?

Only if the firm agrees. The client relationship belongs to the firm. Direct contact without permission can also breach confidentiality or a non-solicit term in your agreement.

Can I work for several firms at once?

Often yes, but check each contract for conflict-of-interest terms and keep each client's information apart. The Code includes guidance on competitors as clients, so read your contracts for any restriction.

Where do I find the official text?

AICPA Code sections 1.150.040, 1.300.040, 1.520.070 and 1.700.040. A copy hosted by the Minnesota Board of Accountancy is linked below.

General information, not legal advice. The Code is revised from time to time and state boards publish their own rules.

Sources

Last verified November 20, 2026. Sources checked by the editorial team; not yet reviewed by a named professional. General information, not legal, tax or accounting advice.

Related pages

Terms used on this page

Professional liability insurance, Workpapers

Join the CORAA CPA network waitlist

CORAA prepares audit files for US CPA firms. Network members are independent contractors who clear what the software flags, with evidence and a note, paid per file under a contractor agreement.

  • Files are offered to you; you accept or decline
  • No exclusivity: you can work for others
  • The firm reviews and signs; CORAA never does

* required