AI that finishes the busy-season chase.Client names stay in the firm.
Partners and staff work in Claude, GPT, and Gemini. Proxara does the chasing and holds anything outbound for approval.
Every return still waiting on a document.
The question spans Karbon, Outlook, and SharePoint, so it rarely gets asked. Proxara reads all three under the preparer’s access and drafts each chase.
The coordination nobody bills for.
Four jobs a preparer does by opening three systems at once.
Engagement status
Where every return stands, read from the systems, not assembled by hand each Monday.
Read under each person’s own accessClient follow-up
The chase written from what is actually outstanding, addressed to the right contact.
Nothing sends without a personHandoff to review
Preparer to reviewer in one note: open points, answers received, what changed.
Every source record citedTasks and deadlines
Follow-ups become real tasks on the right engagement, with an owner and a date.
Written back, then confirmedMapped to the rules an accounting firm answers to.
Each citation lands on the audit chain alongside the interaction that produced it, ready to reconcile.
- IRS · IRC §7216Written consent before tax return information is disclosed or used beyond the return: per purpose, named recipient, signed and dated, never retroactive. Proxara captures each one and keeps it beside the work it authorized.
- IRS · IRC §6713The civil companion. The default lane replaces identifiers before anything leaves, so most tasks never disclose in the first place.
- FTC · Safeguards RuleTax and accounting firms are financial institutions under the rule. The record supplies the AI chapter of the written information security plan: approved tools, named users, what left.
- AICPA · ET 1.700Confidential client information and the third-party service provider step, documented instead of assumed.
- IRS · Circular 230Due diligence and competence for AI-assisted work, attributable to a named person on a record the firm can open.
- AICPA · Peer ReviewWhere the firm has an audit practice, the three-year cycle finds AI use already answerable in one export.
Section 7216, in plain terms.
One federal rule sits over every tax practice’s use of outside software: tax return information may not be disclosed or used beyond preparing the return without the client’s written consent. It has been on the books far longer than AI. Proxara is built so the rule is easy to live with.
Most tasks never touch it
The default lane replaces names, SSNs, and EINs with aliases before anything leaves, so tax return information is not disclosed in the first place.
When a task needs more, consent
For work that uses real return information, the disclosed lane opens only after a section 7216 consent: stated purpose, named recipient, signed and dated.
Proof either way
Both lanes land in the same record, so the firm can always show which lane a task took, and why.
Consent, kept the way the rule wrote it.
Most tasks never need one, because identifiers are aliased by default. When a task does use tax return information beyond the return itself, the client’s written consent comes first, and Proxara files it with the record of the work it authorized.
The busy season case, signed off by the person who answers for it.
The hours come back first: research, summaries, and letters that used to eat evenings. What gets it approved is the other half. Identifiers stay home, consent is captured properly, and one export answers who used what, on which client, under which policy.
- Single-tenant deployment in the firm’s own AWS account
- Supervision in Teams and Slack, not another daily dashboard
- One-click export for reviewers, insurers, and the WISP file
Ready before the diligence conversation.
Put AI to work across the firm’s systems.
Tell us which systems the firm wants AI to reach, and a person will reply.
Talk to us