Cases, returns, audits and compliance in one view.
Tax matters have structure — a jurisdiction, a tax year, a set of returns, a document request with a clock on it. Sapphire Legal holds that structure instead of flattening it into a task list, so an outstanding audit response is a visible state rather than something in an inbox.
- Quick answer
- What is the best tax controversy case management software?
- Sapphire Legal is Private Legal Intelligence for tax practice: a per-tenant platform where a tax matter is a structured record carrying its jurisdiction and tax year rather than a folder of correspondence. Returns are tracked with filing status and their supporting documents, audit document requests are managed with their response deadlines, and compliance items are monitored with status so a recurring obligation does not depend on someone remembering it. The platform records the taxing authority as a field rather than implementing any one country’s code, so it holds the matter while the lawyer supplies the substance. Everything runs in an isolated database and a private model environment per firm.
A document request with a clock is not an email.
Tax controversy work is a sequence of information demands, each with a deadline and a consequence for missing it, arriving across months and often across tax years. Treating them as correspondence means the state of a matter — what has been requested, what has been produced, what is overdue — is reconstructed by scrolling rather than read from a record. And because tax matters span years, the person reconstructing it is frequently not the person who built it.
Requests and productions drift apart
What the authority asked for, what was sent, and what is still outstanding are three different lists that live in an email thread, so the gap between them is only visible to whoever has read the whole thread recently.
Tax year is the organising fact and most software ignores it
A client can have open matters across several years with different authorities and different postures. Without the year as a structured field, the matters blur together and the wrong return gets discussed.
Recurring compliance depends on memory
Filings and elections that recur annually are the easiest obligations to meet and the easiest to drop, because nothing escalates until the window has closed.
The matter knows its year and its authority.
Jurisdiction and tax year are fields, which is what lets returns, audits and compliance items hang off the right matter.
A tax matter opens carrying its jurisdiction and its tax year as structured data, so a client with exposure across several years and authorities has several matters rather than one blurred file. Returns are recorded with their filing status and the documents supporting them, so the question of what was filed and on what basis is answerable from the record. Audit document requests are managed as tracked items with response deadlines, so outstanding and overdue are states the platform shows rather than conclusions someone draws from an inbox. Compliance items are monitored with status, which is what moves a recurring obligation off memory. Correspondence and responses are drafted from the firm’s own templates and prepared ahead, exportable to Word, with any missing input named rather than guessed.
- 1
Matter record with jurisdiction and tax year
The taxing authority and the year are structured fields, so matters stay distinct across a multi-year exposure instead of collapsing into one file.
- 2
Return records with filing status
Returns are tracked with their status and supporting documents, making what was filed and on what basis a matter of record.
- 3
Audit requests as tracked items
Each document request carries its response deadline and status, so outstanding and overdue are visible states rather than inferences from correspondence.
- 4
Productions linked to requests
What was produced is linked to what was asked for, which is what makes the remaining gap readable rather than reconstructed.
- 5
Compliance items monitored
Recurring obligations carry their own status and monitoring, moving them off individual memory and onto the record.
- 6
Responses drafted ahead
Correspondence and responses are drafted from the firm’s own templates and waiting, exportable to Word. Anything built from unverified work says so on its first page.
What ships with the Tax pack
The tax module is the primary workflow on this deployment, not a matter type with a label on it.
- Tax case records with jurisdiction and tax year
- Return filing status and document management
- Audit document tracking with response deadlines
- Productions linked to the requests that prompted them
- Compliance item monitoring and status updates
- Document drafting from your own templates
- Cross-portfolio view for counsel carrying several clients
- Conflict checking across every client and party on intake
A tax file is a complete financial X-ray of the client.
Why private infrastructure matters hereReturns, supporting schedules, bank records and candid assessments of a client’s position sit together in a tax matter, frequently alongside the firm’s own view of how defensible that position is. None of it belongs in a shared model. Each client firm on Sapphire Legal gets its own database and its own document storage, and the AI runs inside Sapphire Legal’s own AWS account rather than routing to an outside provider. Nothing trains a model, nothing is retained by a vendor, and nothing crosses between firms.
Where to go next
The tax pack is one part of the platform. These are the pieces around it.
Tax practice questions.
- Does the platform know my jurisdiction’s tax code?
- It records the taxing authority and tax year as structured fields and holds the matter around them — returns, requests, productions, compliance items. It does not implement any country’s tax code or compute liability; the substance remains the lawyer’s. That is deliberate, and it is why the module works the same way across the markets Sapphire Legal serves.
- How are audit document requests tracked?
- Each request is a tracked item carrying its response deadline and status, and productions are linked back to the request that prompted them. The remaining gap between what was asked and what was sent is readable from the record rather than reconstructed by scrolling an email thread.
- Can one client have matters across several tax years?
- Yes, and that is the point of making the year a structured field. A multi-year exposure is several distinct matters rather than one blurred file, so the wrong return does not get discussed.
- Does it track deadlines with the governing rule?
- Response deadlines and compliance windows are tracked, but the statutory-basis display — a deadline shown with the rule that created it — covers corporate, family and fiduciary matters rather than tax. Tax dates are tracked without the rule citation.
- Can it handle the document volume of an audit?
- Productions are managed against the requests that prompted them, and the Solo plan includes a monthly OCR allowance with itemized per-page overage beyond it, so a heavy production month is a line on an invoice rather than a surprise.
- Is client financial material used to train an AI model?
- No. The AI runs inside Sapphire Legal’s own AWS account rather than calling OpenAI, Anthropic or any outside provider, so returns and financial records never reach a third-party model. Each client firm has its own database and its own document storage.
See it on a live controversy.
Bring an open audit and we will walk what the platform would be tracking — requests outstanding, productions made, the response window that is closest.
14-day free trial. No card required.