Your audit file stays yours.

In a SharePoint site inside your own Microsoft 365, the one your administrator connects when the firm is set up. A paper passes through Kosh when someone uploads or opens it, and rests only in your SharePoint.

Your backup, retention and compliance rules apply to it, the same as to every other file your firm keeps there.

Kosh’s application can open one site, the one you grant. Microsoft enforces that, and your administrator can list the site’s permissions at any time to check.

At sign-in, Microsoft also asks each person to let Kosh reach files that person can already open. Kosh uses that file permission to save a paper into the audit site under the person’s own name, and it is on our list to remove.

Acting as the signed-in person, Kosh also looks up colleagues in your staff directory when a Partner or Admin adds them, and can send invitations and reminders from that person’s own mailbox.

The working record of each engagement: clauses, tasks, notes, review points, and every sign-off with the person and the time. It also holds your team’s names, work email addresses and roles.

Those records rest in a database in Mumbai.

• Only people your firm has added, using their Microsoft work account.
• Kosh stores no passwords. Microsoft performs the sign-in, so your MFA and conditional access rules apply.
• Guest accounts and addresses outside your firm’s domain cannot be added to the team.
• A session left idle for an hour is signed out.

Each person holds a role on the engagements they are assigned to: Performer, Supervisor, Job Leader or Partner. What they can open, sign and change follows from that role, and the firm decides who sits where.

Every firm’s records are kept apart from every other firm’s. Each request is checked against the firm of the person making it.

Submissions, sign-offs, reversals, locks and unlocks are written to an audit trail with the person and the time, and the trail can be exported as a spreadsheet.

One limit, stated plainly: a Partner can delete an engagement that has not been locked, and its trail goes with it. A locked engagement cannot be deleted.

When an engagement locks, TACT files the full trail into your SharePoint as a PDF and an Excel workbook, next to the lockdown report.

Record the date the Tax Audit Report was signed and TACT locks the engagement at the end of the 60th day, as SQC 1 requires. A locked engagement is view-only.

Reopening one takes a Partner’s written request and the firm Admin’s approval. Both go into the audit trail.

No. There is no AI or language model in the product today, so no client data, workpaper or document goes to any model provider.

If that changes, we will tell you before it is switched on for your firm, and it will be your decision.

Sign-in and files

Microsoft 365, your tenant

Database

Supabase, Mumbai

Application server

Render, Singapore

Website

Vercel

Crash reports

Sentry

Your records rest in India. The application server that processes them runs in Singapore, so they pass through it while a request is served, and nothing is stored there.

Email addresses, and the folder paths inside SharePoint links, are stripped from a crash report before it is sent.