Accounting practices hold concentrated financial information about a great many businesses. That makes AI unusually valuable — the work is repetitive, document-heavy and rule-based — and unusually sensitive. Running the model in-house resolves the tension directly.
The concentration is the point. A single practice may hold detailed financial records for hundreds of businesses — turnover, margins, debts, disputes, salaries. That is a more attractive target and a more consequential exposure than any single business faces on its own.
Sending that material to an external service may be permissible under the right terms; keeping it inside means the question of a provider breach, a terms change, or a sub-processor you did not evaluate simply does not arise.
It does not exercise professional judgement, and it should not be trusted to apply tax law unverified. Its value is in the mechanical layer — reading, extracting, sorting, drafting — which happens to be where a large share of billable hours currently disappears. That is a substantial prize without needing to overstate it.
Subject to your professional body's confidentiality requirements and your engagement terms, generally yes — but the tier and terms matter. Many practices are comfortable with business-tier tools under appropriate contracts; others conclude that concentrated client financial data should not leave the practice. Running the model in-house makes that a settled question rather than a judgement call.
Document extraction and transaction classification, by a wide margin. They are high-volume, repetitive, and currently consume junior hours that could go to work clients value more. Start there rather than with anything requiring judgement.
For extracting figures and classifying transactions, yes — with verification. Treat it as a fast first pass that a person checks, not as an authority. The efficiency comes from reviewing extracted data rather than keying it, which is still a large saving.
Peak is when the volume argument is strongest — and when hardware capacity, rather than a per-request bill, becomes the constraint. Size the machine for your busiest month rather than your average one; the cost difference is smaller than the cost of a system that queues when you need it most.
Private AI systems in environments you control — your data never trains public models, and engagements are available under NDA.